Hi!

25-Мар-2004 21:05 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:

EA> HIMEM /HMAMIN=m is indeed not very useful. Being able to allocate PARTS
EA>   of the HMA would be nice but was not introduced before MS DOS 7 or so,
EA>   and before that time, HMAMIN protected the system from giving the HMA
EA>   away as a whole to some program which only wanted a bit of it.

______________O\_/_________________________________\_/O______________
http://burks.brighton.ac.uk/burks/pcinfo/progdocs/xms30.htm

                 eXtended Memory Specification (XMS), ver 3.0

January 1991
Copyright (c) 1988, Microsoft Corporation, Lotus Development
[...]
  DRIVER INSTALLATION:
[...]
   devices or TSRs which use it. An optional parameter after the driver's
   name (suggested name "/HMAMIN=") indicates the minimum amount of space
   in the HMA a program can use. Programs which use less than the minimum
   will not be placed in the HMA. See "Prioritizing HMA Usage" below for
[...]
  Request High Memory Area (Function 01h):
[...]
   This function attempts to reserve the 64K-16 byte high memory area for
   the caller. If the HMA is currently unused, the caller's size
   parameter is compared to the /HMAMIN= parameter on the driver's
   command line. If the value passed by the caller is greater than or
   equal to the amount specified by the driver's parameter, the request
   succeeds. This provides the ability to ensure that programs which use
   the HMA efficiently have priority over those which do not.
[...]
   The second method for optimizing HMA usage is through the /HMAMIN=
   parameter on the XMS device driver line. The number after the
   parameter is defined to be the minimum amount of HMA space (in
   K-bytes) used by any driver or TSR. For example, if "DEVICE=HIMEM.SYS
   /HMAMIN=48" is in a user's CONFIG.SYS file, only programs which
   request at least 48K would be allowed to allocate the HMA. This number
   can be adjusted either by installation programs or by the user
   himself. If this parameter is not specified, the default value of 0 is
   used causing the HMA to be allocated on a first come, first served
   basis.

   Note that this problem does not impact application programs. If the
   HMA is available when an application program starts, the application
   is free to use as much or as little of the HMA as it wants. For this
   reason, applications should pass FFFFh in DX when calling Function
   01h.
[...]
  IMPLEMENTATION NOTES FOR HIMEM.SYS:
     * HIMEM.SYS supports the optional "/HMAMIN=" parameter. The valid
       values are decimal numbers between 0 and 63.
_____________________________________________________________________
              O/~\                                 /~\O




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to