Xref:	news2.mv.net comp.os.msdos.djgpp:8489
From:	"John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: CWSDPMI V3 - what's new versus V2?
Date:	Mon, 09 Sep 1996 19:29:17 -0700
Organization:	Three pounds of chaos and a pinch of salt
Lines:	26
Message-ID:	<3234D27D.729C@cs.com>
References:	<Pine DOT GSO DOT 3 DOT 94 DOT 960909014354 DOT 10067A-100000 AT zippy>
NNTP-Posting-Host:	ppp216.cs.com
Mime-Version:	1.0
To:	Samuel Vincent <svincent AT cs DOT sonoma DOT edu>
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Samuel Vincent wrote:
> 
> Well..  I would have to say that there is nothing that can be done about a
> screen saver that relies only on getting keystrokes from the keyboard
> interrupt.  Quake cannot (and should not) chain to the next interrupt.[snip]

Well, I don't know about you, but I have been playing Doom and Doom 2, both
also id games that run in DPMI, for many years, with the screen saver mode
enabled, and never had any problems before Quake.  I have run Duke3D, Descent
(1 and 2), Mechwarrior 2, and many other DOS games that hook the keyboard,
and they don't shut out my screen saver.  Only Quake does it.  Now you tell
me, is this a CWSDPMI problem, a DJGPP problem, or a Quake problem?  We
already know it has at least one major DPMI bug, so I'm not surprised if it
has more.  Obviously, chaining the keyboard CAN be done in such a way as to
allow screen savers to work correctly and still bypass DOS, so why can't
Quake do it too?

John

-- 
--------------------------------------------------------------------------
|  John M. Aldrich, aka Fighteer I   |         fighteer AT cs DOT com           |
|     *  Proud user of DJGPP!  *     |    http://www.cs.com/fighteer     |
|       ObJoke:  If Bill Gates were a robber, not only would he          |
|        shoot you, but he'd send you a bill for the bullets.            |
--------------------------------------------------------------------------

- Raw text -