Hi Mark,
It could be something as simple as a boot.ini setting or (as you say and I think your right) deeper in the registry.
As you know with multi boots windows puts a new option in the boot.ini so it knows what is the "root" drive and partition. ( multi(0)disk(0)rdisk(0)par
For windows booting up that is translated into a /Device/HarddiskVolumex
The example of what windows does in the registry under
HKEY_LOCAL_MACHINE\SYSTEM\
\Device\HarddiskVolume1\WI
So it probably more comes down to how it's recognising what \device\harddiskvolumex is and how you map it back to your sata.
Then theres subkeys of HKEY_LOCAL_MACHINE\SYSTEM\
which map a physical drive to a clsid (and more importantly a driver subkey). The clsid is used in multiple places in the registry and the driver subkey off it lets you see whats used for the specific device.
Then add in the values of HKEY_LOCAL_MACHINE\SYSTEM\
One mistake with these sorts of keys and the windows will blow up pretty much.
I'm still trying to find the article I had that listed all affected registry keys, but trust me, it's long.
I'd just re-install if I was you, gives you a clean registry and you are safe to attach the other drive without windows or programs mistaking one drive for another.
Main Topics
Browse All Topics





by: mark876543Posted on 2008-08-04 at 08:32:07ID: 22153275
What I am looking for, I think, is how to clean up the registry to stop XP from looking at the old original XP when booted from the new clone, and getting all screwed up because of it. The old history of drive assignments needs to be cleaned maybe.