Originally posted by: Gillbot
I am not sure you can use sysprep after the fact or from safe mode. Try the MS help site for sysprep to see if there is info, otherwise restore the PC and run it before tearing down.
Hi there. Sorry it took me this looong to reply, but here I am with some interesting findings
1) Yes, I was able to run sysprep from safe mode. The sysprep I got is ver 2.0, so really no choices as far as parameters. in the end, it didn't matter as the nice BSOD still greeted me after all the new detection was done
2) So, because sysprep from safe mode didn't work, I took one of the machines that still had the old CPU and mobo, and performed the sysprep in that machine. Ghosted the image to the computer with the new mobo hard drive after sysprep was done. After the ghosting was done, restarted the computer with the new motherboard that now had the sysprepped image... after logging in, still the freaking BSOD.
3) By now, I tried to recover the minidump file and interpret it. After a few hours wasted with the MS tools, I gave up.
4) Restored the last good image of old mobo, uninstalled drivers of almost everything... Ghosted again to new mobo, restarted, logged in... another BSOD.
5) Restored the last good image of old mobo. I decided to perform the XP in place repair with the XP CD. I slipstreammed SP3, and proceed as expected... at the scree that asked me for the license key, I typed it... rejected! XP SP3 didn't like the license.....
6) Restored the last good image of old mobo. I tried another in place repair, this time using the XP SP1 CD... this one took the license key fine, though it went much slower, eventually brought me to the log in screen... "I made it finally" was my thought. Not so fast, after logging in, the dreaded BSOD greeted me again. This time, however, being XP SP1, it gave me more time to peek at the message and identify the culprit, something that didn't happen in all the XP SP3 previous attempts as the machine rebooted right after the crash. Hex address displayed, and then it said
AMDLLD.SYS A quick google search revealed that this is the AMD dual core optimizer, and that some other people had this problem before, which was corrected just by renaming the amdlld.sys
7) Start in safe mode, disable the dualc ore optimizer in msconfig, rename amdlld.sys, restart....
success!!!! No crash after logging in.... Because I wasn't to reinstall sP3 and patch SP1, I just restored the last good Ghost image once again, went directly to safe mode after the restore was complete and disabled the dual core optimizer... smooth as butter. Installed the SB700 drivers, enabled AHCI, and was up and running in a matter of minutes.
So, after like 10 hours wasted,
I learned that the AMD dual core optimizer is extremely picky. Uninstall it to ensure you will make the transition successfully You also know that the mobo SATA must be set to IDE or compatibility, but that was never an issue as I had it in IDE all the time. In gigabyte mobos, enabling AHCI is dumb easy... have your hard drive connected to port 4, go to bIOS, change ports 0 to 3 as AHCI, keep ports 4 and 5 as IDE... restart, install the AHCI drivers, restart, enable AHCI in BIOS, restart... you got hot plug capability Run the raidexpert to enable NCQ
I wonder if the comment of the dual core optimizer can be added to the main post.
Alex