Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!wuarchive!uunet!microsoft!alistair
From: alistair@microsoft.UUCP (Alistair BANKS)
Newsgroups: comp.windows.ms.programmer
Subject: Re: UAE's - how are they detected
Message-ID: <72660@microsoft.UUCP>
Date: 30 May 91 17:34:55 GMT
References: <1991May25.054957.1151@mnemosyne.cs.du.edu> <1991May28.173139.8139@hyper.hyper.com> <1991May29.164121.27600@odi.com>
Reply-To: microsoft!alistair@uunet.uu.net (Alistair BANKS)
Organization: Microsoft Corp., Redmond WA
Lines: 23

In article <1991May29.164121.27600@odi.com> ed@odi.com (Ed Schwalenberg) writes:
>In article <1991May28.173139.8139@hyper.hyper.com> bonneau@hyper.hyper.com (Paul Bonneau) writes:
>> space of several gigabytes, wild writes will be much harder
>> to detect.  One of the (few) benefits of the 386's segmented
>
>It is possible to use the page-protection features of the 386
>architecture to implement much finer-grained memory protection,
>both between applications and within a single application.  This
>will let the programmer have the best of both worlds: a uniform
>address space and a high degree of protection against misbehaved
>programs.

Indeed, as pointed out by Ed Schwalenberg, we will be using page protection
for all 32-bit Windows processes on all implementations of Win32, including
Dos implementations.

All 16-bit Windows apps, for compatibility, will continue to run in one
thread of one process. Thus they will share the same address space, and
be non-preemptive with respect to each other, while being pre-emptive
w.r.t the system and any win32 app.

Alistair Banks
Systems Division, Microsoft.