Want to move system from Asus A7N8X to P5P800 w/o reinstalling software

[Wiz]

Also posted this in OS - but maybe it's more of a Motherboard situation

I'm aware of many issues including but not limited to:
new chipset
new audio
new LAN
single Proc build -> multi proc build
etc...

Win XP Pro SP1 running, also my install disc is same.
Only the mobo & cpu are changing - rest of hardware staying same.

Will simply doing a repair install pick up all the new hardware including the change from single cpu to dual? I've got a load of software installed & don't want to reinstall it.

TIA

 

[Woody419]

There is a way to do this by deleting system items in the device manager before making the move, then Windows will automatically install the correct ones. Very messy, never done it. A clean install is best.

 

[Wiz]

Thanks, I found this about using Sysprep - looks like it will do the trick.

http://www.hardforum.com/showthread.php?t=772307&page=1&pp=20

 

[Fenuxx]

Originally posted by: Wiz
Also posted this in OS - but maybe it's more of a Motherboard situation

I'm aware of many issues including but not limited to:
new chipset
new audio
new LAN
single Proc build -> multi proc build
etc...

Win XP Pro SP1 running, also my install disc is same.
Only the mobo & cpu are changing - rest of hardware staying same.

Will simply doing a repair install pick up all the new hardware including the change from single cpu to dual? I've got a load of software installed & don't want to reinstall it.

TIA

Well, I would say that it would be a complete waste of your time to try and salvage what you have as:

1.) It is possible it may not work
2.) Even if it does work, things may be quirky
3.) It could take you longer to salvage than reinstall
4.) You're switching between TWO COMPLETELY DIFFERENT PLATFORMS!!
-----A.) If you were just updating from, say and 865PE to a 915P, then it would be a little more reasonable.
-----B.) Switching from AMD to Intel is hard enough, but doing it without reinstall? That, IMHO, is just plain wacko!

You see, its just not really worth your time, as it would be much easier to just back up all of your data, and then reinstall from scratch. I tried to do this once with my uncle's computer, going from a P3 to an Athlon XP, but I quickly found out that it would be less frustrating and faster to do everything from scratch. Just back up your data, format the hard drive, and reinstall. Its not that hard, and you'll probably be happier with the outcome of that than a salvage attempt.

BTW, what were you talking about with going from a "single Proc build -> multi proc build"? If you mean HyperThreading, that wouldn't matter, as its not truly a second CPU. Also, WinXP Pro has dual-CPU support built in, so it would just "turn on".

 

[DerKaiser]

There's a guide for doing this at the Arstechnica CPU and motherboard forum.

 

[Wiz]

ok, Im screwed


I tried the sysprep method, but I think I messed up two things.
1. I checked the button to have it NOT create new SID
2. I had a custom boot mod that I forgot to remove

So, the mini setup started - I went through a few screens and then it gave an error.
That's all it would do, over and over.

So I put in the XP CD & tried repair.
It copies files and then reboots tp a blank screen - it's supposed to be continuing to install. Keyboard lites won't go on/off.

That's where it is. Anybody got an idea?

 

[Wiz]

update:

I went into recovery console and deleted boot.ini and then told it to make a new one.
Afterwards it booted into the setup screen like it should have several hours ago.

 

[thunderroller]

i dont think so.but you can try repair opting during installation

 

[Wiz]

ehrm... I was typing that from the system in question - fixing boot.ini solved the issue

After fixing boot.ini it rebooted into the next part of setup, installed devices and all was good.

So far all my software installations seem to be intact. Everything works great!

Repair install was the key - but the fouled up boot.ini was the crippling issue.