Quote Originally Posted by joaquim View Post
we know that Chr(33) & Chr(249) it's the frame start unless you use a diferent way
I use Chr(33) & Chr(249) & Chr(4) because that guarantees the beginning of a gif frame. In t-rex.gif it had an invalid frame and that's why you got that large Delay value. The invalid frame started with Chr(33) & Chr(249) but the next byte was not a Chr(4) which is guaranteed by the specifications to be the 3rd byte. So, when your code processed t-rex it picked up that as a valid frame but it was just garbage in the file.

As far as brucekik.gif goes it has 2 valid frames. It is a valid gif file but your code is not correct in the way you loop through the frames and I am quite surprised that it has worked up till now until you tried to process brucekik.gif.

One thing I have noticed from the very beginning is that when you extract out a frame and then add the header to it you save it as a complete gif file but if I try to use that saved gif it is not a valid gif file because it will not display in the browser or any other gif viewer.

Process any gif file that you have been able to display and save all of the temp.gif files. Now double click on each one of them to see if they are valid - I bet they are not.

You need to re-consider the way you are looping through the frames because somewhere in your code you are not picking up all the data correctly even though you have been able to animate them you have been lucky. Now you try to process brucekik.gif and your code freeze when trying to load the temp.gif back into your image array.