Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!cgh!paul
From: paul@cgh.com (Paul Homchick)
Newsgroups: comp.sys.next
Subject: Re: DPS dictfull error with Win3 PS files
Keywords: postscript, windows, DPS
Message-ID: <1542@cgh.UUCP>
Date: 7 Apr 91 03:11:57 GMT
References: <1537@cgh.com>
Organization: Chimitt Gilman Homchick, Inc.
Lines: 33

In article <1537@cgh.com> paul@cgh.com (Paul Homchick) wrote:
>  I have a copy of Excel 3.0, which runs under Windows 3.0 ...
>I have the Windows printer configured as a NEC LC-890 (v47)...
>When I create a postscript file [... and send it to my NeXT printer,]
>I get a pop-up PostScript error window that reports:
>     %%[Error: dictfull; Offending Command: def]%%
>and, the resulting output is nil.

And, after a bit, he got some help from NeXT.

In using the postscript driver for the NEC, windows was including the
following PS sequence:

	{statusdict begin 2 setpapertray end }stopped pop

If there is no setpapertray (and with a NeXT printer, there is not),
statusdict is left on the dictionary stack.  statusdict is big enough
that the program soon runs out of dictionary room and bombs.  Removing
the above sequence solved the problem.

My correspondent mentioned that "There are better ways to safely
execute a PS operator if it [might] not be present".  Now, I'm
curious, does anyone know the correct way of doing this?

If I had a hat, it would be off to the fine folks at NeXT who are
always trying to help.  This problem was entirely mine and Microsoft's
but someone at NeXT took the time to help me with this.

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