From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: GetVersionEx() depreciated, what should be used instead for Windows 7/8/10?
Date: Wed, 20 Mar 2024 08:26:01 -0600 [thread overview]
Message-ID: <CANV9t=RzYjxnf3qzJjaG6iGmS7zjS_JQk2Or+fO8zfB8dMMjKQ@mail.gmail.com> (raw)
In-Reply-To: <0d8daf74-2861-8b08-b47c-28cf5d3b991f@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On Wed, Mar 20, 2024 at 5:40 AM Christian Franke wrote:
Corinna Vinschen via Cygwin wrote:
>
> > For Cygwin apps, this occured when you built, say, an executable under
> > Windows 8.1 before Windows 10 support was added to the Cygwin toolchain:
> > the manifest linked to the Cygwin executable didn't yet contain a GUID
> > entry for Windows 10 support.
> >
> > In this case, RtlGetVersion returns an OS version 6.3 even when running
> > under the 10.0 kernel. This behaviour exists back 'til Windows Vista.
>
> Could not reproduce the latter on Win10. I tested with recent Win10 and
> Win11 and also found a Win10 1511 (and Slackware 1.1.2, Win3.1, OS/2,
> ...) in my VM image museum.
>
> Regardless of the exe manifest, RtlGetVersion and RtlGetNtVersionNumbers
> return the correct versions:
> 10.0.22621 (Win11 22H2)
> 10.0.19045 (Win10 22H2)
> 10.0.10586 (Win10 1511)
>
> Without a manifest, GetVersionEx returns:
> 6.2.9200 (Win8)
Thanks for testing. That was my recollection (RtlGetVersion is not subject
to manifesting).
Bill
next prev parent reply other threads:[~2024-03-20 14:26 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 [this message]
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
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='CANV9t=RzYjxnf3qzJjaG6iGmS7zjS_JQk2Or+fO8zfB8dMMjKQ@mail.gmail.com' \
--to=bstewart@iname.com \
--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).