tag:blogger.com,1999:blog-3179219424167705024.post3103639650897371996..comments2024-03-21T00:12:28.185-07:00Comments on M365 and AZURE Blog: /3GB /USERVA=3030 parameters on the boot.iniOz Casey, Dedealhttp://www.blogger.com/profile/12226180672457689907noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3179219424167705024.post-82644034870969735232007-07-23T15:22:00.000-07:002007-07-23T15:22:00.000-07:00Here you go, the process seems to be done automati...Here you go, the process seems to be done automatically in 64 Bit Platform<BR/><BR/>On 64-bit versions of Windows Server 2003, the system automatically expands the virtual address space available to 32-bit user-mode programs linked with the /LARGEADDRESSAWARE option as needed without the /3GB boot parameter. On Windows Server 2003 RTM (without Service Pack 1), these 32-bit programs can access up to 3 GB of virtual address space. On Windows Server 2003 with Service Pack 1, they can access up to 4 GB of virtual address space. Native 64-bit user-mode programs can access up to 8 TB of virtual address space.<BR/>Booting with the /3GB parameter decreases the amount of kernel virtual address space on the system. In order to fit all of the kernel resources within the remaining 1 GB of virtual memory, NT-based Windows operating systems prior to Windows Vista, Windows restricts physical memory to frames below the 16 GB physical boundary and on Windows Vista, it restricts physical memory to frames below the 64 GB boundary. Because allocation of memory resources in Windows Vista is dynamic and, therefore, more adaptable and efficient, the system can devote more memory space to addressing, thereby accommodating more physical memory.<BR/>The following table lists the physical memory limits of 32-bit Windows operating systems that support the use of more than 4 GB of physical memory with and without the /3GB boot parameter.http://msdn2.microsoft.com/en-us/library/ms791558.aspx<BR/><BR/>best<BR/>ozOz Casey, Dedealhttps://www.blogger.com/profile/12226180672457689907noreply@blogger.comtag:blogger.com,1999:blog-3179219424167705024.post-45998494859821746892007-07-23T12:31:00.000-07:002007-07-23T12:31:00.000-07:00Does this still apply to Exchange 2007 on WIndows ...Does this still apply to Exchange 2007 on WIndows 2003 x64? It would be nice if Microsoft would add some info about e2k7 to the existing e2k3 article.Anonymousnoreply@blogger.com