Yeah, Ralph Schmidt told me that he didn't want to allow MMU functions, but maybe I didn't explain correctly that I don't want direct access to the MMU but only a set of memory management functions like the ones I have told (memory context for each task/all the tasks, marking parts of memory as read-only/ilegal, remaping parts o memory).

Maybe MOS team will reconsider that decission. You will use functions so they can validate the memory areas that you mark...

The should add an option like the OS4 team to mark some memory areas as "private" so new programs can define areas that can't be overwritten by other tasks (of course, we wouldn't have full memory protection because tasks would continue using the same message system and old tasks wouldn't have their memory areas marked as private)