Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!maverick.ksu.ksu.edu!uafhp!acrosby
From: acrosby@uafhp.uark.edu (Albert Crosby)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: documentation printing
Message-ID: <6711@uafhp.uark.edu>
Date: 12 Jun 91 13:47:18 GMT
References: <1991Jun11.105816.31353@kuhub.cc.ukans.edu> <1991Jun12.065151.27837@klaava.Helsinki.FI>
Organization: College of Engineering, University of Arkansas, Fayetteville
Lines: 17



My $.02 worth is that using copy-to-prn is the better solution for the reason
that Prof. Salmi indicates:  print loads a memory resident program.  Sure,
print allows you to multi-task in a limited fashion (and queue jobs, etc.),
but most people would prefer not to have their environment modified UNKNOWINGLY
by a batch file.  

If it's really a batch file, and it's a big deal to you, just edit the batch file and replace the copy-to-prn to print.

On a side note, I have seen some "compressed" doc printers that allowed you to
specify the port.  Not needful very often, but a nice touch for the author to 
include.

Albert

(Yes, I have no .signature, I have no .signature today!)