9 Jul
2014
9 Jul
'14
11:31 p.m.
On Wed, Jul 9, 2014 at 6:18 PM, Peter Corlett <abuse at cabal.org.uk> wrote:
On Wed, Jul 09, 2014 at 12:24:58PM -0400, John Wilson
wrote:
[...]
Nothing in the architecture or implementation of "modern virtual memory
operating systems" (where "modern" hasn't really changed significantly
since the mid-1970s) precludes what John is talking about. The Windows
Address Windowing Extension (AWE) API he mentions is an existence proof.
That Linux, xBSD, etc. on x86-32 don't provide anything directly equivalent
only demonstrates that there's little demand for such a capability
(probably due to the widespread availability of x86-64), but not that
there's anything fundamentally difficult about it or that it is in any way
incompatible with "modern" operating system architecture or implementation.
Eric
It seems as if 32-bit API support for PAE kind of
didn't happen -- wasn't
AWE32 supposed to be a thing on Win32? I couldn't make it work in real
life.
And I couldn't find a Linux equivalent. So I
find it funny that if you
want
E11 to use the crazy amount of memory your new PC
has, you have to use
the
DOS (or stand-alone) version, rather than one of
the OSes that actually
knows
how to use all that memory. (If someone wants to
set me straight about
mapping windows to 64-bit memory space from a 32-bit program, I'd love to
hear about it please.)
The long answer is basically a lecture on modern virtual memory operating
systems in which Linux and Windows are both held up as typical examples of
the
genre, but I don't currently have the time or inclination to give it.