Xref: news-dnh.mv.net comp.os.msdos.djgpp:1443
Path: news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!news.mathworks.com!gatech!purdue!oitnews.harvard.edu!newsfeed.rice.edu!rice!news!sandmann
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: cprintf.help
Date: Tue, 08 Aug 1995 09:50:08 CDT
Organization: Rice University, Houston, Texas
Lines: 12
References: <DCzDJw DOT Hnw AT jade DOT mv DOT net>
Reply-To: sandmann AT clio DOT rice DOT edu
Nntp-Posting-Host: clio.rice.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

> Another thing, I didn't have CWSDPMI running either.  Do I only need CWSDPMI
> for some things and no others with V2?

V2's stub is smart enough to load CWSDPMI for you automatically then remove
it if it does not see another DPMI.  Some DPMI is needed for all V2 apps,
just as GO32 is needed in some form for all V1.x apps.  The difference is
in V2 if you have DPMI present (Win, os/2, etc) it doesn't need to load
the image, and if it must load CWSDPMI, CWSDPMI is smaller then GO32 and
is reentrant (only one copy for nested tasks).

Loading CWSDPMI as a TSR isn't necessary, it just makes things a tiny bit
faster by removing the search, load, and unload steps for each image.