Benny Pedersen wrote:
> try without muforce :)
>
> if you need to debug use enforcer for a while !
MuForce is more reliable than Enforcer on 68040 and 68060, if you
don't mind running mmu.library.
> MuScan 40.3 (28.11.99) � THOR
>
> 68060 MMU detected.
> MMU page size is 0x1000 bytes.
>
> Memory map:
> 0x00000000 - 0x00000FFF Repairable Invalid (0x00000000)
> 0x00001000 - 0x001FFFFF CacheInhibit Imprecise NonSerial Single
> 0x00200000 - 0x00BBFFFF Repairable Invalid (0x00000000)
[...]
> check muscan, no memory must be Repairable
>
It's the way MuForce works: Any invalid memory ranges get hooked into
the MuLib error handling routines which allows the MuForce task to
know about them. The write can then be blocked or written, depending.
> if its normal, forget i write something :)
:-) Just FYI.
Cheers,
Ian
===
_____________________________________________________________________
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
