Сколько видит х32 Виндовс и можно ли эту планку поднять ?

Сколько видит х32 XP Виндовс оперативной памяти ?
Говорят что только 3 гига,можно ли как то увеличить эту планку на х32 системе ?
Спасибо.

У меня из 4-х виделось 3.3, вроде никак не поднять планку.

О.о а Хр х32 то зачем?

Никак не поднять ;) вот если заменить XP на 2003-й сервер, что сделал я еще 2 года назад, то 4096 мб RAM будет доступно спокойно ;) к тому же, сервер этот понадежнее куда - у меня сейчас аптайм 8 суток и никаких проблем =)

Есть проги которые сами жрут оперативы около 300+ МБ но распознают около 6гб.

When 4 GB or more of memory is installed, why does Windows report less memory than is actually installed?

With the PC/Intel architecture, most PCI devices can't have their address spaces mapped above the 4 GB limit, so PCI address space is allocated below 4 GB. This means that any machine with 4 GB or more of physical memory has some of its physical memory "overlaid" by the PCI address space.

If the memory controller of the machine supports remapping the overlaid physical memory to an address above 4 GB and if the processor is capable of accessing memory above 4 GB and if the operating system supports memory above 4 GB, then all of the physical memory is still usable. If any of the above are not true, then the "overlaid" memory is not accessable and the operating system will report less physical memory than is actually installed. For example a Windows server with 4 GB of physical memory installed might report only 3.5 GB of memory.

In the case of IXS hardware, only type-model 2892-001 and 2892-002 are capable of accessing memory addresses above 4 GB. In the case of IXA attached xSeries servers, check your xSeries server processor and memory controller specifications to determine if the server can access memory addresses above 4 GB. (Most xSeries servers are capable of accessing memory addresses above 4 GB.)

The versions of Windows Server that are supported on IXS and IXA attached xSeries servers and that support memory above 4 GB are Windows 2000 Advanced Server and Windows Server 2003 Enterprise Edition. The versions of Windows Server that are supported on IXS and IXA attached xSeries servers and that do not support memory above 4 GB are Windows 2000 Server, Windows Server 2003 Standard Edition and Windows Server 2003 Web Edition.

If your IXS or xSeries server can access memory addresses above 4 GB and the Windows version you are using supports over 4 GB of memory, but Windows still reports less physical memory than is actually installed, see Microsoft website Large memory support is available in Windows 2000 and Windows Server 2003 for information on how to configure Windows to address all of the physical memory that is available.


Large memory support is available in Windows Server 2003 and in Windows 2000
View products that this article applies to.


Article ID
:
283037
Last Review
:
June 17, 2005
Revision
:
8.1
This article was previously published under Q283037

SUMMARY
This article describes Physical Address Extension (PAE) and Address Windowing Extensions (AWE) and explains how they work together. This article also discusses the limitations of using memory beyond the 4-gigabyte (GB) range that is inherent to 32-bit operating systems.


MORE INFORMATION
PAE is the added ability of the IA32 processor to address more than 4 GB of physical memory. Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Datacenter Server, Microsoft Windows Server 2003, Enterprise Edition, and Microsoft Windows Server 2003, Datacenter Edition, can use PAE to take advantage of physical memory beyond 4 GB. To enable PAE, use the /PAE switch in the Boot.ini file.

Note Windows Server 2003, Enterprise Edition and Windows Server 2003, Datacenter Edition automatically enable PAE only if the server is using hot-add memory devices. In this case, you do not have to use the /PAE switch on a system that is configured to use hot-add memory devices. In all other cases, you must use the /PAE switch in the Boot.ini file to take advantage of memory over 4GB.

Typically, a process running under Windows 2000 or Windows Server 2003 can access up to 2 GB of memory address space (assuming the /3GB switch was not used) with some of the memory being physical memory and some being virtual memory. The more programs (and, therefore, more processes) that run, the more memory you commit up to the full 2 GB of address space.

When this situation occurs, the paging process increases dramatically and performance may be negatively impacted. The Windows 2000 and Windows Server 2003 memory managers use PAE to provide more physical memory to a program. This reduces the need to swap the memory of the page file and results in increased performance. The program itself is not aware of the actual memory size. All the memory management and allocation of the PAE memory is handled by the memory manager independently of the programs that run.

The preceding information is valid for programs that run when the /3GB switch is used. A program that requests 3 GB of memory is more likely to be able to have more of its memory remain in physical memory rather than be paged out. This increases the performance of programs that are capable of using the /3GB switch. The exception is when the /3GB switch is used in conjunction with the /PAE switch. In this case, the operating system does not use any memory in excess of 16 GB. This behavior is caused by kernel virtual memory space considerations. Thus, if the system restarts with the /3GB entry in the Boot.ini file, and the system has more than 16 GB of physical memory, the additional physical random access memory (RAM) is not used by the operating system. Restarting the computer without the /3GB switch enables the use of all the physical memory.

AWE is a set of application programming interfaces (APIs) to the memory manager functions that enables programs to address more memory than the 4 GB that is available through standard 32-bit addressing. AWE enables programs to reserve physical memory as non-paged memory and then to dynamically map portions of the non-paged memory to the program's working set of memory. This process enables memory-intensive programs, such as large database systems, to reserve large amounts of physical memory for data without having to be paged in and out of a paging file for usage. Instead, the data is swapped in and out of the working set and reserved memory is in excess of the 4 GB range. Additionally, the range of memory in excess of 4 GB is exposed to the memory manager and the AWE functions by PAE. Without PAE, AWE cannot reserve memory in excess of 4 GB.

