I've had a nagging problem for a long time that has just come to a head. My ASUS A7V MoBo system (purchased with WinME installed) has been working OK for four years, but at bootup the drive controllers are "not seen" by the BIOS. That is the Primary and Secondary Drive Controllers display "None" at bootup, even though they are most certainly there and the system boots normally! There are three drives in my system, all different (Ultra ATA with 80-wire cables), two on primary and one on the secondary Ultra ATA Controllers. There are also Primary and Secondary IDE Controllers (four total drive controllers!) on the MoBo, but I'm only using them to handle the CD-ROM and DVD drives I've got. No problem with those --they are seen, reported OK and work OK. I've lived with this (everything's otherwise worked!) until now that I am trying to install Win2K in the system. Not surprisingly it hangs with a Stop Code indicating there is an INACCESSIBLE_BOOT_DEVICE. When I try to load the Promise Ultra ATA drivers when prompted by the Win2K StartUp routine, they won't load because the Controller is integrated into the MoBo. I've kept BIOS and MoBo drivers up to date from ASUS, but that doesn't solve the problem. Somehow I've got to get the BIOS to report "seeing" these controllers and drives that are otherwise working fine. This has me perplexed. Any thoughts? I'll be happy to fill in any other useful details that may be necesary to work this through. TIA.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Drives/Ctlrs not "seen" in BIOS -- but work fine?! Cannot load new OS
- Thread starter jordandw
- Start date
The BIOS is reporting the onboard primary and secondary and the drives that are connected to them. This is your primary IDE controller
Not sure about the promise controllers but others that I've used require you to make a change to the controller BIOS to make the secondary controller and connections visible.
Suspect that the 2K is reporting that there are no bootable devices on the primary IDE controller. That for whatever reason it is not looking for another controller.
Ed Fair
Give the wrong symptoms, get the wrong solutions.
Not sure about the promise controllers but others that I've used require you to make a change to the controller BIOS to make the secondary controller and connections visible.
Suspect that the 2K is reporting that there are no bootable devices on the primary IDE controller. That for whatever reason it is not looking for another controller.
Ed Fair
Give the wrong symptoms, get the wrong solutions.
'When I try to load the Promise Ultra ATA drivers when prompted by the Win2K StartUp routine, they won't load because the Controller is integrated into the MoBo'
I don't understand what you mean by this. You press F6 at start of 2k install when prompted? Then later it prompts you to supply floppy with your drivers? What happens when you do this? It doesn't matter how the controller is implemented, 2k install will load ANY valid drivers and then use them as well as its own to detect devices. So if the drivers are not loading its because they are not valid 2k drivers (or the floppy is defective).
I don't understand what you mean by this. You press F6 at start of 2k install when prompted? Then later it prompts you to supply floppy with your drivers? What happens when you do this? It doesn't matter how the controller is implemented, 2k install will load ANY valid drivers and then use them as well as its own to detect devices. So if the drivers are not loading its because they are not valid 2k drivers (or the floppy is defective).
- Status
Similar threads
- Locked
- Question
- Locked
- Question