>>>I know of an application which makes use of the RUN command to run a Windows 3.1 .EXE program, namely AutoCad Lite. Sometimes when AutoCad is run in this manner, it runs very slowly, even on a computer with 32 meg. Is there any trick (.PIF files, memory settings, ??) to making a program run with the RUN command run faster?
>>
>>I belive you can tell Fox how much memory you wish to allocate in Foxrun.pif.
>>
>>Memory Considerations By default, FOXRUN.PIF allocates a minimum of 256K of memory for running an external command or program. If you do not have 256K of free conventional memory, Visual FoxPro displays an error message. To correct this, try one or both of the following:
>>
>>· Close applications and files to free up additional memory.
>>· Edit FOXRUN.PIF to reduce the amount of memory required in the KB Required text box.
>>
>>If the external command requires more than 256K, MS-DOS displays an error message in the FoxPro Run Command window. To correct this, edit your FOXRUN.PIF to increase the amount of memory required in the KB Required text box.
>>
>>Hope this helps.
>
>The AutoCad program runs - no out of memory messages are displayed. It's just that it runs so pitifully slow that it's essentially useless. The FOXRUN.PIF solution has been tried from many different angles. Maybe there's no hope?
You might try setting the memory parameter in CONFIG.FPW. From what I have been told, FoxPro will try to lay claim to as much memory as possible.Perhaps if you set the DOSMEM to 256 or higher may help?