Hi Ian,
On Mon, Nov 6, 2000, at 09:41 PM, you wrote:
>
> Julian Aronowitz said...
>
> > The second. For whatever reason, the Amiga will not let you know
> > when you are running so low on Chip RAM that the machine can crash.
> > This is an inherent problem with the Amiga, itself, not with browsers
>
> Hm, this is not entirely true. :-/ Lack of chipram causing crashes
> is something which is seen with many programs, I will agree, and we
> see it because chipram is so easy to run out of. However, the Amiga
> OS will not crash "because it runs out of chipram", but because
> somebody hasn't coded correctly for that situation. (This includes
> some parts of the OS itself.)
>
> As anyone who knows how to code for the Miggy will tell you, you "ask
> for" memory and then you may or may not get it. In principle, the code
> should gracefully fail if it didn't get what it wants, but in practise
> it is not always very easy to do that when you have very complex,
> multi-threaded, interdependent pieces of code running. Errors can,
> and do, happen. Quite often, though, this sort of error is due to
> some low-level graphical patch a user may be running, which makes the
> lazy assumption that it "cannot fail" to allocate the tiny amount of
> ram it needs...
>
> Cheers,
>
> Ian
> ===
I was referring to what happens when a "ton" of graphics is forced
into the Amiga, as while on a Web site. Here, almost always, the
Amiga does not tell you that it cannot handle anymore, it just crashes.
Julian.
--------------------------------------------------------
Author of "MSH Tutorial V. 3.0". Found on Aminet -- MSHTut30.lha
Julian Aronowitz. Tel.: (718) 654-1681;
E-Mail: [EMAIL PROTECTED] [EMAIL PROTECTED]
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
