Inaccessible_boot_device with new mobo - no IDE driver?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I just replaced an old motherboard (ECS K7VZA - Via KT133 board) with a newer
one (Biostar M7NCG-400 nforce2). I figured that I could then boot off of my
Win2k CD and then install the nforce2 drivers. POST is fine and it starts to
load Win2k, but then gives BSOD with INACCESSIBLE_BOOT_DEVICE error. I'm
guessing that this means that Win2k has no idea what to do with the new IDE
controller and can't communicate with either the HD or CD? (By the way,
Knoppix linux-live boots and runs fine off of the CD, so I think I know that
there is no actual hardware problem.)

The only thing that I can think of to do at this point is to yank the new
mobo, restore the old mobo, boot Win2k, try to install the nforce2 IDE driver
(but how?), then shut down and put in the new nforce2 mobo again. Don't know
if this is possible or if it would work. Or is there something that I can do
w/o having to swap back to the old mobo first?
 
mc510 said:
I just replaced an old motherboard (ECS K7VZA - Via KT133 board) with a newer
one (Biostar M7NCG-400 nforce2). I figured that I could then boot off of my
Win2k CD and then install the nforce2 drivers. POST is fine and it starts to
load Win2k, but then gives BSOD with INACCESSIBLE_BOOT_DEVICE error. I'm
guessing that this means that Win2k has no idea what to do with the new IDE
controller and can't communicate with either the HD or CD? (By the way,
Knoppix linux-live boots and runs fine off of the CD, so I think I know that
there is no actual hardware problem.)

The only thing that I can think of to do at this point is to yank the new
mobo, restore the old mobo, boot Win2k, try to install the nforce2 IDE driver
(but how?), then shut down and put in the new nforce2 mobo again. Don't know
if this is possible or if it would work. Or is there something that I can do
w/o having to swap back to the old mobo first?
Click to expand...

Your guess is correct. The usual cure is pretty much what you
suggest, except that it is usually sufficient to replace the specific
driver for the Master IDE Controller with the generic Microsoft
driver.
 
As an aside, I just replaced a v.old gigabyte mobo with an Asus nforce3
mobo, also replaced cpu and memory.
To my surprise win2k booted normally and found new hardware eg nforce
chipset drivers, which I installed from the mobo cd.
Even though all appears OK I guess I ought to run a win2k repair.
 
Lucky you!


DL said:
As an aside, I just replaced a v.old gigabyte mobo with an Asus nforce3
mobo, also replaced cpu and memory.
To my surprise win2k booted normally and found new hardware eg nforce
chipset drivers, which I installed from the mobo cd.
Even though all appears OK I guess I ought to run a win2k repair.
Click to expand...
 
Back
Top