Hi! On Sat, May 29, 1999 at 02:47:58AM +0000, Odd Skancke wrote: > I have to admit.. this beats me :) Does MMU is protected mean its turned > on? If so, does it know how to check that on a 040 cpu? Think a bit. This is of course just a Ssystem()-call which returns the value of an MiNT-internal variable (!no_mem_prot). If some program messes with the MMU setting, MiNT does not notice. But this change will only affect one process (the one that changed the MMU tree address), as the MMU tree is saved and restored on every context switch. Programs changing the page size or anything else more critical will most likely cause a crash. Also note that Freedom (at least F2, but I guess this is valid for older versions as well) is not capable of running with memory protection - the docs clearly state this. I'd also disable Liberty, as it isn't used by other programs than F2, anyway. Furthermore, if Thing <= 1.27 (i.e. the current official versions) crash with a "private" violation, it's likely some accessory used private memory for the AV protocol. "Infamous" for this is ST-Guide; you need to set the program header flags to at least "readable" to make it work with MP enabled. Ciao Thomas -- Thomas Binder (Gryf @ IRCNet) gryf@hrzpub.tu-darmstadt.de PGP-key available on request! binder@rbg.informatik.tu-darmstadt.de Vote against SPAM: http://www.politik-digital.de/spam/
Attachment:
pgpSZueS8F2Dl.pgp
Description: PGP signature