Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!cgh!paul@dsinc.dsi.com
From: paul@cgh (Paul Homchick)
Newsgroups: comp.sys.next
Subject: Buzzing Graphic Bombs PS Printer
Keywords: postscript, stack
Message-ID: <1296@cgh.UUCP>
Date: 28 May 90 16:33:32 GMT
Sender: paul@cgh.UUCP
Organization: Chimitt Gilman Homchick, Inc.
Lines: 33

It is possible for the NeXT to generate postscript that other
postscript devices cannot deal with.

I recently asked the mail server at purdue for issue 6 of the BuzzNUG
newsletter (now the NeXT Users' Journal).  Since I have a copy of
FrameMaker, I got the .frame version.  I have a NeXT computer, but do
not have one of their printers.  When I tried to print the document on
my QMS PS-800II printer, I couldn't get beyond page 27.  A little
experimentation showed that I couldn't print page 27, and a bit more
investigation showed that I couldn't print the "by AAAndrew Stone"
graphic that is on that page.

When I installed the Adobe ehandler.ps file in the printer to get some
debugging info, I found that this graphic overflows the stack.  I then
took the postscript output over to another system, where I found the
same problem when trying to print it on a NEC LC-890 printer.

Clearly, since Preview and other incarnations of the Window Server are
able to deal with this, the problem is in the other devices, and not
the NeXT.  However, if you need a NeXT to print out NeXT-generated
files, you are missing out on some of the portability that postscript
promises.

Has anyone else duplicated this problem, and does anyone have any
suggestions for dealing with it?

Thanks!

---
Paul Homchick                    :UUCP     {rutgers | uunet} !cbmvax!cgh!paul
Chimitt Gilman Homchick, Inc.    :Internet                   cgh!paul@dsi.com
259 Radnor-Chester Rd, Suite 140 :MCI                               PHOMCHICK
Radnor, PA  19087-5299           :GEnie                              HOMCHICK