Question about ASUS P5LD2-VM Motherboard
I just installed an ASUS P5LD2 with an Intel Pentium D 840 3.2 GHz CPU, and 2 sticks of DDR 667MHz (1Gig each). My boot disk (from my old PC) is a P-ata and is jumpered as the master as I have always had it. The problem is that when I boot, it goes through the cycle until I reach the Windows startup screen where it throws itself into a bootloop. I tried booting from the WinXP install disk in hopes of doing a "repair" on the boot drive, however it gets to the "Windows Starting" screen and freezes. I can't even do a clean install on a new drive, as it gets to the same point and freezes. I've tried about everything and I'm about to pull out what hair I've got left. Any help or suggestions would be appreciated. Thanks
Not sure I completely understand your issue, but there is almost NO Possibility that your old drive will boot up on a new motherboard. (Unless it's nearly identical to the old motherboard)
The Windows HAL (Hardware Abstraction Layer) will have a fit.
Even if it does manage to plug and play through the driver changes and start, the Windows Genuine Disadvantage tool will prompt you to re-activate Windows and you'll have to jump through hoops there. Better to do a clean install on a motherboard change anyway.
ATAPI (Attachment Packet Interface) should only apply to your CD ROM and or Tape backup devices. And this board DOES support them.
Posted on Nov 01, 2007
I think the main problem with this is that there has been a significant enough hardware change for Windows to deny booting up. You should always back up on the previous pc, reformat and expect to have to do a clean installation and re activate Windows. Did you check in the bios that the time, date and HDD settings are correct. There may also be a driver conflict as the old motherboard drivers etc will still be on the HDD. Try this also My computer>properties>advanced tab>Start up and recovery settings, then on System Failure make sure Automatically Re-Start is unticked, as this should then bring up on your next boot a BSOD giving you a clue as to the problem. Keep trying
Posted on Nov 03, 2006
Tips for a great answer:
Usually answered in minutes!