New SATA/IDE mobo won't boot to IDE

December 8, 2010 at 17:39:48
Specs: Windows XP, Phenom II X4 955/4GB
I finally bit the bullet and replaced my aging motherboard/cpu combo, due to failing RAM or the RAM controller on my 11 or 12 year old AMD Athlon PC. This has always been my primary machine. When the startup sequence reaches the point of booting the OS it stops with the following message (in part): "Windows could not start because of a computer disk hardware configuration problem."
I have changed the boot sequence from optical drive after the HDD to before the HDD, I disabled the 2nd HDD, but can not seem to find the correct settings to get the OS to boot.
I could not find anything on the ASUS web site that relates to this, so any help is greatly appreciated.

The replacement parts include new ASUS mobo w/ AMD CPU, RAM & a new PSU. I am using my existing WD HDDs. The boot drive is 80 GB with a 160 GB secondary, which was the boot drive until last March, when I did a fresh install of XP Pro and SP 3. Other than the previously mentioned issue with memory, there have been no significant issues since then.

Mobo is Asus M4A88TD-V EVO/USB3 with five SATA III internal ports and one EIDE internal port.
CPU is AMD Phenom II X4 955 Black Edition
RAM is Patriot 2 x 2GB PC3-12800
PSU is CoolerMaster Extreme Power Plus 550w

Partly because there is only one IDE port on the new mobo, and because I wanted to use my only DVD burner in this machine, I pulled the optical drive from the family PC in the living room, where it has been in use for several months. This drive is SATA, & is the only SATA drive in the newly updated PC.

If you need more info, please let me know.


See More: New SATA/IDE mobo wont boot to IDE

Report •

December 8, 2010 at 17:45:46
You can not replace componets like that and expect the OS to boot.

At a minimum you have to do a repair install of xp to get all of the drivers/registry entries corrected.

web search repair install xp for the how to

Answers are only as good as the information you provide.
How to properly post a question:

Report •

December 8, 2010 at 18:41:35
wanderer is correct. XP does not like being moved from one system to another. You apparently did nothing to prepare the old HDD before swapping it, so when you attempted to boot off it in the new system, XP immediately recognized the difference in hardware & halted. Your old HDD is just that - OLD! Not to mention it's slow & has low storage capacity. Dual platter 1TB HDDs sell for about $50-60. A single platter 500GB costs roughly the same. You had no problem buying the other components, I suggest you open your wallet again & do it right.

OK, enough preaching. You have at least 3 options:

1. attempt a "repair install" & see if that allows you to boot off your old HDD

2. format your old HDD & do a clean install of XP

3. buy a SATA HDD & do a clean install of XP, or better yet, step up to Win 7. If you insist on sticking with XP, you will have to learn how install SATA drivers at the start of the installation (do you have a floppy drive?) because XP doesn't natively support XP.

All of these things have been disussed dozens of times before in these forums. Try using the search feature at the top of the page.

Report •

December 8, 2010 at 22:25:06
Mickliq, Wanderer may be correct about XP not liking the component changes, but I have found that a repair install does not work. It appears that the pci.sys is causing a problem, as that is the driver identified in the bsod which occurs during the repair setup.
No, I no longer have any way to use a floppy, as the new mobo does not have a floppy controller, a point I missed until trying to connect everything up.

Why do people feel the need to "preach" in answers to questions for help? And then give a non-sensical answer like "XP doesn't natively support XP." As for the comments where you state that I did not have trouble buying components, and therefore should "open my wallet again, and do it right!", one should never assume that other people have lots of money to spend. The stated age of my system should have been an obvious indication that I don't regularly replace my PC, or components, just to make sure I have the "latest and greatest" hardware, or even close to it. FYI, my wallet took a much bigger hit than I anticipated in purchasing the above named components, and related parts.
The other point that you apparently missed is that I had little choice but to upgrade or replace because my previous system was failing due to advanced age. Replacing the PC133 RAM, or attempting to ensure that it was the RAM and not the memory controller that was failing, would be both be prohibitively expensive and/or time-consuming. And I most likely would still have had to do a major upgrade anyway.
Just the same, thank you for suggestions.
Unfortunately, I did not find much on this forum that appears to be closely related to the issues I asked about in my posting.

Report •

Related Solutions

December 9, 2010 at 10:11:34

For someone looking for help you are a bit scathing towards those trying to help you. You run the risk of being ignored if you do that.

You might like to know that the people who offer help on this site do it for free out of the goodness of their heart and just may be for their own learning. So do not be too harsh when they occasionally get it wrong or in this case mistype. To err is human and all that.

and then give a non-sensical answer like "XP doesn't natively support XP."
That I am pretty sure was a typo and what he meant was:
XP doesn't natively support SATA drives. You can in fact see it in the context of his response.

What mickliq has suggested in his items 1, 2 and 3 is pretty much what you will probably get from even the most experienced PC users.

With regards to not having a floppy drive you may have to slipstream your XP CD to build in your SATA drivers for your SATA hardware in order that you are able to successfully install XP on your rig.

Here is an article on how you might do it if it interests you:

Your original problem might have been fixable. Here is some information on that as I do not know how far you have got to. Per chance that it helps.

When everything else fails, read the instructions.

Report •

December 9, 2010 at 10:19:03
One other point to consider:
You may need to check the driver availability for your new hardware. The reason I suggest this is that newer hardware sometimes lack drivers for older OSes.

So you may find that drivers are available for Windows 7 and maybe Vista but not for XP in which case you may not be able to install XP without running into other issues.

Hope it helps.

When everything else fails, read the instructions.

Report •

December 9, 2010 at 11:10:39
garyj it would appear you are not hitting f6 and adding the new mainboard drivers which would be why pci.sys is causing you issues.

Since you don't have a floppy you have to slipstream your xp cd [by creating a new one] with the drivers.

Web search nlite and slipstream xp for the how to and software you need to do this.

Answers are only as good as the information you provide.
How to properly post a question:

Report •

December 9, 2010 at 11:31:13
Mosaddique & Wanderer,

It was late last night when I tried the repair install and did not have a lot of time to work on other options with that attempt. When I get off work today, I will try it again with the F6 option. As for otherwise trying to fix ntoskernel or boot.ini as listed on the MS support site, that would have to be done via booting from the CD. I doubt that I could move this HD to our other PC for booting the OS, due to differences in other hardware.
If the F6 does not work as is, I will try to slipstream the CD, as it is probably only SP1. Perhaps I can do that with a flash drive, so I don't have to keep moving the disk burner from one machine to another and back.

These suggestions you listed make a lot of sense.

Report •

Ask Question