Re: jpeGS woes

[gberigan@cse.unl.edu (Greg Berigan)]

be404@yfn.ysu.edu (Adalbert Goertz) wrote:
>@ (Dave Miller) wrote:
>>be404@yfn.ysu.edu (Adalbert Goertz) writes:

>>>I have  afew .jpg files from a http://www
>>>to practice on.
>>>I got error message from 2 .jpg files:
>>>"not a jpeg file: starts with Ox7f Ox58"
>>>
>>>So, why is this not a .jpeg file  that is recognized?

>>It's probably got a MacBinary header on it.  a Lot of pics seem to have
>>these on the web...  I know cuz downloading them to my Mac, a good chunk of
>>them show up with actual filetypes after they're downloaded :)  Might try a
>>MacBinary stripper on them first.

Just because they have filetypes on the Mac doesn't mean they have a
MacBinary header or a resource fork.  (A MacBinary header is on files
ending in ".bin" and is not found in the Mac filesystem.  It's just a way
to encode the resource fork and filetype for transfer.)

Now, if the file had a custom icon on it, then it DOES have a resource
fork.  If you transfer as plain binary (not MacBinary) it will not send
the resource fork.

>The problem is solved: As a newbie I loaded these .Jpg files as TXT files.
>When I downloaded them BIN, the problems were solved.

Yup, that would do it.  Just make sure you transfer as binary and not as
MacBinary.  Transferring as MacBinary will add a MacBinary header, so
don't do that.

-- 
         _-<#)-=# http://cse.unl.edu/~gberigan/ (Greg Berigan)
     ___/___
  _-~_--<###)     $250,000 and two-year prison terms for using "obscene, lewd,
<~c>' __--<       lascivious, filthy, or indecent" language on the Internet in a
 \_--=____#)      manner intended to annoy or harass?  Watch those flames!