Thanks to all who responded:
Todd Pedlar <todd_at_numep1.phys.nwu.edu>
Gyula Szokoly <szgyula_at_skysrv.Pha.Jhu.EDU>
Carlos Sanchez <csanchez_at_cirp.es>
William D. Blasingame <waldorf!daleb_at_uunet.uu.net>
Larry Griffith <larry_at_garfield.wsc.mass.edu>
delcueto_at_r.iie.org.mx
Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>
Steve Crothers <steve_at_eiscat.ag.rl.ac.uk>
Most noted the fact that PostScript printers, when printing PostScript,
wants the raw data of the file. If you print to a printer connected
to a PC and there's a driver installed for that printer, the raw
data is understood to be presented as raw data. So all the necessary
PostScript or PCL commands or whatever are attached to the file.
On the PC, that runs WindowsNT, I was able to print to a file instead of
to the printer (an option in Print Manager) and this gave me actually
the solution:
When printing to a PostScript printer on a PC from a UNIX box the
printer must see nothing but the raw data in the PostScript file.
To do so choose a driver in Print Manager that presents the printer
with the raw data.
On WindowsNT that would be
Generic / Text Only
When sharing it on the network, call it postscript or something.
I was a bit alarmed when printing with this driver to a file in
stead of the printer because the file started with an empty line.
But that didn't cause any problems.
Bjørn Braathen
University of Tromsø
Received on Thu Feb 22 1996 - 10:41:11 NZDT