At 12:56 PM 4/29/2005 +0200, you wrote:

Yes, BUT: You still forgot to compile with FORSYS defined, so prf.c still
outputs to BIOS instead of to (redirectable) DOS.

I didn't forget and I did look at the code. The #define explicitly indicated for SYS files, use it the way it is set up. One of the original EMM386 developers did that very much on purpose and with apparent reason. I'm not changing it out unless and until there is a clear definitive answer that it will work the DOS way even as a SYS file for everyone, including those using MS-DOS. Saying you promise isn't enough.

 Only few programs use int 15.87 at all, but the best
known victim of the problem was FDXMS / FDXXMS (the other XMS manager of FD).

No officially supported with EMM386 and generally a bad idea to use since it's rapidly becoming obsolete. As far as anything other than HIMEM, you're on your own. Might work, might not.

 believe it would not be too hard to do a fixed XMS
allocation if int 2f.4309 is not supported (i.e. more or less switch to
"old style"). As far as I understand, explicitly specifying EMM=... does
select that behaviour?


Same question from me, does EMM= accept values bigger than 32M?

Yes, for VCPI purposes.

By the way, did you manage
to speed up the VCPI allocator, given that VCPI is always allocated in tiny
4k chunks, so programs have to call the allocator very often if they want
a lot of RAM.

There are two internal tracking pointers for last freed and last allocated block, to more quickly locate a pool allocation block for use without a search from the top. Simple is best for most, but for extreme cases, someone could certainly add their own full-blown caching/management code to better track/quickly locate available allocations.

------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! _______________________________________________ Freedos-user mailing list

Reply via email to