I recently built a working Windows XP machine because Ubuntu was just not supported well enough for work. I used my old T40 so I could preserve my T60p until I was sure I had everything right.
Today I went to move the system over. I’ve done this many times over the years both as my computer was upgraded and when migrating demos to temporary machines. I’ve done lots of moves …. T20 -> T40, T40 -> T42, T42p -> T41, X60 -> T60p and even did an X60/T60p swappable drive once. So, I thought the T40 -> T60p would be just as quick as all the rest. ANGK!
I partitioned the new hard drive just like the old one – three partitions: 256MB, 32GB, ‘remainder’. I installed my SystemRescueCD files to the HDD and installed GRUB as well. Just for the record (since I’ve managed to loose my notes three times now), here are the instructions for installing GRUB to the 256mb partition along with SystemRescueCD …
- boot from SystemRescueCD
- create first partition on HDD is 256MB (yes, that little). It will be called “sda1″
- format as ext2
- copy SystemRescueCD files and “boot” directory to “sda1″ (already has my menu.lst customized)
- start GRUB from the SystemRescueCD command prompt
- GRUB> root (hd0,0)
- GRUB> setup (hd0) -or- setup (hd0,0) hd0
- GRUB> quit
So far, so good. I was on a roll. I then launched PARTIMAGE and restored the backup of the T40 to the 32GB partition.
I rebooted, saw the boot loader, the Windows splash screen and the BSOD …. hmmm. that’s odd. I’ve never had that happen before. …
A few more attempts hoping it was just a fluke and then it was off to Google for help. After about 30 minutes, I had my answer. the T60 has a SATA drive and WindowsXP is so “old school” (first released in 2001) it has not default drivers for it. Lots of attempts to get the drivers over and nothing worked. I went off and did other stuff. I cam back and Googled more and tried more stuff. I went off again …
I finally found out about nLite and created a Windows XP install disk with the SATA drivers. I figured I could just use the Recovery Console and add the missing driver and I’d be set. Well, I could not boot my Windows XP install CD and I could get to the Recovery Console and look around my restored drive but I could not find a way to actually install the missing driver. Turns out you can’t add a missing driver even if you have the driver and the Recovery Console lets you see your drive.
The magic (slow painful magic) came from an article discussing how to recover form replacing your PC’s system board. The writer clearly states; “do not use the option for “repair a Windows XP installation using the Recovery Console”. Instead, start the Windows install and then select “repair” once it has found your existing installation. I can only say “that’s far from intuitive!”
I had six or seven nasty looking “missing or corrupted” type pop-ups. I just clicked “OK”. I figured at this point, I’d been walking on thin ice for so long, I might as well dance the jig.
It took an hour for Windows to do what it thought it needed to do and I on the first reboot I saw that pretty blue screen again. It seems Windows never got around to actually installing the missing SATA driver !
… Oy vey !