Xref: utzoo comp.lang.postscript:8835 comp.sys.mac.misc:12605
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!orca.wv.tek.com!pogo!kevind
From: kevind@pogo.WV.TEK.COM (Kevin Draz)
Newsgroups: comp.lang.postscript,comp.sys.mac.misc
Subject: Re: printing captured Mac PostScript files
Message-ID: <10960@pogo.WV.TEK.COM>
Date: 28 May 91 20:37:53 GMT
References: <1991May28.173012.17306@magnus.acs.ohio-state.edu>
Reply-To: kevind@pogo.WV.TEK.COM (Kevin Draz)
Followup-To: comp.lang.postscript
Organization: Tektronix, Inc., Wilsonville,  OR.
Lines: 43


>
>Unfortunately, Mac generated PostScript files won't print.  I captured the
>Mac PostScript files by using either the Command-F or Command-K keys when I
>clicked on "OK" in the print box.
>
>When the Command-K file prints I get the error:
>%%[ Error: invalidaccess; OffendingCommand: setdefaulttimeouts ]%%
>

This is a bug with version 70 of the Apple Prep file.  The problem is that
the prep checks the timeouts to see if they are as it wishes (300, 60, 0)
and then attempts to change these parameters if they are not "correct".
Unfortunately, the command "setdefaulttimeouts" is privilged, and must be
executed from outside the server context (i.e., exitserver).  The Mac issues
the appropriate exitserver sequence when interactively printing to a
LaserWriter.  It does not include these commands when printing to disk,
however.

The solution is easy.  Use a text editor to locate the line in the prep file
which begins with "wtkey", and comment out the entire line by adding a %
character in front of it.

You might save this file as a "fixed" prep, and use only command-F to print
files.  Then, to print the file, just prefix the job with the new prep.  You
could also define the setdefaulttimeouts command to be a no-op with the
following code:

^D
serverdict begin 0 exitserver
/setdefaulttimeouts {pop pop pop}bind def
^D

This job must be sent each time the printer is restarted.

The version 7.0 LaserWriter driver is compatible with version 6.x system
software, and has version 71 of the prep file, which solves the problem.

As for binary data, some Mac applications generate it, however most do not.
The only exceptions I think of at the moment are ColorStudio and PhotoShop.
If I recall, one of these allows you a choice of hex or binary.

KevinD