Date: Wed, 22 Apr 1998 09:35:09 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Castro, Edison M. (PCA)" <edison_castro AT ml DOT com>
cc: "'Nate Eldredge'" <nate AT cartsys DOT com>, djgpp AT delorie DOT com
Subject: RE: Problem with biosdisk
In-Reply-To: <4D61B534C6B1D011B21400805FBEB42F61D616@pca03.pca.ml.com>
Message-ID: <Pine.SUN.3.91.980422093434.4102A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 21 Apr 1998, Castro, Edison M. (PCA) wrote:

> Another twist to the story: If I use the version that fails (v2.x) and I
> disable emm386.exe from being loaded on my config.sys, suddenly everything
> works as expected. So this tells me that the problem is interaction between
> the new v2.x DMPI server cwsdpmi or cwsdpr0 and emm386 in these machines
> (Compaq Deskpro 6000-PII 333 two 4GB Drives and Dell GXPRO -same config)
> 
> My config.sys is:
> 
> device=a:\dos\himem.sys 
> device=a:\dos\emm386.exe noems

NOEMS is usually a bad idea with CWSDPMI (it makes CWSDPMI use raw XMS
services instead of VCPI).  Try loading EMM386, but without the NOEMS
parameter.  (This is described in the DJGPP FAQ list, btw.)

> device=a:\dos\ifshlp.sys

Did you try to not load IFSHLP.SYS?  AFAIK, it is only needed if you
load Windows with 32-bit File Access enabled, which I understand is
not your case.

IFSHLP's purpose is to catch low-level DOS and BIOS calls and reflect
them back to the Windows kernel, so that file access is done
exclusively in protected mode.  It might well be that this is what is
causing your problems.