Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!cgh!paul
From: paul@cgh.com (Paul Homchick)
Newsgroups: comp.sys.next
Subject: DPS dictfull error with Win3 PS files
Keywords: postscript, windows, DPS
Message-ID: <1537@cgh.com>
Date: 2 Apr 91 02:31:05 GMT
Organization: Chimitt Gilman Homchick, Inc.
Lines: 24


  I have a copy of Excel 3.0, which runs under Windows 3.0 on a DOS
machine.  I have the Windows printer configured as a NEC LC-890 (v47)
postscript printer (which is normally connected to the DOS machine),
and the device set as a FILE.  When I create a postscript file from
this system, I remove the ^Ds from the beginning of the file, remove
the CRs and and change the %!PS-Adobe-3.0 line to %!.  When I send the
resulting file to my NeXT (040 cube, Nextstep 2.0) printer with lpr, I
get a pop-up PostScript error window that reports:
     %%[Error: dictfull; Offending Command: def]%%    OK <- (not ok!)
and, the resulting output is nil.

  Presumably, the dictionary is being filled up by all of the stuff in
the Windows postscript header.  Is there a way around this, either by
somehow tuning parameters in DPS, or by performing some surgery on the
Windows postscript file?  I really had my heart set on 400dpi for a
proposal I was working on. ;-(

  Thanks to any and all!
-- 
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