🚀 go-pugleaf

In article <l8e7ubINN4ji@pollux.usc.edu> aabdalla@pollux.usc.edu (Ahmed Abd-Allah) writes:
>
>We have written a piece of software that uses a home-grown, text-mode
>windows library.  Our software drives several peripherals through 

[stuff deleted]

>Unfortunately, something is simply not working.  Our customer has the
>same software running on an IBM PS/2 with no problem.  But on the 
>above IBM-compatible, at a specific place in the code, the program
>consistently locks up.  We have gone over this area of the source 
>over and over again, and we can see nothing wrong till now.  Our
>guess at this point is that it is a hardware related problem - something
>is just not compatible.  Can anyone give us a hand?

To all of you who sent me email trying to help, I'd like to thank you.
In the end, the problem which caused us so much grief and worry, and
which made us examine the software more than three times, and in general
totally befuddled us turned out to be: The customer's keyboard was faulty!
He is now running the original software, and no failures have been
reported...

Sigh...
AAA