Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!ames!elroy.jpl.nasa.gov!gryphon!pnet02!arybicki From: arybicki@pnet02.gryphon.com (Adam Rybicki) Newsgroups: comp.sys.amiga.tech Subject: Re: Unexpected Gurus Message-ID: <17897@gryphon.COM> Date: 20 Jul 89 00:00:14 GMT Sender: root@gryphon.COM Organization: People-Net [pnet02], Redondo Beach, CA. Lines: 30 Here is a reply I got in mail to my original plea for help. It basicaly concludes that iff.library v16.1 has a bug that trashes the free memory list. ------------------------------------------------------------------------ You're pretty right on iff.library, it screws up the free memory list. This happens from time to time, depending on the particular picture. I had some Brushes and some ILBM with XModem garbage, and one caused a bug similar to yours, crashing in Avail, the other caused my 2 1/2 mega fast ram to fragment incredibly. Putting the particular pics through DPaint solved the problem. I traced the bug to OpenIFF(), that is, if you OpenIFF a picture, you're sold if it causes trouble, as you have no possible way to check IFFError() before OpenIFF(), and afterwards it's too late. Certainly not the kind of bug you'd want in a program where other people will input their pictures! Bottom Line: the iff.library causes this, be careful. You're welcome to post this reply, I can't get to post currently - emacs messes this terminal. Actually, I would like you to post this. Yours, Henrik Clausen, hrc@daimi.dk Fido: 2:234/24.1 ------------------------------------------------------------------------- If we could only find out how to contact the iff.library's author... UUCP: {ames!elroy, }!gryphon!pnet02!arybicki INET: arybicki@pnet02.gryphon.com or arybicki.lax1b@xerox.com