S
Stephen Harris
Guest
Re: 4GB of RAM tunning in windows xp professional xp sp2 with 32bi
Re: 4GB of RAM tunning in windows xp professional xp sp2 with 32bi
Yman wrote:
> Thanks,
>
> How about if you have Qautro Process on windwos XP SP2 ?? will that work ?
>
> "John John (MVP)" wrote:
>
>> Yman wrote:
>>> Hi,
>>> I 'm running windows XP SP2 on thinkcentre M55 with Intel Core 2 Duo E6550
>>> @2.33GHZ. I'm trying to tune the memory on windows xp sp2 so I can have 4 GB
>>> of RAM.
>>> I can see the 4GB of RAM in the Bios, but windows can't see it because it's
>>> 32 bit. I found articles with Microsoft so you can tune the memory. I
>>> followed the documentation and modified the bootini. I didn't have much luck
>>> I can only see 3GB in window mean while 4GB in the BIOS.
>>>
>>> This is the bootini "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft
>>> Windows XP Professional" /fastdetect /PAE /3GB /Userva=2900
>>> /NoExecute=OptOut".
>>>
>>> Any Idea, note the machine supports DEP.
>> Windows XP doesn't fully support PAE and the 4GT RAM Tuning doesn't
>> really have anything to do with physical memory (RAM), it affects how
>> the Virtual Address Space is alloted between user mode processes and the
>> kernel-mode components, you should remove these switches from the
>> boot.ini file. Due to hardware addressing needs Windows XP 32-bits
>> cannot fully utilize 4GB of RAM and there is no way to overcome the
>> limitation.
>>
>> John
>>
>>
I wrote a long post on this topic,
http://groups.google.com/group/microsoft.public.windowsxp.general/msg/4b314125a4ac50c1
I'm not sure the /PAE switch actually has functionality.
Quoting the most relevant part of that post,
SH: Nonetheless, there is hope if you have *Windows XP Pro* 32-bit.
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
"Operating systems based on Microsoft Windows NT technologies have
always provided applications with a flat 32-bit virtual address space
that describes 4 gigabytes (GB) of virtual memory. The address space is
usually split so that 2 GB of address space is directly accessible to
the application and the other 2 GB is only accessible to the Windows
executive software.
The 32-bit versions of the Windows 2000 Advanced Server and Windows NT
Server 4.0, Enterprise Edition, operating systems were the first
versions of Windows to provide applications with a 3-GB flat virtual
address space, with the kernel and executive components using only 1 GB.
In response to customer requests, Microsoft has expanded the
availability of this support to the 32-bit version of Windows XP
Professional and all 32-bit versions of Windows Server 2003. ...
The virtual address space of processes and applications is still limited
to 2 GB unless the /3GB switch is used in the Boot.ini file. When the
physical RAM in the system exceeds 16 GB and the /3GB switch is used,
the operating system will ignore the additional RAM until the /3GB
switch is removed. This is because of the increased size of the kernel
required to support more Page Table Entries. The assumption is made that
the administrator would rather not lose the /3GB functionality silently
and automatically; therefore, this requires the administrator to
explicitly change this setting.
The /3GB switch allocates 3 GB of virtual address space to an
application that uses IMAGE_FILE_LARGE_ADDRESS_AWARE in the process
header. This switch allows applications to address 1 GB of additional
virtual address space above 2 GB.
The virtual address space of processes and applications is still limited
to 2 GB, unless the /3GB switch is used in the Boot.ini file. The
following example shows how to add the /3GB parameter in the Boot.ini
file to enable application memory tuning:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="????" /3GB
SH: I think shifting the extra 1GB of memory to applications
will in some situations result in fewer disk writes and
retrieval from data stored on the disk which is more efficient.
Re: 4GB of RAM tunning in windows xp professional xp sp2 with 32bi
Yman wrote:
> Thanks,
>
> How about if you have Qautro Process on windwos XP SP2 ?? will that work ?
>
> "John John (MVP)" wrote:
>
>> Yman wrote:
>>> Hi,
>>> I 'm running windows XP SP2 on thinkcentre M55 with Intel Core 2 Duo E6550
>>> @2.33GHZ. I'm trying to tune the memory on windows xp sp2 so I can have 4 GB
>>> of RAM.
>>> I can see the 4GB of RAM in the Bios, but windows can't see it because it's
>>> 32 bit. I found articles with Microsoft so you can tune the memory. I
>>> followed the documentation and modified the bootini. I didn't have much luck
>>> I can only see 3GB in window mean while 4GB in the BIOS.
>>>
>>> This is the bootini "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft
>>> Windows XP Professional" /fastdetect /PAE /3GB /Userva=2900
>>> /NoExecute=OptOut".
>>>
>>> Any Idea, note the machine supports DEP.
>> Windows XP doesn't fully support PAE and the 4GT RAM Tuning doesn't
>> really have anything to do with physical memory (RAM), it affects how
>> the Virtual Address Space is alloted between user mode processes and the
>> kernel-mode components, you should remove these switches from the
>> boot.ini file. Due to hardware addressing needs Windows XP 32-bits
>> cannot fully utilize 4GB of RAM and there is no way to overcome the
>> limitation.
>>
>> John
>>
>>
I wrote a long post on this topic,
http://groups.google.com/group/microsoft.public.windowsxp.general/msg/4b314125a4ac50c1
I'm not sure the /PAE switch actually has functionality.
Quoting the most relevant part of that post,
SH: Nonetheless, there is hope if you have *Windows XP Pro* 32-bit.
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
"Operating systems based on Microsoft Windows NT technologies have
always provided applications with a flat 32-bit virtual address space
that describes 4 gigabytes (GB) of virtual memory. The address space is
usually split so that 2 GB of address space is directly accessible to
the application and the other 2 GB is only accessible to the Windows
executive software.
The 32-bit versions of the Windows 2000 Advanced Server and Windows NT
Server 4.0, Enterprise Edition, operating systems were the first
versions of Windows to provide applications with a 3-GB flat virtual
address space, with the kernel and executive components using only 1 GB.
In response to customer requests, Microsoft has expanded the
availability of this support to the 32-bit version of Windows XP
Professional and all 32-bit versions of Windows Server 2003. ...
The virtual address space of processes and applications is still limited
to 2 GB unless the /3GB switch is used in the Boot.ini file. When the
physical RAM in the system exceeds 16 GB and the /3GB switch is used,
the operating system will ignore the additional RAM until the /3GB
switch is removed. This is because of the increased size of the kernel
required to support more Page Table Entries. The assumption is made that
the administrator would rather not lose the /3GB functionality silently
and automatically; therefore, this requires the administrator to
explicitly change this setting.
The /3GB switch allocates 3 GB of virtual address space to an
application that uses IMAGE_FILE_LARGE_ADDRESS_AWARE in the process
header. This switch allows applications to address 1 GB of additional
virtual address space above 2 GB.
The virtual address space of processes and applications is still limited
to 2 GB, unless the /3GB switch is used in the Boot.ini file. The
following example shows how to add the /3GB parameter in the Boot.ini
file to enable application memory tuning:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="????" /3GB
SH: I think shifting the extra 1GB of memory to applications
will in some situations result in fewer disk writes and
retrieval from data stored on the disk which is more efficient.