To make a very long story sort of short, I messed up big-time! :( I just installed a new 200 GB hard drive as master (the comp. recognized it as F drive) and used my old 80 GB drive as slave (recognized as C drive) and everything was going fine on reboot...the partition was a full 200GB, all programs were working fine etc., until I decided to try and change the drive letters in the registry (Microsoft Knowledgebase Article #223188). Fortunately, I made a Windows System State Backup on my zip drive before I proceeded to mess my computer up royally. :rolleyes:
Anyway, after several hours of switching drives and jumpers, etc. and finally getting the drives back to where I could boot up (had to FDISK the 200 Gigger and re-install Windows XP), my 200 GB drive now is only recognized as 137 GB. The 80 and 200 GB drives are both showing that they are on Windows Service Pack 1 (Atapi.sys version 5.1.2600.1135) which supports the large drive. Can't figure out why it doesn't recognize the whole 200 unless it was the fact that I had to FDISK the big drive to even get it to boot.
I found the Microsoft KnowledgeBase article #303013 (http://support.microsoft.com/default.aspx?scid=kb;en-us;303013) on how to enable 48-bit Logical Block Addressing Support which is supposed to cure the 137 GB barrier, BUT...quite frankly, I've read and re-read the instructions (which are probably for experienced OEM's instead of wanna-be techie me) and I get more confused each time, so I think maybe I shouldn't even try that?
My question is about the Windows System State Backup I made. Can't I just restore the backup where my drive sizes were OK, and will it fix my current problem with the drive size....or would it be better to just try and follow #303013 to enable the 48-bit LBA Support? I'm really scared to go messing around in the registry again!
And, If I just restore the backup of the System State...the Windows Backup Utility asks me if I want to restore to an alternate location or to the original location. If I restore to the original, it'll erase my current registry which works, but is goofed as far as the drive size goes. What to do??? Windows System Restore won't work either because the last Restore Point showing is today...after the mess-up.
Moral of the story: NEVER, NEVER, NEVER mess with the Registry Editor to change drive letter assignments even if Microsoft Knowledgebase Article #223188 says you can. :o