Xref: news2.mv.net comp.os.msdos.djgpp:1836
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: CWS flames
Date: Mon, 11 Mar 1996 12:49:39 CST
Organization: Rice University, Houston, Texas
Lines: 14
Message-ID: <314475c3.sandmann@clio.rice.edu>
References: <9603110708 DOT AA12518 AT tntnhb3 DOT tn DOT tudelft DOT nl>
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

> Oh, but you shouldn't misunderstand me! I am not asking you to write a
> workaround for this. I just noticed the behavior and wanted to be sure that
> the problem was not in djgpp. This is apparently not the case, so for me the
> case is "solved".

Just ignore me when I act this way ... I have encountered a 1/2 dozen problems
in WFW 3.11, W95, and WNT in the last few months, none of which have a good
workaround, and there seems to be no interest at MS in fixing DPMI/DOS
support bugs.  When the owner of your operating environment is hostile to
you, it's probably time to find something else.  I'm just amazed that 
millions of customers tolerate being treated this way, then buy more.  In
the future I'll try an restrain myself to "know microsoft bug, avoid
MS products unless 100% of your environment is MS purchased".  I have learned
the very hard way to avoid any non-MS drivers in the W95 environment...