On Sun, Jun 29, 2014 at 8:45 AM, Zbigniew <zbigniew2...@gmail.com> wrote:
> 2014-06-29 15:25 GMT+02:00, Mateusz Viste <mate...@viste.fr>:
>> I am not sure it's related to the XMS manager you use.
> Unfortunately, it seems to be related.
>> It's rather a matter of the amount of conventional memory you have.
> No, it was what I checked first before posting.
>> Maybe when using
>> XMGR you end up with more free memory < 640K than when using Jemmex?
> JEMMEX left more memory: 609k conventional and 14k upper - while XMGR
> left 599k of conventional, and no upper at all.

I don't know which versions exactly, but AFAIK, Turbo C tries to use
EMS by default (if found) but not XMS (without some cmdline switches).
So who knows if it's getting confused here. Remember that 32 MB of EMS
is a lot (to it)!

Are you using any switches like NOVCPI or FRAME=NONE? Try eliminating
any unusual switches at load time.

Try using something else like EMSMAGIC (or EMM286 or whatever) and see
if the problem goes away. Heck, it might be JEMMEX specific, so try
using (XMS +) JEMM386 separately. (At least that can LOAD and UNLOAD
manually, so less clashes.)

Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
Freedos-user mailing list

Reply via email to