This lets an individual application access memory addresses over 2 GB within its own address space. Each instance of the VFP application doesn't need nearly this much memory. I don't think this is even applicable to a VFP executable, as VFP has hard coded addressing limits of 2 GB (i.e. table size, etc.), but I'm sure it's not necessary. The intent is to make each instance of the app use as little memory as possible.


>Thank you.
>
>is it reasonable to apply Visual Studio
>
>

Editbin.exe /LARGEADDRESSAWARE

>
>to VFP 9 application exe file when running it under W3K terminal server with 4 GB RAM ?
>
>>Try adding this to your config.fpw file:
>>
>>PROGCACHE=-144
>>
>>If the application works OK, then you can experiment with smaller negative values. The smallest value (i.e closest to 0) which works OK would be optimal. If the cache is too small, you will see error 1202, "Program is too large". If -144 works OK, then try -72, etc. Making the cache smaller will eliminate the initial 9.2 MB memory program cache allocation for each instance of the app, which would be > 730 MB for 80 instances.
>>
>>>I have a W3K server with 4 GB of RAM running VFP 9 application by
>>>80-100 users using Terminal Server. Performance is poor if more that 60 users are working. Task Manager Shows typically:
>>>
>>>PF usage: 2.45 GB
>>>Physical memory 3669388
>>>Available: 1767416
>>>System Cache: 1893012
>>>
>>>CPU usage 10..90%
>>>Mem usage for each vfp application is 9..30 MB
>>>
>>>Maybe poor perfomance is caused by PF usage: 2.45 GB.
>>>How to force server to use all available RAM and decrease page file size ?
>>>
>>>I have sys(3050,1,20000000) and sys(3050,2,10000000) lines in application init code .
>>>
>>>Can I use
>>>
>>>editbin.exe /LARGEADDRESSAWARE myvfpappl.exe
>>>as described in
>>>http://www.gehrytechnologies.com/catia/catia/catia_windows_large_memory.htm
>>>
>>>boot.ini contains
>>>
>>>"Windows Server 2003, Standard" /fastdetect /NoExecute=OptOut /3GB /USERVA=3030
>>>
>>>as described in
>>>
>>>http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx