Re-installation of OS using original HDD

[seamorton]

Is there anybody who knows how to take this on? In the process of replacing a MoBo in older desktop PC. The OS is XP3 that is installed on the HDD of this older unit. Would like what/how to get XP to boot and install on the rebuild like the original using the original HDD. Any an all suggestions would be appreciated as I haven't the foggiest of how to go about doing a reinstall of XP using the HDD with the authenticated version already installed. Hope this help? Thank you very much! SM USAF 62-66

 

[TheELF]

It's not easy and not sure to work,you will have to use sysprep to uninstall all drivers that could cause problems and then clone the old drive to the new one.

It's called "dissimilar disk restore" and a lot of cloning software like norton,, aomei or acronis have specialized versions for this.

 

[VirtualLarry]

Is the mobo you are replacing, a mobo from a branded OEM PC? If so, XP will de-activate on the new mobo, and lock you out of normal mode after 1-3 days. (Safe Mode should work.)

 

[Ketchup]

How "new" is it? Replacing anything else, like CPU and RAM? There is very little chance a board with a recent chipset will even have the drivers needed for XP.

 

[Bubbaleone]

Back in the day, I'd use nLite to integrate the XP installation ISO with a universal DriverPack as the best solution for this exact scenario i.e., installing XP on dissimilar hardware. I'm guessing your mobo is probably within the same generation as the other older hardware you're working on rehabilitating. This would be a good learning exercise for you to learn about working with ISO images, at the very least, and at best you'll have XP up and running.

.

 

[TheELF]

Back in the day, I'd use nLite to integrate the XP installation ISO with a universal DriverPack as the best solution for this exact scenario i.e., installing XP on dissimilar hardware. I'm guessing your mobo is probably within the same generation as the other older hardware you're working on rehabilitating. It would be a good learning exercise for you to learn about working with ISO images at the very least, and at best you'll have XP up and running.

.

He want's to avoid re installing and starting from scratch that's the whole point,keeping everything the way you spend your time to set it up perfectly.

 

[Bubbaleone]

He want's to avoid re installing and starting from scratch that's the whole point,keeping everything the way you spend your time to set it up perfectly.

Exactly...and the accepted procedure for installing an existing installation of XP, onto dissimilar hardware, is to boot the XP installation CD and perform a "repair" installation. This method keeps all of the existing user data and third-party software completely intact, refreshes all the OS files and installs all the device drivers. The problem is that an original copy of XP will very likely not contain suitable device drivers for the newer mobo and the repair installation will simply fail.

However, performing that same repair installation using an XP installation disk that has been integrated with a driver pack, is very likley to succeed. The guys at DriverPack have been doing this for a long, long time and their goal has always been to provide driver packs that will allow XP to support a far wider range of hardware and devices than the original XP drivers are able to support.

.

 

[cubby1223]

Is the mobo you are replacing, a mobo from a branded OEM PC? If so, XP will de-activate on the new mobo, and lock you out of normal mode after 1-3 days. (Safe Mode should work.)

?

You've been around long enough to know that OEM licenses reactivate on hardware other than the original purchase. He will not be "locked out" of normal mode.

 

[seamorton]

Is the mobo you are replacing, a mobo from a branded OEM PC? If so, XP will de-activate on the new mobo, and lock you out of normal mode after 1-3 days. (Safe Mode should work.)

Let's see if I can answer your question? I rather doubt it as I purchased it from an online seller? P5GC - M/X 1333 W/SLA8 x 2.2 CPU. If that helps? I'll make note of the SAFE MODE possibility. Thank You! SM

 

[seamorton]

It's not easy and not sure to work,you will have to use sysprep to uninstall all drivers that could cause problems and then clone the old drive to the new one.

It's called "dissimilar disk restore" and a lot of cloning software like norton,, aomei or acronis have specialized versions for this.

Interesting procedure. My problem is not knowing which drivers to uninstall from the OS or HDD that Could cause problems from the old drive to the new one? May have to pass on that one for now, as I haven't the foggiest idea of the procedure. Thank you for taking the time to mention this. SM

 

[seamorton]

How "new" is it? Replacing anything else, like CPU and RAM? There is very little chance a board with a recent chipset will even have the drivers needed for XP.

Now that is a question I can answer for you. It is a newer ASUS P5GC-MX/1333 came with Intel CPU and I have 2 - 4 gb of DDR2 ram to install. Probably the limit for XP3. I am replacing a Biostar M7VIG DDR mobo. I have all the drivers on a disk for the P5GC if I can get it installed and booted. That should help some. Hope that helps? Thank you .... SM

 

[seamorton]

Back in the day, I'd use nLite to integrate the XP installation ISO with a universal DriverPack as the best solution for this exact scenario i.e., installing XP on dissimilar hardware. I'm guessing your mobo is probably within the same generation as the other older hardware you're working on rehabilitating. This would be a good learning exercise for you to learn about working with ISO images, at the very least, and at best you'll have XP up and running.

.

