CompuServe Thread

#general protection fault

5 messages in this thread
#159840From: John HaberMar 20, 1995 11:02 AM
I downloaded an fli from a forum today. Whenever I run it, whether through the Windows Media Player or directly from AAWIN, after about ten seconds I get a General Protection Fault in Module aaplay.dll. What do I do? I assumed that the dll was corrupt and downloaded aawin again, but no improvement. My system is a 486sx/33 with 8 Meg and no duplicate dll or drv files anywhere. I had been (and am) running with aaplay.dll and the mciaap.drv (if I recall its name correctly) in c:\windows\system, all other aa-related files in c:\windows.
#160053From: Brian Rudolph [Adesk]Mar 21, 1995 2:39 PM
John, The .DLL file is conflicting with something else on your system. Try starting Windows in Standard mode and see if that helps. Also, try booting with only Files, Buffers, and HIMEM.SYS in your CONFIG.SYS file. That is the "vanilla" boot or Windows. -Brian
#160064From: John HaberMar 21, 1995 3:51 PM
>Try standard mode. Since I obviously can't run that way routinely, what's it tell me? >Try a plain-vanilla config.sys Here's my actual config.sys. The remaining lines are strictly necessary for the sound card and compressed disk drive, I believe. I wouldn't consider dropping them every time I use aawin. So again, what's it tell me (unless that autodesk products are too much trouble)? DEVICE=C:\DOS\himem.sys DEVICE=C:\DOS\EMM386.EXE NOEMS WIN=ED00-EFFF buffers=15,0 files=60 dos=UMB lastdrive=H fcbs=4,0 DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE DEVICE=C:\DOS\ANSI.SYS dos=high stacks=9,256 DEVICEHIGH /L:1,39568 =C:\DOS\DRVSPACE.SYS /MOVE DEVICE=C:\PASTUDIO\MVSOUND.SYS D:5 Q:7 S:1,220,1,5 M:0 J:1 DEVICEHIGH /L:1,34976 =C:\PASTUDIO\TSLCDR.SYS /D:MVCD001 /R 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. Thanks for your analysis. I'll try the options independently now once I log off. Bye, John
#160074From: Brian Rudolph [Adesk]Mar 21, 1995 5:05 PM
<< 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
#160251From: John HaberMar 22, 1995 12:44 PM
Thanks for your patience, Brian! I bet you've got it. The system setting don't seem to be it. I got the fli from another forum library (Astronomy). Since it always crashss in the same place, I could probably debug it just like you said. I might, in fact, because it would help me learn about the software. Still, it's not worth it: it's just a tiny little bit of interest from another amateur like myself. Best,