Spooky keyboard behaviour

Question

This probably doesn't belong in the programming forum, but I'm interested in finding out if someone has had a similar problem. I have installed my app at a client site. The app is run on 9 machines. 7 of the 9 operate fine, but on two of the machines I have strange keyboard behaviour.
Ocasionally the app will stop erwsponding to the keyboard, but will still respond to the mouse and still paints ok. Restarting the app doesn't help. But, if the user opens MS Word, types a few chars and then restarts my app, it operates normally.
One of the machines is a laptop running WinXP home and the other is a Desktop running Win98.
I am using JRE 1.4.2_05 as the runtime and Swing for the UI components.
The only parts of my code I can think of that may interfere with keyboard processing are:
I have a KeyEventPostProcessor which checks for the escape key nad arrow keys
I also have an event processor which looks like this:
     private static final class EventProcessor extends EventQueue {
          public EventProcessor() {
          protected void dispatchEvent(final AWTEvent evt) {
               try {
                    super.dispatchEvent(evt);
               catch (Exception e) {
                    // Catch any uncaught AWT Exceptions
                    try {
                         MedEDI.showException(e);
                    catch (Exception ignored) {     
                    getInstance().shutdown();
     }I'm completely foxed as I cannot recreate this in my development environment. Has anyone else come across a similar issue?
Graeme

Answer 1

Some possibilities:
1. Dirt under the keysIt is only my app (the only java app on the system) that has this trouble, which makes it unlikely that dirt is causing the problem. At one stage I thought that it might be a USB keyboard or keyboard driver problem, but given that one of them is a laptop with XP and the other is a desktop with 98, this seems unlikely too. Especially seeing that the other 8 terminals are all the same hardware and setup as the desktop.
2. Badly-programmed spyware installedNever thought of that. Might not be the problem, but what the hey, it's worth a try. I'll have them check for spyware on Monday and I'll let you know how it turns out.
Graeme