In article <1995Oct31.121039.45581 at yogi.urz.unibas.ch>, doelz at ubaclu.unibas.ch (R.Doelz,Biocomputing Basel;+41 61 267 22 47) writes:
>>>Dear colleagues,
>>We run Molscript 1.4 on a DEC 1152 printer and encounter problems
>to print once a single plot has completed - the postscript
>output will block the printer for further requests.
Hmm, we have not seen that one. We print Molscript output through
Impressario to an HP Deskjet 550c, or via lpr to an LPD on our OpenVMS
system, and out from there through DCPS to a Printserver. In neither case
does a print job jam the printer. On the other hand, we're still using
Molscript 1.2.
The two possibilities are:
1. Something funny about the postscript from molscript.
2. Something funny about the postscript driver.
3. Combination of 1 and 2.
"1" would seem to be discounted by DCPS sending it successfully to the
LPS20. A good test would be, assuming you've got lpr via Multinet or some
such on the VMS platform, to send that to the HP5 LaserJet. If it prints
from the VMS side, but not the Unix side, then it is a Unix problem, not
a file problem. Another test that would be easy to perform would be to
move the 1152 to a serial line on the VMS system, set that up as a print
queue, and see if printing through it jams.
What happens when you print two *text* postscript jobs to the 1152, does
the first jam the second? If not, then that suggests case "3", a
combination of postscript and printer problems.
Take a look at the postscript output, does it have these as the last few
lines:
grestore stroke
MolScriptPlotSave restore
showpage
%%Trailer
%%BoundingBox: 49 99 551 701
%%EOF
The most likely culprit would seem to be a missing %%EOF -
easy to see how that might jam the printer.
Regards,
David Mathog
mathog at seqaxp.bio.caltech.edu
Manager, sequence analysis facility, biology division, Caltech
