unmountable_boot_volume with known-good HD

[xenocidebrm]

This is my second build and I'm a little confused. I can get Win Server 2k3 to load, but not Windows XP Pro, or Pro CE, or Pro with SP2. I've tried with several disks and nothing has changed. I know that the HD is good because I've loaded and run a couple things when I had Server ed. running. When I checked the M$ knowledge base, they said something about -
"(You maybe be having this problem because) Your computer uses an Ultra Direct Memory Access (UDMA) hard disk controller, and the following conditions are true:
You use a standard 40-wire connector cable to connect the UDMA drive to the controller instead of the required 80-wire, 40-pin cable.
The basic input/output system (BIOS) settings are configured to force the faster UDMA modes."



Venice AMD 64 3000+
TUL XPRESS 200P Mobo
2x WINTEC 512 D400
Apollo 6600GT PCIE
Seagate 120 GB HD
Rosewill Silver Case

[Statica]

Have you tried loading up the SATA drivers during the blue stage install of XP. It might be the reason why XP is not able to recognize them while Server 2k3 (a newer OS) is.
The SATA drivers are here: ftp://driver1.cptech.com.tw/driver/a...%20utility.zip
From the page: http://www.tul.com.tw/Global/driver.aspx?folderid=2

[faulkner132]

Is the drive a Basic or Dynamic disk? If it is Dynamic, you won't be able to load any other OS without first reformatting it. Check under your Disk Management.

[xenocidebrm]

I don't know about basic or dynamic drives, but I reformat every time that I try to install, Faulkner.

I'm trying the SATA drivers now, despite the fact that I'm not using SATA.

Updates in a few.

--EDIT--

Not working, can't get SATA drivers on my system - I think it's irrelevent anyhow.

[faulkner132]

What I am saying is if after you installed 2003, if you upgraded the disk to a "Dynamic Disk" through Disk Management, you will not be able to load another OS in addition to 2003.

[xenocidebrm]

bump.

I know that everyone is helping out of the goodness of their hearts and beggars can't be choosers, but I've gotta go back to college soon, and I'll leave this incomplete with a customer if I can't get it to work. I mean, I can leave them with server 2k3, but I'd rather not. Anyway, thanks for all the help, you guys are awesome.

[faulkner132]

Try 0-writing the drive using the hard drive diagnositics. You can download the utilities to do this from the manufacturer's website. This will completely erase anything on the disk and truely give you a clean HD.

[stylin19]

The MS article recommends trying the chkdsk /r.
Did you try it ? everything else being equal ( good HD other OS's ok), the install must be getting whacked.

BIOS CMOS setup - set CDRom as 1st boot device and save.

Use the XP cd to boot and when you see the Welcome to setup press the letter R
You will get a dos prompt
Then type "chkdsk /p" without the quotes and hit enter
When that is done type "fixboot" and hit enter
"Y" and enter at the prompt
Then type "exit" and hit enter
The system SHOULD boot into Windows

If that don't work for you, you can boot to the recovery console like above and...
Type "chkdsk /r" then enter
When done type "exit" and hit enter.
This will take longer, but the system should boot back into Windows.

not much...good luck

[xenocidebrm]

stylin, good find, although unfortunately I've already tried it...

I'm left to conclude that I was wrong and that there is bad hardware in there somewhere - however, when I delivered the computer to my client, and showed him the server 2k3 to "workstation" 2k3 conversion, he was more than satisfied. So I have put aside the problem until later.

Thank you all for your generous help.