Hi Brenton,
            I'm still playing with comms, uarts, interrupts and stuff
like that... jeeze!

  I finally found out why the dickhead's program was eating my mouse:
if you do a loopback test in Windows it generates an interrupt that
goes wrong. It's Windows doing it as much as the program; an evil
partnership like sex and drugs without the rock 'n' roll.

  But like Tim Shaw, there is more...

  I have to disable the mouse IRQ in the PIC and then put it back when
I'm done. I started out trying to find out what IRQs the com ports
were using, but before I can do that I need to find out what IRQ the
mouse is using! ROFL!!! The bloke who thought up this system is my
kinda guy! There are layers upon layers of lunacy.

BTW, I found out what you meant when you told me to back everything
up. I accidentally removed all the interrupts and the whole thing
stopped! ROFL!! Except Windows. It just kept on truckin'... too stupid
to realise it was running on empty.

... [later]

  How disappointing. Int(33.24) actually tells me the mouse IRQ, and
it got it right, too. Someone has seriously stuffed up.

  But I guess you'll tell me that it can't be trusted anyway... I'm
beginning to fall in love with my PC.

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

---