• 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.

XP pro refuses to boot up in new machine.

R

RobertPters77

Senior member
I copied an xp pro install from my broken DVR machine onto a new disk. I wanted to install the DVR on a new AMD system. But every time I turn the computer on it just goes into an endless reboot cycle. I don't know wtf is going on. The disk works fine in my old system but refuses to boot up in my new system. I think it's the DVR cards at fault because the Manufacturer states the cards only work with Intel chipsets. But my other DVR machine has the same cards but it running fine on a socket 940 system. And even without the dvr cards the system just endlessly reboots.

The old DVR system has a P4 3.4ghz, 2gigs of DDR2 533, 925XE chipset on an Asus p5ad2-e premium mobo. The other DVR system has an Opteron at 1.8ghz, 2 gigs of DDR400, Motherboard and Chipset N/A.

edit: I put the cloned disk into the other dvr system with the amd cpu. Still reboots.
 
Last edited:
It won't work unless you strip out all the device drivers. Those are very different motherboards and chipsets.
 
skyking said:
It won't work unless you strip out all the device drivers. Those are very different motherboards and chipsets.
Click to expand...
Tried that, no go.

Nothinman said:
You may be able to get it to boot by doing a repair install, but even that's hit or miss with XP.
Click to expand...
I'm afraid of losing all my data.

VirtualLarry said:
Google "XP SP3 AMD CPU reboot loop". It's a known issue, when going from intel to AMD rigs.
Click to expand...
I have an old p965 e6400 system that I tried to run it in. Still endless reboots. Even with new chipset drivers.
 
At this point, it looks like you need to acquire a new HD, and do a fresh install of windows on it, and then slave the old drive to it, and read the data off of it.
 
The main problem with XP is the hard drive controller probably changed. This will give you the blue screen and refuse to progress. Sometimes it is other device drivers, but most of the time in my experience it was hard drive controller. What I used to do in the EIDE days was install a separate Promise Ultra 66 PCI controller in the machine before transferring the drive. Let XP detect and install all the correct drivers. If you want you can now even connect your drive to the Promise card and reboot. But you can also probably just swap the drive to a new computer and connect to the Promise controller card. This will get you further in the boot process, possibly even to the point where you can install all the new drivers. You will need to reactivate.
 
VirtualLarry said:
At this point, it looks like you need to acquire a new HD, and do a fresh install of windows on it, and then slave the old drive to it, and read the data off of it.
Click to expand...

I did. Bought a 1tb seagate disk. Old drive is IDE 80gb new drive is sata. Don't have windows XP pro disks. Could I maybe install 7 and run XP mode? Will that work?


SimMike2 said:
The main problem with XP is the hard drive controller probably changed. This will give you the blue screen and refuse to progress. Sometimes it is other device drivers, but most of the time in my experience it was hard drive controller. What I used to do in the EIDE days was install a separate Promise Ultra 66 PCI controller in the machine before transferring the drive. Let XP detect and install all the correct drivers. If you want you can now even connect your drive to the Promise card and reboot. But you can also probably just swap the drive to a new computer and connect to the Promise controller card. This will get you further in the boot process, possibly even to the point where you can install all the new drivers. You will need to reactivate.
Click to expand...

That could work. But like I said new drive is Sata old drive is IDE. Will there be any compatibility issues? I cloned the new drive with seatools and it worked fine on the old DVR pc. Putting either the new or old drive in either the Intel or Amd system resulted in BSOD.
 
XP Mode (nor any other VM system besides Xen and I'm not sure if it still even supports it) can access PCI hardware directly, so that won't help you.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top