XMS
XMS_HANDLES
Function:
Specifies the number of XMS extended
memory block (EMB) handles. A handle is used with each XMS EMB. This number
is required because XMS pre-allocates all the handle space to be compatible
with XMS specifications. This setting should be used only if an application
uses a large number of handles.
Advantages:
This
setting restricts the number of block handles, thereby reducing memory consumption.
Drawbacks:
Specifying
a large number of handles will increase memory consumption and adversely
impact system performance.
Default:
The
default value of this setting is 32.
Settable:
Examples:
XMS_MEMORY_LIMIT
Function:
Specifies the per VDM XMS memory
limit. This setting should be used under the same guidelines as described
above in XMS_HANDLES. The global limit is the overall maximum XMS memory
consumption, and the per-VDM limit is the maximum allowed for each VDM.
See also Extended Memory Manager
(Initialization) for defining global and per-VDM limit in the CONFIG.SYS.
Drawbacks:
Specifying
a large number may adversely affect system performance.
Default:
The default value is 2MB per-VDM.
Settable:
Examples:
4096; this specifies a limit for each VDM.
XMS_MINIMUM_HMA
Function:
Specifies the minimum HMA memory
request allowed. This setting allows the user to fine tune the XMS. HMA
is slightly less than 64KB in size. Only one request can be fulfilled from
this area at a time.
Advantages:
If
a TSR takes a very small allocation, then it will waste this area for other
applications. In such cases a limit can be specified.
Default:
The default value is zero, which means all
the requests will be allowed.
Settable:
Examples:
2048;
this sets a limit of 2KB.
[Back: Video]
[Next: WIN-OS/2]