Dio wrote:It's not, on the server versions.
32 bit server doesn't run apps in 64 bit does it?
It's the same mess as the desktop versions afaik
Dio wrote:It's not, on the server versions.

No, it will use a maximum of 4Gb - X, where X is the physical mappings requested by your IO devices. Generally half a meg. There is no support whatsoever for memory above the 4G line. The latter does not apply on Server versions, where PAE is used to support 4Gb-X per application maximum.gravy wrote:As for WINDERS my understanding is Vista 32 bit windows will use a maximum of 4gb of your physical RAM and any extra mem is supported by paging.
Go and read up on it, I think there's a big article about it on Arstechnica.Dio wrote:No, it will use a maximum of 4Gb - X, where X is the physical mappings requested by your IO devices. Generally half a meg. As I said above, this does not apply on Server versions.gravy wrote:As for WINDERS my understanding is Vista 32 bit windows will use a maximum of 4gb of your physical RAM and any extra mem is supported by paging.
I presume the method you're describing must thunk all IO through the 32-bit accessible space, so there's probably a big hit in IO performance somewhere?


Looks like a thunking architecture as I thought. I'm very surprised that doesn't cause major hits on IO benchmarks, but there you go.gravy wrote:Go and read up on it, I think there's a big article about it on Arstechnica.
If you ask me, the craziness was allowing Vista32 in the first place. Would have made everything a lot simpler.Winders is a bit shit. I'm annoyed we have to use Vista 64 for our machines at work to get the benefit of the 8gb of RAM on the machine and then sometimes have hassles with drivers.


