On 13 Feb 2001, at 9:42, the Illustrious Earnie Boyd wrote:
> Mattia Barbon wrote:
> > Hello, is there any #define I could use
> > to determine w32api version?
> Not yet. I've thought about doing such. What is it you're
> trying to do with such a variable?
Indeed, we need more information...there are different release
versions (NT4 is version 4.00, Win95B is version 1.00 ) of the
win32api, however, those are mostly handled by checking your
system to determine which OS is being used. Mingw already knows
whether you are using WinNT or some other Windows OS.
Here are a few things about how to determine which MS version
of the Win32api you are currently using:
In a makefile, check what your OS system directory is (eg, if
C:\winnt is system directory then this is a WinNT platform, if
c:\windows is system directory, then this is a Win9x/WinME/XP? -
- not sure about Win2k) or what OS you are using (Environment
variable "OS"=Windows for Win9x, Windows_NT for WinNT4/5 and
Using quickview, the Operating System Version reference
(WinNT/Win98/Win95B is 4.00) is always included as part of the
.dll being loaded which allows you to determine how you might
handle a version specific Win32api call.
The Image Versions are different. Win98/Win95B image
version=1.09, WinNT4 image version=4.00.
Win95 has an Operating System Version number of 1.00 (api
reference or "Win32api v. 1.00").
All of that information is part of what is stored in
I am not sure but I think that NT5 is OS Version 5.00 (Win32api
reference), and I am not at all sure what the OS Version is for
Win2k (though I am inclined to believe it is also 5.00).
Most often, however, if you know your OS, you don't need to be
concerned with the api version being used.
Nothing real can be threatened.
Nothing unreal exists.