Ok, thanks.

What I think happened is this:

The animation was *way* too huge, spilling over into the final flash memory block of the kernel. When uploading Hijack, it overwrote the tail end of the animation, which just happens to contain the "frame index table" of the animation. This caused the animation player to "go wild" while trying to display it, which could make just about anything happen..

Of course, that's just my theory for now. If the actual animation was not "too huge", then something else must have been wrong.

Cheers