Re: PROBLEM: Mac JPGs via Photoshop 3.0 and the IIgs

[nathan@visi.com (Nathan Mates)]

In article <pFPw-hQ.rocketusa@delphi.com>,
Darren Johnson  26 yo  32 MPG  <rocketusa@delphi.com> wrote:
>yes, but the binscii and uu programs (which are prodos) won't encode/decode
>my Mac jpgs, like they would other jpgs. I get a prodos error 4
>w/ both programs...

   Error 04 (or just 4), as listed at the page of GS error codes at
http://www.visi.com/~nathan/a2/faq/gserrors.html is the ProDOS and
GS/OS error code for 'Bad Parameter Count'. [In other words, a
programmer bug that shouldn't be a problem that end users get to see.]

   I'd make sure the original filename is ProDOS legal (15 characters,
A-Z, 0-9, period (.), starting with a letter). Also, uuencode has some
form of file permissions in the begin xyz somefilename' line. Try
various combos for those like 644, 666, 600, and 400. [Those are the
numerical values for various read/write permissions for yourself, your
'group' and everyone else under Unix; try a 'man chmod' on a unix
machine for the gory details.]

   UUencode in general is a very bad system that unfortunately got
popular, kinda like Windoze. It can't deal inteligently with
extraneous characters in the file, it must have all segments in
perfect order, etc. Binscii's far more powerful; too bad Todd Whitesel
and company didn't get Binscii II out the door a few years ago before
the PC and Mac types wanted to send GIFs and JPEGs around and only
used uuencode.

Nathan Mates

--
<*> Nathan Mates http://www.visi.com/~nathan/      <*>
# What are the facts? Again and again and again-- what are the _facts_?
# Shun wishful thinking, avoid opinion, care not what the neighbors
# think-- what are the facts, and to how many decimal places?  -R.A. Heinlein