Hi!
10-Фев-2005 16:41 [EMAIL PROTECTED] (Michael Devore) wrote to
[email protected]:
>>mimic the behaviour of XMSMMGR.EXE on a Windows installation cdrom.
MD> drivers have loaded. There's little to no way to make sure you don't stomp
MD> on already loaded drivers. The XMS/HMA driver needs a clean memory map to
MD> operate.
For this reason, drivers, which use extended memory directly (hm...
which one you know?), recommended to write in top-bottom manner, when they
allocate memory from top and just decrease value, returned by INT15. There
is only one issue with vdisk, which allocates bottom memory. Thus, there
shouldn't be problems with correct drivers (or vdisk-like drivers, if you
implement recognizing vdisk-like bottom method).
MD> Same goes for turning XMS off after it's been turned on. Where
MD> do the drivers already loaded in extended memory go?
But what if there are no "drivers loaded in extended memory" (you wish
to say "in XMS?)?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
