winscape 2304

Any time a computer system stops delivering computing services and has to reload the kernal forcing all users to redo what they were doing is a crash. This includes power outages.

If the lockup (which is really a keyboard or mouse lockup) doesn't cause Windows to detect a panic problem, then it cannot try to write out corrupted FATs. The reason a BSOD causes corruption is because the subroutine called tries to "save" the data and file info before flashing the user's TTY. One of the most common reasons that a BSOD happens is because this data was overwritten. As a result, the OS preserves the contens of the memory that just got clobbered. When the contents is the FAT data, your file system is not worthless and you have to reinstall. Reinstall is almost a cold start.

And the user interface has been designed so that all users, including the sysadmins and developers, can never learn by themselves.

This is a modified form of the scientific method and is essentially in any system analysis. However, having to revert back to a reinstall of the whole software system is like forcing a man to go back to Caveman living styles to light a match.

This is unacceptable if what isn't working is a user mode program. You are thinking only PC. You are not thinking systems that do more than one thing in their uptimes.

No, this is completely unacceptable just to troubleshoot a glitch. The only time I can recall when we had to reinstall (and we a monitor development group) was a head crash. I can't describe how appalled I am that a reinstall is not the backup Plan Z..not A, not B, but Z the last one.

This is not an approach to problem diagnosis (you've just elided the conditions that cause the problem so you don't anything to look at to diagnose. If you have nothing to diagnose, you will never have a resolution.

I don't know. I can't recall what the OP said. I don't care either. I'm talking about this automatic buttumption that things needs to be reinstalled.

BAH