Hi Brenton,
            I don't think *anyone* understands serial comms!

  My reference material is the Pacal comm.SWAG, which has snippets and
large lumps of code to do with things serial, and the more code I
read, the more obvious it is that these fuckwits don't jave a clue!

  I wanted to identify what sort of UART (8250, 16450, 16550) and to
save me the trouble of nutting it all out from basics I copied some
code from a Dutchman. The Dutch seem to be very large in Pascal and
this guy had the cheek to say "call me" if I wanted to use his code
commercially. ROFL! Fat chance, either way. 

  I ran it, and it identified the UARTs correctly but it removed the
mouse! In the biggest possible way! I had to switch off and start
again to get the mouse back. Vale mousey.

  So I had a closer look at the code... the guy is a fuckwit. He does
everything twice and most of it for no reason at all. He writes values
to the MSR read-only register! He's crazy! It's obvious that he copied
it off someone else and claimed it for his own without understanding
any of it... and I still can't see why it makes my mouse disappear. I
was hoping to see how an "expert" did it... and now I know.

  Christ almighty! I have six separate versions of COM programs,
fossils and bits and pieces, and none of them work! One guy disables
intererupts on every second line and the next doesn't bother at all!
ROFL!!  They just do not have a clue! I'm beginning to think there's
only you and me... and I'm not too sure about me.

...[later]

  Well, I nutted it out myself and it's all rather simple and I've
still got a mouse. The silly bastard was setting a whole lot of
useless shit that only confused poor mousey. Microsoft strikes back! 

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

---