Skip to main content
Visitor II
September 18, 2003
Question

Num Lock/Caps Lock/Scroll Lock didn't work?

  • September 18, 2003
  • 4 replies
  • 1199 views
Posted on September 18, 2003 at 13:50

Num Lock/Caps Lock/Scroll Lock didn't work?

    This topic has been closed for replies.

    4 replies

    jack1Author
    Visitor II
    September 10, 2003
    Posted on September 10, 2003 at 08:19

    Why don't the three keys working in DOS? (Num Lock/Caps Lock/Scroll Lock )

    Visitor II
    September 12, 2003
    Posted on September 12, 2003 at 08:11

    I had same problems with STPC Industrial and STPC Elite with Winbond W839 Please check attached keyboard driver for dos.

    ________________

    Attachments :

    kbd16.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HtqK&d=%2Fa%2F0X0000000aXj%2FZz5F62xSqw1JH6iLkCjN3udp67gew0KfKPAnFe4nN7E&asPdf=false
    jack1Author
    Visitor II
    September 15, 2003
    Posted on September 15, 2003 at 06:45

    Benno2:

    Thanks for your help!

    But the three keys yet were useless after run the driver(kbd16),why is that ?

    Thank you very much!

    [ This message was edited by: jackluo on 17-09-2003 06:23 ]
    Visitor II
    September 18, 2003
    Posted on September 18, 2003 at 13:50

    When you send a command to the keyboard (or the mouse), you have to wait for the acknowledge (0xFA) sent back by the keyboard, then you send the data and another acknowledge is returned. This is the keyboard protocol.

    Most software sends the data without waiting for the command acknowledge. We saw that the data is accepted by the controller, but it is really sent after the keyboard sends the acknowledge (the command’s one).

    This is not implemented in the STPC controller. We have to wait for the command acknowledge before sending the data. An interrupt is generated for each acknowledge.