home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.networking
- Path: sparky!uunet!wupost!gumby!destroyer!sol.ctr.columbia.edu!eff!news.oc.com!spssig.spss.com!uchinews!ellis!sip1
- From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
- Subject: Re: remote postscript printing problem
- Message-ID: <1992Aug18.235447.28054@midway.uchicago.edu>
- Keywords: postscript OS/2 TCP/IP
- Sender: news@uchinews.uchicago.edu (News System)
- Reply-To: sip1@midway.uchicago.edu
- Organization: Dept. of Econ., Univ. of Chicago
- References: <2039@deadmin.ucsd.edu>
- Date: Tue, 18 Aug 1992 23:54:47 GMT
- Lines: 25
-
- In article <2039@deadmin.ucsd.edu> lu@topcad.ucsd.edu (George Lu) writes:
- >I installed TCP/IP 1.2.1 on our 386 running OS/2. I setup lprmon to
- >monitor lpt1 and send the print job to a postscript printer on an
- >Appletalk (or is tat LocalTalk ?) network via aonther Sun workstation.
- >I printed a MS Word document, only to get a few pages of postcript
- >code from that printer. The source of the problem are the control-D
- >at the beginning of the postcript file.
- >One workaround is to print to a file, edit out the control-D, then lpr
- >from an OS/2 command window, but that does not seem like an elegant
- >solution. Is there a way to strip those control-D's?
-
- We had a similar problem. The solution we chose was to modify things
- on the Sun so that it would interpret such files as Postscript and
- print them appropriately.
-
- There are several ways to do that, the easiest being to write some
- sort of filter to remove a leading CTRL-D, then pipe that output to
- the print queue. (The filter would run on the Sun and accept printer
- output from the OS/2 station.)
-
- --
- Get the OS/2 FREQ. ASKED QUESTIONS LIST | Timothy F. Sipples
- from 128.123.35.151, anonymous ftp, | Internet: sip1@ellis.uchicago.edu
- directory pub/os2/all/faq, or from | Dept. of Econ., U. Chicago, 60637
- LISTSERV@BLEKUL11.BITNET (send "HELP"). | Tsongas > Perot > Clinton. Yay.
-