Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!chinacat!woody
From: woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal)
Newsgroups: comp.lang.postscript
Subject: Re: eexec?
Summary: you can write your own
	 perhaps
Message-ID: <1388@chinacat.Unicom.COM>
Date: 10 Jul 90 02:37:46 GMT
References: <1223@mtk.UUCP>
Distribution: usa
Organization: a guest of Unicom Systems Development, Austin
Lines: 36

In article <1223@mtk.UUCP>, marmar@mtk.UUCP (Mark Martino) writes:
> If one is not using an Adobe interpreter, eexec is not handled very
> gracefully.  Usually the printer just skips the rest of the file and
> 
> Is there a way to jump over the part of the PostScript file that
> involves eexec and the data eexec would use if it were there and
> continue on with the rest of the file?

eexec is fairly easy to decrypt.  What I would do is to decrypt the eexec
stuff into it's original form, and then download the file.  The Adobe
black book (type 1 font book) documents it.  Don Lancaster published
a routine in the Computer Shopper (written in PostScript) to do that.
There are several 'C' routines floating around that let you do it.
I have one that I use quite a bit.  Unfortunatly, the source is on my
machine at work, so I can't dump it down here, but I will do that
and post it here shortly.  If you decrpt the eexec stuff then it should
go through o.k.  You might have to hexify it first.

I have discovered that Appletalk and the serial port handle things
diffrently when you send stuff like that.  for example, the following
apparently works on  appletalk, but flat fails over the serial port.

currentfile 200 string readstring
22aa1f2f.....(200 bytes worth of hex data)

Under the serial port, if you send a cr/lf in the middle of the hex
string, it will give you an error message.  The only way that I have
found to make it work, is to bracket the hex data with
<.....hex....>   That works.  I have recieved several cexec files that
flat would not work until the <> was wrapped around the hex.  The RED
book specifies that the <> are required, but apparently does not
enforce it over appletalk.


Cheers
Woody