Xref:	news2.mv.net comp.os.msdos.djgpp:6080
From:	Paul Shirley <Paul AT chocolat DOT foobar DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Quake and Win95...
Date:	Mon, 15 Jul 1996 21:59:59 +0100
Organization:	DrinkSoft
Lines:	26
Distribution:	world
Message-ID:	<Kqt7UEAPFr6xEw+j@chocolat.foobar.co.uk>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 960703132356 DOT 22257B-100000 AT is>
	<Pine DOT OSF DOT 3 DOT 91 DOT 960704030456 DOT 21211A-100000 AT pioneer DOT nevada DOT edu>
NNTP-Posting-Host:	chocolat.foobar.co.uk
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <Pine.OSF.3.91.960704030456.21211A-
100000 AT pioneer DOT nevada DOT edu>, Jag <gaghon AT nevada DOT edu> writes
>> 
>> > But in Quake, it does not go into Win95.   What are they doing?????
>> 
>> Most probably, Quake installs its own keyboard interrup handler, like 
>> every decent game out there.
>> 
>
>That's whats funny.  I too am installing a keyboard handler. It locks out 
>DOS fine, and Win 3.1, but not 95.

Its almost certainly a bug in your interrupt handler. Are you writing to
the win95 keyboard buffer, variables or passing values onto a chained
interrupt? (Can't help on details - I've only done this on the ST &
Amiga ;)

Incidentaly, you probably cannot stop Win95 seeing keypresses ahead of
your code, otherwise altTab would not work, and its only failed just
before or after an obvious machine crash for me.

(If you want to kill that pesky Windoze key, get the Mickysoft Kernel
Toys)

-- 
Paul Shirley

- Raw text -