Bob, at 08:39 on Aug 08 1996, you wrote to Bill Grimsley...

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? :)

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

Even trying to load just that one driver on its own failed, so there is now
no doubt that the driver itself was simply very poorly written (maybe it's
one of Paul Edwards' more recent efforts).  :)

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

At one stage, I had just that one driver in config.sys, and no autoexec.bat
(not that that was relevant, as the PC hung long before autoexec was
processed anyway), and it still refused to install.  It has since
transpired that other people have had problems with that particular driver,
and replacing it with a different ATAPI driver immediately solved the
problem.

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

No need, there were no IRQ conflicts, nor anything like that at all.  Just
a shitty driver, which has now been replaced (and works perfectly).

Regards, Bill
@EOT:

--- MsgedSQ/2 3.50