Xref: utzoo comp.sys.ibm.pc.programmer:1774 alt.msdos.programmer:1713
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!rpi!sci.ccny.cuny.edu!cucard!dasys1!cooper!phri!cmcl2!yale!think!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!husc6!wjh12!djb
From: djb@wjh12.harvard.edu (David J. Birnbaum)
Newsgroups: comp.sys.ibm.pc.programmer,alt.msdos.programmer
Subject: checking the kb shift status
Message-ID: <477@wjh12.harvard.edu>
Date: 3 Jun 90 11:56:53 GMT
Reply-To: djb@wjh12.UUCP (David J. Birnbaum)
Distribution: na
Organization: Harvard University, Cambridge MA
Lines: 18

Programs that monitor the keyboard status (such as tsr that
use ctrl+shift as a hotkey) seem to read the keyboard status
in one of two ways.  Some check 0:0147, while others use
function 2 of int 16h (which apparently does the same thing
for you).  Is one method better?  Is one better for certain
types of applications?

Please respond by email.  I will post a summary.

Thanks,

David


============================================================
David J. Birnbaum         djb@wjh12.harvard.edu [Internet]
                          djb@harvunxw.bitnet   [Bitnet]
============================================================