home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!darwin.sura.net!jvnc.net!netnews.upenn.edu!netnews.noc.drexel.edu!coe.drexel.edu!news
- From: stuart@lorelei.ece.drexel.edu (Stuart R. Harper)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: physical memory protection with MMU
- Message-ID: <1992Nov10.154421.18725@cbis.ece.drexel.edu>
- Date: 10 Nov 92 15:44:21 GMT
- References: <1992Oct26.162400@uni-paderborn.de> <heinz.04a3@edohwg.adsp.sub.org>
- Sender: news@cbis.ece.drexel.edu
- Reply-To: heinz@edohwg.adsp.sub.org (Heinz Wrobel)
- Organization: Drexel U. - CCD - E4
- Lines: 16
-
- In article <heinz.04a3@edohwg.adsp.sub.org> heinz@edohwg.adsp.sub.org (Heinz
- Wrobel) writes:
- >In article <1992Oct26.162400@uni-paderborn.de> chandler@uni-paderborn.de
- (Martin Grote) writes:
- >>I don't think it's impossible to install such a solution, so how about
- >>implementing it sometime?
- >
- >But how? YOu can't really use MEMF_PUBLIC as it has been misused a _lot_.
- >You can't just track memory that was allocated to one task as it might be
- >legally shared with other tasks and etc ...
-
- Absolutly! I WISH we in the amiga programming community could get Commodore of
- their butts and implemeting a protected/virtual memory environment. I think I
- could live with the block memory/tracking scheme of the Mac or Windows if I had
- the ability to track and kill aberant processes.
-
-