#Imagine Crashes
6 messages in this thread
Hi I'm having some trouble running Imagine 1.1 under WB 2.04. After I
first installed WB 2.04 Imagine started giving me recoverable alerts which
eventually turned into unrecoverable alerts (guru). It never occurred at
exactly the same place in a render. Occasionally it even completed a
render. But never more than 3 in a row. For the last couple of weeks I
have had no problems, so I thought nothing about it. But it has now started
again. I have just rebooted from a guru caused by:
11 recoverable alerts (0100 0009) attempting to free memory already
freed
followed by 1 alert (0100 000F)
followed by the guru (8100 000F)
This occurance happened while Imagine was attempting to clean-up after
completing a render.
Does anyone have any idea what's going on?
Kevin Ushko
Edmonton, Alberta
Kevin, I haven't seen any gurus (excuse me… 'recoverable alerts') in
Imagine since switching to WB 2.04. Haven't seen any messages from others
about it either, and would have expected to if it was a problem (there are
a lot of Imagine users online 🙂
During the time everythign seemed to work ok did you reconfigure WB 2.04
any? ie. WB screen sizes, modes, colors, fonts, input handling, etc, etc?
Did you make any other changes to the system when it started acting up
again? (ie. new progs, utilities, etc)
Boy you are tenacious! *11* recoverable alerts and still going strong? I'd
likely have given up on the 3/4th!
–jp–seattle–
Thanks for the info John,
I think it is somehow memory related. I am running WB 2.04 using ZKick
from my developers package, so I lose about 1/2 Meg of memory. After I
posted my message last night I rebooted under 1.3 and was able to render
without any probelms, but as soon as I booted under 2.0 and ran Imagine I
got the 'alerts' again. I'm going to sit and watch memory tonight or
tomorrow to see what happens during the render. The object I'm rendering
is 260K so it isn't small, but I have 5 Megs of memory.
My system hasn't changed at all in about a month. But I have tried
running without anything except Imagine, but it's no good.
I felt like you that if there was a problem others would have gotten it
too, well before I did. I just didn't know how else to title the message.
Tenacious? I was just hoping that it would continue and complete the
render.
I dont know about your Gurus Kevin, but I havent been able to reliably
render very many pictures in Trace mode that are bigger than 320×200 on my
A1000 with Lucas/Frances and 4 Megs 32bit ram. I am running 1.3.3 and
Imagine 1.1 and most traces that have texture maps will blow up with a
0000000D.xxxxxxxx. This has been going on for months. I know I am not
running out of memory. I have a total of 5.5megs and have tried dozens of
different combos and Imagine still pukes on many traces. All my other
software works flawlessly. What gives?? I even sent for the most recent
copy of 1.1. It was a different size than the one my friend has and it
still blows up regularly. I am getting damn tired of fighting with Imagine
to do anything useful.
So much Great Amiga Software, so little Time !! John Lemoine via Whap!
75320,143 Edmonton, Alberta, Canada
Since current Imagine reconfigures all mapping file to 24bit it requires a
whole lots a RAM! Imagine is a most Memory monger program (TAD comming as
second?), it seems like 2 picture files are most you can map with 8meg!
– THANX R.SATOH ->via Whap!
I think my problem may be memory related (see my message to john p.). I
have 5 Megs, yet it doesn't seem to be enough for most of the things I'm
trying to do. Guess I'll have to find some more memory somewhere.