Rod, at 12:59 on Aug 04 1996, you wrote to Bill Grimsley...

BG> Does anybody have any idea why my DOS CD-ROM driver CR_ATAPI.SYS
BG> refuses to load on this Triton II 430VX board (Cx6x86/120 CPU) ? 
BG> Win95 and OS/2 both perform perfectly, but if I attempt to boot
BG> native MS-DOS, the system halts with a Divide Overflow, and its
BG> definitely the CD-ROM driver at fault.

RS> Do you get that with JUST the driver in the CONFIG.SYS and deliberately
RS> not loading any MSCDEX at all just to prove that it is the driver itself ?

MSCDEX is installed from autoexec.bat, and the system hangs long before
then.  In fact, stepping through each line of config.sys works fine until I
get to CR_ATAPI.SYS, then it locks solid with the Divide Overflow message. 
Haven't tried JUST that driver on its own though, but will later today.

Later:  No joy, that driver flatly refuses to load under any circumstances.

RS> I have seen an occasional weirdness actually caused by
RS> particular versions of MSCDEX in some hardware combinations.

It definitely isn't that, as autoexec.bat is not even processed.

RS> The other approach is to just use a different DOS CDROM
RS> driver, once you move to ATAPI CDROMS they normally dont give
RS> a damn about the fine detail of the particular CDROM drive.

Might be worth a try.  I've grabbed the very latest drivers from Edge, but
the same thing is still happening.  Funny thing is that both Win95 and OS/2
work just fine (just as well, as I don't need to use native MS-DOS 6.22
anyway).

Regards, Bill
@EOT:

--- MsgedSQ/2 3.50