From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: GetVersionEx() depreciated, what should be used instead for Windows 7/8/10?
Date: Sat, 23 Mar 2024 10:57:31 +0100 [thread overview]
Message-ID: <38b3f5df-ea63-8eb4-f0f9-4057c0eeae90@t-online.de> (raw)
In-Reply-To: <ZfxPIbU5K_VgX5hZ@calimero.vinschen.de>
On Mar 21 16:15, Corinna Vinschen via Cygwin wrote:
> On Mar 21 09:58, Christian Franke via Cygwin wrote:
>>>> ..
> I just gave it a try on W11. The results are even more funny than I
> anticipated:
>
> ...
>
> So, yeah, with your observations especially on older W10 versions and
> with 8.1 doing the same thing, I guess we can safely drop the extra call
> to RtlGetNtVersionNumbers now.
Or:
Keep RtlGetVersionNumbers, compare result with RtlGetVersion and emit
debug output if both differ. This would allow to diagnose a possible
future reappearance of the issue.
> After such a long time, I don't know
> on which version of Windows we observed the problem.
Some developer preview?
Meantime I also tested with Win10 1607, 1703, 1709, 1803 VM snapshots
with same result.
--
Regards,
Christian
next prev parent reply other threads:[~2024-03-23 9:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 6:25 Cedric Blancher
2024-03-19 10:20 ` Christian Franke
2024-03-19 14:03 ` Bill Stewart
2024-03-19 15:00 ` Richard Campbell
2024-03-19 15:18 ` Bill Stewart
2024-03-19 16:20 ` Corinna Vinschen
2024-03-19 16:32 ` Bill Stewart
2024-03-20 11:39 ` Christian Franke
2024-03-20 14:26 ` Bill Stewart
2024-03-20 19:06 ` Corinna Vinschen
2024-03-21 8:58 ` Christian Franke
2024-03-21 15:15 ` Corinna Vinschen
2024-03-22 22:13 ` Ray Satiro
2024-03-23 9:37 ` Corinna Vinschen
2024-03-23 9:57 ` Christian Franke [this message]
2024-03-23 21:04 ` Corinna Vinschen
2024-03-24 14:42 ` Christian Franke
2024-03-24 21:05 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38b3f5df-ea63-8eb4-f0f9-4057c0eeae90@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).