The following is an example of a Boot.ini file where the PAE switch has been added:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /PAE


Warning The contents of your Boot.ini file will vary based upon your configuration. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
317526 (http://support.microsoft.com/kb/317526/) How to edit the Boot.ini file in Windows Server 2003
To summarize, PAE is a function of the Windows 2000 and Windows Server 2003 memory managers that provides more physical memory to a program that requests memory. The program is not aware that any of the memory that it uses resides in the range greater than 4 GB, just as a program is not aware that the memory it has requested is actually in the page file.

AWE is an API set that enables programs to reserve large chunks of memory. The reserved memory is non-pageable and is only accessible to that program. For more information about AWE and PAE, click the following article number to view the article in the Microsoft Knowledge Base:
268363 (http://support.microsoft.com/kb/268363/) Intel Physical Addressing Extensions (PAE) in Windows 2000
For more information, visit the following Microsoft Web sites:
http://msdn.microsoft.com/library/psdk/sql...server_1fnd.htm (http://msdn.microsoft.com/library/psdk/sql/ad_1_server_1fnd.htm)
http://msdn.microsoft.com/library/default..../awewindata.asp (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dngenlib/html/awewindata.asp)
If you add more memory to the system, it is possible that the BIOS will recognize the full amount of physical RAM that is installed in the server but that Windows will recognize only a part of the RAM. If the server has a redundant memory feature or a memory mirroring feature that is enabled, the full complement of memory may not be visible to Windows. Redundant memory provides the system with a failover memory bank when a memory bank fails. Memory mirroring splits the memory banks into a mirrored set. Both features are enabled or disabled in the BIOS and cannot be accessed through Windows. To modify the settings for these features, you may have to refer to the system user manual or the OEM Web site. Alternatively, you may have to contact the hardware vendor.

For example, if you are running a system that has 4 GB of RAM installed and you then add 4 GB of additional RAM, Windows may recognize only 4 GB of physical memory or possibly 6 GB instead of the full 8 GB. The redundant memory feature or the memory mirroring feature may be enabled on the new memory banks without your knowledge. These symptoms are similar to the symptoms that occur when you do not add the /PAE switch to the Boot.ini file.

APPLIES TO


•
Microsoft Windows Server 2003, Standard Edition
•
Microsoft Windows Server 2003, Enterprise Edition
•
Microsoft Windows Server 2003, Datacenter Edition
•
Microsoft Windows 2000 Advanced Server
•
Microsoft Windows 2000 Datacenter Server




Back to the top



Keywords: 
kbenv kbinfo kbmemory KB283037

виндовс или приложения?
если приложения, то:
- тк указатель = 32 бита, то им можно указывать на 2^32 = 4GB.
- чтобы быстро работали системные вызовы из приложений к винде, они пришли к решению разделить память на два кусочка - один для "винды", другой для приложений, чтобы не приходилось очищать тлб кэши(связывают странички виртуальной памяти с физической) и поэтому приходиться довольствоваться распределением 2GB/2GB.. либо с опцией /3GB получаем 3 гига виртуальной памяти для приложения..
- AWE наврятли ваши приложения используют :)
вот вроде простым языком расписал :)
если для операционки, то:
пост повыше на английском вещает про /PAE в бут.ини :)

Лутше линуху ставить для сервака

а чем отличается линукс от windows server 2003 SP3 ? 0_O

sahas: а чем отличается линукс от windows server 2003 SP3 ? 0_O

ставь 64 битную систему, я тоже столкнулся с такой проблемой, виста или хп 64бит и никаких проблем.

У нее просто проц не 64 битный , че вы заладили , наивные...

Я поставила виндовс хп х64,но т.к у меня нету нужных дрейверов для программ,которыми я пользуюсь,а в интернете их тоже нету-пришлось перевести обратно на х32....
значит Х32 видит 4ГБ ОПЕРАТИВНОЙ ПАМЯТИ !?ТОесть я могу спокойно ставить 4 гб оперативки ?
А сколько видит Виндовс сервер 2003 максимум ?

2003 спокойно видет 8гб насчет 16гб утверждать не буду ,но если материнка определит то думаю проблем небудет.

а х32 хп видит до 4 гб включительно ?

Нет. 3,5 (и то не факт) + тока для явы 1,5 максимум выдаёт...

Для явы лучше 64 (если расчитываешь на высокий онлайн)
Больше 70 человек, сервак уже задыхается в собственном поту...

Откапал старый журнал CHIP посещённый виндовсу сервер 2003
Виндов сервер 2003 нескольких видов, и у каждого свои пределы, вот отсканирывал:
<a href="http://dump.ru/file/1307631" title="Скачать файл Изображение.jpg"><img src="http://dump.ru/viewer/preview/biggest/1307631/" alt="Скачать файл Изображение.jpg" /></a>

Откапал старый журнал CHIP посещённый виндовсу сервер 2003
Виндов сервер 2003 нескольких видов, и у каждого свои пределы, вот отсканирывал:
http://dump.ru/file/1307631