Inwhich you are intitled to..
But...
We aren't talking about hibernation. Have you ever noticed when you do hibernate, when you return to the session you had, some of the hardware aren't being initalized until you DO a "true" reboot? Because you are only saving the previous session or what is in the RAM and what has been swapped to the hard-drive
TO the hard-drive. The power goes off and when it comes back on the hardware isn't reinitalized because it wasn't initalized from the bootstrap..
Well, we all will differ about HOW he shut down his machine and how the info got corrupted, but I can tell you this: He lost his bootstrap, his BIOS didn't or couldn't read this info, so it couldn't initialize his hard-drive.
Win2K or XP aren't the "old" Windows Filesystems and they aren't "Boot-diskable" anymore, they emulate *NIX filesystems now and need a loader just like a UNIX-based OS. (Hence, the NTLDR. I can almost bet my life he formatted his hard-drives in NTFS.) The system files on his NTLDR weren't written back and gotten corrupted, so when he switched drives and installed 2K on the new master, his BIOS detected both bootstraps but ran the more recent and correct one because the new information pointed it so.
The screen going blank, was the OS initializing the monitor, don't worry about it.
Anyone else who disagrees...?
