This week has been a rough on for me and tech gadgets. I had a monitor burn out on me at work, it made all kinds of buzzing, hissing and popping noises before it died in a puff of smoke.
I was alone in the basement workshop where I work and was a little freaked out by the whole thing. At first I could not figure out what was going on, but I caught on real quick when I saw the smoke and the monitor went black.
Then last night I decide to take one of the hard drives out of my home PC, it happens to be the one that has Red Hat installed on it. I restart the computer and get a grub bootloader error, and the machine just stops dead. OK, I can fix this i think. I just pop in my trusty win98 boot disk, reset the machine, and after it boots, I run fdisk /mbr to rewrite the master boot record on the hard drive and get rid of the grub bootloader. This works, but it also changes the drive letter assignments on all the other partitions on the drive. Kiss Win2K and XP goodbye. I could boot, and get to a login screen, but when I try to log in, it gives me an error and I go back to the login screen again.
I crank up one of my other machines, and lo and behold, I can still access all of the shares on the 2K/XP machine, I just can't login.
I use remote management to try and change the drive letters, but you cannot change the drive letter of a boot or system drive in disk management. After a little searching through the MS knowledge base, I find a remote registry hack that will let me change the drive letters back to what they should be.
It is actually a quick and easy fix if you have access from another computer on the network, but I would have been royally screwed if I only had a stand alone machine.
I think this week I would have been better off working with an abacus or slide-rule than working around computers.