Prev: BSOD, mismanaging system PTEs, x64/WinServer2003?
Next: VSS problem on an Windows 2003 Enterprise R2 SP2 Server
From: jorgen on 3 Jan 2008 12:56
Charlie Russel - MVP wrote:
> With Windows x64 Edition, you don't need to do ANYTHING
> to allow that 32-bit application to see >2GB of memory. It happens
> automatically, and every 32-bit application automatically has a full 4GB
> of memory address space available to it.

Just to clear that up. I say something else in my post.

http://support.microsoft.com/kb/888732

Unless the flag in set, the application only gets 2GB in both 32-bit and
64-bit Windows
From: Charlie Russel - MVP on 3 Jan 2008 13:22
No, the Application GETS 4 GB in x64. It it can't USE or SEE the 4GB unless
the application is compiled accordingly. But the memory address space is
allocated regardless. This is _different_ from 32-bit Windows, where the
application only GETS 2GB unless you boot with the /3GB switch.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"jorgen" <na(a)invalid> wrote in message
news:en2gCIjTIHA.2000(a)TK2MSFTNGP05.phx.gbl...
> Charlie Russel - MVP wrote:
>> With Windows x64 Edition, you don't need to do ANYTHING to allow that
>> 32-bit application to see >2GB of memory. It happens automatically, and
>> every 32-bit application automatically has a full 4GB of memory address
>> space available to it.
>
> Just to clear that up. I say something else in my post.
>
> http://support.microsoft.com/kb/888732
>
> Unless the flag in set, the application only gets 2GB in both 32-bit and
> 64-bit Windows

From: jorgen on 3 Jan 2008 13:30
Charlie Russel - MVP wrote:
> No, the Application GETS 4 GB in x64. It it can't USE or SEE the 4GB
> unless the application is compiled accordingly. But the memory address
> space is allocated regardless. This is _different_ from 32-bit Windows,
> where the application only GETS 2GB unless you boot with the /3GB switch.

That can very easily be misunderstood. I wouldn't use the word GET, when
it is not available to the application.
From: jorgen on 3 Jan 2008 13:38
jorgen wrote:
> Charlie Russel - MVP wrote:
>> No, the Application GETS 4 GB in x64. It it can't USE or SEE the 4GB
>> unless the application is compiled accordingly. But the memory address
>> space is allocated regardless. This is _different_ from 32-bit
>> Windows, where the application only GETS 2GB unless you boot with the
>> /3GB switch.
>
> That can very easily be misunderstood. I wouldn't use the word GET, when
> it is not available to the application.

"and every 32-bit application automatically has a full 4GB of memory
address space available to it. "

maybe i just misunderstood that part. I thought you claimed that all
applications would get 4GB with or without the LARGEADDRESSAWARE flag
From: Bo Persson on 3 Jan 2008 13:35
jorgen wrote:
:: Charlie Russel - MVP wrote:
::: No, the Application GETS 4 GB in x64. It it can't USE or SEE the
::: 4GB unless the application is compiled accordingly. But the
::: memory address space is allocated regardless. This is _different_
::: from 32-bit Windows, where the application only GETS 2GB unless
::: you boot with the /3GB switch.
::
:: That can very easily be misunderstood. I wouldn't use the word
:: GET, when it is not available to the application.

But it IS available, it is up to the application to be able to use it.


Bo Persson


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: BSOD, mismanaging system PTEs, x64/WinServer2003?
Next: VSS problem on an Windows 2003 Enterprise R2 SP2 Server