Xref: news2.mv.net comp.os.msdos.djgpp:4813
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bug in CWSDPMI?
Date: Mon, 10 Jun 1996 14:53:20 CDT
Organization: Rice University, Houston, Texas
Lines: 12
Message-ID: <31bc7d30.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960609183529 DOT 342r-100000 AT is> <4ph0gv$eeh AT ns DOT felk DOT cvut DOT cz>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

>   I do not think so. I have same problems on :
>        1) DOS 6.2, 8-12 MB RAM, DOS=HIGH, "single computer" 
>            only Windows logo, than DOS prompt (no windows...)
>   Add emm386 to config.sys and this bug disapers..

Interesting.  Does the problem only happen after running GCC (which nests
programs) or after a single execution of a simple "hello world" type
program?  I'm assuming you don't have CWSDPMI resident, but it auto
loads.  Do you have any tools to make sure the memory and interrupt
tables are the same before and after the "hello world" test?  Does it
fail with the same config if you don't have DOS=HIGH? No smartdrv or
ramdrive?