Keystroke Capture

[Condon Thomas A KPWA]

> > One could run ``script'' which captures everything to a file.
> 
> Or expect, which is surely already installed. You can even 
> play it back
> to see if it is repeatable. Provided the codes make it out of 
> the kernel.
> If there is a lockup, then a user-level app may be too late 
> in the chain to
> tell very much. Have you checked for debugging options on the kernel
> keyboard stuff? Don't know if there is any, but you mey gety 
> lucky. Does
> this heppen in X or in console mode? And, what exactly gets locked up?

The system uses a Rose Box (KVM switching) to select which of the processors
to display and access.  The method of selection is to hit L-Shift, L-CTRL,
n, individually, where "n" is the CPU number (4 of them) to select.
*Sometimes* after performing this the image will shift to the selected CPU
but the keyboard will provide no more input that the system can see.  The
keyboard that causes the trouble is an "Orbit" keyboard.  We see the problem
whether running Linux or WinNT on the system, but more often (as would be
expected) with WinNT.  Since the Rose Box intercepts the keystrokes, I'm not
sure whether a user-level app will work, either.

Thanks for the suggestions of apps that may work, though.


In Harmony's Way, and In A Chord,

Tom  :-})

Thomas A. Condon
Barbershop Bass Singer
Registered Linux User #154358