it depends NOT from 32 or 64 bit machine, it depends ONLY from the .exe which cannot handle more than 2.9 GB anyways, and which does not empty the vRam automatically.
The better work with Win7/64 is because the Win7/64 automatically makes free the range between the 2GB XP-border and the 2.9 GB limit, and as it can read for some operations (not for all of Civ4) with more than 1 CPU/2 kernels but 2 CPU/4 kernels.
The difference you may test when you run the game in XP compatibility mode and w/o that flag. It is significant faster w/o the compatibility flag on Win7/64.
The vRam limit you can touch easy, if you open in later game the workd builder and scroll over the world, and do this several times. Then comes a CTD with address memory allocation error, as the game touches the 2.9 GB border and makes not free the vRam and/or Ram used by the former world builder operations.
However, the overall limit for the game on an XP and a Win7/65 system is same: 2.9 GB Ram, 2.9 GB vRam, there is no difference in working on XP and working on Win7/64, except the better speed on Win7/64. The game's exe cannot address above the 2.9
The better work with Win7/64 is because the Win7/64 automatically makes free the range between the 2GB XP-border and the 2.9 GB limit, and as it can read for some operations (not for all of Civ4) with more than 1 CPU/2 kernels but 2 CPU/4 kernels.
The difference you may test when you run the game in XP compatibility mode and w/o that flag. It is significant faster w/o the compatibility flag on Win7/64.
The vRam limit you can touch easy, if you open in later game the workd builder and scroll over the world, and do this several times. Then comes a CTD with address memory allocation error, as the game touches the 2.9 GB border and makes not free the vRam and/or Ram used by the former world builder operations.
However, the overall limit for the game on an XP and a Win7/65 system is same: 2.9 GB Ram, 2.9 GB vRam, there is no difference in working on XP and working on Win7/64, except the better speed on Win7/64. The game's exe cannot address above the 2.9
. I'm surprised Win7 even runs on 2.3G. Maybe there is actually no RAM left over for big programs (ie. all allocated to system processes).