Name: brander Date: August 11, 2006 at 23:22:00 Pacific Subject: new mobo DOS OS: Real DOS from Win98 CPU/Ram: 3.0G/2G Model/Manufacturer: Home made
Comment:
There seems to be no support for DOS CDRom drivers on my new Gigabyte 965-DS3 board. It will boot to DOS fine with a bootable CD but all cd drivers(ie oakcdrom.sys)then report that there is no cd drive on the system. There is no support for DOS from Intel or Gigabyte, so I wonder if anyone has another solution. The PATA disk controller is made by JMicron who also do not support DOS.
Simple, here it is: DEVICE=HIMEM.SYS DEVICE=OAKCDROM.SYS /D:MSCD001 COUNTRY=044,850,COUNTRY.SYS This is the config.sys from the boot image on the CD(or the floppy I made it from). Yes it boots to drive A(and the floppy becomes drive B) but it always says no CDrom drives found and I have tried about 100 other ones instead of OAKCDROM and they all say the same thing. I haven`t put autoexec.bat here as it is irrelevant if the above driver does not find a CD drive.
I have tried many drives too, all of which normally work, but I think the culprit here is the Jmicron disk controller which just does not seem to support drives in DOS.
Aside from CDroms, I agree the last "official" DOS release was 6.22, but if you transfer the system from Win98 and use the files in its |command folder you get a very good DOS which supports FAT32 and does everything that 6.22 does except defrag.
Thanks for the info Dosser, I tried QCDROM and QHimem bit it still says no CD/DVD drives on system. I really think that the ide controller maker has just dropped any DOS support because it works fine in XP and I have tried just about everything now. There are no bios settings for the controller other than on/off.
Conversely, a USB pendrive works fine in DOS without any drivers loaded. It becomes the B: drive which is nice.
The driver download page for that motherboard says it doesn't support 9X or ME. It doesn't mention dos but that may be implied.
Under the SATA driver download is this message, '. . .press F6 during Windows setup to read from floppy'. The manual may explain that in more detail but possibly hitting F6 prevents built-in SATA drivers from loading, thereby allowing a bootdisk to see the cdrom.
MS-DOS works at a lower level than Windows therefore usually IDe controller drivers are not required, even some older PC's with on-board SCSI would work without drivers.
I do appreciate that NT4/W9x support has been dropped from Motherboard Chipsets. Is there any settings under the Optical Drive Listing in BIOS to change the mode usually available are PIO and DMA !
I have tried that driver for using with F6 while installing Windows, but those are 32-bit drivers and are anyway only for the built-in Intel SATA controller and then only if using RAID or hot-swap drives.
I am now wondering when SATA CDrom drives will arrive and then will they work with our old DOS drivers.
Thanks Petit Jean, but the eltorito driver says the same as all the other ones: no CDrom drive found despite the fact that bootable cdroms boot up fine to the A drive.
Hmm... I am having the exact same problem- new Gigabyte board that's not able to load any cdrom drivers.
What I've tried so far is swapping between multiple optical drives, usually with no hard drive attached at all, and updated the firmware on all of them.
Brander, one of the other things I tested was using a PATA>SATA cable converter. Sorry to say, I don't think you're going to have any better success with a drive that's natively SATA.
I'm still looking around for a solution, the system obviously reads the CD well enough to boot, so there has to be a way to hook back into it afterward- Er, right?
Dear all, the same problem...!!!! I'm sure the problem is on the new SATA Controller thet does not support IDE under dos. please can someone tell me where to find the gcdrom.sys driver. The above link does not work and i can't find sth on gigabyte site.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE