🚀 go-pugleaf

>In article <9103132036.AA25566@crayola.cs.UMD.EDU> 3IU4TOB@CMUVM.BITNET writes:
>I am interested in hearing about anyone's experience with the QMS 410 printer,
>in particular in a mixed PC and Mac environment.

We have 5 QMS410s and we are having a terrible time with them.  In our case,
they are set up on a Sun network.  With the exception of a printer that is
connected to a Sun 3/80, the printers were configured with this postscript
code:

%!
executive
serverdict begin 0 exitserver
executive
statusdict begin 0 setsoftwareiomode
statusdict begin 25 19200 67 setsccbatch
end
quit

We connected a terminal directly to the printer to do this.  The Test
Configuration Page shows this:

Serial RS-232C:	Postscript, 19200, none, 8, 1, XON/XOFF/DTR

In the case of the Sun 3/80, the communications protocol was set to: DTR/DSR
The 3/80 also required a special null modem that is different from the ones
that we use on the other suns.

In all cases, we are getting messages like this:

psbanner: sun:bkp  Job: stdin  Date: Fri Feb 15 15:17:54 1991
psif: sun:bkp 3b107qms serial start - Fri Feb 15 15:17:56 1991
psif: initial status - %%[ status: idle; source: serial 25 ]%%^M
/u/ps/pslib/psif: 22068 Emulator trap - core dumped

psif: sun:pgm 3b107qms serial start - Thu Feb 28 14:59:04 1991
psif: initial status - %%[ status: idle; source: serial 25 ]%%^M
psif: ERROR: printer is idle, giving up!
/u/ps/pslib/psif: 2790 Killed

The stuff in %%[]%% and "Emulator trap - core dumped" come from the
printer.  The rest comes from the transcript software that we are running.
We don't think the software is the problem because we have other models of
QMS printers and a Data Products printer that work just fine.

As you can see jobs are getting killed.  In fact, on one printer about 100
jobs were killed in a 3 week period.

If anyone has had the same experiences or even has a fix please respond through
this group or by e-mail.

Thanks,
Mark Dennis
att!aloft!vmd