Not at all familiar with the nlite and driverpack solution. Wouldn't mind the learning exercise, if it comes to that. I must have purchased and still have the original XP software that I received. Microsoft has been pretty considerate as from time to time I've had to install XP, even on HDD that were fine. Starting from scratch and doing a reinstallation & activation. I just thought that it would be a simple & less time consuming to just connect the original HDD from the other defunct mobo and connect everything and be just like the older one when it was working. Apparently it doesn't work that way but does have some advantages. Thank you for the suggestion. SM

 

[seamorton]

Exactly...and the accepted procedure for installing an existing installation of XP, onto dissimilar hardware, is to boot the XP installation CD and perform a "repair" installation. This method keeps all of the existing user data and third-party software completely intact, refreshes all the OS files and installs all the device drivers. The problem is that an original copy of XP will very likely not contain suitable device drivers for the newer mobo and the repair installation will simply fail.

However, performing that same repair installation using an XP installation disk that has been integrated with a driver pack, is very likley to succeed. The guys at DriverPack have been doing this for a long, long time and their goal has always been to provide driver packs that will allow XP to support a far wider range of hardware and devices than the original XP drivers are able to support.

.

Well I guess I may be best to use the XP installation CD I have and see if I can get it set up using the "repair" rendition. I like to be able to keep all the existing user data, and the drivers that may be helpful. I do have the drivers for the newer board and if I can get internet connection, email that is really all I will need plus XP to install is all I need to make the PC great again. You folks have thrown up the names of some interesting software to search out. Thank you for the suggestion I may get a chance to work on it a little this PM. SM

 

[Bubbaleone]

Not at all familiar with the nlite and driverpack solution. Wouldn't mind the learning exercise, if it comes to that. I must have purchased and still have the original XP software that I received. Microsoft has been pretty considerate as from time to time I've had to install XP, even on HDD that were fine. Starting from scratch and doing a reinstallation & activation. I just thought that it would be a simple & less time consuming to just connect the original HDD from the other defunct mobo and connect everything and be just like the older one when it was working. Apparently it doesn't work that way but does have some advantages. Thank you for the suggestion. SM

I think you misunderstand: Performing a "repair" installation is the only way you're going to be able to install the old drive containing your "original" XP operating system, including all of your personal data and programs, onto different hardware.I realize that for a newbie this all sounds intimidating, but I've been following your posts and I believe you can handle this just fine. Re-read post #7 then follow the links I provided for nLite and DriverPack in post #5.

The author of nLite and the guys at DriverPack have cooperated for years to make the whole process of integrating the XP driver packs, via nLite, relatively painless.


.

 

[xgsound]

YMMV
If you can startup in safe mode you should be fine. I have even changed from Intel to AMD like this.
If you have XP drivers for the "new" board, I would startup in safe mode, then install the new drivers, and reboot. Several reboots and a trip to device manager may be necessary to clear yellow marks.
YMMV
Should this fail you can still perform a repair install. You will need your XP serial number for this. Check this YouTube (music/ sound not needed) for XP repair install instructions if you never did one. https://www.youtube.com/watch?v=Q7OOkqXqagk You will need your XP serial number for this.

Jim

 

[Ketchup]

Now that is a question I can answer for you. It is a newer ASUS P5GC-MX/1333 came with Intel CPU and I have 2 - 4 gb of DDR2 ram to install. Probably the limit for XP3. I am replacing a Biostar M7VIG DDR mobo. I have all the drivers on a disk for the P5GC if I can get it installed and booted. That should help some. Hope that helps? Thank you .... SM

OK. So you are going AMD to Intel. Following the steps in Bubbaleone's post (#7) is your best shot at getting this to work. If you just put the drive in and boot it, 99% sure it will crash, even in safe mode (AMD to Intel systems that are 6+ years apart).

 

[cubby1223]

Well I guess I may be best to use the XP installation CD I have and see if I can get it set up using the "repair" rendition. I like to be able to keep all the existing user data, and the drivers that may be helpful. I do have the drivers for the newer board and if I can get internet connection, email that is really all I will need plus XP to install is all I need to make the PC great again. You folks have thrown up the names of some interesting software to search out. Thank you for the suggestion I may get a chance to work on it a little this PM. SM

First is to look in the bios settings of the new board and if there is anything relating to the IDE or SATA ports saying "AHCI" you need that disabled, or set to "IDE" for XP to work.

Try the repair install from the installation cd. Note it is different from the "recovery console".

The first reboot of the system, XP might hang at the initial black screen with the Windows logo. This is normal. Let it sit for about 5 minutes, then do a hard reset. The setup will continue afterwards.

The other catch is if it is successful, well, you need a copy of the install file of Internet Explorer 8 on a cd or usb drive, go into safe mode and install IE8. Without IE8, the activation screen for the OS will not function.

 

[VirtualLarry]

?

You've been around long enough to know that OEM licenses reactivate on hardware other than the original purchase. He will not be "locked out" of normal mode.

No, they don't. SLP (BIOS-locked) licenses, will lock out after a few days, if you swap mobos with one that doesn't have the code in the BIOS.

Edit: You may be able to activate, if you type in the product key on the sticker, perhaps that's what you meant? The volume SLP key that is pre-installed, will only activate on the corresponding SLP-locked motherboard.