Message-Id: <200004042222.AAA00922@smtp.hccnet.nl>
From: "Willy J. Hoogstraten" <w DOT j DOT hoogstraten AT hccnet DOT nl>
Date: Wed, 05 Apr 2000 00:51:59 +0100
X-Mailer: Arachne V1.61
To: opendos AT delorie DOT com
Subject: Re: DPMI Continued
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Reply-To: opendos AT delorie DOT com

Hi,

On Tue, 4 Apr 2000 04:37:56 -0700, Marc D. Williams wrote:

> Well, some/most/all of the djgpp-compiled stuff will use either
> cwsdpmi (I think that's right) or go32.exe automatically if they're
> in the path (probably won't work if not anyway).
> For these programs, lynx to name one, they're usually started via a
> batch file so I would use the dpmi=off/on anyway and things worked fine.

I never have any trouble /w the DR-DOS 7.03 DPMI host for programs that
require DPMI. Only the NWCACHE causes trouble. So I made the max. and min.
cache size the same and turn lend=off.


> Non-djgpp programs that require DPMI and don't like DR-DOS's is
> something else but I'm not sure if I ever came across any of those.
> I'm sure there's gotta be a generic replacement out there that works.

I know one of them: TASM 5.0, but if I prepare the use of it, I use a
BATch-file to arrange the path and switch the DPMI off (and back on when
I quit using TASM). No problems with this.

BTW, I tried to use CWSDPMI, but I discovered some problems when launching
programs from within VC (and DC and NC (all file managers)). Especially
after using ISDN software, most programs, incl. DJGPP, where not able to
find CWSDPMI while it was at the path or in the current dir.
BTW, the ISDN software needs DPMS, but I experienced the same on a 386 w/o
ISDN software.


- Best regards,
- Willy J. Hoogstraten.

- End of message -