New
#21
The most frequent cause of this failure is XP not having the more modern SATA controller driver.
Needs to be slipstreamed into installer using NLite.
The most frequent cause of this failure is XP not having the more modern SATA controller driver.
Needs to be slipstreamed into installer using NLite.
Yeah it did.
I don't think Windows 7 is like XP in you can't change hardware, but yeah... i just installed it plainly then set it all up on the actual computer.
Quite a show when it changes out all the drivers, huh?
So far after a dozen times doing the HD changeout install on various machines, not one turned out to be a bad install.
In XP, it requires a repair install to even start it up.
Not really Greg.
All the drivers the o/s has are in the driverstore on the HD.
For some time, Paragon has had "adjust o/s to boot on new hardware" as part of it's boot corrector module. Others (including, I believe Acronis) have since followed.
What that does is make changes in the registry to unlock the drivers so the correct ones will be installed for the new hardware - just as they are when installing the o/s.
If MS have stopped doing that, it's not a moment too soon.
What's surprising is that it hasn't been widely reported.
You have moved an XP HD from one computer to another and it starts up without Repair install?
How?
This is the top Google search result on the subject: Changing a Motherboard or Moving a Hard Drive with XP Installed
This is the second top Google result: http://www.theeldergeek.com/move_harddrive.htm
If the top two sources on the internet say that it requires a repair install, and even warn not to try it without doing so, then how is it "nonsense"?
Last edited by gregrocker; 14 Dec 2009 at 01:46.