From:	apsh AT ecr DOT mu DOT oz DOT au (Alistair_P SHILTON)
Newsgroups:	comp.os.msdos.djgpp
Subject:	keyboard int 9 and djgpp
Date:	15 Sep 2000 02:12:38 GMT
Organization:	Computer Science, University of Melbourne
Lines:	24
Message-ID:	<8ps0im$f84$1@mulga.cs.mu.OZ.AU>
NNTP-Posting-Host:	gromit.ecr.mu.oz.au
X-Trace:	mulga.cs.mu.OZ.AU 968983958 15620 128.250.61.61 (15 Sep 2000 02:12:38 GMT)
X-Complaints-To:	usenet AT cs DOT mu DOT OZ DOT AU
NNTP-Posting-Date:	15 Sep 2000 02:12:38 GMT
X-Newsreader:	TIN [version 1.2 PL2]
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I've recently written (as part of an emulator) a keyboard handling routine.
It is a simple assembly program that hooks into interupt 9 and 
stores a key up/down (state) map in upper (non-visible) video memory.  
Modifier keys are passed to the old int9 handler, but all other keys are
blocked.  My program (in DJGPP) spawns the handler and uses the up/down
map for keyboard emulation. 

What I don't understand is how come control-c still works (ie. stops the
program!).  I've tested the handler without djgpp, and control-c is disabled
ok, so why/how does djgpp allow it to continue operating even though the
keystroke is (should be) blocked?  Am I missing something here?  Any pointers
would be greatly appreciated.


----------------------------------------------------

thanks

Alistair Shilton

http://www.ee.mu.oz.au/pgrad/apsh

- Raw text -