Return to BSD News archive
Xref: sserve comp.periphs.printers:14471 comp.os.ms-windows.networking.misc:1407 comp.os.ms-windows.misc:33183 comp.unix.bsd:14985 comp.unix.misc:14161 comp.os.os2.misc:106142 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!usc!news.service.uci.edu!rosslare.ece.uci.edu!jrefling From: jrefling@rosslare.ece.uci.edu (John Refling) Newsgroups: comp.periphs.printers,comp.os.ms-windows.networking.misc,comp.os.ms-windows.misc,comp.unix.bsd,comp.unix.misc,comp.os.os2.misc Subject: Re: How to remove Ctrl-D from PostScript output (lpr)? Date: 30 Sep 1994 02:39:18 GMT Organization: University of California, Irvine Lines: 23 Distribution: inet Message-ID: <36ftom$5ng@news.service.uci.edu> References: <36a251$kkj@csdsun2.arlut.utexas.edu> NNTP-Posting-Host: rosslare.ece.uci.edu Keywords: ms-windows, OS/2, UNIX, lpr, bsd In article <36a251$kkj@csdsun2.arlut.utexas.edu>, Jonathan Abbey <broccol@arlut.utexas.edu> wrote: >Hi folks. We've got a user who is trying to print from Microsoft Word >for Windows to an Apple LaserWriter II via a TCP/IP lpr client running >under OS/2 2.1. Things printed using the standard PostScript driver >for Windows spits out a Ctrl-D as the first character of the generated >PostScript, which causes the Apple LaserWriter II to interpret the >datastream as literal text, and not as PostScript. I don't believe that the control-d switches the printer out of postscript, but rather just ends the current job. Big difference. Unless adobe has redefined the control-d from the laser writer I to the LW II and back again to the LW NT. I always give all our laser writers (I, I plus, NT, not using II at the moment) a control-d at beginning and end of the job, to clear whatever has happened before or during the current job. You can test this by talking directly to the printer over a serial line, and watching its messages back to you. You can add as many control-d's at the beginning and end as you want. You may find that some software inbetween you and the printer (either network, or printer drivers, etc) is messing things up for you.