I agree Terry, they should do all those things but ... it's never going to happen, as you probably realize. People are very impatient and this software is a little intimidating. People are not inclined these days to RTFM until it doesn't work.

The only way around it is to make the software easier to run initially or have a walk-through setup that at least makes them look at the important steps they should do BEFORE even allowing them to start running it.

I understand your frustration, but the reality is it isn't going to happen, but at least you tried.

The problem with RTFM is that one would need to zoom in on the problem for the manual to be helpful. NOBODY is going to read the whole manual to solve a problem. Yes to help them do something, but not to fix an issue, manuals are not written for that in mind.

IMHO, the manual would need to have an index as well as a troubleshooting section to be helpful if there are problems. That would be a beginning, but not a substitute for a quickie question here.

Also, as I remember from my early days in computing when I started (April 1992!) the issue is not knowing what something is called to be able to look it up.

N5INP's idea to modify the install routine is an excellent one.

Just because an amateur has a licence, it should not be taken to assume that they are adept at using computers.

73 de Guy G4DWV 4X1LT

You've never known happiness until you're married; but by then it is too late.

The problem with searching the manual is that problem phrases do not bring up any hits. I have just tried a few. Also, everybody is different as to what they would use to search for a given situation. For example, what I may call a crash, you may call a freeze.

Manuals are not designed to troubleshoot. Sure, the answer will be there, but it is the difficulty of finding it. A few pages of FAQs and/or a troubleshooting section, with many included key words would help, maybe.

OTOH, the traffic in this forum is not that great that there should be a cull of those who do not RTFM. What better advertisement for a new user than to get a warm welcome and a helpful response even though they did not RTFM.

You've never known happiness until you're married; but by then it is too late.

Solution A) without manual the program is undocumented. Someone complains

Solution B) with short manual the program is documented, but a lot of hidden features and "how do you expect i can know that" will arise. Someone complains

Solution C) with a big manual, tutorials and everything else someone will says: ok, it's documented, but i have lack of time so i will ask to someone to read the manual. Also, big manual can be scary, and someone, finally, complains.

Assuming we're catching almost every bug on the code and real "bugs" are very rare at this stage, the issue usually reside on the user side of the keyboard. We cannot ask users to use their brain, we provide full support but let us moaning a bit…