From: Endlisnis <s257m AT unb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Keyboard handler problem
Date: Sat, 12 Sep 1998 13:29:39 -0300
Organization: NBTel Internet
Lines: 24
Message-ID: <35FAA173.3EB5F2D2@unb.ca>
References: <35FA1969 DOT 4D46 AT post DOT tau DOT ac DOT il>
NNTP-Posting-Host: fctnts07c20.nbnet.nb.ca
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Tal Lavi wrote:
> I did everything as I supposed to do, chained my new handler to the old
> one and all, and it works, except for a little problem.
> After about ten key presses that works fine, the keyboard buffer seems
> to be full, and it's beeping me whenever I press a key. Does anyone know
> how to fix it(clean the buffer or something)?
	It is still calling the old keyboard handler, just like in normal DOS if you
hold down a key, after 16 (or something) it will start beeping.  You probably
just want to replace the DOS handler and not chain it.  But, if you are always
going to be running under Win95, you can probably call getch() during your
interrupt.  This is tricky as well because you can only call that when one of
the normal DOS keys has been pressed.

> Does anyone knows what "outportb(0x20,0x20)" is for? I just ripped that
> part from someone else's handler, and it doesn't seem to do anything!
	That's the End Of Interrupt signal.

-- 
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT GeoCities DOT com
          Endlis AT nbnet DOT nb DOT ca