moving XP system disk to a new mobo/cpu

[logicmaster2003]

hi guys,

Last week I have cloned my 500GB ( 3 partitions: winXP SP3, movies, PC games) into another 500GB.

The system that I've been using: Asrock 939 dual sata 2, AMD Opteron-148 o.c. to 2.7ghz, 2GB ddr400, msi 7900GT.

The new barebone system that I want to have the cloned disk run: Biostar P4M900-M7-SE, Intel Pentium D 945, 3GB DDR3, and I want to move the MSI 7900GT over to this machine.

When I turn the new barebone system on, i get BSOD with these message:
Quote:

A problem has been detected and windows has been shutdown to prevent damage to you computer
....
technical information:
*** STOP: 0x0000007B (0xF789E528, 0xC00000034, 0x00000000, 0x0000000)


I have read about booting it up with winXP CD and going thru the whole enchiladas, but I'm not so sure about wanting to do all those tedious works (download all the drivers for the new barebone into floppy and have winXP CD read from there, losing and having to re-install my Service Pack and other windows settings, etc).

Has anyone else tried this before ? what are the solutions ? Any better way and easier way ??


Thanks !!

 

[Paperlantern]

I would NOT recommend doing what you did in any instance. When you clone a machine, the hardware that is in place is the ideal machine to clone it to (in many cases cloned machines are in large corporations or even in small businesses where they buy a few on up to thousands of the exact same model and configuration PCs and blow the image out to all of them so they are all the same). What you are doing has such a drastic change windows XP freaks out, doesn't know why the hardware is so different, cant load any drivers for it, and upchucks.

My honest and professional opinion would be to load XP from scratch on the new machine, loading each driver separately, the way you're supposed to, you will have a much more stable and happy system on your hands when you are through, then if you try to patch this one up.

If you simply cant stand to do that, I would suggest maybe sys prepping the machine before cloning and moving the drive to the other system, sys prep will re detect hardware to a certain extent, wheather this situation goes beyond that extent I cant say (though i would think that it would), I'm not going to go into the specifics on how a sys prep is done, there are plenty of guides out there you can find on Google, but I will say you need your XP disc handy. Ive never sys prepped a machine that was THAT different, but you never know, I was in a situation where we used the same Image for a Dell GX1 and a Dell GX280, but we included alot more drivers in the image then perhaps you have. Though, it might be worth a shot.

 

[timswim78]

You could slipstream SP3 and your drivers onto your XP disc with Nlite. Then do a repair installation. All of your stuff should still be there. Also, it may help to run SYSPREP on the cloned drive before plugging it into the new barebones.

See this thread for ideas:
http://www.hardforum.com/showthread.php?t=772307

 

[Arkaign]

I use a method that I call mergeide, it works about 97 or 98 times out of 100. Out of 100 successful mergeide uses, about 15-20 of them will have oddities; poor performance, etc.

It's definitely worth trying, as it's easy and quick.

(1)- Put the disk back in the original bootable system.
(2)- Copy 4 original files over the files in windows\system32\drivers
(3)- Run mergeide.reg
(4)- Shut down system, and immediately take out HDD to place into the system you're transferring windows to
(5)- Boot new system up, it will boot using standard IDE drivers, then attempt to load drivers for new HW.

google mergeide.reg for info on the files you need.

 

[logicmaster2003]

oh oh I just thought of something different !

DO you think this will work ??/


1) fresh-install win XP on my new barebone
2) transfer my current gamer REGISTRY and game directories into this

will all my games and applications work ?