Another section of the same Global Event Queue shows that multiple
devices reported events to this queue. Below we see that those
events include: VDisplay, Keyboard, Andisplay, and Tone events.
Similar to the VDisplay events described in the last section,
Andisplay events contain a millisecond time, time-of-day, sequence
number, a starting offset, a length and a display string.
Tone events include frequency and duration.
Keyboard events contain a scancode, function code and a text label.
Scancode are hardware defined.
When the InSight Dump Formatter first encounters a Keyboard event
it attempts to connect to the MIB to resolve the scancode and get
the corresponding function code and key text label. For more
information see
Using the InSight
Dump Formatter.
In the example shown below the highlighted section shows that the
InSight Dump Formatter was able to connect to the MIB and retrieve
the corresponding function code of 76 and key label text of
“Signon” for the scan code x20. If the connection to the MIB had
failed, the KeyBd events are still formatted, however the fCode
will be ‘0’ and text will be blank.
Converted from CHM to HTML with chm2web Pro 2.85 (unicode) |