lfk@mbio.med.upenn.edu (Lee Kolakowski) (07/07/89)
-- 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 <litigate.h> || One-Liner Here! | =====================================================================
lfk@mbio.med.upenn.edu (Lee Kolakowski) (07/07/89)
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 <litigate.h> || One-Liner Here! | =====================================================================
nelson@sun.soe.clarkson.edu (Russ Nelson) (07/21/89)
Ghostscript 1.3 is available from the CUHUG bbs, with the iscan bug fixed as
per lpd's message of a few days ago, and with the 80386 executable replaced
by a 80286 executable. There are three archives, gs13src.arc, gs13doc.arc,
and gs13exe.arc. If you're ftping, they're in /d/graphics. If you're calling
via modem, they're in file area 12. Details on the CUHUG bbs follow:
The semi-official c.b.i.p archives are on grape.ecs.clarkson.edu which
is a Zenith Z-248 running a modified version of KA9Q's TCP/IP NET that
allows you to shell out to DOS while still processing packets. After
shelling to DOS, we run an Opus BBS. The particulars:
FTP: grape.ecs.clarkson.edu [128.153.13.196], user anonymous, password guest.
Look in 00readme for timely information.
Look in /d/general/cuhug.lst for a listing of files w/ descriptions.
Look in /[cdef]/allfiles for listings of all files.
Look in /c/bin1/*.* for c.b.i.p postings.
Look in /d/graphics/pa.arc for Painter's Apprentice
Look in /d/dosutil/postprn.arc for the PostScript device driver
Look in /e/freemacs/*.* for Freemacs
Look in /f/gif/*.gif for .GIF images.
Look in /f/games/*.* for Simtel20's games.
Opus: 260/360 in the Nodelist. (315)268-6667, 8N1, 1200/2400 Baud, 24 hours.
Look in file area 7 for PostPrn.
Look in file area 12 for Painter's Apprentice
Look in file area 23 for Simtel20's games.
Look in file area 25 for Freemacs
Look in file area 26 for c.b.i.p postings.
Look in file area 27 for .GIF images.
Submitting files to grape by FTP:
You can just put the file where you believe it belongs. Note that you
cannot overwrite files, so if you want to update something, you need
to change the name. Send mail to root if you need to delete or
overwrite a file.
To help us keep the 'files.bbs' up to date, we need a .DSC file. This
file should have its first line be a one-line description less than 40
characters in length. The rest of the file (no more than ten lines)
can be a more verbose description. Either put the file in the arc, or
else in the same subdir as the arc.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu])|(70441.205@compuserve.com)