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

 BL> Try changing the order you load things in config.sys... or load
 BL> it high, or something.

 BG> Tried all of that, still no good. Next suggestion, please? :)

  When I was fiddling with my CD-ROM using two I/O cards and mixed
addresses and IRQs I got a few Divide Overflows that sometimes worked
okay and then failed when I ran MSD or Norton or something that 
accessed the BIOS directly. There is something fundamentally wrong 
with the PC that lets it sort-of work when it should fail.

  Most of it was associated with the bloody mouse, and the second-hand
VESA card that didn't *really* disable the floppy driver. My guess is
that you have something wrong with your IRQs and addresses but Win95
and OS/2 handle it.... and so does DOS until the CD driver wants a
share.

  How about moving the mouse onto another port? Or the CD? Does your
CD driver let you use another IRQ?

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---