Has anyone noticed what causes a clone to a new system to require a repair sometimes and not others?


Example:

I have Windows XP installed on my AMD based system.
Motherboard or whatever dies.

I build new system.
I clone old HDD to new HDD and boot.

Sometimes it will blue screen upon boot until you run a windows repair, other times it will not.


It doesnt seem to have anything to do with the hardware, as it worked today going from AMD (socket 7) to intel (core 2 duo).

It still trips the activation, but it doesn't bluescreen.


hmmm?

7/11/2007 2:35:35 PM

normally you can't clone an xp installation from one computer to another, or you'll get blue screens etc. now if you run sysprep or UIU something like that, then you'll probably have better luck.

if you were able to clone an xp installtion from an AMD computer, then put that image on a C2D system (not that the procs matter, its just going from 1 pc to another thats a problem), then I have no idea how that worked unless you ran sysprep.

7/11/2007 2:46:44 PM

nope. no sysprep.



I was under the same impressions, synapse.

7/11/2007 3:03:11 PM

It can work but like you said you will have quite a few BSODs. The problem is you are moving from one set of hardware (i.e. CPU, Mobo, chipset, etc) to another and Windows freaks out cause it thinks its on the old hardware. When you repair the OS that wipes out the drivers and everything and just kinda re-initializes it so it can figure out whats going on.

7/13/2007 10:04:32 PM

it depends a lot on the onboard components. it's really a crapshoot to try it the way you just did.

I had it work sometimes back in the day going from Athlon to PIII setups, but other times it would fail just swapping out the motherboard. Sometimes it failed even one a new motherboard with the same chipset but a different brand or model.

It just depends on what was configured in the HAL setup when you first installed and what got left out.

7/13/2007 11:56:16 PM

yep. if the HAL is expecting one set of hardware (specifically, the IDE controller) and it sees something else, it freaks the fuck out

(cue the calvin and hobbes "whoa there, too much goddamn information" picture)

that is normally the cause of the bluescreens. windows has never liked switching major hardware around. your best bet is to reformat. if you can't do that, either reseal it and run mini-setup again using sysprep or do a repair.

7/14/2007 12:00:39 AM