Message-ID:	<00ef01c093d5$c3c29400$d908e289@mpaul>
From:	"Matthias Paul" <Matthias DOT Paul AT post DOT rwth-aachen DOT de>
To:	<opendos AT delorie DOT com>
References:	<3A859A43 DOT 4312993F AT icubed DOT com>
Subject:	Re: EMM386 Setting
Date:	Sun, 11 Feb 2001 03:52:51 +0100
Organization:	Rechenzentrum RWTH Aachen
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id VAA04472
Reply-To:	opendos AT delorie DOT com

On 2001-02-10 MedCure Systems wrote:

> I am using a DOS4GW application with drdos 7.03 that does not have
> enough memory to run without a memory manager.  When the EMM386 is used
> there is plenty of memory, but a conflict causes the program to crash.
> What are the specific setting for the emm386 that will eliminate this
> conflict?

Try EMM386 PIC=ON to inform VCPI applications that the PIC
is not re-vectored (it still is).

Maybe there´s a way to reconfigure your DOS extender to make
use of DPMI instead of VCPI? If so, try this.

Just for curiosity, please try to exclude all UMB memory using
the EXCLUDE= option of EMM386.EXE.

> Is there a better memory manager to use when running DOS4GW
> applications?

If you don´t need UMBs maybe HIMEM.SYS instead of EMM386.EXE
will help (it still provides XMS and thereby HMA support, so you
can still free up some amount of comventional memory by loading
the kernel into the HMA).

Please let us know if it helps...

 Matthias

------------------------------------------------------------
Matthias Paul, Ubierstrasse 28, D-50321 Bruehl, Germany
<Matthias DOT Paul AT post DOT rwth-aachen DOT de> <mpaul AT drdos DOT org>
http://www.rhrz.uni-bonn.de/~uzs180/mpdokeng.html
------------------------------------------------------------

- Raw text -