Date:	Wed, 1 Oct 1997 11:11:02 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	"Jeff T. Williams" <jeffw AT darwin DOT sfbr DOT org>
cc:	djgpp AT delorie DOT com
Subject:	Re: CWSDPMI and LOADHIGH
In-Reply-To:	<199709302033.PAA29868@kendall.>
Message-ID:	<Pine.SUN.3.91.971001111019.10422J-100000@is>
MIME-Version:	1.0

On Tue, 30 Sep 1997, Jeff T. Williams wrote:

> Some of the FAQ and mailing-list material discusses
> the use of DOS LOADHIGH to stuff CWSDPMI into the HMA.
> Is there a preferred way to do this?  I tried using
> 
> LOADHIGH c:\djgpp\bin\cwsdpmi
> 
> in my CONFIG.SYS file,  with and without the -p and -s
> options, and it hangs the machine every time (a 386SX
> with DOS 5.0).

This is a DOS issue, it has nothing to do with DJGPP or CWSDPMI.

It is usually a bad idea to load a TSR, either HIGH or LOW, in
CONFIG.SYS.  You need to do that in AUTOEXEC.BAT, or from the DOS
command prompt, after the system has come up.

CONFIG.SYS can load device drivers (with DEVICE= or DEVICEHIGH=
directives), but CWSDPMI isn't a device driver.  CONFIG.SYS can also
load TSRs with the INSTALL= directive, but AFAIK INSTALL= doesn't
support loading HIGH, and it only works with some TSRs; I'm not sure
if CWSDPMI will work with it, but I won't be surprised if it won't.
So I don't recommend it.

Why do you need to load CWSDPMI high, anyway?  IMHO, it is not worth
the hassle in most cases to load it permanently into memory at all.
The DJGPP startup code will automatically load it when you run a DJGPP
program and unload it when the program exits.

- Raw text -