Message-Id:	<200004050320.XAA21702@server1.mich.com>
MIME-Version:	1.0
To:	<opendos AT delorie DOT com>
From:	"Mark at Cross+Road's" <mark1 AT mich DOT com>
CC:	<w DOT j DOT hoogstraten AT hccnet DOT nl>
Date:	Tue, 04 Apr 2000 23:20:26 +0400
X-Mailer:	Net-Tamer 1.12 Beta
Subject:	Re: DPMI Continued
Reply-To:	opendos AT delorie DOT com

This is interesting what then was the size you chose?  Or didn't that make
any difference?, wouldn't think so though.
     Please let us know.
        Mark


On 2000-04-05 opendos AT delorie DOT com said:
   >On Tue, 4 Apr 2000 04:37:56 -0700, Marc D. Williams wrote:
   >>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.

- Raw text -