Xref: news2.mv.net comp.os.msdos.djgpp:4852
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bug in CWSDPMI?
Date: Tue, 11 Jun 1996 10:39:54 CDT
Organization: Rice University, Houston, Texas
Lines: 16
Message-ID: <31bd934a.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960610174529 DOT 3539C-100000 AT is> <31bca3c6 DOT sandmann AT clio DOT rice DOT edu> <31bca5e2 DOT sandmann AT clio DOT rice DOT edu> <4pj63i$jpd AT artemis DOT ibernet DOT es>
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 had the same problem a couple of months ago and ONE AND ONLY way to solve
> it was placing EMM386 NOEMS in the CONFIG.SYS file. 

While I appreciate your flexibility in changing your computer settings to
work around the bug, it is a bug, and the only way to fix the bug is to
collect enough information to allow me to reproduce it and fix it.  I never
know if a bug like this is specific to a single buggy release or pervasive
until I get lots of help in this sorts of testing.

So, if you see such bugginess in CWSDPMI, drop me a note and post it.
The personal note makes sure I see it (lost news and/or not having time
to read news).  When I get a chance to do CWSDPMI stuff I will try to
resolve all known bugs at that time.

Oh, I'm bad about forgetting too, so it doesn't hurt to harrass me.
Thanks for the info.