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: Thu, 19 Sep 2002 15:36:24 +0200 Message-ID: <250B3114DA16D511B82C00E0094005F809D31671@MSGWAW11> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ntvdmpat.exe and Win2K SP3 (fwd) Thread-Index: AcJf3/jMhgKcPvbpTjuszC8XLG+1TAAAUfSA From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= To: "Charles Sandmann" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g8JDaUP02464 Reply-To: djgpp-workers AT delorie DOT com Perhaps by posting a question to one of microsoft.public newsgroups ...? Thezse have been actively screened out by Microsoft developers for some time -----Original Message----- From: Eli Zaretskii [mailto:eliz AT is DOT elta DOT co DOT il] Sent: Thursday, September 19, 2002 2:32 PM To: Charles Sandmann Cc: DJGPP developers Subject: Re: ntvdmpat.exe and Win2K SP3 (fwd) On Mon, 16 Sep 2002, Charles Sandmann wrote: > 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 ... Is there any way to request (and get) from MS a list of changes in NTVDM?