From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP and Windows 2000
Date: Fri, 10 Aug 2001 12:57:53
Organization: Aspen Technology, Inc.
Lines: 23
Message-ID: <3b73da51.sandmann@clio.rice.edu>
References: <09D1E9BD9C30D311919200A0C9DD5C2C03E08992 AT mcaexc01 DOT msj DOT maxtor DOT com> <c997nto7c6rebcng858c8qjtao5mth6cmj AT 4ax DOT com>
NNTP-Posting-Host: dcloan.hou.aspentech.com
X-Trace: selma.aspentech.com 997468653 29004 10.32.115.107 (10 Aug 2001 18:37:33 GMT)
X-Complaints-To: postmaster AT aspentech DOT com
NNTP-Posting-Date: 10 Aug 2001 18:37:33 GMT
X-NewsEditor: ED-1.5.8
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

There are a number of issues with Windows 2000 and DJGPP - but the
severity of those issues depends a lot on what you are doing with
DJGPP.  If you want to rebuild the CVS tree, it's a huge pain with
a stock W2K system and stock V2.03 binaries (impossible unless you
know the tricks).  Even with the CVS tree there are about a 
dozen issues I'm still aware of - but I see a stable full featured
release at the end of the tunnel.

If you just want to compile some small projects with make, the
ntvdm patches and lfn=n workarounds make v2.03 usable.

What has made DJGPP so stable on the other platforms is lots of
use - and I'd like to attract volunteers to make Windows 2K a
good platform (since XP and W2K behave very much alike).

Many users have privately emailed telling me that the patches
and tricks allowed them to get their work done on Windows 2000.
I'd rather them hang in there while we get the bugs worked
out (or add to the discussion) instead of dumping DJPPP
because they can't wait or change OSes.  Certain things just
won't work at all under Windows 2000 without rebuilding the
applications.  If the user must have one of those tools, he
will need to help debug it or wait.