Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bionet!ames!sun-barr!sun!kilowatt!raz
From: raz%kilowatt@Sun.COM (Steve -Raz- Berry)
Newsgroups: comp.sys.amiga.tech
Subject: Re: DeluxePaint III and IFF
Keywords: IFF DPIII
Message-ID: <111373@sun.Eng.Sun.COM>
Date: 21 Jun 89 02:02:43 GMT
References: <1419@dover.sps.mot.com> <110824@sun.Eng.Sun.COM> <10102@polya.Stanford.EDU> <17962@usc.edu>
Sender: news@sun.Eng.Sun.COM
Reply-To: raz@sun.UUCP (Steve -Raz- Berry)
Distribution: na
Organization: Sun Microsystems, Mountain View
Lines: 22

In article <17962@usc.edu> addison@pollux.usc.edu (Richard Addison) writes:
>>>In an article I wish I didn't write:
>>> [I Describe a problem... but not with EA's iff images...]
>In article <10102@polya.Stanford.EDU> rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes:
>> [Tom panic's because of my mis-information.]
>>-tom

>Now, for the real test.  Yup, there is a pad byte at the end of that odd
>length BODY chunk.  (Hmm, "BODY by IFF"  Naaah.)

Yep, I looked too. The original problem was with the way I did the parsing.
(surprize, surprize) Although the EA format is different than all the other
IFF's I've seen, there is nothing wrong with it.

Ok, now that I have admitted to messing up, you can all scream at me ;-)

Now I guess I'll have to fix it.


Steve -Raz- Berry      Disclaimer: I didn't do nutin!
UUCP: sun!kilowatt!raz                    ARPA: raz%kilowatt.EBay@sun.com
KILOWATT: sun!kilowatt!archive-server     archive-server%kilowatt.EBay@sun.com