- May
- 3,515
- 5
On my WinXP SP3 system the control of the CapsLock, NumLock and ScrollLock
states by the KEYBD command is unpredictable. While repeating the same
command at least once always results in the direct indications (i.e.,
keyboard lights, and the state reported either by the _...LOCK variables or
by the KEYBD command in reporting mode) matching the specified ones, the
actual operational mode does not always match the observations. For example,
the "numlock" light may be on, but the numeric keypad is not in numeric
mode. In some cases either of the commands KEYBD /S0 or KEYBD /S1 toggles
the actual scroll state. I have not yet found a consistent, repeatable
sequence. The problem occurs just as much in 4NT versions going back to
6.02.245 as in the latest 10.00.031.
I had only recently had a need to use these options, hence had not
previously observed the issue.
--
Steve
states by the KEYBD command is unpredictable. While repeating the same
command at least once always results in the direct indications (i.e.,
keyboard lights, and the state reported either by the _...LOCK variables or
by the KEYBD command in reporting mode) matching the specified ones, the
actual operational mode does not always match the observations. For example,
the "numlock" light may be on, but the numeric keypad is not in numeric
mode. In some cases either of the commands KEYBD /S0 or KEYBD /S1 toggles
the actual scroll state. I have not yet found a consistent, repeatable
sequence. The problem occurs just as much in 4NT versions going back to
6.02.245 as in the latest 10.00.031.
I had only recently had a need to use these options, hence had not
previously observed the issue.
--
Steve