🚀 go-pugleaf

In article <35.2b41ce0c@wrglex>, l_seibert@wrglex writes...
> 
>I have a problem to use a postscript printer as a postscript printer under VMS.
>The printer is a Brother HL-10PS, it is connected serial with the DECserver200 
>and everything is working fine as long as I use it as a text printer, but as
>soon as I send a postscript file or I connect it to a queue created with DEC's 
>CPS-software, it doesn't print anything. If it is connected to a text queue, 
>the printer tells me IGNORE DATA. If it is connected to a CPS queue, it takes
>sometime and then the queue is stalled.
> 

The CPS software inquires from the printer as to what kind of printer it is.
If its not recognized, it assumes DEC LN03R (Scriptprinter), and utilizes 
vendor and model specific knowledge in communicating to the "LN03R".  Of
course, if its not an LN03R, that's likely not to work.  DEC is comming out
with a new software package which might expand into knowlegde of non-DEC
printers, but I haven't seen any promises as to what will be supported.

Various third party vendors offer solutions to these problems, I don't have the
names of the top of my head, but your Brother and/or DEC salesmen might
actualy know.

Connecting the printer in Poscript mode to a text queue isn't likely to work
unless you find another way to add the necessary handshaking and Postscript
commands to your printouts prior to queueing them, which brings you back to 
needing software.  Typically text queues are one-way communications (except for
flow control via XON/XOFF or modem signals), but often Postscript does a bit
of two way (like CPS's inquiring what kind of printer).

------------------------------------------------------------------------------
Bob Koehler                     |   Any illusion to these opinions being other
rkoehler@author.gsfc.nasa.gov   |   than just mine alone is just that.

 " Life is life, and fun is fun, but it's all so quiet when the goldfish die. "
                         - Blixie