WinXP: i440BX to Nforce2

[pitz]

I have a WinXP SP3 setup that is nicely running on an i440BX motherboard. Would like to move it to a Nforce2 motherboard (and AMD AthlonXP 2500+ Barton).

Disabled agp440.sys. In the bootup log, it gets to Mup.sys, and then quits.

Anyone dealt with this before? It doesn't seem to be able to write to the disk.

 

[notposting]

That might be too much of a change for XP. Try uninstalling all the hardware specific drivers in Windows and then booting on the nforce board.

However, going from old Intel to not-as-old AMD system will probably make Windows unhappy. Hope you have data backed up.

 

[JackMDS]

As far as my experience goes moving from BX to nforce would result with BSOD when during the Boot the OS starts to read from the HD.

Unless you are willing to buy Acronis True Image with Universal Restore, you are better of starting with new install.



😎

 

[Binky]

I've successfully moved between very different chipsets by using the WinXp "repair" option from the install disk. Google something like "change motherboard without reinstalling windows," and be absolutely sure to take the SECOND repair option that it gives you.

Oh, and make a backup. This has a very high chance of failure.

 

[pitz]

Okay, I have a backup (an identical HDD with the copy of the existing drive imaged). I moved the HDD over. Get stuck at a STOP 0x0000007B error (but strangely, not the "INACCESSIBLE_BOOT_DEVICE error -- so it almost seems like its getting hung on a proprietary Intel driver more than anything!).

Same thing happens regardless of whether I boot from the physical, or boot from an iSCSI image over the network from my SAN.

Unfortunately, I really can't go the 'new install' route because the XP setup (on the i440BX system) contains (very expensvie) licensed software, and dealing with the vendors for new license codes will be a royal PITA. 🙁.

Acronis Trueimage....how much?? 🙂 I was able to fire it up as a VM on Sun Virtualbox.... So there is an exit path if the hardware suddenly starts to become majorly unstable.

Thanks everyone... I'll give the Repair function a try, and I'll also take a look at the costs involved with the Acronis product..

 

[JackMDS]

Yeah Microsoft VPC would work too because the VM emulates the BX chipset regardless of the current computer.

As for TrueImage, here is the flat version ($19) after rebate, http://www.newegg.com/Product/Produc...e+2010&x=0&y=0

Universal restore ad-on for Home version, http://www.acronis.com/homecomputing/products/trueimage/plus-pack.html

Read, and make sure that it works togather. I have the more expensive old Echo version.

If Home level combo works well, any one who spend time on migrating from one chipset to another will find the $50 spend the best deal for the money he/she ever got.




😎

 

[ViRGE]

Unfortunately, I really can't go the 'new install' route because the XP setup (on the i440BX system) contains (very expensvie) licensed software, and dealing with the vendors for new license codes will be a royal PITA. 🙁.

Perhaps I'm asking a stupid question here, but have you confirmed that the applications in question aren't tied to the hardware in the first place?

 

[PingSpike]

Do you still have the i440bx motherboard? If so, boot off it, go to device manager and change the hard disk controller driver to "Standard PCI IDE controller"...its under microsoft I believe. In my experience, that lets me boot switching between hardware. If it tries to use the intel (any vendor specific driver really) on a different kind of controller, it balks with the inaccessible boot device BSD. The other devices can sort themselves out after boot. 😛

The only trouble with this method is that when a motherboard fails and gets replaced, it obviously is not possible to do. This is one area where windows9x was much more forgiving.

 

[HannibalX]

You could SysPrep the install and then Ghost it. You would need to add any additional drivers to the SysPrep setup though.

 

[eplebnista]

Do you still have the i440bx motherboard? If so, boot off it, go to device manager and change the hard disk controller driver to "Standard PCI IDE controller"...its under microsoft I believe. In my experience, that lets me boot switching between hardware. If it tries to use the intel (any vendor specific driver really) on a different kind of controller, it balks with the inaccessible boot device BSD. The other devices can sort themselves out after boot. 😛

The only trouble with this method is that when a motherboard fails and gets replaced, it obviously is not possible to do. This is one area where windows9x was much more forgiving.

If the bx is still working, I have also had success with adding a promise pci card and installing the driver for it, then moving the boot drive to it. Then booting once to make sure the promise drivers work OK. Then hooking up the hard drive to the promise card in the new mobo and it generally boots right up, XP registers the hardware changes and usually prompts for reactivation shortly thereafter.

 

[PingSpike]

If the bx is still working, I have also had success with adding a promise pci card and installing the driver for it, then moving the boot drive to it. Then booting once to make sure the promise drivers work OK. Then hooking up the hard drive to the promise card in the new mobo and it generally boots right up, XP registers the hardware changes and usually prompts for reactivation shortly thereafter.

I actually did that as well with a promise controller once. I didn't really think it was going to work at the time but thought I'd give it a shot since I didn't feel like reinstalling windows at the time.