RE: [MiNT] XaAES / GEM memory issues

["Julian F. Reschke" <julian.reschke@gmx.de>]

> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Konrad M. Kokoszkiewicz
> Sent: Friday, January 12, 2001 3:22 PM
> To: MiNT mailing list
> Subject: Re: [MiNT] XaAES / GEM memory issues
>
>
>
> > Hence my suggestion of the Pvaldate_vector system call.
>
> The call only would allow to verify pointers. While the main evil thing is
> that an AES with traditional design needs the memory protection to be
> hacked and overridden, which in turn creates all sort of crap problems
> with stability, signals, shutdown, exception handling and so on. That's
> why the F_OS_SPECIAL facility _will_ be removed some day. You apparently
> are the only one of the followers of this topic, who does not seem to
> understand this.
>
> And btw about removals: we have just exterminated the critical error
> handler. In 1.16 changing this vector will have no effect. I think AES
> developers may be interested in this information.

Why did you do this? What's the gain?

How can a TTP program no suppress the AES disk change alert box????