Date: Thu, 6 Jun 1996 09:14:02 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Shawn Hargreaves <slh100 AT york DOT ac DOT uk>
Cc: djgpp AT delorie DOT com
Subject: Re: Blocking Keys in Win95
In-Reply-To: <Pine.SGI.3.91.960605215910.16873B-100000@tower.york.ac.uk>
Message-Id: <Pine.SUN.3.91.960606090949.27903J-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Wed, 5 Jun 1996, Shawn Hargreaves wrote:

> > I have a keyboard interrupt in my game.  Under DOS, you cannot reboot the 
> > system or anything.  The controler take total control of the keyboard 
> > like it is supposed to.  But with win95, If I hit the START button, or 
> > Cntr-Alt-Del, windows takes over.  How can one stop this?
> 
> Basically you can't. What you are getting under win95 is not a direct 
> hardware interrupt: it is a virtualised interrupt which the OS has 
> already looked at and decided to pass on to your app. Some keys it keeps 
> for itself, and so your program never sees the interrupt.

I think this is true for *any* DPMI server.  It just happens that
Ctrl-Alt-Del is passed through by some of them.  I think it is generally
wrong to assume that you get *all* of the original keystrokes under DPMI. 
For example, under QDPMI, Ctrl-C is handled in a certain (buggy) way that
you cannot change even if you hook the keyboard interrupt (and every 
DJGPP program hooks that interrupt, in case you didn't know).