Path: utzoo!dciem!nrcaer!sce!graham
From: graham@sce.UUCP (Doug Graham)
Newsgroups: comp.sys.ibm.pc
Subject: Re: "script" for MS-DOS?
Message-ID: <342@sce.UUCP>
Date: 20 Feb 88 20:18:15 GMT
Article-I.D.: sce.342
Posted: Sat Feb 20 15:18:15 1988
References: <3865@umn-cs.cs.umn.edu>
Organization: Systems Eng., Carleton University, Ottawa, Ontario, Canada
Lines: 23
Summary: I have one that works reasonably well

In article <3865@umn-cs.cs.umn.edu>, indermau@dg (Kurt Indermaur) writes:
> I am looking for a utility that behaves like the UNIX "script" command 
> (i.e., something that will write everything -- text only, really -- that goes
> to the screen to a file).  Does anyone know of such a program?  

   A while back, I wrote such an animal. It bothered me that when running a
long compile, I could either let the compiler diagnostics go to the
screen, and then have to write down where all the errors were so
I could go into an editor and fix them, or I could direct the compiler
output into a file and then sit wondering what was happening while the
compiler crunched away.

   My script command works by chaining to int 21, and then examining each
DOS function call to see if the call would result in output going to the
console. If it would, this output is copied to an internal buffer and
eventually flushed to disk. Of course, this method does not work if
the running program does output either by calling the BIOS, or writing
to the hardware directly, but this has not been a problem for the
type of programs that I use it with.

   I can post the Turbo C source if there is any interest.

Doug.