Okay, I already know 32-bit OS's can only read 3.25GB at the maximum while leaving the remaining 768MB of memory to whatever is connected to the PCI Bus.
The thing with my question is, I just ordered a Dell M1530, but won't be getting it until around April 6th, with 4GB of RAM, and an 8600M GT with 256MB dedicated.
With Windows Vista they say maximum amount of shared video memory is 1GB.
Does anyone know, or have experience with this as to where I can changed the shared video memory to lets say 768MB of RAM (which is the 768MB that isn't being used up by Windows) and add the 768 (shared) to my 256 (dedicated) and would it read the 8600M GT as a 1GB video card, and still list in Control Panel > System that I still have 3.25GB of physical memory?
OR will that 768 instead be taken off my current 3.25GB?
It's just something that'd be great to know before my laptop gets shipped. Can't wait for this machine.
Full Version: Need Answers Bad!
Are you sure the 8600M even uses system memory? 
Isn't shared memory only for non-dedicated, low end GPUs? something doesnt sound right..
Isn't shared memory only for non-dedicated, low end GPUs? something doesnt sound right..
changing shared memory would involve teh system bios.
Not sure really, apparation.
I've read reviews on it, says maximum they have is 512 (dedicated) and can be used up to 1GB shared.
I've read reviews on it, says maximum they have is 512 (dedicated) and can be used up to 1GB shared.
Well, with a 32-bit OS and physical address extension you'll max at 3.5 GB of RAM (And most programs might not support physical address extension). In essence, you'll pretty much be wasting 3GBs of your RAM (haha, unless you run a virtual machine and dedicate a few gigs to it).
Your 8600M GT is the 256MB version, it won't use shared memory since it's a discrete component.
Your 8600M GT is the 256MB version, it won't use shared memory since it's a discrete component.
Just some comments on things posted in this thread.
1) There is no hard rule stating that 32 bit OS can only use up to 3.25 (without PAE) or 3.5 (with PAE). The actual amount below 4 GB which is not addressable varies depending on how much of your virtual address space is used by other things other than your main system ram. Although 3.25 is a good estimation but it is possible to go more or below depending on your hardware.
2) It shouldn't be generalized that all 32 bit OS's are limited to 4GB or less. Windows XP/Vista 32 bit are limited in this fashion, but Windows Server 2003 Enterprise 32 bit and almost all *nix 32 bit OS's can go well beyond 4GB (with proper configuration). However, per process limitations still exist as addressable virtual address space is still 4GB on a 32 bit OS.
3) It's not that applications don't support PAE (they aren't aware), its the fact that in Windows, a single process can only use 2GB max with the remainder reserved for the system (or 3Gb with /3gb extension). Whether you have PAE on or off, does not affect how apps actually use memory. Access to the total amount of memory with PAE enabled for notepad.exe would be no different than for a host based virtualized guest. Even if such a limitation did exist, it would affect all apps; including host based virtualization (Vmware, Citrix Xen, Hyper-V, etc).
Honestly, everyone should consider migrating to a 64 bit OS if memory becomes a constraint. From a workstation perspective, 64 bit drivers and application compatibility has come a long way since it was first introduced. I have personally been using 64 bit Vista for over a year now and although I had some incompatibilities a year ago (which I was able to find work arounds anyway), most issues have been resolved as of today. I'm sure there are some drivers/apps which still don't work, but the compatibility gap is increasingly shrinking and what drivers/apps that still don't work are mostly legacy and/or "one offs" (one offs mostly being web related activex applications).
1) There is no hard rule stating that 32 bit OS can only use up to 3.25 (without PAE) or 3.5 (with PAE). The actual amount below 4 GB which is not addressable varies depending on how much of your virtual address space is used by other things other than your main system ram. Although 3.25 is a good estimation but it is possible to go more or below depending on your hardware.
2) It shouldn't be generalized that all 32 bit OS's are limited to 4GB or less. Windows XP/Vista 32 bit are limited in this fashion, but Windows Server 2003 Enterprise 32 bit and almost all *nix 32 bit OS's can go well beyond 4GB (with proper configuration). However, per process limitations still exist as addressable virtual address space is still 4GB on a 32 bit OS.
3) It's not that applications don't support PAE (they aren't aware), its the fact that in Windows, a single process can only use 2GB max with the remainder reserved for the system (or 3Gb with /3gb extension). Whether you have PAE on or off, does not affect how apps actually use memory. Access to the total amount of memory with PAE enabled for notepad.exe would be no different than for a host based virtualized guest. Even if such a limitation did exist, it would affect all apps; including host based virtualization (Vmware, Citrix Xen, Hyper-V, etc).
Honestly, everyone should consider migrating to a 64 bit OS if memory becomes a constraint. From a workstation perspective, 64 bit drivers and application compatibility has come a long way since it was first introduced. I have personally been using 64 bit Vista for over a year now and although I had some incompatibilities a year ago (which I was able to find work arounds anyway), most issues have been resolved as of today. I'm sure there are some drivers/apps which still don't work, but the compatibility gap is increasingly shrinking and what drivers/apps that still don't work are mostly legacy and/or "one offs" (one offs mostly being web related activex applications).
QUOTE (dot1q @ Mar 26 2008, 08:34 AM) 
Just some comments on things posted in this thread.
1) There is no hard rule stating that 32 bit OS can only use up to 3.25 (without PAE) or 3.5 (with PAE). The actual amount below 4 GB which is not addressable varies depending on how much of your virtual address space is used by other things other than your main system ram. Although 3.25 is a good estimation but it is possible to go more or below depending on your hardware.
2) It shouldn't be generalized that all 32 bit OS's are limited to 4GB or less. Windows XP/Vista 32 bit are limited in this fashion, but Windows Server 2003 Enterprise 32 bit and almost all *nix 32 bit OS's can go well beyond 4GB (with proper configuration). However, per process limitations still exist as addressable virtual address space is still 4GB on a 32 bit OS.
3) It's not that applications don't support PAE (they aren't aware), its the fact that in Windows, a single process can only use 2GB max with the remainder reserved for the system (or 3Gb with /3gb extension). Whether you have PAE on or off, does not affect how apps actually use memory. Access to the total amount of memory with PAE enabled for notepad.exe would be no different than for a host based virtualized guest. Even if such a limitation did exist, it would affect all apps; including host based virtualization (Vmware, Citrix Xen, Hyper-V, etc).
Honestly, everyone should consider migrating to a 64 bit OS if memory becomes a constraint. From a workstation perspective, 64 bit drivers and application compatibility has come a long way since it was first introduced. I have personally been using 64 bit Vista for over a year now and although I had some incompatibilities a year ago (which I was able to find work arounds anyway), most issues have been resolved as of today. I'm sure there are some drivers/apps which still don't work, but the compatibility gap is increasingly shrinking and what drivers/apps that still don't work are mostly legacy and/or "one offs" (one offs mostly being web related activex applications).
1) There is no hard rule stating that 32 bit OS can only use up to 3.25 (without PAE) or 3.5 (with PAE). The actual amount below 4 GB which is not addressable varies depending on how much of your virtual address space is used by other things other than your main system ram. Although 3.25 is a good estimation but it is possible to go more or below depending on your hardware.
2) It shouldn't be generalized that all 32 bit OS's are limited to 4GB or less. Windows XP/Vista 32 bit are limited in this fashion, but Windows Server 2003 Enterprise 32 bit and almost all *nix 32 bit OS's can go well beyond 4GB (with proper configuration). However, per process limitations still exist as addressable virtual address space is still 4GB on a 32 bit OS.
3) It's not that applications don't support PAE (they aren't aware), its the fact that in Windows, a single process can only use 2GB max with the remainder reserved for the system (or 3Gb with /3gb extension). Whether you have PAE on or off, does not affect how apps actually use memory. Access to the total amount of memory with PAE enabled for notepad.exe would be no different than for a host based virtualized guest. Even if such a limitation did exist, it would affect all apps; including host based virtualization (Vmware, Citrix Xen, Hyper-V, etc).
Honestly, everyone should consider migrating to a 64 bit OS if memory becomes a constraint. From a workstation perspective, 64 bit drivers and application compatibility has come a long way since it was first introduced. I have personally been using 64 bit Vista for over a year now and although I had some incompatibilities a year ago (which I was able to find work arounds anyway), most issues have been resolved as of today. I'm sure there are some drivers/apps which still don't work, but the compatibility gap is increasingly shrinking and what drivers/apps that still don't work are mostly legacy and/or "one offs" (one offs mostly being web related activex applications).
That was informative. I'll do more research about 64-bit support for the programs and games I run and then I will consider moving to Vista 64-bit.
I thought it was sorta lame that MS released Vista in 2 different versions, a 32bit and a 64bit version (along with like 7 variants of each--ie. home basic, home premium, biz, ultimate, ETC). the whole 64bit thing would've taken off if they just released a 64bit vista...so it would make it easier on the dev and the consumer.... /rant
and i think that if you game, 32bit vista is still the way to go. maybe in a few years, you can upgrade to 64bit windowsXXX.. but for compatibilities' sake, 32bit is still where its at...esp. if you still have older games in your collection that you play with friends for example
and i think that if you game, 32bit vista is still the way to go. maybe in a few years, you can upgrade to 64bit windowsXXX.. but for compatibilities' sake, 32bit is still where its at...esp. if you still have older games in your collection that you play with friends for example
yeah, I'm waiting for a better 64-bit Windows to come out before switching over. Or if Linux can ever play any games.
free 64bit for consumers already with 32bit vista - cd key required , may need to pay shipping.
http://www.microsoft.com/windowsvista/1033...ia/default.mspx
http://www.microsoft.com/windowsvista/1033...ia/default.mspx
QUOTE (angelqian @ Mar 27 2008, 12:48 AM)
yeah, I'm waiting for a better 64-bit Windows to come out before switching over. Or if Linux can ever play any games.
Whats wrong with Vista x64? Application/Driver compatibility isn't a "OS problem". It would be expected of any new major OS release. Linux is just as prone when it gets major version upgrades. Vista's stability and performance is much better than XP. Sure it needs more cpu/memory... but isn't that the natural progression of software/technology evolution?
QUOTE (Han The Geek @ Mar 25 2008, 09:59 PM)
Okay, I already know 32-bit OS's can only read 3.25GB at the maximum while leaving the remaining 768MB of memory to whatever is connected to the PCI Bus.
The thing with my question is, I just ordered a Dell M1530, but won't be getting it until around April 6th, with 4GB of RAM, and an 8600M GT with 256MB dedicated.
With Windows Vista they say maximum amount of shared video memory is 1GB.
Does anyone know, or have experience with this as to where I can changed the shared video memory to lets say 768MB of RAM (which is the 768MB that isn't being used up by Windows) and add the 768 (shared) to my 256 (dedicated) and would it read the 8600M GT as a 1GB video card, and still list in Control Panel > System that I still have 3.25GB of physical memory?
OR will that 768 instead be taken off my current 3.25GB?
It's just something that'd be great to know before my laptop gets shipped. Can't wait for this machine.
The thing with my question is, I just ordered a Dell M1530, but won't be getting it until around April 6th, with 4GB of RAM, and an 8600M GT with 256MB dedicated.
With Windows Vista they say maximum amount of shared video memory is 1GB.
Does anyone know, or have experience with this as to where I can changed the shared video memory to lets say 768MB of RAM (which is the 768MB that isn't being used up by Windows) and add the 768 (shared) to my 256 (dedicated) and would it read the 8600M GT as a 1GB video card, and still list in Control Panel > System that I still have 3.25GB of physical memory?
OR will that 768 instead be taken off my current 3.25GB?
It's just something that'd be great to know before my laptop gets shipped. Can't wait for this machine.
No, you can't just transfer unused system ram into a dedicated VC.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.