[comp.lang.postscript] Help Zapping a LaserWriter

<SMITHM@QUCDN.QueensU.CA> (08/27/90)

I tried to send this directly to Tom but the mailer punted it back at me.


In the /etc/printcap file you can define a trailing string that the
line printer daemon will append to each job.  I don't have Unix manuals
with me but the option is something like:

   :tr=\004

Add the above sequence to the entry for your PS printer and life should
improve.  (Check your manual to verify the sequence.  My recollection is
that /etc/printcap is *very* fussy about things like spaces and blank lines.
There's also some syntactic convention to indicate a description continues
on the next line.  Perhaps a backslash at the end of the line?)

Also, if your printer is waiting for a CTRL-D, you should see the green Ready
lamp flashing on the LaserWriter.  If the CTRL-D arrives intact, the lamp
will stop flashing indicating that the printer is idle.

 Mike Smith                                  SMITHM@QUCDN.BITNET
 Queen's University                          Michael.D.Smith@QueensU.CA
 Computing and Communications Services       (613) 545-2024

bb@wjh12.harvard.edu (Brent Byer) (09/02/90)

In article <90239.115514SMITHM@QUCDN.BITNET> SMITHM@QUCDN.QueensU.CA writes:
>
>In the /etc/printcap file you can define a trailing string that the
>line printer daemon will append to each job.  ... something like:
>
>   :tr=\004
>
>Add the above sequence to the entry for your PS printer and life should
>improve.

Yes, life will be better, but it won't always be good.  On some (all?)
lpd implementations, the "tr" string does not get sent after each job,
but only after the last of the queued jobs has been output.  Thus,
each job *might* not see an "initialized" printer.  If all applications
are kosher, you probably won't feel it; else, the world gets weird.

caveat utilior

Brent Byer

shiva@well.sf.ca.us (Kenneth Porter) (09/04/90)

I've had trouble with my LC890 hanging and requiring a power
cycle to reset.  It is normally controlled from a Sun under a
lpd and some filters of my own design.  I send a ^D after every
job, as well as sending stuff before the job to put the host
and filename in the printer's LCD display.
 
I just started seeing this hanging phenomenon after some months
of operation.  If I connect the printer to a PC running a
terminal emulator after it gets into this state, I can do a ^T
and see %%[status: idle]%%, but typing normal commands gets no
response, even an error message.  Since it doesn't happen
frequently, and the last time it happened, I needed some
printout immediately, I just power-cycled it.  Next time, I'll
try ^C and ^Q, but I think I did try this with no effect, as
they're obvious things to try.

woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal) (09/05/90)

In article <20118@well.sf.ca.us>, shiva@well.sf.ca.us (Kenneth Porter) writes:
> 
> 
> I've had trouble with my LC890 hanging and requiring a power
> cycle to reset.  It is normally controlled from a Sun under a
> of operation.  If I connect the printer to a PC running a
> terminal emulator after it gets into this state, I can do a ^T

you might check to see if there is any code looking for a sequence of comments
as in the font example that I posted.  The only way out of that one, was to
powercycle the printer.  If you could arrange to make sure that your
spooler can notify you of the file that was sent, perhaps that would
show if this is the problem

Cheers
Woody