GEM and memory protection

[Konrad Kokoszkiewicz <draco@mi.com.pl>]

Hi,

it seems from previous discussions that memory protection is practically
unusable with GEM, mainly because of the AV protocol.

What about a patch that would set the process protection flags to Global,
if the process is a GEM application (i.e. it is launched by AESSYS).

That would of course make the GEM applications unprotected, but they would
work with the memory protection enabled. And the advantage would be that
the rest of the system, i.e. the kernel, unix-like processes and other ram
areas would be still under protection. That means, one GEM application
could destroy another GEM application, but hopefully wouldn't be able to
destroy the system.

This sounds a hack, but IMHO a partial protection is better than no
protection at all (and the memory protection feature of MiNT is not widely
used mainly because of troubles that GEM causes). 

BTW. I've recently enabled the memory protection on the TT and it works
fine, though it is exactly the same system (a direct copy, no new
installation) as on the Falcon, where the memory protection prevented the
login from coming up. 

Has anyone experienced similar problem regarding Falcons and the memory
protection? Seems like another "feature" of TOS 4.

Gtx,

--
Konrad M.Kokoszkiewicz
|mail: draco@mi.com.pl                  | Atari Falcon030/TT030/65XE |
|http://www.orient.uw.edu.pl/~conradus/ | ** FreeMiNT development ** |

** Ea natura multitudinis est,
** aut servit humiliter, aut superbe dominatur (Liv. XXIV,25)
*************************************************************
** U pospolstwa normalne jest, ze albo sluzy ono unizenie,
** albo bezczelnie sie panoszy.