Date: Tue, 10 Aug 1999 13:48:33 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Delbeke P." <bg000834 AT online DOT be>
cc: djgpp AT delorie DOT com
Subject: Re: cwsdpmi
In-Reply-To: <7onkea$q6p$1@trex.antw.online.be>
Message-ID: <Pine.SUN.3.91.990810134300.4964A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 10 Aug 1999, Delbeke P. wrote:

> Can someone tell me why DPMI disappears each time a program used it.

CWSDPMI comes with documentation, a file called CWSDPMI.DOC.  Please read 
it whenever you have any problems, and you will avoid the embarrassment 
of asking here questions for which the answer is right at your 
fingertips.  (The file CWSDPMI.DOC unzips into the bin subdorectory, the 
same place where your DJGPP binaries should be.)

> C:\...\>game.exe
>   Load error : no DPMI - get csdpmi*b.zip

You didn't put cwsdpmi.exe neither in the same directory where game.exe 
resides, nor on your PATH.  If you would, every DJGPP program will 
automatically load cwsdpmi.exe at startup and unload it when it exits.

> C:\...\>cwsdpmi.exe
> C:\...\>game.exe
>   (play the game)
>   (quit the game -- it's not good anyway :-)
> C:\...\>game.exe
>   Load error : no DPMI - get csdpmi*b.zip

From the CWSDPMI docs:

  1) "cwsdpmi" alone with no parameters will terminate and stay resident 
     FOR A SINGLE DPMI PROCESS.  This means it unloads itself when your 
     DPMI application exits.  This mode is useful in software which needs
     DPMI services, since CWSDPMI can be exec'ed and then will unload on exit.

  2) "cwsdpmi -p" will terminate and stay resident until you remove it.
     It can be loaded into UMBs with LH.  "cwsdpmi -u" will unload the TSR.