Will i have to reinstall XP?

[fustercluck]

I got a new CPU/Mobo on the way, and will hopefully install them tomorrow (if i get them), my bro says i'll need to reinstall XP once i get the new parts in. Is that correct? I really don't want to reinstall all my programs and everything. If i can avoid it i would certainly like to.

If it matters the cpu is an Opteron 146 and the Mobo is an Epox EP-9NDA3J.

 

[skisteven1]

Many times no, though you may ahve to re-activate it. On the other hand, the cpu/mobo are the most complicated parts of the OS (ie. most integrated). So if there are any parts you could replace that would require a re-install, those would be them. Chances are if you're changing out cpu/mobo, you'll have to re-install (probably, if not certainly)

You can try using sysprep (very cool tool) to prevent having to reinstall. It (I believe) gets the system to wipe its internal drivers and prepares it to move to a different hardware configuration... which is basically what you're doing. Check it out.

 

[fustercluck]

Ok, thanks for the info. Anyone else know much about sysprep?

 

[fustercluck]

Ok, thanks for the info. Anyone else know much about sysprep?

 

[spherrod]

http://support.microsoft.com/default.aspx?scid=kb;en-us;302577&sd=tech

 

[imported_dakota81]

The most important step seems to be going into safe mode and removing the ide controller drivers from device manager before switching motherboards. XP hangs up when trying to load incorrect ide drivers. You have to be quick removing all the drivers from device manager, and do not reboot, as when XP loads up again, it will reload all the drivers again that you wanted removed.

 

[skisteven1]

according to some of the stuff from the MS website (thanks spherrod), it appears that you may be hit or miss depending on the two mobo's your using.

? The reference and destination computers must have compatible HALs. For example, Advanced Programmable Interrupt Controller (APIC)?based MPS (multiprocessor systems) must use the same APIC HAL. A standard HAL Programmable Interrupt Controller (PIC)?based system is not compatible with either the APIC HAL or the MPS HAL.
? The reference and destination computers must have the same Advanced Configuration and Power Interface (ACPI) support.

So you can try, and IMO, sysprep will give you a better chance, if anything -- though it may not end up doing the trick.

EDIT for aesthetics

 

[Fern]

Hey JT,

Here's an Anandtech article on how to do this (new mobo etc and keep current install) LINKY.

Basically, your OS has all the drivers for the old mobo (chipset etc.) and those won't work on the new mobo unless they use the same chipset & drivers.

Scroll down on the link above and look at the "Misc Notes" section.

Let us know how the opty OC's.

Fern

 

[Fern]

Hey JT,

Here's an Anandtech article on how to do this (new mobo etc and keep current install) LINKY.

Basically, your OS has all the drivers for the old mobo (chipset etc.) and those won't work on the new mobo unless they use the same chipset & drivers.

Scroll down on the link above and look at the "Misc Notes" section.

Let us know how the opty OC's.

Fern

EDIT: Wow, the forums have really been acting up lately. This is my First ever DP

 

[fustercluck]

An importent piece of the puzzle I forgot to mention is that my old motherboard (DFI Lanparty NF3 250GB) seems to be dead. It just would not boot up one day. The trick setup looks like my best bet, thanks Fern. If that doesn't work, can sysprep be run from the recovery console with a new motherboard?

 

[Fern]

Originally posted by: jacktackle
If that doesn't work, can sysprep be run from the recovery console with a new motherboard?

Honestly, I don't know. Haven't tried it.

I don't do mobo upgrades often. So when I do, I take the opportunity to do a reformat and reinstall to clean out all the crap I've accumulated.

Fern

 

[skisteven1]

I do not believe that sysprep can be run from the recovery console. Maybe from something like BartPE, but I dont know.

 

[birdpup]

[*]Swapping a hard drive, with the system files ( C: ), from one system to another
Swapping a hard drive with the operating system files on it, from one system to another is similar to changing a motherboard in one system. The hard drive and motherboard must communicate through drivers and if either the hard drive or motherboard are changed, then the drivers must be updated. There are different ideas on how to update these drivers for the operating system and these ideas include:

• Clean Installation
• Repair Installation
• Use of Sysprep (more than one system)
• Standard PCI IDE Controller trick (only one system)
  
  • Helping Windows Survive a Motherboard Upgrade
  • How to: Upgrade your motherboard without reinstalling Windows.
  • "Standard PCI IDE Controller" trick
    • Put the HDD in the old machine, change the HDD controller to "Standard PCI IDE Controller", and then immediately shut the PC down and move it to the new PC. As long as the HAL is the same, the PC will boot. Be ready with driver CDs or floppies, and you're all set. (written by dclive)
  • Google: How to Move a Windows XP Installation to Different Hardware
  • Microsoft Support: How to Move a Windows XP Installation to Different Hardware
  • How to use the Sysprep tool to automate successful deployment of Windows XP
  • Windows XP Setup - Missing HAL.DLL
  • Microsoft: HAL Compatibility List

 

[fustercluck]

Well, thanks for all the help, very informative stuff. Luckily though I didn't need to do any of it, i put in the new cpu/mobo and it just booted up fine, heh. Surprised me. I love it! - Now i don't have to stay up all night reinstalling everything. I guess it's because i was also using an NF3 mobo and A64 cpu before, so i guess that wasn't a big enough change to mess up everything.