Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.14 $; site siemens.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!siemens!jrv
From: jrv@siemens.UUCP
Newsgroups: net.micro.pc
Subject: Re: READING PC/XT KEYPAD
Message-ID: <23900022@siemens.UUCP>
Date: Wed, 4-Jun-86 10:06:00 EDT
Article-I.D.: siemens.23900022
Posted: Wed Jun  4 10:06:00 1986
Date-Received: Sat, 7-Jun-86 04:26:52 EDT
References: <728@tekcbi.UUCP>
Lines: 20
Nf-ID: #R:tekcbi:-72800:siemens:23900022:000:900
Nf-From: siemens!jrv    Jun  4 10:06:00 1986




Whether you use DOS calls or ROM BIOS (Int 16) calls you are *not* going
to get anything for the "5" key on numeric pad unless the key pad is in
numeric mode. The ROM BIOS keyboard interrupt handler prevents this. A
make/break code is sent from the keyboard but nothing gets put into the
ROM BIOS keyboard buffer. To get this information you will have intercept
the keyboard interrupt (Int 9) and handle scan codes directly. I have done
this and used the ROM BIOS interrupt service to process all those scan
codes which were not of special interest. Then use the original Int 16
routine to get the processed codes from the ROM BIOS keyboard buffer. This
data along with my processing of the special scan codes went into my
own keyboard buffer for access by a new Int 16 routine.


Jim Vallino
Siemens Research and Technology Lab.
Princeton, NJ
{allegra,ihnp4,seismo,philabs}!princeton!siemens!jrv