Disk Hardware Configuration Error!

[arthmx]

Hi people I really need help !

When the setup of Windows Server 2003 Standard finished copying files after it reboots , and When In the boot loader it load the next step of installation it says to me :

"Windows could not start because of a computer disk hardware configuration problem.

Could not read from the selected boot disk. Check boot path and disk hardware.

Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information. "

I already tryed bootcfg , fixboot , fixmbr , copying ntdetect.com , copying ntldr , and a chkdisk

Thanks to you :S

[fdv]

Allright. First, are you sure you have valid CD media with no errors on the CD?

Suppose the CD is fine, no scratches, no errors.

This can be the result of an error on the disk in the first sectors of the drive. Test the drive with a more reliable tool than chkdsk, using a PE CD.

Say the drive turns out fine too.

Then, it's possible that some oddball situation is happening where Windows is failing to load a driver to see a drive because of, say, a faulty integrated SATA driver, doesn't see the SATA drive, and so gave you that message.

But say you didn't integrate any drivers.

Examine the BOOT.INI file for invalid entries. Do this using a PE CD, such as maybe Ultimate Boot CD 4 Windows.

There are a lot of variables. Reply with info about your hardware and SP and patch level (in case someone wants to know that too).

Edited May 19, 2008 by fdv

[arthmx]

Thanks for your answer!

My PC configuration is :

640mb of RAM

Pentium III

Maxtor STM3320820A (ATA) with 3 partition

C: Windows XP

D: Miscellaneous

E: Server2003

I actually downloading UBCD but it's big , another software for scanning disk?

EDIT : I maybe can rewrite the partition table with testdisk?

Edited May 19, 2008 by arthmx

[fdv]

I maybe can rewrite the partition table with testdisk?

I don't think that will help. Looking at the fact that you've XP and 2003 on different drives, I am suspecting more an invalid BOOT.INI entry. Try editing that (using the PE) and see if that doesn't do the trick.