dad@aluxz.UUCP (DAPKUS) (04/28/85)
[Does this bug still exist, or is this for sentimental feelings?]
A while ago someone asked for a program to move parallel printer
output to a file. I replied that I believed there was such a
program on the local RCP/M. Following is the .DOC file, if you
want more info, mail me.
Donald A. Dapkus
AT&T Bell Laboratories, Allentown, PA
{ ihnp4, allegra } aluxz!dad
-------
[called FSPOOL]
SPOOL COMMAND DOCUMENTATION
The SPOOL command allows you to redirect output which would normally be sent to
a parallel printer and store it in a disk file. This might be useful if you
plan to later send the file over a modem to another computer for printing.
SPOOL is invoked as follows:
SPOOL <filename>
Where <filename> is the file into which the print data is to be placed. The
file need not exist, but if it does, it will be deleted and recreated. Once
SPOOL has been invoked for the first time the message:
SPOOL INSTALLED
will appear and the command portion will exit, leaving behind a permanant
printer interrupt handler built-in to DOS. Output directed to the printer will
be directed to the file until an error occurs or the disk containing the file
becomes full (in this case an error message will be displayed and the file is
closed).
At any time the user may stop the spooling process and redirect printer output
to the printer by typing:
SPOOL
with no filename. SPOOL may be restarted at any time again as described above
(but the permanent part remains resident even when it has been disabled).
SPOOL works with DOS 2.0 (other versions of DOS may work, but they have not
been tested). It uses about 4K of memory once installed. Because of a DOS
version dependent patch it is possible to use the PrtSc key with SPOOL but
this is sometimes a risky business! SPOOL should work with most word
processors just fine, however.
This program is provided as is and no warrantee, expressed or implied, is
made as to its usefulness for any intended purpose or its reliability. The
author and the University of California are not liable for any loss resulting
from the use of this program.
Don D. Worth
UCLA/OAC
1/11/84