Path: utzoo!attcan!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Message-ID: <1517@faatcrl.UUCP>
Date: 20 Jul 90 13:30:39 GMT
References: <619@cbnewsb.ATT.COM> <3339@usceast.UUCP> <1508@faatcrl.UUCP> <26052@usc.edu>
Distribution: na
Organization: FAA Technical Center, Atlantic City NJ
Lines: 17

papa@pollux.usc.edu (Marco Papa) writes:

>Sorry Jack, BUT memGuard III won't be of much help since it can't catch a
>memory "read" on a A1000.  You need a A2500, and 68020 or 68030 board with
>MMU (like Commodore A2620 or A2630) or an A3000 with Bryce's enforcer. [P.S.:
>I'm not saying that this is the reason for JRComm GURUs. Simply that you can't
>be sure it isn't until you have the appropriate tools]

Enforcer works with an A3000?  I thought you posted that it wouldn't.  Anyways,
yes, I know that MenGuard III only groks writes, but all my pointer code writes
after checking if the pointer is not NULL.  Uh, at least I *think* so.

Anyways, I have a tester who has access to the necessary machine to run the
enforcer program and has located it to a system call, now we have to ferret
out which call that is.  I hope to post the results here tonight.

  -jack-