If you have joy with C:\ drive you should be able to go into "add new hardware" and add the cd-rom drives. Another way is to just put the OS' CD into the drive and toggle the Bios to boot from the cd-rom drive first. Q: Are the drives showing up at Post? If not, have you been under the hood lately to cause a hardware problem. And, if they are not listed at Post, have the Bios re-detect the drives. Hope this helps.
I had a similar condition with mine but only had 1 CD. I had both HD's on the primary controller and the CD-Rom on the secondary= no CD. I put the CD as slave on the primary and everything worked fine. You might try switching them around to see if you find a combo that works. Hope that helps.
After you clear up the drive problem, you might want to consider copying your OS' cab files to your HDD. It saves hunting for your cd-rom every time the OS asks for it, or in this case, all the drivers files would be on C:\. Just a suggestion.
my cab files are already on my HDD, but i dont see how thats going to help me get win98 to recognize the drives.
i tried recognizing them in the BIOS but nothing is showing up.
i ran the setup file for the Burner (its drivers were on a floppy) and it showed it but whenever i tried to open the drive, it would just show an empty window, even when i had a cd with files on it in the drive. this is really not making sense
You shouldn't see anything in the BIOS (like if you were using the auto-detect option for IDE HDDs) but did you set the Primary/Slave to AUTO-Detect on boot-up? If they don't show up at POST then there's something wrong with the IDE channels, if they do, then there's probably something wrong with the OS.
well, i have an Ultra ATA/66 controller, 3 hard drives are plugged into that, the CD Roms are on an IDE cable into the Primary IDE on the Mobo, Nothing shows up in BIos, and it is on Auto Detect All
Train,
I asked you if it was a Creative CD because the Abit boards have trouble recognising the Creative CD ROMS(48x drives). I have had this problem with four or five machines. Upgrading to the latest BIOS seems to have fixed this problem. Goog luck.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.