Article View: comp.sys.amiga.tech
Article #4731Re: MMU + A3000 + AmigaOS2.0 == Non-crashing system?
From: Ed Hanway
Date: Mon, 06 Aug 1990 11:55
Date: Mon, 06 Aug 1990 11:55
18 lines
1270 bytes
1270 bytes
valentin@cbmvax (Valentin Pepelea) writes: >In article <2489@clinet.FI> dix@clinet.FI (Risto Kaivola) writes: >> >> 1)If the OS2.0 does not support the MMU upto the extent where all >> application programs could run independently, i.e not corrupting other >> programs' data, can you tell me what is the reason? > >Backward compatibility. As an intermediate step to full memory protection, why not just forbid read and write access to free memory? This won't do a thing to stop programs from corrupting each other, but it might help catch the bugs that cause these problems. I think the only "correct" programs that might break under this scheme would be those that use the kind of non-standard memory allocation like VD0:. -- Ed Hanway (speaking for myself, not my employer)
Technical Details
Message-ID:
<1990Aug6.115552.14352@sisd.kodak.com>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!samsung!usc!rutgers!mephisto!udel!rochester!kodak!sisd!athena!jehReferences:
<2489@clinet.FI> <13624@cbmvax.commodore.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!samsung!usc!rutgers!mephisto!udel!rochester!kodak!sisd!athena!jeh From: jeh@athena.sisd.kodak.com (Ed Hanway) Newsgroups: comp.sys.amiga.tech Subject: Re: MMU + A3000 + AmigaOS2.0 == Non-crashing system? Message-ID: <1990Aug6.115552.14352@sisd.kodak.com> Date: 6 Aug 90 11:55:52 GMT References: <2489@clinet.FI> <13624@cbmvax.commodore.com> Sender: news@sisd.kodak.com Organization: Printer Products Division Eastman Kodak Lines: 18