Hi!
16-Сен-2004 00:14 [EMAIL PROTECTED] (Michael Devore) wrote to
[EMAIL PROTECTED]:
>>PS: About option for HIMEM to limit available (allocated?) memory: is it
>>affects only XMS2 or both XMS2 and XMS3?
MD> XMS 3.0 functions were explicitly created to allow and report >64M
MD> allocations, so it's not much good to limit that call to <64M. The
MD> built-in throttle only affects the reported available memory for 2.0
----^^^^^^^^^^^^^^^^^ ?
MD> query. You could allocate over that amount via an XMS 3.0 alloc function
MD> or multiple 2.0 alloc functions.
MD> /MAX=<K-value> option actually stops any extended memory usage by HIMEM
MD> beyond what is listed as the value. That's all anything gets or sees
MD> through HIMEM.
As I understand second paragraph, (currently) I may only limit memory,
handled by HIMEM (and available through both XMS2 and XMS3), but how first
paragraph relates to second (in first paragraph you say, that XMS3
shouldn't be affected)?
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
