X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Subject: RE: ntvdmpat.exe and Win2K SP3 (fwd) Date: Tue, 17 Sep 2002 11:43:45 +0200 Message-ID: <250B3114DA16D511B82C00E0094005F809D3164D@MSGWAW11> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ntvdmpat.exe and Win2K SP3 (fwd) Thread-Index: AcJduRgWXbPksradRAus0vKgZ3W/pAAdW08g From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g8H9hnP13769 Reply-To: djgpp-workers AT delorie DOT com Perhaps they have used more optimizing compiler that produced different binary output, without actually changing anything. -----Original Message----- From: Charles Sandmann [mailto:sandmann AT clio DOT rice DOT edu] Sent: Monday, September 16, 2002 9:29 PM To: DJGPP developers Subject: ntvdmpat.exe and Win2K SP3 (fwd) FYI - it seems that Microsoft has been messing with NTVDM in the recent service packs without fixing things - which means they might be breaking things also. Something else to test ... Forwarded message: > From: Manfred Schwarb > > i have upgraded to Windows 2000 ServicePack 3 which seems to > come with a new version of ntvdm.exe (5.0.2195.4127). > your patch ntvdmpat.exe does not match anymore, giving the > message "Old patch string not found in C:\WINNT\system32\ntvdm.exe!" > > have you already investigated this issue? at fist glance it seems that > also the new version shows the nesting bug, so your patch seems to > remain valuable. > > http://clio.rice.edu/djgpp/W2K_workaround.htm shows not yet any information > concerning SP3.