Chris Wiles..:

> erm, this is a system problem, not Voyager :)
> 
> If the system nukes, due to low chip-mem situations, there is nothing we can
> do in Voyager to somehow 'override' this with an error message :)

Sure, AmigaOS doen't like extremely low chipram situations.  Once you
get down to 10 or 20Kb menus refuse to appear, gadgets don't respond,
etc, and often sooner or later its just going to die.. *BUT* when a
program AllocMem()'s the system will either allocate it or not and, if
it fails the program in question should deal with it.  I know from
personal experience how easy this can be to overlook and how difficult
it can be to implement in some hideously deep subroutine which is all
interdependent on other stuff. 

When I have nearly a megabyte of chipram sitting free and V tries to
allocate it all and the allocation fails, I don't think its a
low-chipram situation, its a bug in V.  I'm not suggesting it is
something dreadful, lets call it an oversight on the programmer's
part.  Perhaps the zero-pointer that gets returned is used for the
memory by mistake and the first million bytes of ram just get
overwritten. This could easily create exactly the instant fireworks
display that I've seen. So easy to do, but its still V's fault, not
the system.
 
> Anyway, the answer is to buy a GFX card (makes a major difference to
> computing, especially web browsing), to eliminate *all* low chip-mem

As I said, I'd like a gfx card.  A nice PPC card with a BVision, oh,
and a tower case to put it in (unless any brave soul can vouchsafe
that they have such kit successfully runnning in a desktop case :) -
I'm really tempted to try that...) will set me back a fair amount of
money.  Still something I'm likely to buy one day though.

> situations *or* to try V� which has even more support for avoiding low

Oh, I will!  As soon as NC3 is out, you will get my order. Or maybe
even preorder.:)

I received an email from the author of FBlit on this subject.  He
maintains that the V task can crash or corrupt the display with very
graphically intensive sites if used with FBlit.  So best not use it if
you are unsure.  OTOH, it would have crashed long before then anyway
due to being out of chipram.

I'm glad this problem, wherever the fault may lie, is being addressed
for V�. The suggestion was simply for any adventurous ppl out there
running V2.96 on aga.

Regards,

Ian
===
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>

Reply via email to