Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!news.nd.edu!mentor.cc.purdue.edu!gauss.math.purdue.edu!wilker
From: wilker@gauss.math.purdue.edu (Clarence Wilkerson)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: STOP that device driver screen!
Message-ID: <3025@mentor.cc.purdue.edu>
Date: 22 Dec 90 13:59:57 GMT
References: <B45iu1w163w@brainiac.raidernet.com>
Sender: news@mentor.cc.purdue.edu
Reply-To: wilker@gauss.math.purdue.edu.UUCP (Clarence Wilkerson)
Organization: Purdue University, West Lafayette
Lines: 7


 I think it would be easy to write an "empty" device driver
that had an initialization section that printed a message
and waited for input before leaving and freeing up the
the space. You could load a copy of this after each real
device call in CONFIG.SYS to get the needed pause.
Clarence Wilkerson