The InformationWeek -- Blogs
Microsoft

Topics:   Microsoft

  • Email this page E-mail this page
  • Print this page Print this page
  • Bookmark and Share
  • icon

Windows Memory Has Physical, Design, and Marketing Limitations


Posted by Dave Methvin, Jul 25, 2008 03:40 PM

Mark Russinovich is one of Microsoft's best technical people, and he shows that every time he makes a blog post. This week he has a great post about the maximum supported memory in different versions of Windows. I thought I knew this story pretty well by now, but learned several new things about the limits--and the interesting reasons behind them.

The blog points to an MSDN article on memory limits, which does have a few quirks. As the commenter on that page points out, why should 64-bit Windows Vista Business (a desktop OS) allow 128 GB of RAM, but 64-bit Windows Server 2008 Standard top out at 32 GB? These are not limits born of technical reasons, but simply put there by the marketing department to convince one group or the other to pony up more money for what is essentially the same OS.

There is a way for 32-bit Windows to access memory using a technology called Physical Address Extensions (PAE). However, Microsoft intentionally limited desktop XP and Vista to 4 GB of RAM because many third-party drivers did not work properly when trying to access a memory address above 4 GB. Rather than risk crashes and system problems, Microsoft made it impossible to do.

This issue is compounded by hardware, particularly video boards, that map some of their memory into the 4 GB address space. Windows can do that fine, but in the process it maps some real RAM into the space above 4 GB where it won't be accessed by either applications or the operating system itself. That's why you'll often see Windows use much less than 4 GB RAM on 32-bit XP or Vista, even if you've installed 4 GB of physical memory.

I completely understand why Microsoft instituted the 4-GB limit for 32-bit desktop operating systems by default, but the finality of the implementation leaves something to be desired. Since this was ostensibly a patch to work around bad device drivers, it would have been good to have perhaps a boot.ini option that technical users could use to regain their missing memory. If I have well-behaved drivers, I should be able to use them with more than 4 GB on 32-bit Window -- or at the very least, get a full usable 4 GB of RAM.

One point that Russinovich didn't emphasize, perhaps because it's a hardware problem and not a Microsoft problem: many Pentium 4 northbridge chipsets for portables and desktops were limited until recently to addressing 4 GB of RAM. Even if you install a 64-bit version of Windows on these systems, you won't be able to install more than 4 GB of RAM, so it doesn't help much. Server chipsets allow a more generous helping of RAM as you might expect.

« OSCON, Pt. 4.2: openSUSE's Eleventh Hour (And Twelfth, And Thirteenth...) | Main | The View From Google Knol »



Sign Up Now
For InformationWeek News Alerts




This is a public forum. United Business Media and its affiliates are not responsible for and do not control what is posted herein. United Business Media makes no warranties or guarantees concerning any advice dispensed by its staff members or readers.

Community standards in this comment area do not permit hate language, excessive profanity, or other patently offensive language. Please be aware that all information posted to this comment area becomes the property of United Business Media LLC and may be edited and republished in print or electronic format as outlined in United Business Media's Terms of Service.

Important Note: This comment area is NOT intended for commercial messages or solicitations of business.




 

  1. Actors, Messages and Low Lock Contention for Java
  2. Of Course The Transformers are Multicore with SMT technology
  3. Find John Fast!!


Join The InformationWeek Group On LinkedIn


                           


  1. Why I'm Dropping Bing For Google
  2. 3G iPhone Burns User
  3. 64-Bit Firefox: What's Your Hurry?
  4. So Long, And Thanks, Google Earth, For All The Fish
  5. Windows 7 Pricing: How Much Lower?


  1. Review: Apple's Speedy iPhone 3GS
  2. Tech Innovation USA: From Resilient Networks To Self-Scheduling Devices
  3. How Government's Driving Cloud Computing Ahead
  4. Government As Early Adopter
  5. InformationWeek Analytics: Data Loss Prevention
  6. Strategic Security: Web Single Sign-On

 

  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag

  DECEMBER 2008
NOVEMBER 2008
OCTOBER 2008
SEPTEMBER 2008
AUGUST 2008
JULY 2008
JUNE 2008
MAY 2008
  APRIL 2008
MARCH 2008
FEBRUARY 2008
JANUARY 2008
DECEMBER 2007
NOVEMBER 2007
OCTOBER 2007
SEPTEMBER 2007