Re: [Freedos-devel] XMS fragmentation follow-up

2006-07-28 Thread Arkady V.Belousov
Hi! 26-Июл-2006 16:19 [EMAIL PROTECTED] (Michael Devore) wrote to freedos-devel@lists.sourceforge.net: MD> Okay, I can get minor XMS free block fragmentation during direct calls to MD> the VCPI/EMS allocator for large blocks. Since the VCPI/EMS allocator MD> directly manipulates the XMS handles,

Re: [Freedos-devel] XMS fragmentation follow-up

2006-07-27 Thread Japheth
> I can't duplicate the XMS memory block fragmentation with DOOM or anything > else handy, so whatever's happening depends upon the gameplay or memory > configuration or moon phase or any of the usual suspects. The errer has been described in Bugzilla more accurately. Especially it is mentioned

Re: [Freedos-devel] XMS fragmentation follow-up

2006-07-27 Thread Michael Devore
At 02:22 PM 7/26/2006 -0500, I wrote: >I can't duplicate the XMS memory block fragmentation with DOOM or anything >else handy, so whatever's happening depends upon the gameplay or memory >configuration or moon phase or any of the usual suspects. Okay, I can get minor XMS free block fragmentation

[Freedos-devel] XMS fragmentation follow-up

2006-07-26 Thread Michael Devore
At 06:20 PM 7/18/2006 +0200, Japheth wrote: >There is a bug left in the FD-Himem.exe memory manager. > >When a program that had allocated several XMS blocks doesn't release these >blocks in the order FD-Himem likes it, it will report a too small "largest >free block". Luckily the memory is not "p