CompuServe Thread

lockup during -=> *.FLC

7 messages in this thread
#120891From: Yost GroupAug 29, 1994 10:23 AM
Sounds like a hardware problem to me. Perhaps one of the hardware experts here on the forum would have some specific ideas for ya. – G
#121388From: Mike RatledgeAug 31, 1994 4:04 PM
Hopefully so, Gary! It's wierd – sometimes I can go hundreds of *.FLC-based frames without a single lockup, and then it'll kick my tail every hour on the half-hour (jocular mode on) for the next five hours… Rendering to *.TGA or *.JPG has absolutely no problems – could that maybe point in the code for the Vibrant driver , or is that outside their realm?
#121405From: Yost GroupAug 31, 1994 5:56 PM
Could be heat related, or it could just be a failure of your memory manager re Phar Lap at some point. (I'm sure it has nothing to do with the Vibrant drivers, though.) – G
#121969From: Mike RatledgeSep 3, 1994 8:21 PM
hmmm… I'm using QEMM 7.04 for VM services… Oh, well – seems to have calmed itself down to "once-in-a-while" right now
#122044From: Mark SloatmanSep 4, 1994 1:35 PM
Mike, I read of your plight with lock ups. Did you say that if you use the Graphite board it never locks up? You might try disabling the video shadow ram in the "advanced bios setup" of setup. What bios do have? Mark
#122085From: Mike RatledgeSep 4, 1994 10:11 PM
it's an AMI BIOS, but not sure 'xactly which one. The board I have is a VLB 486/66 w/32MB RAM onboard.
#122455From: Mark SloatmanSep 6, 1994 11:06 PM
Usually problems like yours are caused by memory conflicts. Did you try my suggestions? If that didn't help you might outline all hardware in your system, as well as the contents of your autexec.bat and config.sys files. Good luck, Mark