"Inaccessible Boot Device" in Win2k with addition of an SIIG PCI IDE Controller

[ran]

Well, Here I am thinking I'd like to put in a PCI IDE controller since I've got 4 devices and my only hard drive is piggy backed..slowing it down.

So, I purchased an SIIG ATA66 PCI IDE controller M#SC-PE4612

My system:

Windows 2k/Win98 dual boot (funky config, though)
Soyo 6KL MB
256MB PC133
10.2GB Western Digital HD
CDROM, CDburner, Zip drive(internal)

So, I pop this card in, and no problems with the Win98 side..everything seems to work fine, the SIIG controller installs under "SCSI" devices...but this is expected according to the manual.

*BUT* In comes our booting to Windows 2000.

At first, I wanted to just get the device installed, so I did not change my IDE configuration, leaving everything installed on the on-board IDE channels.
1. Everything looks ok in the BIOS
2. I see the PCI IDE card message, no BIOS loaded since no devices attached
3. I even get the Win2k splash screen, followed by the "Booting Windows 2000, hit F8 for menu" stuff, but right after that, I get the message:

"INACCESSIBLE BOOT DEVICE" with a Blue screen of Death (BSOD)

No matter what I try, as long as that card is plugged in, I continually get this message.

I've tried unplugging all my IDE devices and plugging my Hard drive (only one I have)into the PCI controller. Same results

I've tried disabling the onboard IDE controllers in the BIOS, but still same result.

I've upgraded the BIOS to v1.28 according to SIIG's website..but no effect.


I'm at a loss. What is happening? Why can't I "access" the boot device if in fact I can initially access it to see the Win2k splash screen and to boot up Win98 just fine.

I would greatly appreciate any and all help!

Thanks!

Randy

 

[Nevo]

Here's what happens:

The BIOS finds the first active partition and loads the partition boot sector.

The partition boot sector finds and loads ntldr.

NTLDR loads the boot start device drivers, including the disk controller driver.

NTLDR loads the kernel.

The kernel attempts to start all the device drivers that were preloaded by ntldr.

Either the disk controller driver is not starting properly, or it's not appropriate for the new controller.

Try putting the drive on the old (original) IDE controller, and editing HKLM\System\CCS\Services\NewDiskControllerDriver\Start. Set the Start parameter to 0 for the driver for the new IDE controller.

Let me know if that solves the problem.

 

[ran]

Thanks for responding. Here's a little more info:

When I put the card in a PCI slot, the system *will* initially boot up. I then get prompts to install drivers for Mass Storage Devices. Well, the drivers that are supplied or the drivers recently downloaded from SIIG's website for Win2k will **NOT** work. That is to say, the Hardware setup wizard does not recognize them as appropriate driver files for the new hardware. Now, I can go through and "install" the new hardware without assigning drivers, and I now have two "Mass Storage Devices" under the Other devices column.

Again, if I attempt to install the drivers, it *won't* work. I can install them manually, in the sense that I can choose what the hardware is and install the driver *I* think is best. However, the drivers from SIIG are for the controller, and I don't think I'm supposed to install ***two*** controller drivers. I **THINK** I'm supposed to somehow install the controller driver once for the two channels which I think are being recognized as Mass Storage Devices.

Anywho, even if I dont' install drivers or attempt to install the IDE controller drivers from SIIG, upon reboot I get the BSOD with the inaccessible boot device error message. If I take the card out, it goes away. If I switch the card to another PCI slot, I can go through the above steps, but still wind up woth the BSOD.


NEVO: in regards to your suggestion, I can find no listing for the NewDiskController\Start. I may not have it, or it may be due to the fact that I've currently got the card unplugged, so I can work in my Win2k partition.
Also, I didn't even try to switch my boot drive to the new controller initially....and I still got the BSOD.

What I think: Well, it has *something* to do with the drivers that are loaded, I guess. I'm not sure how to go about that process in a manner that will get the correct drivers loaded.
I'm guessing that I *could* just format and reinstall Win2k and in the process get the drivers installed during setup following MS's knowledgebase articles.....but obviously that is a very unattractive option. Especially right now as I've got a lot of work to do.

Well, I appreciate your response NEVO, and perhaps I can figure out how to get this thing working.....it would be nice....

 

[Nevo]

<< NEVO: in regards to your suggestion, I can find no listing for the NewDiskController\Start. >>



Replace &quot;NewDiskController&quot; with the name of the driver for your new disk controller.

The Start value indicates when the OS should start the driver. A value of 0 is boot start, 1 is system start, 2 is automatic start, 3 is demand (manual) start, and 4 is disabled.

 

[ran]

Oh, don't I feel stupid. But, as I said, I don't even see the listing for it...perhaps I may if I plug the card back in...hmmmmmm