Windows 2008 R2 Sp2
I know that from looking at the web that Microsoft are not intending to release a Service Pack 2 for Windows 7. It's seems that this is a ploy to get people to upgrade to Windows 8. But for Windows Server 2008 R2, as they planning to release a Service Pack 2? Upgrade Windows Server 2003 SP2 to Windows Server 2008 R2 Notes - Microsoft is at it again. Server 2003 is last day of support is next.
A version of the Windows NT operating system | |
Screenshot of Windows Server 2008 R2 Datacenter Service Pack 1 | |
Developer | Microsoft |
---|---|
OS family | Microsoft Windows |
Working state | Current |
Source model |
|
Released to manufacturing | July 22, 2009; 10 years ago |
General availability | October 22, 2009; 9 years ago[1] |
Latest release | 6.1 (Build 7601: Service Pack 1) / February 22, 2011; 8 years ago[2] |
Marketing target | Business |
Update method | Windows Update, Windows Server Update Services, SCCM |
Platforms | x86-64, Itanium |
Kernel type | Hybrid (Windows NT kernel) |
Default user interface | Windows shell (Graphical) |
License | Commercial software (Retail, volume licensing, Microsoft Software Assurance) |
Preceded by | Windows Server 2008 (2008) |
Succeeded by | Windows Server 2012 (2012) |
Official website | technet.microsoft.com/en-us/windowsserver/bb310558 |
Support status | |
Mainstream support ended on 13 January 2015.[3] Extended support will end on 14 January 2020 along with Windows 7 (for Windows Server 2008 R2 Service Pack 1). | |
Articles in the series |
Windows Server 2008 R2 is a serveroperating system produced by Microsoft. It was released to manufacturing on July 22, 2009[4] and became generally available on October 22, 2009.[5]
Enhancements include new functionality for Active Directory, new virtualization and management features, version 7.5 of the Internet Information Servicesweb server and support for up to 256[6] logical processors. It is built on the same kernel used with the client-oriented Windows 7, and is the first 64-bit–only server operating system released from Microsoft.
Seven editions of Windows Server 2008 R2 were released: Foundation, Standard, Enterprise, Datacenter, Web, HPC Server and Itanium, as well as Windows Storage Server 2008 R2. A home server variant called Windows Home Server 2011 was also released. It was succeeded by Windows Server 2012.
History[edit]
Microsoft introduced Windows Server 2008 R2 at the 2008 Professional Developers Conference as the server variant of Windows 7.
On January 7, 2009, a beta release of Windows Server 2008 R2 was made available to subscribers of Microsoft's TechNet and MSDN programs, as well as those participating in the Microsoft Connect program for Windows 7. Two days later, the beta was released to the public via the Microsoft Download Center.[7]
On April 30, 2009, the release candidate was made available to subscribers of TechNet and MSDN.[8] On May 5, 2009, the release candidate was made available to the general public via the Microsoft download center.[9]
According to Windows Server Blog,[10] the following are the dates of the year 2009 when Microsoft Windows Server 2008 R2 has been made available to various distribution channels:
- OEMs received Windows Server 2008 R2 in English and all language packs on July 29. The remaining languages were available around August 11.
- Independent software vendor (ISV) and independent hardware vendor (IHV) partners have been able to download Windows Server 2008 R2 from MSDN starting on August 14.
- IT professionals with TechNet subscriptions were able to download Windows Server 2008 R2 and obtain product keys for English, French, German, Italian, and Spanish variants beginning August 14 and all remaining languages beginning August 21.
- Developers with MSDN subscriptions have been able to download and obtain product keys for Windows Server 2008 R2 in English, French, German, Italian, and Spanish starting August 14 and all remaining languages starting August 21.
- Microsoft Partner Program (MPP) gold/certified members were able to download Windows Server 2008 R2 through the MPP portal on August 19.
- Volume licensing customers with an existing Software Assurance (SA) contracts were able to download Windows Server 2008 R2 on August 19 via the Volume License Service Center.
- Volume licensing customers without an SA were able to purchase Windows Server 2008 R2 through volume licensing by September 1.
Additionally, qualifying students have been able to download Windows Server 2008 R2 Standard edition in 15 languages from the Microsoft Imagine program (known as DreamSpark at the time).[11]
Microsoft has announced that Server 2008 R2 will be the last version of Windows supporting the Itanium architecture, with its extended support ending earlier than for the regular non-Itanium edition or 'until July 10, 2018.'[12][13][14]
New features[edit]
A reviewer guide published by the company describes several areas of improvement in R2.[15] These include new virtualization capabilities (Live Migration, Cluster Shared Volumes using Failover Clustering and Hyper-V), reduced power consumption, a new set of management tools and new Active Directory capabilities such as a 'recycle bin' for deleted objects. IIS 7.5 has been added to this release which also includes updated FTP server services. Security enhancements include encrypted clientless authenticated VPN services through DirectAccess for clients using Windows 7, and the addition of DNSSEC support for DNS Server Service. Even though DNSSEC as such is supported, only one signature algorithm is available:[16] #5 / RSA/SHA-1. Since many zones use a different algorithm – including the root zone – this means that in reality Windows still can't serve as a recursive resolver.
The DHCP server supports a large number of enhancements[17] such as MAC address-based control filtering, converting active leases into reservations or Link Layer based filters, DHCppP Name protection for non-Windows machines to prevent name squatting, better performance through aggressive lease database caching, DHCP activity logging, auto-population of certain network interface fields, a wizard for split-scope configuration, DHCP Server role migration using WSMT, support for DHCPv6 Option 15 (User Class) and Option 32 (Information Refresh Time). The DHCP server runs in the context of the Network Service account which has fewer privileges to reduce potential damage if compromised.
Windows Server 2008 R2 supports up to 64 physical processors[18] or up to 256 logical processors per system. (Only the Datacenter and Itanium editions can take advantage of the capability of 64 physical processors. Enterprise, the next-highest edition after those two, can only use 8.)[19] When deployed in a file server role, new File Classification Infrastructure services allow files to be stored on designated servers in the enterprise based on business naming conventions, relevance to business processes and overall corporate policies.[20]
Server Core includes a subset of the .NET Framework, so that some applications (including ASP.NET web sites and Windows PowerShell 2.0) can be used.
Performance improvement was a major area of focus for this release; Microsoft has stated that work was done to decrease boot time, improve the efficiency of I/O operations while using less processing power, and generally improve the speed of storage devices, especially iSCSI.
Active Directory has several new features when raising the forest and domain functional levels[21] to Windows Server 2008 R2: Two added features are Authentication Mechanism Assurance and Automatic SPN Management. When raising the forest functional level, the Active Directory recycle bin feature is available and can be enabled using the Active Directory Module for PowerShell.[22]
Service Pack[edit]
On February 9, 2011, Microsoft officially released Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2 to OEM partners. Apart from bug fixes, it introduces two new major functions, RemoteFX and Dynamic Memory. RemoteFX enables the use of graphics hardware support for 3D graphics in a Hyper-V based VM. Dynamic Memory makes it possible for a VM to only allocate as much physical RAM as is needed temporarily for its execution. On February 16, SP1 became available for MSDN and TechNet subscribers as well as volume licensing customers. As of February 22, SP1 is generally available for download via the Microsoft Download Center and available on Windows Update.[23]
System requirements[edit]
System requirements for Windows Server 2008 R2 are as follows:[24]
- Processor
- 1.4 GHz x86-64 or Itanium 2 processor
- Memory
- Minimum: 512 MBRAM (may limit performance and some features)
- Recommended: 2 GBRAM
- Maximum: 8 GB RAM (Foundation), 32 GB RAM (Standard), or 2 TB RAM (Enterprise, Datacenter and Itanium)
- Display
- Super VGA (800×600) or higher
- Disk Space Requirements
- Minimum (editions higher than Foundation): 32 GB or more
- Minimum (Foundation edition) 10 GB or more.
- Computers with more than 16 GB of RAM require more disk space for paging and dump files.[24]
- Other
- DVD drive, keyboard and mouse, Internet access (required for updates and online activation)
Editions[edit]
Features | Foundation | Standard | Web | HPC | Enterprise | Datacenter | Itanium |
---|---|---|---|---|---|---|---|
Maximum RAM on x86-64 | 8 GB | 32 GB | 32 GB | 256 GB | 2 TB | 2 TB | 2 TB |
Maximum physical CPUs | 1 | 4 | 4 | 4 | 8 | 64 | 64 |
Failover cluster nodes (Nodes) | N/A | N/A | N/A | N/A | 16 | 16 | 8 |
Cross-file replication (DFS-R) | No | Yes | Yes | Yes | Yes | Yes | Yes[26] |
Fault tolerant memory sync | No | No | No | No | Yes | Yes | Yes |
Memory modules: Hot addition | No | No | No | No | Yes | Yes | Yes |
Memory modules: Hot replacement | No | No | No | No | No | Yes | Yes |
CPUs: Hot addition | No | No | No | No | No | Yes | Yes |
CPUs: Hot replacement | No | No | No | No | No | Yes | Yes |
IAS connection | 10 | 50 | No | No | Unlimited | Unlimited | 2 |
Remote Desktop Services connections | 50 | 250 | No | No | Unlimited | Unlimited | No |
RRAS connections | 50 | 250 | No | 250 | Unlimited | Unlimited | No |
Virtual image use rights | Forbidden | Host + 1 VM | 1 VM | Host + 1 VM | Host + 4 VMs | Unlimited | Unlimited |
Features | Foundation | Standard | Web | HPC | Enterprise | Datacenter | Itanium |
See also[edit]
References[edit]
- ^http://www.microsoft.com/presspass/features/2009/Jun09/06-02SteveGuggenheimer.mspx
- ^http://blogs.technet.com/windowsserver/archive/2009/07/22/windows-server-2008-r2-rtm.aspx
- ^Microsoft. 'Windows Server 2008 R2 Lifecycle Policy'. Microsoft. Retrieved 2012-09-01.
- ^Server and Cloud Platform Team (2009-07-22). 'Windows Server 2008 R2 Reaches the RTM Milestone!'. Blogs.technet.com. Retrieved 2011-06-15.
- ^'Windows 7 and Windows Server 2008 R2 Timelines Shared at Computex'. News Center. Taipei, Taiwan: Microsoft. June 3, 2009.
- ^'Windows Server 2008 R2 Datacenter Edition Overview'. Microsoft.com. Retrieved 2011-06-15.
- ^Emil Protalinski. 'Windows 7 public beta is available now'.
- ^'Announcing Windows Server 2008 R2 Release Candidate (RC)'. Microsoft TechNet.
- ^'Download Windows Server 2008 R2 RC .iso images (May2009)'. Microsoft.
- ^House, Crissy (22 July 2009). 'When to expect Windows Server 2008 R2 RTM'. Windows Server Blog. Microsoft.
- ^'Windows Server 2008 R2 on DreamSpark'. Microsoft.
- ^'Windows Server 2008 R2 to Phase Out Itanium'. Windows Server Blog.
Why the change? The natural evolution of the x86 64-bit (“x64”) architecture has led to the creation of processors and servers which deliver the scalability and reliability needed for today’s “mission-critical” workloads.
- ^'Microsoft ending support for Itanium'.
SQL Server 2008 R2 and Visual Studio 2010 are also the last versions to support Itanium.
- ^'Microsoft Dropping Itanium Support -- Redmond Channel Partner'. Redmond Channel Partner. Retrieved 2018-05-14.
- ^'Windows Server 2008 R2 Reviewers Guide'. Microsoft. November 2008. Retrieved 2009-08-31.
- ^'Understanding DNSSEC in Windows'. Technet.microsoft.com. 2009-10-07. Retrieved 2011-06-15.
- ^'New features in DHCP for Windows Server 2008 R2 / Windows 7'. Blogs.technet.com. Retrieved 2011-06-15.
- ^'Windows Server 2008 R2: Scalability for the Enterprise Customer'. Microsoft.com. Retrieved 2011-06-15.
- ^'Windows7 and Windows Server 2008 R2 support more than 64 Processors in one System'. Microsoft. November 2008. Retrieved 2009-03-06.
- ^'R2: How Would You Manage Without It?'. MSDN Blogs. Retrieved 2009-04-30.
- ^'Appendix of Functional Level Features'. Microsoft Technet. Retrieved 2009-10-06.
- ^'Server 2008 R2: Active Directory Functional Levels'. Praetorian Prefect. Retrieved 2009-10-06.
- ^'Announcing Availability of Windows 7 and Windows Server 2008 R2 SP1'.
- ^ ab'Windows Server 2008 R2: System Requirements'. Microsoft.com. Retrieved 2011-06-15.
- ^'Windows Server 2008 R2 Editions Comparison by Technical Specifications'. Archived from the original on 22 December 2010.
- ^Archiveddocs. 'What's New in Distributed File System'. technet.microsoft.com. Retrieved 2 April 2018.
External links[edit]
- Windows Server 2008 R2 on Microsoft TechNet
- Thurrott, Paul (6 October 2010). 'Windows Server 2008 R2 Preview'. Supersite for Windows. Penton.
This topic describes the memory limits for supported Windows and Windows Server releases.
Limits on memory and address space vary by platform, operating system, and by whether the IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and 4-gigabyte tuning (4GT) are in use. IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the /LARGEADDRESSAWARE linker option.
4-gigabyte tuning (4GT), also known as application memory tuning, or the /3GB switch, is a technology (only applicable to 32 bit systems) that alters the amount of virtual address space available to user mode applications. Enabling this technology reduces the overall size of the system virtual address space and therefore system resource maximums. For more information, see What is 4GT.
Limits on physical memory for 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit Windows systems to use more than 4 GB of physical memory.
Memory and Address Space Limits
The following table specifies the limits on memory and address space for supported releases of Windows. Unless otherwise noted, the limits in this table apply to all supported releases.
Windows Server 2008 Sp2 End Of Life
Memory type | Limit on X86 | Limit in 64-bit Windows |
---|---|---|
User-mode virtual address space for each 32-bit process | 2 GB Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT | 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default) 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set |
User-mode virtual address space for each 64-bit process | Not applicable | With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default): x64: 8 TB Intel Itanium-based systems: 7 TB Windows 8.1 and Windows Server 2012 R2: 128 TB 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared |
Kernel-mode virtual address space | 2 GB From 1 GB to a maximum of 2 GB with 4GT | 8 TBWindows 8.1 and Windows Server 2012 R2: 128 TB |
Paged pool | 384 GB or system commit limit, whichever is smaller. Windows 8.1 and Windows Server 2012 R2: 15.5 TB or system commit limit, whichever is smaller. Windows Server 2008 R2, Windows 7, Windows Server 2008 and Windows Vista: Limited by available kernel-mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value. Windows Home Server and Windows Server 2003: 530 MB Windows XP: 490 MB | 384 GB or system commit limit, whichever is smaller Windows 8.1 and Windows Server 2012 R2: 15.5 TB or system commit limit, whichever is smaller. Windows Server 2008 R2, Windows 7, Windows Server 2008 and Windows Vista: 128 GB or system commit limit, whichever is smaller Windows Server 2003 and Windows XP: Up to 128 GB depending on configuration and RAM. |
Nonpaged pool | 75% of RAM or 2 GB, whichever is smaller. Windows 8.1 and Windows Server 2012 R2: RAM or 16 TB, whichever is smaller (address space is limited to 2 x RAM). Windows Vista: Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value. Windows Home Server, Windows Server 2003 and Windows XP: 256 MB, or 128 MB with 4GT. | RAM or 128 GB, whichever is smaller (address space is limited to 2 x RAM) Windows 8.1 and Windows Server 2012 R2: RAM or 16 TB, whichever is smaller (address space is limited to 2 x RAM). Windows Server 2008 R2, Windows 7 and Windows Server 2008: 75% of RAM up to a maximum of 128 GB Windows Vista: 40% of RAM up to a maximum of 128 GB. Windows Server 2003 and Windows XP: Up to 128 GB depending on configuration and RAM. |
System cache virtual address space (physical size limited only by physical memory) | Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value. Windows 8.1 and Windows Server 2012 R2: 16 TB. Windows Vista: Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value. Windows Home Server, Windows Server 2003 and Windows XP: 860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT. | Always 1 TB regardless of physical RAM Windows 8.1 and Windows Server 2012 R2: 16 TB. Windows Server 2003 and Windows XP: Up to 1 TB depending on configuration and RAM. |
Physical Memory Limits: Windows 10
The following table specifies the limits on physical memory for Windows 10.
Version | Limit on X86 | Limit on X64 |
---|---|---|
Windows 10 Enterprise | 4 GB | 6 TB |
Windows 10 Education | 4 GB | 2 TB |
Windows 10 Pro for Workstations | 4 GB | 6 TB |
Windows 10 Pro | 4 GB | 2 TB |
Windows 10 Home | 4 GB | 128 GB |
Physical Memory Limits: Windows Server 2016
The following table specifies the limits on physical memory for Windows Server 2016.
Version | Limit on X64 |
---|---|
Windows Server 2016 Datacenter | 24 TB |
Windows Server 2016 Standard | 24 TB |
Physical Memory Limits: Windows 8
The following table specifies the limits on physical memory for Windows 8.
Windows 2008 R2 Sp2 End Of Support
Version | Limit on X86 | Limit on X64 |
---|---|---|
Windows 8 Enterprise | 4 GB | 512 GB |
Windows 8 Professional | 4 GB | 512 GB |
Windows 8 | 4 GB | 128 GB |
Physical Memory Limits: Windows Server 2012
The following table specifies the limits on physical memory for Windows Server 2012. Windows Server 2012 is available only in X64 editions.
Version | Limit on X64 |
---|---|
Windows Server 2012 Datacenter | 4 TB |
Windows Server 2012 Standard | 4 TB |
Windows Server 2012 Essentials | 64 GB |
Windows Server 2012 Foundation | 32 GB |
Windows Storage Server 2012 Workgroup | 32 GB |
Windows Storage Server 2012 Standard | 4 TB |
Hyper-V Server 2012 | 4 TB |
Physical Memory Limits: Windows 7
The following table specifies the limits on physical memory for Windows 7.
Version | Limit on X86 | Limit on X64 |
---|---|---|
Windows 7 Ultimate | 4 GB | 192 GB |
Windows 7 Enterprise | 4 GB | 192 GB |
Windows 7 Professional | 4 GB | 192 GB |
Windows 7 Home Premium | 4 GB | 16 GB |
Windows 7 Home Basic | 4 GB | 8 GB |
Windows 7 Starter | 2 GB | N/A |
Physical Memory Limits: Windows Server 2008 R2
The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.
Version | Limit on X64 | Limit on IA64 |
---|---|---|
Windows Server 2008 R2 Datacenter | 2 TB | |
Windows Server 2008 R2 Enterprise | 2 TB | |
Windows Server 2008 R2 for Itanium-Based Systems | 2 TB | |
Windows Server 2008 R2 Foundation | 8 GB | |
Windows Server 2008 R2 Standard | 32 GB | |
Windows HPC Server 2008 R2 | 128 GB | |
Windows Web Server 2008 R2 | 32 GB |
Physical Memory Limits: Windows Server 2008
The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.
Version | Limit on X86 | Limit on X64 | Limit on IA64 |
---|---|---|---|
Windows Server 2008 Datacenter | 64 GB | 1 TB | |
Windows Server 2008 Enterprise | 64 GB | 1 TB | |
Windows Server 2008 HPC Edition | 128 GB | ||
Windows Server 2008 Standard | 4 GB | 32 GB | |
Windows Server 2008 for Itanium-Based Systems | 2 TB | ||
Windows Small Business Server 2008 | 4 GB | 32 GB | |
Windows Web Server 2008 | 4 GB | 32 GB |
Physical Memory Limits: Windows Vista
The following table specifies the limits on physical memory for Windows Vista.
Version | Limit on X86 | Limit on X64 |
---|---|---|
Windows Vista Ultimate | 4 GB | 128 GB |
Windows Vista Enterprise | 4 GB | 128 GB |
Windows Vista Business | 4 GB | 128 GB |
Windows Vista Home Premium | 4 GB | 16 GB |
Windows Vista Home Basic | 4 GB | 8 GB |
Windows Vista Starter | 1 GB |
Physical Memory Limits: Windows Home Server
Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.
Physical Memory Limits: Windows Server 2003 R2
The following table specifies the limits on physical memory for Windows Server 2003 R2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
Version | Limit on X86 | Limit on X64 |
---|---|---|
Windows Server 2003 R2 Datacenter Edition | 64 GB (16 GB with 4GT) | 1 TB |
Windows Server 2003 R2 Enterprise Edition | 64 GB (16 GB with 4GT) | 1 TB |
Windows Server 2003 R2 Standard Edition | 4 GB | 32 GB |
Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)
The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 2 (SP2). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
Version | Limit on X86 | Limit on X64 | Limit on IA64 |
---|---|---|---|
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition | 64 GB (16 GB with 4GT) | 1 TB | 2 TB |
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition | 64 GB (16 GB with 4GT) | 1 TB | 2 TB |
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition | 4 GB | 32 GB |
Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)
The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 1 (SP1). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
Version | Limit on X86 | Limit on X64 | Limit on IA64 |
---|---|---|---|
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition | 64 GB (16 GB with 4GT) | X64 1 TB | 1 TB |
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition | 64 GB (16 GB with 4GT) | X64 1 TB | 1 TB |
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition | 4 GB | 32 GB |
Physical Memory Limits: Windows Server 2003
The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
Version | Limit on X86 | Limit on IA64 |
---|---|---|
Windows Server 2003, Datacenter Edition | 64 GB (16 GB with 4GT) | 512 GB |
Windows Server 2003, Enterprise Edition | 64 GB (16 GB with 4GT) | 512 GB |
Windows Server 2003, Standard Edition | 4 GB | |
Windows Server 2003, Web Edition | 2 GB | |
Windows Small Business Server 2003 | 4 GB | |
Windows Compute Cluster Server 2003 | 32 GB | |
Windows Storage Server 2003, Enterprise Edition | 8 GB | |
Windows Storage Server 2003 | 4 GB |
Physical Memory Limits: Windows XP
The following table specifies the limits on physical memory for Windows XP.
Version | Limit on X86 | Limit on X64 | Limit on IA64 |
---|---|---|---|
Windows XP | 4 GB | 128 GB | 128 GB (not supported) |
Windows XP Starter Edition | 512 MB | N/A | N/A |
Physical Memory Limits: Windows Embedded
The following table specifies the limits on physical memory for Windows Embedded.
Version | Limit on X86 | Limit on X64 |
---|---|---|
Windows XP Embedded | 4 GB | |
Windows Embedded Standard 2009 | 4 GB | |
Windows Embedded Standard 7 | 4 GB | 192 GB |
How graphics cards and other devices affect memory limits
Devices have to map their memory below 4 GB for compatibility with non-PAE-aware Windows releases. Therefore, if the system has 4GB of RAM, some of it is either disabled or is remapped above 4GB by the BIOS. If the memory is remapped, X64 Windows can use this memory. X86 client versions of Windows don’t support physical memory above the 4GB mark, so they can’t access these remapped regions. Any X64 Windows or X86 Server release can.
Causes of Butt crack rash: Contact dermatitis. Atopic dermatitis. Genital herpes. Keratosis pilaris. Jock itch (ringworm). Lichen sclerosus. Candida skin infection. Itchy rash in butt crack. Butt crack rashes can be red, clustered or single bumps that are itchy. They can appear on the butt crack, near the bum hole or even around the butt cheeks. Here are pictures to help you identify your symptoms. A red rash on skin can be caused by fungal or even viral infection, or even an STD.
X86 client versions with PAE enabled do have a usable 37-bit (128 GB) physical address space. The limit that these versions impose is the highest permitted physical RAM address, not the size of the IO space. That means PAE-aware drivers can actually use physical space above 4 GB if they want. For example, drivers could map the 'lost' memory regions located above 4 GB and expose this memory as a RAM disk.