>>Hi All,
>>
>>Several days or even weeks ago I read a post here which I think was from Hank Fay. It mentioned something about the maximum amount of memory that all running instances of VFP could collectively have was the 2Gb limit. I understand that VFP cannot reach beyond 2Gb. But why would this affect separately running instances of VFP on a single machine? If they share the same DLLs then again I can understand it. But what if they all had their own copies of the VFP DLLs? Could someone expand on this?
>
>Pretty sure you misinterpreted his post.
>It was about the possibility to patch vfp with the LARGEMEMORY[too lazy too Google] or something flag,
>which IN OTHER programs allows those to adress 3 insted of 2 GB RAM inside each W32 process.
>So it is not collectively, but in each instance the maximum "program" footprint, as some memory is needed from the top as well,
>hence the 1 GB even with LARGEMEMORY. There are some programs that look for the correct location in an exe and patch,
>but if Hank says it doesn't work, I would first look at other alternatives. SSD can speed up previosly disc bound programs like crazy -
>this is the direction I went 18 month ago. Depending on the task I got a speedup of 20 - 60%, elevating single core allocation from
>30 ~50 to 90 ~ 95%. If you are running VM's on big RAM HW check out the different modes of using that RAM:
>depending JUST on the configuration the speed can be different by a factor of 3 on the same HW.
>
>regards
>
>thomas


Hi Thomas, thanks for the reply. I am not actually solving a problem - I was just curious about the post and had forgotten at the time to inquire about more information. Thanks for your input. SSD = Solid State Disk, yes?