I don't understand this. I start up BF2 (retail) in XP32, and it takes so painfully long to load a level. At loading 'Collision', it takes probably another 2 minutes until it gets to loading 'Geometry'. In XP64, it takes about 5 seconds. In game play in XP32, the game stutters awfully, unbearably. In XP64, it's smooth as a baby's ass. I've defragmented, and the problem remains. I have no more background programs in XP32 except Azureus (and not all the time). Why is it so slow in XP32 compared to XP64? XP64 feels like Linux to me. Is this a sign of a rewriting of memory management for Windows? I sure hope it is.
BTW, XP64 is on another partition to prevent conflicting "Program Files" directories. Perhaps my XP32's page file needs defragmenting (which isn't normally done)? BF2 is on the same partition though. I installed BF2 on XP32, and I just run it as an EXE from Program Files in XP64.
Just a note to everyone in the same situation as me with two 512 sticks. Don't get shell out for another gig before I report back on defragging my page file! This may very well be the problem. It also explains why some people that have a gig run it just fine.
I also have another theory. I ran CacheMan the other day (set to Gaming setting and may have actually made this worse). Maybe people that have a gig and run BF2 fine have the correct cache adjustments versus other's?
I'm going to defrag my XP32's page file with the free Sysinternals utility and report back. If that doesn't help I'll screw with my cache settings and find out the best settings for BF2.
BTW, this problem is consistent. Rebooting XP32 didn't help. Also my settings for BF2 in XP32 and XP64 are identical.
My conclusion is either XP64's memory management is near as good as Linux now, cache settings can prevent you from buying another gig of RAM, or you just need to defrag your page file and you'll be fine. All good news... In any case, I'm determined to figure out why some people with one gig have no stutter and others have it bad.
BTW, XP64 is on another partition to prevent conflicting "Program Files" directories. Perhaps my XP32's page file needs defragmenting (which isn't normally done)? BF2 is on the same partition though. I installed BF2 on XP32, and I just run it as an EXE from Program Files in XP64.
Just a note to everyone in the same situation as me with two 512 sticks. Don't get shell out for another gig before I report back on defragging my page file! This may very well be the problem. It also explains why some people that have a gig run it just fine.
I also have another theory. I ran CacheMan the other day (set to Gaming setting and may have actually made this worse). Maybe people that have a gig and run BF2 fine have the correct cache adjustments versus other's?
I'm going to defrag my XP32's page file with the free Sysinternals utility and report back. If that doesn't help I'll screw with my cache settings and find out the best settings for BF2.
BTW, this problem is consistent. Rebooting XP32 didn't help. Also my settings for BF2 in XP32 and XP64 are identical.
My conclusion is either XP64's memory management is near as good as Linux now, cache settings can prevent you from buying another gig of RAM, or you just need to defrag your page file and you'll be fine. All good news... In any case, I'm determined to figure out why some people with one gig have no stutter and others have it bad.