Mail Archives: djgpp/2000/03/16/20:10:27

From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups: comp.os.msdos.programmer,comp.os.msdos.djgpp
Subject: Re: Is DOS dead?
Date: Thu, 16 Mar 2000 17:27:11 +0200
Organization: NetVision Israel
Lines: 27
Message-ID: <Pine.SUN.3.91.1000316172141.5735H-100000@is>
References: <fmj8csoh6qqnpvrsdtlk83ec462s8a4sbe AT 4ax DOT com> <38C7D12E DOT 1E12 AT gmx DOT net> <i57gcsk294pgff526i9gihqsjmarlvhnv3 AT 4ax DOT com> <38CD09B3 DOT 7373 AT gmx DOT net> <Pine DOT SUN DOT 3 DOT 91 DOT 1000314094608 DOT 4527E-100000 AT is> <38CE19B2 DOT 69C7 AT gmx DOT net> <Pine DOT SUN DOT 3 DOT 91 DOT 1000315104128 DOT 17230G-100000 AT is> <38CF7CED DOT 505A AT gmx DOT net> <Pine DOT SUN DOT 3 DOT 91 DOT 1000315185511 DOT 20407P-100000 AT is> <38D0B4D1 DOT 380F AT gmx DOT net>
Mime-Version: 1.0
X-Trace: 953220591 16321 (16 Mar 2000 15:29:51 GMT)
X-Complaints-To: abuse AT netvision DOT net DOT il
NNTP-Posting-Date: 16 Mar 2000 15:29:51 GMT
X-Sender: eliz AT is
In-Reply-To: <>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

On Thu, 16 Mar 2000, Michael Tippach wrote:

> > > > > it takes 3 more lines of assembly code to detect NT.
> > > >
> > > > That's not really true, especially now that you need to distinguish
> > > > between NT and W2K.
> > >
> > > So does W2K return a different value than 0x3205 from function 0x3306?
> > 
> > No, it reports the same value, but behaves differently.
> In how far does it behave differently? Could this different behaviour be
> used to detect either version or is there no way to, by means of code,
> inspect the differences without crashing the NTVDM on one system?

No, I don't know about any way of telling NT and W2K apart without 
crashing the system.  This test is required *because* different 
work-arounds are needed in each case to avoid crashes and other 

One problem with NT that needs to be worked around is that NT ignores the 
hight 16 bits of the user procedure address that is installed as a 
real-mode  callback (e.g., for handling mouse events).  One problem with 
W2K that needs to be worked around is that nested DPMI (well, DJGPP, to be 
precise) programs crash NTVDM; the reason for the latter problem is still 
unknown at this time.

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019