(SOLVED) macro _WIN32_WINNT return wrong

[VANYA]

Hi All!

Why does the _WIN32_WINNT macro on a Windows 7 system return & h502? Must return &h601 https://docs.microsoft.com/ru-ru/cpp/po ... ew=vs-2017

result command VER in the console:

Microsoft Windows [Version 6.1.7601]

Compiler incorrectly returns version windows

[VANYA]

Probably many did not understand ...

I'm talking about a serious compiler error, due to which data from 70 headers (where this macro is used) will be inaccessible for windows systems starting with Windows Vista and higher!

[fxm]

???

Code: Select all

#include "windows.bi"
Print _WIN32_WINNT

Microsoft Windows [version 10.0.17763.348]
(c) 2018 Microsoft Corporation. Tous droits réservés.

1282

[dodicat]

Hi VANYA
It was discussed here
viewtopic.php?f=14&t=26930&p=250229&hil ... 2A#p250229

Probably should have put the new definition at the head of windows.bi for version 1.06, but it will probably be fixed now.

from andykmv:

Code: Select all

#define _WIN32_WINNT &h0602
#include "windows.bi"

print hex(_WIN32_WINNT)
Dim DynamicTimeZoneInfo As DYNAMIC_TIME_ZONE_INFORMATION
GetDynamicTimeZoneInformation(@DynamicTimeZoneInfo)
Print DynamicTimeZoneInfo.TimeZoneKeyName
sleep
  

Code: Select all

602
GMT Standard Time  

What do you get?

[VANYA]

Hi All!

Microsoft Windows [version 10.0.17763.348]
(c) 2018 Microsoft Corporation. Tous droits réservés.

1282

Yes, hex(1282) = &h502 = Windows Server 2003

#define _WIN32_WINNT &h0602
#include "windows.bi"

Yes, adding a constant before #include "windows.bi" solves the problem, but is it really correct? It seems to me that the compiler should determine the version of Windows itself and, on the basis of this, draw a conclusion about the inclusion of headers. I understand that experienced programmers will not stop at this problem (there are a lot of ways to create a bicycle), but what about newcomers? Every time ask a question on the forum or immediately look for another compiler?

[dodicat]

fbide gives me
Windows NT 6.2 (build 9200)
For my win 10 ( Microsoft Windows [Version 10.0.17134.590])
But that is bye the way.
My win 10 is broken after fidelling around with the suspected malware GoRc.exe in fb 1.06.
But I have no other real choice, it seems that win 8.1 is on the way out, and three versions of win 10 reign supreme at the moment.
Of course everybody else in the known universe is in the same boat.
Anyway, happy cycling VANYA.

[MrSwiss]

Windows NT 6.2 (build 9200)

Aka: Windows 8.0 (Win 8.1 = NT 6.3)
Seems, that fbide is not interpreting correctly ... (never liked it, anyway).

[sancho3]

FBEdit on Windows 7
confirm &h502.

[jj2007]

Win7-64 should be version 6.1, build 7601 but the macro returns 1282.

[Josep Roca]

Which macro? _WIN32_WINNT is not a macro but a constant. Therefore, it will hold whatever value you assign to it.

If you don't define it, it will have a default value of &h0502.

Code: Select all

#ifndef _WIN32_WINNT
	const _WIN32_WINNT = &h0502
#endif
#ifndef WINVER
	const WINVER = _WIN32_WINNT
#endif

[VANYA]

Which macro? _WIN32_WINNT is not a macro but a constant. Therefore, it will hold whatever value you assign to it.

If you don't define it, it will have a default value of &h0502.

Code: Select all

#ifndef _WIN32_WINNT
	const _WIN32_WINNT = &h0502
#endif
#ifndef WINVER
	const WINVER = _WIN32_WINNT
#endif

WOW! I really thought that the Windows version is determined by the compiler. And this is a constant :)))))))))
I am ashamed. The question is closed. Thanks Josep Roca for the cold shower!

[jj2007]

To clarify one more bit: It's a constant because YOU instruct the compiler which is your target platform. So, if you are working on an application that is supposed to run on a thousand very, very old Windows XP machines, then you tell the compiler "hey, this is old stuff, please do not use functions that do not exist on such old machines".