Inaccesible Boot Device on ECS - K7VZA

MrCraphead

Platinum Member
Sep 20, 2000
2,977
0
76
I just put in a new motherboard and AMD CPU for my friend's computer, using an ECS K7VZA as the motherboard. After hooking everything up, and configuring the BIOS, the computer came to a blue screen while loading Win2K, saying that it was an inaccessible boot device.

My hypothesis is that the mobo and the HD aren't exactly communicating properly b/c the OS does not have the VIA4in1 drivers for the onboard ATA/100, since his previous mobo was a 440BX chipset.

If this is the case, how would I get the ATA/100 drivers to the OS, if I can't even boot into it?

And if that's not the problem, what is?
 

Pederv

Golden Member
May 13, 2000
1,903
0
0
Did you boot from the cd, when you get this message? If so have you tried disabling UDMA for the cd in the bios? Is this happening when you're trying to boot for the first time? If so, is the system properly recognizing the HD? Or did you just swap everything over and have the OS still on the HD from his old MB? If so start in safe mode and delete the ENUM key from the registry
 

MrCraphead

Platinum Member
Sep 20, 2000
2,977
0
76
<<Did you boot from the cd, when you get this message?>>

No, this message was received when booting from the HD

<<Is this happening when you're trying to boot for the first time? If so, is the system properly recognizing the HD?>>

Yeah, it's happening when I'm booting for the first time with the new mobo, and yes the computer is correctly recognizing the drive on boot up.

<<did you just swap everything over and have the OS still on the HD from his old MB? If so start in safe mode and delete the ENUM key from the registry>>

Yes, this is the SAME HD and OS from his OLD mobo. I cannot get into safe mode, it gives me the same blue screen.
 

Pederv

Golden Member
May 13, 2000
1,903
0
0
When changing motherboards all sorts of hardware is reassigned, especially when a chipset change is taking place also. Try booting from the win2k cd and doing a repair. The alternatives are to put the old motherboard in so you can delete the enum key, or re-installing from scratch. Someone else may have a couple more things to try, so don't go postal on the system yet.