🚀 go-pugleaf

After three days of tracking what I believed was the nastiest bug known to man,
I finally ended up calling Borland Tech Support.  Here was the situation:

I am writing an event-driven windowing system (sort of like D-flat if you read
Dr. Dobbs).  Part of the event system installs my own mouse handler using
int 0x33.  Anyway, every now and then when I am: A.) In the IDE, B.) Using my
mouse, and C.) Debugging a program I get a "GP at xx xx xx xx" with a 
"System halted: kernel cannot be loaded" or something like that.

I, being a C programmer, assumed that it was a pointer problem.  After checking
my code for eons I finally broke down and called tech support.  There a nice
gentleman informed of the following:

1.  There is no bug list from Borland.
2.  There is a problem using a mouse with BCX.  This meant ME.  However, he
added that I shouldn't rule out a pointer problem.
3.  There will be another patch disk, but God knows when.
4.  There have been some problems with MOUSE.COM 7.04.

It seems that Mouse drivers in general have a bad time with BCX because BCX is
not polite in its context switching and sometimes non existent interrupts
or vectors are executed (whoops).

Anyway, this is to save anyone else some grief.

Brian