An answer should do the following in my opinion. If it fails to do these three things, there is likely something wrong with the answer, and much of the time something can be done to improve the answer.
- The question should clearly demonstrate an understanding of the author's question. For example a question on how to copy and paste in a Windows 7 command prompt shouldn't talk about that capability being different in Windows 10 and being able to do it with a keyboard shortcut.
- This leads to the second point, the answer should in detail answer the question proposed, a statement the author of an answer, does not explain how to SOLVE the problem then it can't possibly be considered an answer. Stackexchange websites are about answers not questions honestly, all it takes to make a good question, is one person to understand what the question actually is and explain how to solve that problem.
- The third, and perhaps the most important reason, but only listed last for no particular reason. An answer shouldn't produce additional questions. If an author of an answer is asking questions, like asking for system information, that is more of a comment, and best done outside of an answer.
Since I almost forgot this, I won't even give it a ranking, an answer should be self-contained. It after all is an answer to a question. You don't answer a question, when you are talking, by telling somebody to click on a link to more about a subject when asked "what would you link to order?" You just answer the question, and order, what you would like.
You should also speak from a stance of authority. If you use the words "I believe ..." the you better be able support that stance.
For example: https://superuser.com/review/low-quality-posts/382809
Mount your external drives to a server with NFS and Samba.
This statement is an action statement, but there is no explanation, of how to perform that action. This type of an answer is what Q&A websites were like before Stackexchange, in other words, its complete rubbish. Anyone could have told the user to mount their external drives to a server. It isn't helpful to anyone honestly.
Of course if one takes a literal view at the question. One can see this statement does not answer the question. So you are left with an irrelevant statement about NFS and Samba.
I would like my external drives to be readable and writable from Linux, Mac OS X and Windows. FAT32 works, but ....Are there any alternatives?
So the author is asking for ways to share external drives with OS X, Linux, and Windows. Multiple answers explained what file systems could be used across those platforms.
We can also looked at your failed audit: https://superuser.com/review/first-posts/382819
Borrow/buy a USB keyboard to do the pre-boot stuff.
So the user's question indicates that he has known the keyboard won't work before Windows boots. He also explains he normally just let it crash or automatically pick the option, and he was willing to accept this. He wants to know the following.
Is there a way to change a file with something such as a Linux live CD
to force the computer to skip the start-up repair menu?
So the answer to "is there a way to change a file with something" is to burrow a USB keyboard? Lets just put aside the fact, if the built-in keyboard isn't working before Windows boots its very unlikely a USB keyboard is going to work either. Even if this solution did work, it does not answer the author's actual question, how to bypass the start-up repair menu.
So you are left with a below average comment, broken by the technical facts of the problem, which should have been researched before even submitting the answer. If the author of the answer had done this, they wouldn't have bothered submitting the answer.