Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Message-ID: <26069@usc.edu>
Date: 21 Jul 90 03:28:39 GMT
References: <1508@faatcrl.UUCP> <26052@usc.edu> <1517@faatcrl.UUCP>
Sender: news@usc.edu
Distribution: na
Organization: Felsina Software, Los Angeles, CA
Lines: 24

In article <1517@faatcrl.UUCP> jprad@faatcrl.UUCP (Jack Radigan) writes:
|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.

No, I didn't. The A3000 has an MMU, so it is the perfect machine for running
Enforcer.  At DevCon, one of the sessions done in the lab involved having 
developers trying their software with Enforcer.  The lab was all A3000s.

|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.

Do you mean that indeed Enforcer finds a faulty 'read' access to low mem?

-- Marco
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=