From:	"Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: djgpp and W2K
Date:	Wed, 1 Aug 2001 23:54:36
Organization:	Aspen Technology, Inc.
Lines:	24
Message-ID:	<3b6896bc.sandmann@clio.rice.edu>
References:	<3B68BA51 DOT 34F1 AT earthlink DOT net>
NNTP-Posting-Host:	dcloan.hou.aspentech.com
X-Trace:	selma.aspentech.com 996728557 27810 10.32.115.107 (2 Aug 2001 05:02:37 GMT)
X-Complaints-To:	postmaster AT aspentech DOT com
NNTP-Posting-Date:	2 Aug 2001 05:02:37 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

> I have been compiling and running several small but critical C programs
> with DJGPP under NT 4.0 with no problems at all.  Now I would move to
> Windows 2000.  I have tested some of my programs under W2K and all seems
> OK. Are there problems with djgpp and w2k?  What should I be looking
> for?

The NTVDM for Windows 2000 has a bug (as does XP RC1) which aborts when
you nest DPMI images.  If you don't try to rebuild the images (make/gcc)
you probably won't see too many problems.  There are other issues around
behavior (expecting NUL to stat in a directory?)  If your images work,
great.  Many will probably still work under XP also.

Included below are binary diffs to NTVDM.EXE to work around the bug in
Windows 2000.  Eventually I'll provide an executable to do it.  You must
either disable file protection or also patch the ones in dllcache.

Comparing files ntvdm.sp2_pat and NTVDM.SP2
0004C89F: 58 AC
0004C8A0: 5E E6

C:\WINNT\system32>fc /b ntvdm.exe *.exo
Comparing files ntvdm.EXE and ntvdm.EXO
0004C864: 58 AC
0004C865: 5E E6

- Raw text -