Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!netnews.upenn.edu!lfk From: lfk@mbio.med.upenn.edu (Lee Kolakowski) Newsgroups: gnu.ghostscript.bug Subject: Ghostscript 1.3 Message-ID: Date: 6 Jul 89 18:27:29 GMT References: <8906200258.0.UUL1.3#5127@aladdin.com> Sender: news@netnews.upenn.edu Distribution: gnu Organization: University of Pennsylvania, Dept. of Chemistry Lines: 41 Cc: lpd@aladdin.com (L. Peter Deutsch) Sorry about the previous message ^C-c slipped 8~> I have explored ghostscript versions 1.0 1.1 1.2 and now 1.3, and as yet, I have not been able to do what I wanted. I use eroff from elan on the PC and generate some rather complex troff graphs, figures, etc. The postscript prints fine on a laserwriter once I have found all my coding errors. What I would like to do is use a PostScript interpreter to debug most of the problems and to preview my output. I have always just gotten the latest version of the executable and the accompanying g*.ps files and tried $ gs mypostscript.out And for 1.0-1.2 I get just a little of the title page and then "hard reboot" for 1.3 I don't see anything for any input file. Perhaps the executable for 1.3 on prep.ai.mit.edu is corrupted, but it hangs my hardware (AT with Paradise EGA card). If ghostscript is not yet developed enough at this point to use this way, could someone recommend and alternative? (BTW, what is GoScript?). Thank you, I don't want to seem ungrateful to the development of ghostscript, but at this time I need a tool that works. -- Frank Kolakowski ===================================================================== |lfk@mbio.med.upenn.edu || Lee F. Kolakowski | |kolakowski@mscf.med.upenn. || Univ. of Penna. | |c/o jes@eniac.seas.upenn.edu || Dept of Chemistry | |kolakowski@c.chem.upenn.edu || 231 South 34th St. | |bcooperman.kolakowski@bionet-20.arpa || Phila, PA 19104 | |AT&T: 1-215-898-2927 ||--------------------------| |#include || One-Liner Here! | =====================================================================