CompuServe Messages

<< I wouldn't consider dropping them every time I use aawin. So again, what's it tell me>> John, What it will tell you is where the problem is. If we can identify, for example, that the AAWIN module is conflicting with sound card driver, or the CD-ROm driver, or whatever, then we can start to solve the problem. Until we know where the problem is, we can't find a solution. <<Last, would it help to know that the problem arises so far only with one particular fli? It runs through once and crashes when it is set to loop. When it is set not to loop, it doesn't even start and there's no gpf. Curiously, it runs fine with a DOS player. >> Yes, indeed. This tells us the problem is most likely the Flic, and not your setup or the program. Perhaps the problem is a corrupt file. It could be a small as one bit out of sequence. That would explain the reason it works in DOS but not in Windows. Can you recreate the FLC? Where did it come from originally? You might try using AAPRO or utilities from the forum to send the FLC out to individual frames (gif, Tga, etc) and then recompile into a new .FLC. That might corect a corrupted file. -Brian