We recently upgraded our Terminal Server running Windows Server 2003 Enterprise Edition that serves a Visual Foxpro 6 based application for our retail stores from 4GB to 8GB of memory. We of course also had to use the /PAE switch in the Windows BOOT.INI file in order for Windows to address the full 8GB of memory.
Ironically, before the memory upgrade, Visual Foxpro would use nearly all 4GB of memory. I remember even during peak times, sometimes the physical memory remaining would show maybe 100 megabytes or so (this not even including what it was using in the paging file).
However, since the upgrade, the free physical memory seems to hover around 5.9GB free out of 8 - as if VFP is only using maybe 2GB or less of the physical memory - and the paging file is showing 4+GB usage. What's maybe eve a little more weird, it actually shows it's using 5GB of paging file - even though I set a MAX limit of 4092MB for the paging file (MIN-MAX) - and it's the only paging file specified.
I checked the paging drive - and sure enough, the file only shows to be 4GB.
What could be going on here? Is there anything special I need to do to allow VFP to see the extra memory? Or does it support PAE?
I've posted a link to a screenshot of what I'm seeing. And this is with the server loaded with about 50 connections on Terminal Services and most all of those using the VFP program.
I've allowed 500 points because I'd like to figure this out soon obviously - and the complexity of the question.