>To add to what you're saying: on our Citrix servers I set Foreground to 32MB, and set ProgCache=0 in the config file. Sys(3050) manages memory for things like data or rushmore bitmaps. Progcache manages memory for program caching, which can be a real issue for large apps that have stuff (deliberately, and with good reason) buried in them. That setting does not set program cache to 0, but rather makes it dynamic. For a Terminal Server this is essential, to handle bigger loads by degrading gracefully. <s>
>
>Keep in mind: VFP uses _only_ the first 2GB of memory, no matter what else you do with the machine (and nothing is needed with Windows 2008 R2 SP2, which only comes in 64-bit versions, to utilize additional memory, if the application is able to do so). So keeping the total memory usage under control is essential to TS operation.
>
>In theory, one could set the LargeAddressAware flag in the EXE's header, so that VFP would use more than 2GB when it was available (assuming it was written in a way that could handle the larger numbers). I was able to set the flag in a VFP application EXE, but tests (using Process Explorer) showed no increase in memory usage. Oh well. So memory settings are key in TS/Citrix usage.
>
>Hank

I know Hank. Was just saying that if every TS user grabs 2GB or so, the system is likely to start paging - may look like freezing