dave@unislc.uucp (Dave Martin) (03/30/91)
From article <388@mixcom.COM>, by oovvoo@mixcom.COM (Mike Shawaluk): > I recently acquired Post 1.5 (a PostScript interpreter library & > CrossDOS. The problem I encounter is when I attempt to use that font, I > get an error message referring to "eexec" (sorry, I didn't write down > the exact error message, but it's easily reproducable). I tried this > with a number of fonts that I had converted, and they all seem to give > the same error message. As a "by the way", I was able to download some > fonts via a FTP site, and those .PFB files worked just fine! I too have noticed this "eexec" problem, with fonts that work fine on a NeXT. Also, I aquired a file called warbird.PS (I believe it was from ab20.larc.nasa.gov somewhere, look in FILES.Z). This is a rendering of the Romulan Warbird from Star Trek the Next Generation. It also works fine on the NeXT, but apparently causes an infinite loop in Post 1.3-1.5. I've never tried an earlier version of post with it. It is necessary to reboot to get out of it, Post just locks up. I've also noticed that Post uses horrible colors (very bad contrast) for the file requester when in color mode. Otherwise, I like this program very much, but am disturbed by these annoying problems with the eexec and the lockup. I hope the author can be made aware of them and fix them. Sorry about crossposting this, but I am trying to attract the author's attention, if he has usenet access. -- VAX Headroom Speaking for myself only... blah blah blahblah blah... Internet: DMARTIN@CC.WEBER.EDU dave@saltlcy-unisys.army.mil uucp: dave@unislc.uucp or use the Path: line. Now was that civilized? No, clearly not. Fun, but in no sense civilized.
mcmahan@netcom.COM (Dave Mc Mahan) (03/31/91)
In a previous article, dave@unislc.uucp (Dave Martin) writes: >From article <388@mixcom.COM>, by oovvoo@mixcom.COM (Mike Shawaluk): >> I recently acquired Post 1.5 (a PostScript interpreter library & >> CrossDOS. The problem I encounter is when I attempt to use that font, I >> get an error message referring to "eexec" (sorry, I didn't write down >> the exact error message, but it's easily reproducable). I tried this >> with a number of fonts that I had converted, and they all seem to give >> the same error message. As a "by the way", I was able to download some >> fonts via a FTP site, and those .PFB files worked just fine! > >I too have noticed this "eexec" problem, with fonts that work fine >on a NeXT. > >Also, I aquired a file called warbird.PS (I believe it was from >ab20.larc.nasa.gov somewhere, look in FILES.Z). It also works >fine on the NeXT, but apparently causes an infinite loop in Post 1.3-1.5. >I've never tried an earlier version of post with it. It is necessary to >reboot to get out of it, Post just locks up. > >I like this program very much, but am disturbed by these >annoying problems with the eexec and the lockup. > >I hope the author can be made aware of them and fix them. There is a BBS in Palo Alto, Calif. Where the author of Post calls into. He lives in England, and I'm not sure if he has Usenet access. If you send me DETAILED explainations of what is going wrong with the latest version of Post (must be the latest, I doubt he is trying to support superceded versions), I'll cross post on that BBS system for you and let you know if I get an answer. You might also try posting to the PostScript newsgroup for an answer to your problem, or at least a forwarding address for the author. If you want to try this method, please try and focus the problem on the smallest size of PostScript file that is causing the problems. I don't want to try and have the author modem a 300 Kbyte file across half the world and find out that it was something silly in the first three lines of the PostScript. He pays the phone bill. >VAX Headroom Speaking for myself only... blah blah blahblah blah... >Internet: DMARTIN@CC.WEBER.EDU dave@saltlcy-unisys.army.mil >uucp: dave@unislc.uucp or use the Path: line. -dave -- Dave McMahan mcmahan@netcom.com {apple,amdahl,claris}!netcom!mcmahan