CompuServe Thread

#m

7 messages in this thread
#11013From: June NishimotoMar 22, 1992 11:48 AM
I am having considerable problems keeping Ani Pro from crashing. I have simplified my configuration down to : Config.sys: BUFFERS=20 FILES=40 STACKS=0,0 AUTOEXEC.BAT:@ECHO OFF $P$G PATH C:\;C:\DOS C:\WINDOWS\MOUSE.COM /Y I have reinstalled Ani Pro from scratch several times. I have run diagnostics on my entire system. I have removed the mouse from the configuration. I still get the same kind of Memory Protection errors. (I also have tried erasing AA.CFG before running.) The problem usually occurs in running a FLC. I typically get 1-5 seconds before a crash. Sometimes AniPro won't even get started before going down. Typically I get messages like: "Abnormal Program Termination: Memory Protection Fault CS:EIP=0008h:000062e7h My dealer just scratches his head and says he can't help me with it. I called Autodesk and they suggested trying this forum under Compuserve. I would very much appreciate any help in solving this problem either directly or through a pointer to someone who can help me with it. Thanks very much… June Nishimoto 70214,332
#11016From: Mar 22, 1992 12:51 PM
June: Hi there! I saw your cry for help on CompuServe. I have seen similar problems with some of my clients, the problem being a bad memory chip or SIMM. get yourself a program such as CheckIt or QA-Plus (diagnostics tools, both under $100) and do a RAM check. Also, try removing some of your memory to see if it helps. Assuming you have enough to run the system, take out 1/2 of the chips and see if the problem still occurs. If not, swap out the chips with the 1/2 you removed and try again! If it crashes either time, it is a bad chip! Good Luck, Greg Pyros 73027,3632 or >INTERNET:gpyros@pyros.COM (faster reply!)
#11020From: Craig Sharp [Mem TM]Mar 22, 1992 1:55 PM
June: First, let's get down to some basics before you go out and get a memory checking routine or start pulling memory chips at the risk of ruining them with static electricity… Please list the COMPLETE information about your system, including the DOS version, memory size, and disk size, etc.. You config.sys files and autoexec.bat files don't need to be listed again. Next, try to describe a situation in detail that ALWAYS produces this error. If you can't do that, do the best you can <g>. After you do that, we'll try a few other things. C#
#11025From: Steve ClaytonMar 22, 1992 3:29 PM
June , I had the same type of problems, with Ani pro, as you are having. I had tried running diags with no errors found. I had also tried replacing the all the simms. this did not fix the problem. The solution was to replace the mother board. I was using a Gateway 2000 at the time, Gateway was real cool and replaced the board at no cost and this fixed the problem. Also I had sixteen megs of memory on my system. Im sure the problem was the design of the motherboard. My guess is that there was some sort of noise on the memory bus, that Ani pro could not handle. Sorry about your problems. Hope I helped. Steve Clayton
#11055From: Kurt McKeeverMar 23, 1992 9:32 AM
You need to have QEMM or some type of ext/exp memory manager to run AAPro.
#11085From: Craig Sharp [Mem TM]Mar 23, 1992 8:56 PM
Kurt: That's not necessarily true. It is true if you want to do something other than provide all of your memory as extended, and I know you don't need a memory manager prior to DOS 5.0. Just to make sure I bounced out of this message and loaded Animator Pro on a DOS 5 system with no memory managers loaded whatsoever… unless I'm missing part of the conversation. C#
#11241From: Bob ProkoppMar 26, 1992 2:17 PM
Hello, June. I think a little more information is needed. Since you've stripped your AUTOEXEC and CONFIG, you've completed the first step in solving this. I'm wondering, does this error occur with AAPro in Vanilla <320×200> mode? Or are you loading a VESA driver via some other batch file to execute AAPro? I have seen some VESA drivers produce a memory protection fault. Other considerations in your hardware set-up may be active caches or shadowbios that are initialized when you boot the system. These would be in your C/MOS setting for the hardware, not through AUTOEXEC or CONFIG, and sometimes machines have these utilities active when you pull the computer out of the box. Checking and , if active, disabling them may help. Get me some more information, and we'll go from there.