Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!emory!mephisto!prism!fsu!loligo!schrader
From: schrader@loligo (David F. Schrader)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Need input for future DOS release
Message-ID: <770@fsu.scri.fsu.edu>
Date: 4 May 90 13:03:15 GMT
References: <1892@cod.NOSC.MIL> <4497@plains.UUCP>
Sender: news@fsu.scri.fsu.edu
Organization: Florida State University Computing Center
Lines: 21

In article <4497@plains.UUCP> person@plains.UUCP (Brett G. Person) writes:
>
>How about some way to allow dos to blank the screen?
>You could include a driver for config.sys, or something.
>-- 
>Brett G. Person

Amen!

Make it a device driver that can be turned off/on by writing to it (like
_burndev_) and make it check not just whether keys have been pressed but
also whether the serial ports are active (mouse movement, modem usage,          and the like) since many of these do direct screen writes without using
bios/dos calls.

Make it be able to post an user selectable image and move it around to
prevent screen burn-in. Or make it call another program (like the one
that has exploding fireworks) which is exited upon key/mouse activity.
 
Let it be time adjustable.
 
David