Mail Archives: djgpp/1996/09/10/23:37:58
In article <3232578D DOT 4859 AT cs DOT com>, John M. Aldrich <fighteer AT cs DOT com> wrote:
: Ian D Romanick wrote:
: >
: > This may actually be a problem with Quake. I sent them a bug report
: > that it does just this when I run 386MAX. To which they responded, "If
: > it crashes when you do that, then don't do that!" Nothing quite like
: > quality software...
:
: I sent them a bug report about incompatibilities between Quake's keyboard
: driver and TSR DOS screen saver utilities, and got back a similar response.
: For those who are interested, it seems that Quake's keyboard handler does
: not chain, so any screen saver which detects keyboard activity will be
: fooled into thinking that nothing is happening, and will merrily blank out
: the screen (or whatever) once its time expires.
This happens with most games I know of. It is not always desireable
to chain keyboard interrupts - you may find keyboard buffers filling
up, tsr popups occuring, macro keys being fired. Those sorts of
problems.
I wrote a screen blanker which had this problem. I cured it by making
it test that it was still on the interrupt chain (by firing off a
dummy interrupt) before blanking the screen.
: Apparently, id isn't particularly interested in fixing incompatibility
: problems with its software; they just tell you "not to do it."
If there is a known workaround then why not use it? If enough people
do complain, it probably will be fixed.
Steve
--
____ ____
/ __//___ \ Steve Piner - spiner AT comp DOT vuw DOT ac DOT nz
\__ \ | _/-----------------------------------------------------
/___/ |_| (yes, I know it's a BUAF, but it's *my* BUAF) :-)
- Raw text -