Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site Glacier.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!oliveb!Glacier!info-vax@sri-kl
From: info-vax@sri-kl
Newsgroups: fa.info-vax
Subject: Tektronix emulation on QMS 12 laser printer
Message-ID: <13618@Glacier.ARPA>
Date: Thu, 24-Oct-85 15:17:45 EDT
Article-I.D.: Glacier.13618
Posted: Thu Oct 24 15:17:45 1985
Date-Received: Sat, 26-Oct-85 06:11:34 EDT
Sender: daemon@Glacier.ARPA
Organization: Stanford University, IC Laboratory
Lines: 20

From: Peter Manera  

We had a similar problem with an LN01S and SAS/GRAPH.  I tried everything I
could think of and finally tried allocating the printer to myself and COPYing
the .GSF file (produced by SAS as an output stream file of graphic directives)
to the printer and, lo and behold, perfect graphs.  My best guess, then, is
that the print symbiont is doing something nasty.  Having something that works,
and a large student population looking for laser graphs, my workaround for the
time being is a batch job which stops the que, makes the printer non-spooled,
allocates the printer, copies any graphic files waiting to print to it, then
reverses the operation for normal operation.  I run it once an hour and, to
date, it runs pretty well.  (A preliminary step is that the file be copied by
the user to a special directory - I called it LASERGRAPH - and the batch DCL
looks there for files to print.)

If you don't want to reinvent this little wheel, I'll be glad to send you the
DCL.

Peter
NYU Graduate School of Business