• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

so swapping MOBO's messes up XP?

T

thecolorifix

Member
I'm getting a new mobo and proc, I wasn't planning to re-install xp, but is that what I'll have to do?

It's not too big a deal, I probably need to do it anyway, but are there any workarounds?
 
Definitely do a repair.

You just act like you're installing XP. It'll tell you you already have Windows installed. First it'll ask you if you want to repair using the recovery console. That's not what you want. Just tell it to install XP. Then on the next screen it'll ask you if you want to repair the existing installation.

Then it'll go through the entire process of installing XP, but it'll save your data files.
 
I read your post wrong, though ... If you haven't actually installed the mobo yet, you might as well backup your stuff and do a regular XP installation. I've never had a single problem with repairing XP, though, no matter how much hardware I changed.
 
My motto is to always try before i format. What's to lose?

I find 90% of the time, a simple mobo swap is perfectly fine. my current system is running on a mobo swap install from back in mid 2005. Runs flawlessly. Just remember to install drivers for new MB (if chipset has changed) prior to disassembly so during first boot the new drivers are ready. That's all you should have to worry about.
 
If its same brand/cpu type (like nvidia/amd to nvidia/amd) and relatively close (like nf3 vs nf4) then it might just start up fine. There is also xpdeploy tool (somewhere I found on anadtech forums) that basically re-detects all your hardware after u install new.. U can try that too.
 
Originally posted by: lyssword
If its same brand/cpu type (like nvidia/amd to nvidia/amd) and relatively close (like nf3 vs nf4) then it might just start up fine. There is also xpdeploy tool (somewhere I found on anadtech forums) that basically re-detects all your hardware after u install new.. U can try that too.
Click to expand...

What are you talking about? You can yank the C: drive out of a P3-450 and put it in an Athlon X2 and a repair install will make it work. It totally reinstalls Windows on top of itself and re-detects everything. So why would you need a tool to do that for you?

Repairing the installation when changing hardware has worked 100% for me, but I have seen other people say that's not always the case. I absolutely wouldn't recommend just swapping motherboards and booting up like nothing happened, no matter how "relatively close" the chipsets are.
 
"I absolutely wouldn't recommend just swapping motherboards and booting up like nothing happened, no matter how "relatively close" the chipsets are."

Agreed! I would highly recommend doing a fresh install when installing a different m/b.
 
I have done it both ways, there is an the advatage of not having to reinstall all your software if you just do the swap/repair. But if it doesn't work you can always do the full format at that point.

So the key here is to make sure your crap is backed up before doign anything, that way, it doesn't matter. *grin*
 
There's been like 8 threads about this in the last week.

Just swapping the system generally works fine. The only issue is that the drivers for the old chipset and other devices are still installed on the system, and may still be loading even though they aren't actually in use. Simple way to prevent this is to uninstall any drivers that you installed from the motherboard CD or downloaded from the manufacturer for any devices which will not be installed in the new system, and in Device Manager, uninstall any brand-specific devices so that Windows will not load the drivers into memory. Then do the hardware swap and Windows will just detect all the new hardware.

The second option is a Repair install, which is a good compromise between making sure Windows is cleaned up, and not wasting time. The Repair install wipes out all device configurations in the Registry, as well as all Windows updates, while leaving all your data files and installed applications alone. When you boot after a repair install it will detect all the hardware as if it were a new installation, so you'll have to reinstall all drivers (however any downloaded drivers from before will still technically have the driver files on the hard drive, but Windows won't have any references to them in the Registry except for the Add/Remove Programs entries; it's best to just uninstall them before the swap when possible). You will also have to download all the Windows Updates again, however you won't generally need to reinstall any applications.

Only as a last resort should you do a complete reformat and reinstall.
 
I recently switched from a nforce2 chipset with a 2500+ to a Opteron with a ULi chipset MB. I bought a new HDD and did a new install of WinXP. However, just to see what would happen, I put my old HDD in. It started up no problem, ran just fine. I still wouldn't say it's a good idea to do this, but it IS possible for it to work.

Since I bought a new HDD, I did a fresh install. However, in situations where the current HDD would be used, repair install FTW.
 
Just a quick fact to the writer of this post. And for those that aren't that familiar with how the XP product activation really works.
When you install XP (any version) windows takes the cd-key that you enter , and then takes digital "signatures" from certain peices of hardware in your system. Each piece Processor, video card , sound card , RAM , and network adapter ...etc. And then uses the key and all the "signatures" for each piece of hardware to come up with your "installation ID". That is what identifies your computer to Windows XP every time you turn it on.
When adding or upgrading hardware , you can do it , Windows is actually really flexible in what it considers "drastic hardware changes" , before it asks you to reactivate the software. All of the above pieces of hardware are also given a point system that Windows goes by when deciding if there has been a big enough change in your setup to qualify for a re-activation. Total of 10pts.
For example...your processor may be worth only 1pt. , memory 1pt. the one that I know is a biggy is your network adapter which scores 3pts. on the scale.
So if you are upgrading motherboards , and use all the same hardware on the machine except for the motherboard. you might get away with it , as long as the new parts don't exceed the 10 point scale.
Does that make sense?
But ya , with a new build , I'd definately back it all up first , and f-disk the bad boy , do a complete format and fresh installation of the OS. Nothing like a fresh PC. It's like puttin on a clean pair of socks.
 
the reason you would have to do a "Repair" is because of the activation being in question with XP. Other than that , Windows will detect and set up any new hardware that it detects. You don't need to "Repair" when doing an install of hardware do ya?
 
Originally posted by: Maxspeed996
the reason you would have to do a "Repair" is because of the activation being in question with XP. Other than that , Windows will detect and set up any new hardware that it detects. You don't need to "Repair" when doing an install of hardware do ya?
Click to expand...

The Repair install is an effective way to eliminate all references to the previous hardware configuration, in order to ensure a stable system. There are reasons for wanting to do it regardless of the activation issue. Activation shouldn't even matter anyway, if you're using a legitimate copy of XP in the first place; it takes all of 10 seconds to get through unless you're installing, activating, then reinstalling and trying to activate again within a certain period of time, and then it just takes a phone call.
 
I learn something new every day. I didn't think that mattered when removing and replacing hardware. The system keeps a record of it being there. But I've never had THAT be an issue.
Bottom line is BRO , if ur droppin in a new MOBO. I'd do a fresh install of the OS as well. Shouldn't take but an xtra hour or so to f-disk , format and install. depending on the size of your drive (s) of course.
 
The time to install Windows isn't the issue, it's the time to install all the applications and get them updated and configured just the way you like them again. Why spend the hours doing that when you don't have to?

A Repair install of Windows takes pretty much the same amount of time as a normal install, as all the Windows files are pulled off the CD and replaced.
 
Maxspeed996: Looks like you've found yet another reason why even if you own a legit copy of XP Pro, you're better off using a corporate edition or getting a copy from your university library and using their key which doesn't require activation.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top