BSOD after mirroring an IDE to SATA

[AlaDes]

I have a customer who would like everything on one of their systems (Dell Dimension 2400 with an Intel processor) transfered over to another one (Dell Dimension E521 with an AMD processor) via mirror. The problem is that one PC has an IDE HDD and Intel processor and the other PC has a SATA HDD and an AMD processor. He has a valid XP license for both machines, and isn't worried about anything on the second machine he wants everything transfered to, so I plan to use that license to reactivate XP when it asks me to (I don't see anything illegal about that, so please correct me if I'm wrong).

I have performed the mirror and am now getting a BSOD of 0X7. I know this is a common problem when going from one type of drive to another or from one type of processor to another but am wondering if any of you know of a work around or have succesfully done this. The only options in the BIOS are for "SATA" or "No SATA", therefore I will have to manually edit the registry using DART tools, which I have.

 

[compnet]

Check out fixide on foolishIT.com

 

[gikstar]

In the Bios, is the Sata hard drive set as AHCI? If it is, switch it to IDE and see what happens.

 

[Ccomp5950]

Going from one machine to the next you may have issues with HAL types as well as drive access methods (FIXHDC in UBCD4WIN will help with that or what compnet suggested)

Go into the BIOS and turn off ACPI

If the single processor non-ACPI HAL is installed you are also going to have the problem with the new processor (it's a duel core processor so requires the multicore HAL)

If all else fails run a repair install on the system and it will more then likely replace the HAL with the correct version.

 

[johnrobert]

Transfer XP from One Computer to Another | Trick to Bypass BSOD (Intel to AMD)

http://www.gcsdblogs.org/roodhouse/?p=867&cpage=1

 

[YeOldeStonecat]

While "moving" a Windows install from one piece of hardware to a similar piece of hardware (like Intel chipset based motherboard to similar Intel chipset based motherboard)....it can work..sorta OK. But when you do an entirely different generation and chipset type (like Intel to AMD..and the AMD one will have entirely different drive controllers)...you'll not end up with a good stable system.

Uninstalling all of the base motherboard .infs of the old system, old NIC, AGP, sound....and then downloading/installing all of the drivers for the new system, you still end up with "dirty" old drivers left in the system.

Will the system be able to boot up? Yeah..probably after you fidget around with forcing in new drivers, flipping around SATA modes to legacy, etc.

But will the system have odd quirks....end up hanging now and then, lock up once a week or once a month, have other subtle instability issues? Probably.

Best off with a clean install and migrate the data.

 

[ComputerRepairTech]

Transfer XP from One Computer to Another | Trick to Bypass BSOD (Intel to AMD)

http://www.gcsdblogs.org/roodhouse/?p=867&cpage=1

Good call, I remember this one from that HP screw up a while back. I think Nick implemented this into D7 a while back.

 

[AlaDes]

Thanks for all your help people, but I have found a solution. I happened to be using D7 today and noticed Nick had a incorporated a utility under "Offline Ops" called "FixIDE (WinXP)". It's used to fix the registry when swapping out motherboards on XP machines. It worked like a charm! Of course, I had to use D7 in a PE environment, which Nick provides a great tutorial for on his website

 

[drpcfix]

holy crap - I was just going to write a big post about how I've never been able to make that work going from intel to amd or the other way - only same CPU type..

I'm going to check out D7

thanks

 

[FremontPC]

Transplant system to different hardware

Paid versions of Acronis, Macrium Reflect and StorageCraft (Shadowprotect) all offer bare-metal, hardware agnostic restores from disk image backups, usually as an add-on to their standard backup software. The process strips out the driver info and allows Windows to rebuild that info on the target system. Basically, you create an image of the source system and during the restore process you can opt to restore to different hardware. You will need to have the drivers for the target system on hand.

N.B., some installed software (Adobe, Quickbooks, etc.) will require you to reactivate before it will run on the new system. You might want to uninstall such software from the source system after the transplant (and before you connect the target system to the net), but be sure the old system is connected to the internet so their registration servers can verify the uninstall. Some software may have a specific procedure or additional steps you need to take in order for this to work.

 

[NYJimbo]

Are you really sure this is an issue between processor type and not motherboard chipset types ? Chipsets are not automatically related to CPU type, although some motherboards have chipsets made by that CPU manufacturer.