Help! Built new box!

Thanks2C

Member
May 10, 2001
112
0
0
Hey all!

I just built a new box, but for some reason when I try to install Windows on it I get the UMOUNTABLE_BOOT_VOLUME error in the XP setup. Here's the specs:

AMD Duron 1.3GHz
Soyo SY-K7ADA
256 Kingston DDR RAM
Using a temp 8mb video card
IBM 75GXP 41GB HD
Standard Floppy & CDROM


Any ideas on why I could be getting this error? I've tried getting this to work for countless hours yesterday and stil no luck at all. I keep getting the same damn error! Any help would be grealy appreciated. Thanks!
 

Jeff H

Golden Member
Oct 11, 1999
1,611
4
81
Thanks2C, I did a Google search and first ended up on a Compaq site. It referred me to an MS KB, Q315403. Read down the KB article a ways and there's a link to a patch. Here's another KB article, Q297185 that likely also addresses your issue. Good luck!

EDIT: Here's one more link that discusses the fix in English.
 

Thanks2C

Member
May 10, 2001
112
0
0
Thanks a ton!

I didn't try that one command to do. However keep in mind that I'm installing a complete new copy of Windows, not an upgrade. It's a completely brand new harddrive. Will that command that's on those pages still work??

Any other suggestions as well?
 

Thanks2C

Member
May 10, 2001
112
0
0
As far as the patch goes, I need to have Windows installed to actually to actually install the patch, right? So there's really no point to it right?
 

spinner

Junior Member
May 15, 2002
10
0
0
This might seem like a goofy question, but it sounds like you did'nt fdisk your new hdd and created a partion on it. If you havent you should try that. If you have i dont really have a clue whats wrong :)
 

acejj26

Senior member
Dec 15, 1999
886
0
0
spinner...if he's installing XP on a fresh disk, the setup will do that for him

i got the same error two days ago on my IBM hard drive....but my computer was set up and running perfectly....it froze, i rebooted, and it kept coming up with the error message you're getting. now, i managed to do an XP install on a previously unused partition of the drive, but the drive sounds like it's dying now. my new seagate drive will be here today.

i don't know what caused the problem, but i do know that i'm not running my computer off that drive anymore, and coupled with all the reports online about faulty IBM drives, i'll never buy another IBM drive again

my suggestion....return said drive, and pick up a Seagate drive
 

Thanks2C

Member
May 10, 2001
112
0
0
I did try doing fdisk and creating a partition as well, although XP will do it for you.

I did try putting in an old HD as well to see if the HD was bad, but I got the same error with both, so I don't thinkt that's the problem
 

Thanks2C

Member
May 10, 2001
112
0
0
So is doing chkdsk /p my best chance to get this thing to work? Nothing else? I just built this box, I need it to work!! :)
 

Thanks2C

Member
May 10, 2001
112
0
0
OK, well, no matter what I did I couldn't get it to work, I've gotten about 10 errors, so I RMAed the motherboard and the CPU.

Instead of the Soyo I'm getting the EPOX EP-8KHAL VIA KT266A CHIPSET ULTRA ATA100 ATX FORM FACTOR 1xAGP(4X)/5xPCI/3xDDR W/AC97 AUDIO with the same AMD Duron 1.3GHz CPU. Now, this *SHOULD* all work currectly with Windows XP, right?

I also have a 256 Kingston DDR RAM PC2100 RAM and IBM 40.0GB 60GXP 8.5MS 7200RPM IC35L040 [07N6654] UATA-100 HDD. Now, this should all work together, right? I dunno what went wrong before, I'm suspecting that the motherboard was bad or something. This needs to work, no more RMAs...hehe :D
 

acejj26

Senior member
Dec 15, 1999
886
0
0
i still say it's a crappy IBM hard drive.....if you get your new board and proc and it still comes up with that error, send that drive back and pick up a Seagate or Maxtor