Conference 7.286::postscript_printing

7112.0. "DEClaser 3500's and MS Apps - "ONLINE WAITING"" by NPSS::JOHNSON (Mike J., Network Products Support) Thu Mar 06 1997 14:01

Hi,

I have several 3500 printers in a mixed environment of VAX/VMS and WIN95.  The
WIN95 systems access the printers via file shares to the VAXen, which in turn
connect to the printers via the network interface card which is configured for
LAT.  The VAX hosts are running VMS 6.2 and DCPS V1.1A.  Also, in the
environment are various other DEC printers such as LPS17, 20, 32, and LN08's 

If we print to the 3500's from any VMS application, there is no problem. 
However, quite often, if we attempt to print from any MS application (I've
tried both Word and eXcel today), the document will print TO COMPLETION but
the printer will then remain in an "ONLINE WAITING" state until I put it
offline and flush the job.  Considering that everything HAS BEEN PRINTED, I
won't guess what is left to be flushed.  Today this has happened from two
different PC's with three different files while attempting to print on either
of two 3500's.  The same PC's were able to print these same files to a LPS20
and a LAT connected LN08. 

The 3500's were delivered with NO WIN95 drivers so I am been using a setup
floppy I pulled from an internal web site several months ago.  The only
identifier I have says it contains Dc3500_1.ini and .spd, both dated 7/11/95. 
I have AltaVista searched the Digital InTRAnet and can't find anything newer. 

Does anyone know of a problem similar to what I have described, and if so, do
you know of any potential solution, other than abandoning MS apps 8^). 

Thanks,
/mj

Check PostScript options and make sure send data in binary is not selected,
also verify send ctrl-d before or after job is not selected. ALso in some
drivers in PostScript options select protocol options = none.

Ed

Ed,

THANKS !!!  Ctrl D at end of job was enabled.  Turned it off and all is well 
with the world.

/mj