IMO, nothing went wrong...other than possibly your expectation that it would be easy and successful.
Hey man, I'm not claiming tech godliness, and I'm certainly not questioning your superiority at operating system support. I can say that I at *no* point expected this to be easy and successful. Like I said, the gods smiled and swapping the drive managed to work. That much was fine, and I'd have left it at that if it were any other client. I was avoiding the repair because of the stuff you and I both ended up doing.
Computers aren't magic though. I'm happy to perform the usual voodoo of sacrificing the soul of the installation on an altar of goat bones prior to transfer into a new system, then summoning the gods of hardware to bless the new system with life, but with so many changes being made in this mystical process, it'd be nice to know what's *really* happening. I get what happened to the hardware that did work, why the drivers needed a trick to be removed, and how the applications react when a repair is done, as well as why the updates magically disappear while their files stay intact. So far, all of the above involves specific entries in the registry and adjustments of base system files. I just wanted to know what makes an OS fail to recognize data sent to it from the BIOS during boot, and if there were a known issue/solution surrounding it. If you don't know, that's fine, but don't bother me unless you know something I don't.
Edit: BTW, that's the same procedure I found for removing extraneous drivers, although I went with the batch file mentioned later in the replies. More straightforward, I thought.
Edited by Bochulain, 30 January 2009 - 09:17 AM.