[comp.lang.postscript] LaserWriter IINT spits up.

hurf@batcomputer.tn.cornell.edu (Hurf Sheldon) (11/18/88)

I posted this as a query earlier, it or any responses haven't come around yet,
we fixed it ourselves, thankyou.

	Our LaserWriterIINT would not accept the LaserPrep captured
via  command  k, made executable (%!) and then spooled via the serial line.
I speculate that the new printer has a different access level set for the
localtalk interface. Our older Plus doesn't seem to  mind.

We have gotten it to work by splitting the laserprep into two parts, the
privelged command part with 'serverdict begin 0 exitserver' added before 
the line 'statusdict begin waittimeout' and ending the file at the end of the
first binary string. 

The second part is the laserprep with the above  section removed. We have set
up a shell script to lpr the first part, hence an implied ^D, and then lpr the
second part with the 'command F' generated file appended.

This appears to be a prom bugfix. -It uses the unrefrenced (in the postscript
 red book) command 'setrealdevice'


This work was done for Plasma Studies by Phil Lacroute

Flame on:

 I consider this a 'make work project' courtesy of  Apple Computer's
totally uninformative manual. Considering the number of Apple
customers that do have LaserWriters on serial connections it should
work or be explained in the documentation why it doesn't. Especially
when earlier models do work correctly. At the very, very least the 
dealers who are supposed to provide technical support should have 
a bulletin about changes between models. Considering the technical
sophistication of the printer, a little more detailed information as
standard equipment is in order. Considering the needs of a large share
of customers who do other than hook the wonderful printer to the cute 
computer, a few explanatory comments about what is going on in whatever
version of the LaserPrep would be a boon.

Flame off:


Its a great printer, we  are very happy with the hardware.
The 'manual feed' setup is a very nice feature.

hurf

ps: if there is a better way to fix this problem, please let us know.
-- 
     Hurf Sheldon			 Network: hurf@ionvax.tn.cornell.edu
     Lab of Plasma Studies		  Bitnet: hurf@CRNLION
     369 Upson Hall, Cornell University, Ithaca, N.Y. 14853  ph:607 255 7267
     I sold my Elan, got a job in science; Now, no one takes me seriously.

sun@venus.ycc.yale.edu (11/19/88)

In article <6852@batcomputer.tn.cornell.edu>, hurf@batcomputer.tn.cornell.edu (Hurf Sheldon) writes...
 
> 
>I posted this as a query earlier, it or any responses haven't come around yet,
>we fixed it ourselves, thankyou.

	I also posted a similar question and nobody answered. Now I also 
sort of fixed it.
   ....
>ps: if there is a better way to fix this problem, please let us know.
	I don't quite understand what was your problem ans what you did. 
Here is mine and what I have done. Our LaswerWriter IINT is connected via 
serial port to a MicroVax and I like to print control-f captured postscript 
file on it. However, the APPLE form that was set up for normal LaserWriter 
doesn't work. The offensive command is SETSCCINTERACTIVE. I was suggested 
that I should set up a new form, NEWAPPLE, from the control-k captured 
LaserPrep, and I did. This time the offensive command is WAIT TIMEOUT, or 
something like that. Since I don't have any of the poscript referece book, 
I just try my luck. Comparing the old APPLE form and the new NEWAPPLE form, 
I deleted all the lines below "%%BeginProcSet:..." and above "systemdict .." 
and the line containing "SETSCCINTERACTIVE...", and now it works for me. 
			--- Kang Sun

oster@dewey.soe.berkeley.edu (David Phillip Oster) (11/19/88)

In article <6852@batcomputer.tn.cornell.edu> hurf@tcgould.tn.cornell.edu (Hurf Sheldon) writes:
>	Our LaserWriterIINT would not accept the LaserPrep captured
>via  command  k, made executable (%!) and then spooled via the serial line.
>ps: if there is a better way to fix this problem, please let us know.

APDA sells something called a serial laserwriter driver. This my let you
print to a serially connected postscript printer in one step, without
having to go to the 'k' or 'f' key kludge. It certainly should if your
laserwriter is directly connected to a mac over a serial port, and it
might help if there is another computer in the way. It is quite cheap, so
someone who uses this configuration should certainly look into it.

--- David Phillip Oster            --When you asked me to live in sin with you
Arpa: oster@dewey.soe.berkeley.edu --I didn't know you meant sloth.
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu

trevor@mit-amt (Trevor Darrell) (11/28/88)

In article <26868@ucbvax.BERKELEY.EDU> oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster) writes:

>APDA sells something called a serial laserwriter driver. This my let you
>print to a serially connected postscript printer in one step, without
>having to go to the 'k' or 'f' key kludge. It certainly should if your
>laserwriter is directly connected to a mac over a serial port, and it
>might help if there is another computer in the way. It is quite cheap, so
>someone who uses this configuration should certainly look into it.


Does this package allow the capture of postscript into a file? Does
anyone know of a "laserwriter driver" that can divert postscript to a 
file in a non-kludgey way?

--trevor