Xref: utzoo comp.windows.ms:13279 comp.windows.ms.programmer:2806
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!ux1.cso.uiuc.edu!usenet
From: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Newsgroups: comp.windows.ms,comp.windows.ms.programmer
Subject: Re: Over 16 Meg
Message-ID: <1991May31.012439.4019@ux1.cso.uiuc.edu>
Date: 31 May 91 01:24:39 GMT
References: <1991May30.174414.19047@midway.uchicago.edu> <1991May30.000945.12529@xanadu.com>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 22


In article <1991May30.174414.19047@midway.uchicago.edu> lair@ellis.uchicago.edu (Scott A. Laird) writes:
>In article <1991May30.000945.12529@xanadu.com> ravi@xanadu.com (Ravi Pandya) writes:
>>Has anyone had any success at all trying to get Windows 3.0 Enhanced
>>Mode to recognize the existence of over 16 Mb of RAM? I have 32 Mb of
>
>Windows is still more or less a 286 app, with segments and 24-bit addressing,
>and shouldn't be able to directly access 32 Mb of RAM.  Nothing designed to
>run on a 286 can use more than 16 Mb of extended memory.  Even in 386 enhanced
>mode, Windows is still only capable of 16 Mb, because the computer is still
>more or less running like a 286, it is just using virtual memory and the
>virtual-86 mode for running DOS apps.  It still shouldn't be capable of
>32-bit addressing.
>


I do not understand this. In 386 enhanced mode, Windows 3.0 uses virtual
8086 mode for DOS programs. It should be able to run those above 16 megs.
Does it?


Doug McDonald