Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!brazeau.ucs.ualberta.ca!unixg.ubc.ca!ubc-cs!uw-beaver!zephyr.ens.tek.com!vice!bobb
From: bobb@vice.ICO.TEK.COM (Bob Beauchaine)
Newsgroups: comp.lang.pascal
Subject: Re: Interrupt 9 Processing
Message-ID: <7681@vice.ICO.TEK.COM>
Date: 28 Jun 91 16:08:55 GMT
References: <27309@adm.brl.mil> <1991Jun27.234613.6472@ux1.cso.uiuc.edu>
Reply-To: bobb@vice.ICO.TEK.COM (Bob Beauchaine)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 32

In article <1991Jun27.234613.6472@ux1.cso.uiuc.edu> amead@s.psych.uiuc.edu (alan mead) writes:
> [stuff, mostly correct, about keyboard processing]

>So, to capture each key and especially to "trick" the computer, you
>will need to install your own INT 09 handler.  But if you don't want to
>write your own, the code from a Turbo Technix article used to be
>available by anon FTP.  I didn't see any familiar names on GArbo or
>Wustl, but the package below at wuarchive.wustl.edu might be useful, or
>I could make the above package available to a FTP site.
>
  IMHO, the only time that you need to actually trap the interrupt 9
  vector is when you want to 
   1.  Trap the shift,alt,ctrl,caps,or numlock keys BY THEMSELVES or
   2.  You want to keep a key press from reaching another application
       that might be running, like when you press the hot key for 
       a TSR.

   At almost all other times, you can get the same functionality by
   using the BIOS interrupt $16 and monitoring the keyboard status byte
   in low memory.  Far,far simpler, and probably more portable.  I have
   an interrupt 9 handler written in TP, and I never use it except in
   TSR's.

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ 

Bob Beauchaine bobb@vice.ICO.TEK.COM 

C: The language that combines the power of assembly language with the 
   flexibility of assembly language.

   "It seems that the less a statesman amounts to, the more he appears
   to love the flag".