[comp.sys.amiga] Memory management in A3000

al158305@mtecv2.mty.itesm.mx (Gustavo Cordova) (05/05/90)

In article <18247@snow-white.udel.EDU> BARRETT@owl.ecil.iastate.edu (Marc Barrett) writes:

> Path: mtecv2!cs.utexas.edu!wuarchive!udel!mmdf
> From: BARRETT@owl.ecil.iastate.edu (Marc Barrett)
> Newsgroups: comp.sys.amiga
> Date: 2 May 90 01:00:44 GMT
> Sender: mmdf@udel.EDU
> Lines: 8


 > In article <11201@cbmvax.commodore.com> bryce@cbmvax (Bryce Nesbitt) writes:
 >The MMU maps in the virtual system ROMs (V1.3 or 2.0) and provides the
 >_ENFORCER_ option.
>  
>    Would anyone be willing to explain exactly what the _ENFORCER_ option
> is?  From the context I assume it is some sort of debugging tool.  How
> does it work?  Does it use a 9600bps terminal like ROMWack?  

EEEEKK!!  How primitive!  Why not better run the program to be debugged in
a protected segment of memory, follow all it does step by step, and if it
goes bogus it doesn't bring down the whole machine, you know, something a'la
TurboDebugger '386 (ouch, sinfull word)..

+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| Isn't it refreshingly similar the syntax of | My other mainframe|
| UNIX commands and AmigaDOS stuff?  :)       | is an Amiga :)    |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| Gustavo Cordova | Computer Systems majoring @ ITESM, Mexico     |
+=================+ Internet: al158305 @ mtecv2.mty.itesm.mx      |
| If at first you |           al158305 @ 131.178.1.5              |
| don't succeed,  | BitNet: bl158305 @ tecmtyvm.bitnet            |
| to hell with it.|         al158305%mtecv2.mty.itesm.mx@tecmtyvm |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
--
disclaimer: These are my opinions, only mine, freely distributable, for
	    non-commercial use only.