At 08:17 AM 5/1/2005 +0200, Eric Auer wrote:
Hi, I did extensive testing with HIMEM /max=... to limit the
amount of available XMS memory. The biggest value for /max which
works for me is 84992, one kilobyte more and ZIP starts to
crash (emm386 illegal instruction message, cs:ip at 0:b, ds=f, es=0..
At 02:07 AM 5/1/2005 -0500, I wrote:
Could be the sideways nibble that EMM386 does if it doesn't have a full
(1.5M * n) pool allocation block from a previous allocation. It tries to
eat 32K off an adjacent address free XMS handle and pass it over to the
currently used handle to fill out the blo
At 08:17 AM 5/1/2005 +0200, Eric Auer wrote:
Hi, I did extensive testing with HIMEM /max=... to limit the
amount of available XMS memory. The biggest value for /max which
works for me is 84992, one kilobyte more and ZIP starts to
crash (emm386 illegal instruction message, cs:ip at 0:b, ds=f, es=0..
Hi, I did extensive testing with HIMEM /max=... to limit the
amount of available XMS memory. The biggest value for /max which
works for me is 84992, one kilobyte more and ZIP starts to
crash (emm386 illegal instruction message, cs:ip at 0:b, ds=f, es=0...).
Interesting enough, you can add a bit (
