Nearly a year ago, I reported that I'd purchased a new laptop with the dual intentions of running Windows Vista Ultimate 64-bit and getting full use of 4GB of RAM. Unfortunately, I also had to report that while I did get Vista Ultimate 64-bit running, my HP NX6325 was able to use only 2.9GB of RAM. Since then, I've watched what might be called the "4GB frontier" and I have both good and bad news to report.
First, the bad news: Once you install Vista SP1 on your system, it's going to be a bit harder to figure out if your computer is indeed using the 4GB that you purchased. Prior to SP1, a look at the System applet on Vista showed how much memory your system was using, just as it had on Windows XP, Windows Server 2003, and Windows 2000. But for some mysterious reason, SP1 changed what the System applet shows from "memory Vista uses" to "memory your BIOS reports--irrespective of whether Vista can figure out how to use it." Why did Microsoft do this? No one to whom I've talked seems to have an answer, so come on, Microsoft, knock it off--reporting how much memory that I might have if only my OS could understand it but doesn't is just plain unfair. Why not do the right thing and fix this with the next Windows update?
Meanwhile, people wondering how much RAM their system really sees have a number of avenues. First, you can open an elevated command prompt and type
systeminfo | findstr /c:"Total Physical"
Or you can just open up Task Manager, click on the Performance tab, look under Physical Memory (MB), and read the number to the right of Total. Thus, in my NX6325's case, the System applet reports 4.0 gigs on the nose, while systeminfo and Task Manager report 2,943MB.
On to the good news: There are laptops that can deliver a full four gigs to 64-bit Vista. I've heard from three users of Lenovo's T61 ThinkPad that the T61 can easily accommodate and use four gigs with Vista (and yes, I did ask them if they verified that through Task Manager rather than the System applet). Many people who own the larger "mobile workstation" lines of laptops such as the Dell Vostro 1700 or the HP Pavillion DV9700T, tell me that they get access to all of their RAM with their systems. I like the larger systems, as they offer more space and can therefore accommodate a second hard disk. But they're of course heavier than the basic business laptops, and they just plain don't fit into many laptop bags, and so might not be the optimal choice for some.
After writing about my need to hit the four-gig frontier, many of you have written to ask me why on earth I need so much RAM. The answer: virtual machines (VMs), of course! With 2.9GB usable RAM, I can just squeeze a couple of Windows Server 2008 VMs and a Vista VM onto my system before it makes the painful transition from "useful computer" to "constantly paging system that takes 10 minutes to respond to a mouse click." I know that some of you also run VMs on your workstation, so while I'm on the topic, let me pass along a tip from one of my colleagues, Dan Holme. Dan tells me that the solid state "hard disks" that plug into an ExpressCard slot are fast enough to accommodate one large VM or a couple of smaller VMs, and by his report they make VMs run noticeably faster. I haven't had time to try that out yet, but I'm definitely going to soon--products like Lexar's 16GB SSD (solid state disk) run just a bit above $200, and 16GB would easily accommodate a Windows 2008 or Vista VM. Now all we need is a laptop that lets you outfit it with 16GB of RAM…
Reader Comments
So, the bottom line is that Microsoft still can't count past 3 ... hardly news, really. That's why people who need more RAM use *nix.
mflopez -April 02, 2008
Hardly valid, mflopez. Mark states clearly some laptops make 4GB available to Windows, so it's obviously a BIOS thing. Your precious *nix won't even work on some newer laptops.
TheLanMan -April 02, 2008
I have a Lenovo's T61 ThinkPad with 4 GB or RAM, I have Vista SP1 installed, but I can see only 3 GB.
C:\>systeminfo | findstr /c:"Total Physical"
Total Physical Memory: 3,069 MB
gtopala@hotmail.com -April 02, 2008
My Dell XPX M1530 running Vista SP 1 sees all 4 GB.
C:\>systeminfo | findstr /c:"Total Physical"
Total Physical Memory: 4,093MB
yardemus -April 02, 2008
It's a combination of the BIOS and the video card. The video card is mapping itself into the 4GB addressable memory space in the system, effectively blocking access to the physicak memory in the machine. The 4GB is there, it's either the system BIOS or the video BIOS that's wrecking havoc.
jimsj -April 02, 2008
BIOS, video and chipset. Video borads can "steal" memory, but if BIOS and the chipset can't deal then you will be stuck <4GB. My Compaq 6715b (AMD chipset) will see all 4GB. Intel boards seem to have more trouble with the >3GB thing in my experience.
jb7706 -April 02, 2008
I quess I don't understand the problem. I have a Dell 1501. I replaced standard 2GB memory with 4GB (not authorized). I first ran XP 64 and then upgraded to Vista 64 because of support for ATT wireless drivers. This is a rock solid system configuration that Device Mgr thinks it has 4GB and task manager says 3.9 GB. There is a trick to finding drivers.
elarsen -April 02, 2008
I tried it with a 32 bit Windows Vista using PAE and 4GT. My asus p5B motherboard with the latest bios has a "memory remap" feature which I enabled. This then allowed the BIOS to see all 4GB where as if it was disabled it only saw what ever was shown in Performance montior of task manager, which is ~3GB.
However, whenever memory remap is enabled, Vista(SP1) only uses 2GB but the system applet still shows 4GB. Withouth memory remap, Vista sees 3GB and so does the BIOS.
Before I updated to the latest BIOS however, the BIOS only sees 2GB with the memory remap feature enable. Obviously they've fixed that with the latest BIOS but Vist still sees only 2GB.
j3rrry -April 02, 2008
Apparent from video card that is steeling some memory there is an issue with memory controller being 32bit and thus not able to see all the 4G of memory, though you may have a 64 bit capable processor.
levies,spap -April 03, 2008
I've been running 4GB's on my Asus V1S laptop since August. However, I choose Windows Server 2008 64bit as my Operating System. There are many online guides that describe how to switch this server OS to a "workstation" and I can easily say this is the best OS Microsoft has ever released.
As for the Asus V1S, another benefit of this notebook is that the drive bay is swappable so I was able to purchase a second hard drive which now contains all my VM images and this has really helped the performance with all VM development work. In addition, the eSATA port allows for an additional external SATA drive to be connected if even more VM storage and access is needed.
Good luck
cipher7 -April 03, 2008
Thanks again Mark,
The T61p can now support 8GB of RAM - thanks to Kingstons new 4GB Chips.
Read more here
http://blogs.technet.com/keithcombs/archive/2008/06/04/my-lenovo-thinkpad-t61p-now-has-8gb-of-ram.aspx
and here
http://www.ec.kingston.com/ecom/configurator_new/modelsinfo.asp?SysID=47204&mfr=Lenovo&model=ThinkPad+T61p+645
7&root=us&LinkBack=&Sys=47204-Lenovo-ThinkPad+T61p+6457-xxx&distributor=0&submit1=Search
Free CDs Offer Fundamental Content for IT Pros Are you up to speed on the latest technologies and solutions? Don't miss out on your chance to get up to speed quickly on fundamental, in-depth information on some of the hottest topics in our library of content.
Let Your Users Reset Their Own Passwords: Free Download Try a 30 day free trial of Desktop Authority Password Self-Service – it provides an easy-to-use, robust system for allowing users to reset their own forgotten passwords or locked accounts.
Get Windows IT Pro & Mark Minasi’s Favorite Power Tools Guide Order Windows IT Pro now and get "More of Mark Minasi's Favorite Power Tools"--a in-depth guide to the most useful Windows commands --FREE with your paid order! Subscribe today, and save 58% off the cover price!
Deep Dive into VMware vSphere, eLearning Series Join John Savill to explore the major functionality capabilities of the vSphere virtualization platform, including identification of the changes from ESX 3.5.