Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-sdd!ncr-sd!tw-rnd!jml
From: jml@tw-rnd.SanDiego.NCR.COM (Michael Lodman)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Was - Re: Xerox sues Apple!!! Now processor wars.
Message-ID: <205@tw-rnd.SanDiego.NCR.COM>
Date: 5 Jan 90 00:45:49 GMT
References: <6767@tank.uchicago.edu> <1989Dec17.112127.27333@me.toronto.edu> <3368@rti.UUCP> <899@lzaz.ATT.COM> <1989Dec29.165724.12683@sj.ate.slb.com> <199@tw-rnd.SanDiego.NCR.COM> <5305@skinner.nprdc.arpa>
Reply-To: jml@tw-rnd.SanDiego.NCR.COM (Michael Lodman)
Organization: NCR Corporation - Distributed Systems Lab
Lines: 17

In article <5305@skinner.nprdc.arpa> malloy@nprdc.arpa (Sean Malloy) writes:
>In article <199@tw-rnd.SanDiego.NCR.COM> jml@tw-rnd.SanDiego.NCR.COM (Michael Lodman) writes:
>The 'virtual 8086' mode comes to mind -- it allows you to isolate a
>process so that it can't step all over any other process's memory
>space. It also permits the process in that space to crash without
>taking the rest of the system with it.

This is a feature of most memory management schemes I have seen. In fact, this 
is one of the basic reasons for having memory management in the first place.
No, sorry, this doesn't make the '386 memory management unique or better.

-- 
+-----------------------------------------------------------+
| Michael Lodman               Mike.Lodman@SanDiego.NCR.COM |
| NCR Corporation  -  Distributed Systems Lab  -  San Diego |
| 9900 Old Grove Rd.  San Diego, CA.  92131  (619) 693-5353 |
+-----------------------------------------------------------+