Mike can I make a suggestion with some of this? After reading the last post, I went to your Installation page in Post 1 of this thread and below are the trouble shooting help notes:
www.codeproject.com
They make some huge assumptions with regard to users knowledge on how to program in a pc. Could I suggest you make the guide average pc user proof because many pc users aren't programmers so won't know how to even open a terminal?
A good example of assumed knowledge that amongst the above instructions I found these for help with re-installation:
It says open a terminal. As a non programmer, even I don't understand that. The standard way of using Run is to type "Run" into the search box at the bottom left of windows and then type the item you want to run into that window. 99% of PC users don't know how to even do that.
Even then, the use of the word "Terminal" and "Admin Mode" would make me suspect you want the user to actually open a Command Line Prompt not the Run App. Again 99% of PC users don't know how to open a Command Line . Even if you know how to open a command line prompt, you get the standard:
C:\Windows\system32>
So is that:
C:\Windows\system32>run sudo bash...\...\setup ?
Most people don't know if you can or can't use a run command after the command prompt. I don't even though I know how to open run and do some commands in Command Prompt (I've only used the Windows run command box as a run command before) I tried it using just run with no file path as a pure test scenario and got a message saying "command not recognised". That wasn't "file path not specified" which leads me to believe you you probably can't use run after the command prompt, although I'm guessing you probably can in some way given the instructions say open a terminal in admin mode and the Windows Run Command Box doesn't have an admin mode option.
Equally, even if a user resolves that, I doubt many who aren't programmers or who don't work in IT would know what to fill in for the file path, ie the gaps in the dots between bash...\...\setup.
I think it would be really helpful from a perspective of making it accessible to as many as possible and helping to reduce support requests to maybe explain the process further down to avergae pc user level as opposed to some knowledge of programming level or working in IT level as atm even quite advanced PC users can be left unable to know how to proceed. Some basic instruction on how to open a terminal would both clear up which command prompt to use (Run or CMD Prompt) and instruct Joe Average who doesn't even know what a terminal is, on how to open one. Some explanation of how to execute a "run" command and the file path ie what should be replacing ....\.,..\ would also clear up issues where someone has got as far as opening the terminal but doesn't know what to do next.
Just a suggestion to reduce support dependency.