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: Tue, 19 Mar 2024 10:32:31 -0600 [thread overview]
Message-ID: <CANV9t=TOtT6S8K6D5qo1kV7ZMVGBxBhHGPPq36LzWfb2LfWkWw@mail.gmail.com> (raw)
In-Reply-To: <Zfm7ZqZBdMBaoEOM@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Tue, Mar 19, 2024 at 10:21 AM Corinna Vinschen wrote:
On Mar 19 09:18, Bill Stewart via Cygwin wrote:
>
> > I'm not sure of the exact scenario that led to the "RtlGetVersion is
> > subject to manifesting" conclusion, but I can't reproduce it.
>
> You have to create an application with an application manifest not
> supporting your OS.
>
> 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.
>
> Fortunately Microsoft didn't change the required manifest GUID entry
> since the introduction of Windows 10. Even Windows 11 is still using
> the same GUID.
>
Interesting. Thanks for the clarification!
Bill
next prev parent reply other threads:[~2024-03-19 16:33 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 [this message]
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
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=TOtT6S8K6D5qo1kV7ZMVGBxBhHGPPq36LzWfb2LfWkWw@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).