Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!comp.vuw.ac.nz!cc-server4.massey.ac.nz!A.G.Bishop
From: A.G.Bishop@massey.ac.nz (A.G. Bishop)
Newsgroups: comp.windows.ms
Subject: Printing to PS printer over NFS
Summary: Postscript printers over NFS from Win3
Keywords: Postscript, NFS
Message-ID: <1991Feb4.205509.6259@massey.ac.nz>
Date: 4 Feb 91 20:55:09 GMT
Organization: Massey University, Palmerston North, New Zealand
Lines: 37
X-Reader: NETNEWS/PC Version 2.1

Hi Win-netters,

I have an intermittent problem printing to a laserwriter plus over
NFS from windows.

I am using LPT1.OS2 (before you ask.)

Is there any way that the Print manager could appear to the network
software to terminate then restart while printing a single job?

Our fancy spooler detects non-postscript files sent to postscript
printers and adds stuff (just a header, I think) to make it print the
file.
Consequently, when a postscript file is not recognised as such you
get a postscript dump.

Occasionally when printing from eg. Write or Notepad a printout will
switch to postscript dump halfway through.  This happens particularly
with fancy .WRI readme tpye files with corporate logos and such (but
not exclusively.)

The spooler takes program completion as its end-spool signal, so that
no printed output appears on the printer until you exit a Dos app.
Using the Print manager under Windows the printed output appears when
the Print manager terminates at the end of the print.

The spooler recognises postscript files by %! appearing as the first
two characters.

Any body had this problem or have any clues?  Suggested texts would
be most helpful.

Thanx - especially for reading this far.

-- 
Tony Bishop
Massey University @Palmerston North.New Zealand