home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!portal!danb
- From: danb@shell.portal.com (Dan E Babcock)
- Subject: Re: Problem with Enforcer
- Message-ID: <C1LI6C.MEp@unix.portal.com>
- Sender: news@unix.portal.com
- Nntp-Posting-Host: jobe
- Organization: Portal Communications Company -- 408/973-9111 (voice) 408/973-8091 (data)
- References: <shf.728210763@well.sf.ca.us>
- Date: Fri, 29 Jan 1993 03:11:00 GMT
- Lines: 19
-
- In article <shf.728210763@well.sf.ca.us> shf@well.sf.ca.us (Stuart H. Ferguson) writes:
- >I just pulled the lastest version of Enforcer off the net, installed
- >it and tried running my standard test suites and hit a brick wall.
- >
- >It seems that the system cannot allocate chip ram. I get an Enforcer
- >hit at 00001FE0 and the AllocMem returns 0. That address seems a bit
- >high for Enforcer protection.
- >
- >I have an RCS 68040 board. Any ideas how to make Enforcer more
- >useful for me? Thanx.
-
- The problem is that Enforcer belives that access to the memory header at
- $1FE0 is an illegal access, so you get "a few" hits. :-)
- As you noticed, this also screws up the system.
- There is a program called "MoveMH" which moves the chip mem header to
- fast RAM to avoid the bogus enforcer hits.
-
- Dan
-
-