Article View: comp.os.os2.networking
Article #568Re: remote postscript printing problem
From: Andrew Little
Date: Thu, 20 Aug 1992 12:54
Date: Thu, 20 Aug 1992 12:54
28 lines
1576 bytes
1576 bytes
In article <2039@deadmin.ucsd.edu> lu@topcad.ucsd.edu (George Lu) writes: > >Hello there, > >I installed TCP/IP 1.2.1 on our 386 running OS/2. ...lpr stuff deleted >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. I have this problem as well, but only when printing postscript from Win/OS2. If I use an OS/2 app, like PM Chart, the postscript is fine. Is there a problem in the Win/OS2 driver? I haven't tried installing a "regular" windows 3.0 postscript driver yet. BTW, I don't have TCP/IP yet, and always print to a file and then move it up to my Unix system to print. Gives me the opportunity to tweak the postscript code by hand tho :-). >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? I'll let you know if I find any solution Andy Little BALR Corporation andy@balr.com Software Solutions in Real Time
Technical Details
Message-ID:
<1992Aug20.125445.11985@balr.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!newsserver.pixel.kodak.com!laidbak!tellab5!balr!andyReferences:
<2039@deadmin.ucsd.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.os2.networking Path: arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!newsserver.pixel.kodak.com!laidbak!tellab5!balr!andy From: andy@balr.com (Andrew Little) Subject: Re: remote postscript printing problem Message-ID: <1992Aug20.125445.11985@balr.com> Keywords: postscript OS/2 TCP/IP Organization: BALR Corporation, Oak Brook, Illinois. References: <2039@deadmin.ucsd.edu> Date: Thu, 20 Aug 1992 12:54:45 GMT Lines: 28