Date: Wed, 7 Feb 2001 14:33:48 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Eric Botcazou <ebotcazou AT libertysurf DOT fr>
cc: Djgpp newsgroup <djgpp AT delorie DOT com>
Subject: Re: Win2k vs Win NT4
In-Reply-To: <006001c090ec$95eea320$038724d5@zephyr>
Message-ID: <Pine.SUN.3.91.1010207143147.4599P-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 7 Feb 2001, Eric Botcazou wrote:

> Quite right, the standard mouse mickeys driver (based on a RMCB) works
> perfectly under Win2k, while it crashes under Win NT4. The problem is: how
> to pick between this one and the workaround ('polling' driver) when the
> detected OS is 'WIN_NT' ?
> 
> > The problem is, there's no simple way of distinguishing between NT and
> > W2K from a DJGPP program.
> 
> I'm just trying to find one !

Good luck; we tried but couldn't.  If you find a reasonable way, please 
post it here.

> It was reported that the 'polling' driver,
> which uses only direct int33 functions calls, doesn't behave the same under
> Win2k as it does under Win NT4. This might be an angle of attack...

IMHO, it hardly makes sense to use Int 33h calls to distinguish between 
two version of the OS.  It's certainly wrong for a library to do that; 
perhaps on the application level it is justified.