From: Martin Stromberg <Martin DOT Stromberg AT epl DOT ericsson DOT se>
Message-Id: <200105041148.NAA02489@lws256.lu.erisoft.se>
Subject: Re: win2000/ntvdm/djgpp (fwd)
To: djgpp-workers AT delorie DOT com
Date: Fri, 4 May 2001 13:48:22 +0200 (MET DST)
Cc: theowl AT freemail DOT c3 DOT hu
In-Reply-To: <3AF29483.25527.47F6564@localhost> from "The Owl" at May 04, 2001 11:37:39 AM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

The Owl said:
> this brings up another possibility for detecting NT (and even various
> versions of it), provided you are willing to use certain Bop interfaces:
> you would do this by 'executing' an specific invalid opcode and detect
> if you trigger an invalid opcode exception or get back some result. in
> the latter case you would then know that you are under NT, and examining
> the result would give you very specific ntvdm build info as there is
> one specific Bop function that returns a flat address inside ntvdm which
> i think is different for each build.

Sounds like a good idea, but perhaps a little to varying as this might
be broken by the next SP. 

But perhaps there is a BOP for getting the WINDOZE version (the one
reported to WINDOZE programs and not the one to DOZE programs)?


Right,

						MartinS