Eylon

Have you looked into the FOXR.Exe loader program? I wish I
could be of more help but it has been awhile since I used this
stuff. Anyway I thought this was what the loader EXE was
all about...

Tom


>>Eylon
>>
>>Look on page 2-17 of the FPD Installation &
>>Configuration
>>manual. It talks about an EMS setting in
>>Config.FP.
>>
>>Let me know if you need more.
>>
>>Tom
>>
>>>To: everybody
>>>
>>>
>>>We have an application that calls an external
>>>program (via run) that
>>>must have expanded memory. When we run this
>with
>>>the regular
>>>foxpro there is no problem, but when we try to
>>run
>>>it with
>>>the expanded foxpro (foxprox.exe) foxpro
>>>invariably uses the
>>>expanded memory in the system and treats it as
>if
>>>it were
>>>extended memory. Is there any way to disallow
>>>foxpro's using
>>>of expanded memory, and keep it free for othere
>>>applications?
>>>
>>>
>>>
>>>Thanks
>>>
>>>
>>>
>>> Eylon
>>>
>>
>
>
>Tom,
>
>Thanks for answering. The problem is that the EMS
>setting is
>valid only for the regular version of foxpro, and
>not the
>extended version (foxprox.exe).
>We must use the extended version, in our
>application.
>The -E switch (which is equivalent to
>EMS=OFF in config.fp) works only with the regular
>version.
>
>So I still need new ideas,
>
> Thnx,
>
>
> Eylon
>
>
>