Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!microsoft!edwardj
From: edwardj@microsoft.UUCP (Edward JUNG)
Newsgroups: comp.sys.next
Subject: Re: DPS dictfull error with Win3 PS files
Summary: Try generic postscript driver
Keywords: where known
Message-ID: <71765@microsoft.UUCP>
Date: 8 Apr 91 21:47:29 GMT
References: <1542@cgh.UUCP> <471@heaven.woodside.ca.us>
Reply-To: edwardj@microsoft.UUCP (Edward JUNG)
Organization: Microsoft Corp., Redmond WA
Lines: 36

In article <471@heaven.woodside.ca.us> glenn@heaven.woodside.ca.us (Glenn Reid) writes:
>Paul Homchick writes
>
>> In using the postscript driver for the NEC, windows was including the
>> following PS sequence:
>> 
>> 	{statusdict begin 2 setpapertray end }stopped pop
>> 
>> 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?
>
>There are two operators that are designed for this kind of thing.
>They are "where" and "known".  Since "statusdict" may be missing in
>addition to "setpapertray", you should check for both of them.
>
The NEC printer *does* have a paper tray operator; you might
want to use the generic postscript driver in Windows in
preference to the NEC one -- this may clear up your problem
with use of operators not supported by the NeXT printer.

Please note that the reason all those print drivers are shipped
with Windows is so that the driver output can be tweaked to
match the selected printer hardware. A number of companies,
including Microsoft, are investigating how to do this without
involving the user, but if this is to be done in a generic
store and forward manner (e.g. the eventual target device is
not known and cannot be communicated with at the time the
output file is generated), the problem is very intractable
for high-end output.

--
Edward Jung
Microsoft Corp.

My opinions do not reflect any policy of my employer.