Microsoft KB Archive/110359: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 29: | Line 29: | ||
NOTE: When you use the MEMLIMIT command, be sure to include the last two parameters on the command. In the following example, using MEMLIMIT=85 may not yield the same result as using all three parameters: '''''' | NOTE: When you use the MEMLIMIT command, be sure to include the last two parameters on the command. In the following example, using MEMLIMIT=85 may not yield the same result as using all three parameters: '''''' | ||
<pre class="CODESAMP"> MEMLIMIT=85,2048,4096 </pre> | <pre class="CODESAMP"> MEMLIMIT=85,2048,4096 </pre> | ||
For more information about MEMLIMIT, see page 1-2 in the | For more information about MEMLIMIT, see page 1-2 in the "Update" manual. | ||
<br /> | <br /> | ||
Revision as of 10:51, 20 July 2020
The information in this article applies to:
SUMMARYFoxPro does not use the memory specifications in a program information file (PIF). This is because FoxPro is running under an MS-DOS Protected Mode Interface (DPMI)-compliant memory manager (Microsoft Windows).
NOTE: When you use the MEMLIMIT command, be sure to include the last two parameters on the command. In the following example, using MEMLIMIT=85 may not yield the same result as using all three parameters: ' MEMLIMIT=85,2048,4096 For more information about MEMLIMIT, see page 1-2 in the "Update" manual.
MORE INFORMATIONThe 32-bit Extended version of FoxPro (FOXPROX.EXE) is a DPMI client. Therefore, it allocates memory from the DPMI server just like Windows does. The 32-bit version of FoxPro does not use the pool of extended and expanded memory that Windows apportions to it based on the PIF. Additional query words: FoxDos 2.50 2.50a 2.50b Keywords : Version : Platform : Issue type : |
Last Reviewed: August 25, 1999 |