The MBR— Master Boot Record— is the Rosetta Stone that unlocks the contents of your hard drive: It’s usually the first sector of a hard drive, and contains the "partition table" (a record of how the hard drive’s files are set up, including where the operating system software is located) and the initial boot loader that the BIOS uses to launch the actual operating system. When the MBR is messed up, your PC isn’t going to do much:
Fred: Just yesterday morning I locked horns with the devil. DriveImage5 would not let me run it from windows (where it boots to DOS and back). When running from floppies it told me to eat a big one. HUH?!?
[Two weeks earlier] I received a 250gig drive. I put it in my hotrod Dell main machine. I’ve had goofy problems with a 200gig that never did make sense.
Windows Disk Management and Partition Magic 8 both saw the drive as 128gig. Huh? I’ll spare you the blow-by-blow but it turns out my BIOS wasn’t supporting the large drives. A BIOS flash upgrade cures that hours into the problem. But in the mean time I used the CD that came with the Maxtor drive. Along the way it kept asking "I’m gonna do this, OK?" along the path of preparing the new drive. Then AFTER the final step it informed me it had installed software on my boot drive. What? I didn’t want it that way, AND the drive was destined for another machine anyway.
The beast wedged itself in before Windows altogether. So I went about uninstalling it. After lots of Googling I found where the buried uninstall option was. Even then it took me 5 minutes to get it to work correctly. Well not correctly as you’ll read later, but "at all".
I got the problem of formatting the disk correctly straightened out:
1) Upgrade motherboard BIOS
2) Set an obscure registry entry allowing Win2K to see 128g+ drives (long time spent discovering that thorn as well). Read that whole battle to at least know it exists:
3) Now format & partition under Win2K or Partition Magic.
[Now,] DriveImage5 would not let me run it from windows (where it boots to DOS and back). When running from floppies it told me to eat a big one. The message was to the effect "Disk Manager" was found on the disk so DriveImage wouldn’t tough it and existed to DOS! But wait, I had removed Disk Manager!
Long story shortish: I had to recreate the "Master Boot Record" on the boot drive for Win2K http://langa.com/u/8h.htm . You used to be able to fix that with "fdisk /mbr" but no, not in Win2K. There you have to use the command "fixmbr", while booted into the "Recovery Console" from the installation CD. [note: XP works the same way]
Yikes. Through those two sessions I spent a lot of time at wits end, and I consider myself an above average user. (OK, I’m attempting to be humble but I choked on the word "user").
Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 10, Windows 8, Windows 7, Firefox, Internet Explorer, Google, etc. Join our 460,000 subscribers!
Subscribe and get our monthly bonuses - free!
The Windows 7 Guide, Volume 3: Advanced maintenance and troubleshooting provides advanced tools for keeping Microsoft's premier operating system up and running smoothly. Get this excerpt and other 4 bonuses if you subscribe FREE now!