LPR Does Not Print PostScript Files CorrectlyID: Q123107
|
When you use LPR from the command line to submit print jobs to a LPD print server, PostScript files may print out as PostScript source code files instead of a normal printout. In addition, a print job sent to a PCL printer may reset the printer, losing any previous setting to origination and fonts.
The command line LPR prefixes the print job with a reset command. This is a
common practice as many print jobs do not clean their settings concerning
origination and fonts. This would cause the next job to print incorrectly.
Some print queues, including Windows NT, try to determine if an incoming
print job for a PostScript printer is already in PostScript form or not. If
not, the queue assumes it is a text print job and converts it into
PostScript form. If it is in PostScript form, the job prints out as
PostScript source code instead of the intended form.
The reset command can cause the queue to incorrectly identify the incoming
print job as a text file. Some PCL printer queues may have a Separator Page
defined to change font information and origination. This may be done to
print large text files in a meaningful manner. The reset command added by
the LPR causes the changes to be wiped out of the printer and set back to
the default settings.
To correct this problem, do one of the following:
LPR -S <server> -P <printer> -o <filename>.PS-or-
COPY <filename>.PS \\<server>\<printer>
Additional query words: prodnt lpq
Keywords : kbprint ntprint
Version : 3.5
Platform : winnt
Issue type :
Last Reviewed: February 12, 1999