"Inaccessible Boot Device" - Stop error - win2k

godot

Member
Sep 6, 2000
25
0
0
i have two HDDs, one with windows 2000 installed on the
5th partition ( a logic partition)of the primary master
IDE drive.
on primary IDE, i have 1.6GB fat 16
400MB fat 15
128MB Linux Swap
2G Linux
2GB NTFS ( windows 2000)
4GB NTFS

Primary Slave IDE drive has only one partition with size
8GB.

after i changed my MB and CPU, i tried to boot it up,
i got an error message saying that "Inaccessible Boot Device"
windows 2000 reminds me to check virus, disconnect new IDE
device, CHKDSK /f blah blah. I disconnect primary slave
drive
and still got the same message. I boot it up with a
Windows 98
disk and can't see the NTFS partitions.

i installed NTFS under win98 but since i can't specify
the NTFS driver files, i still can't see the NTFS partitions.

there is a previous thread about this, but it doesn't seem
to help. :-(

What shall i do now to make it boot to win2k?

THanks a lot
 

godot

Member
Sep 6, 2000
25
0
0
rocmonster :

The old MB is P2B and i broke it when trying to
hook it up with a Copp 750 and

The MB i'm using is Asus P3V4X, bios version 1005

HDDs are : quantum 13.6GB ATA66 for primary master and
WD 8.4GB for primary slave

Thanks

 

rocmonster

Golden Member
Oct 9, 1999
1,669
0
0
Usually ATA66 contollers and win2k don't play nice together. Try to find comaptable ATA66 drivers that work with win2k for your board (my suggestion comes from troubles I had earlier in the year with Highpoint ATA66 controllers and win2k, before I fixed the problem with workable drivers, I would get the same "inaccessable boot device error" message). Hopefully someone with your MB can expand on the problem :)

good luck
 

rocmonster

Golden Member
Oct 9, 1999
1,669
0
0
Try booting up with your hard drives connected to the regular IDE (non ATA) channel (all ATA66 drives are ATA33 backwards complient), install the new ATA66 controller drivers (you can go to the device manager, click on the "scsi device" icon (which when expanded should have two yellow '!' next to them so you have to do this twice), choose properties, choose "update driver"), shut down, switch the HD's from the regular IDE channel to the ATA66 input, reboot and win2k should detect your hard drives and all should be good.
 

slipperyslope

Banned
Oct 10, 1999
1,622
0
0
Actually it is just that win2k doesnt like having a motherboard changed on it. I believe it has to do with the way it handles hardware. I have seen many people complain about this problem.

I got the exact same thing when i switched to my Abit Kt7. All i could do was reinstall win2k.

Jim
 

Shudder

Platinum Member
May 5, 2000
2,256
0
0
At least you're getting a message. I took out my Gigabyte 7IXE and put in a MSI k7T and although it would start to boot, right before it got to the splash screen it would just reboot. Maybe it's because I have it set to reboot on errors automatically, but I just reinstalled Win2k (No biggie these days..) and all is fine now.
 

imhotepmp

Golden Member
Mar 23, 2000
1,418
0
76
Exactly what shudder and slipperyslope were saying. Ive had this happen to me several times. It seems like Win2k despises being switched to a different mb. However i usually get the message"NTldr is missing" The best thing to do if you have to change the mb again, boot up into safe mode in win2k and remove EVERYTHING from the device manager. Theres bound to be one or two things that will not be removed but those should be fine. Take it out and out it into the other board. On boot up it should redetect all the hardware again. This worked for me.


imhotepmp