Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54535

Since this API sporadically fails with STATUS_INFO_LENGTH_MISMATCH
as GetLastError() (sic!) on Windows 11, retrying the call let us get
the relevant output.

No clear explanation of the cause of the failure, it's maybe generated
when modules are still loaded into child process and it detects
modification of the modules' list while enumerating all modules.
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Also some needed header files from Zycore version 1.4.1.

Instead of the 4 bytes array wire size returned by get_type_size,
which will truncate the pointer on 64-bit.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54562

Windows 11 uses a narrow non-breaking space instead of a plain one when
formatting numbers.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54583

NtGetNlsSectionPtr() supports an unknown section 14 which presumably
takes no id parameter such that the call succeeds.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54584

Microsoft backported support for the 60403 NLS version from Windows 11
21H2 to Windows 10 22H2 to ensure better compatibility between the two
systems. This is similar to when they preserved support for NLS
version 6020f when switching Windows 10 2004 to 60305.
So use larger version changes to check that IsValidNLSVersion() does
reject invalid versions.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54582

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54581

Signed-off-by: Torge Matthies <tmatthies@codeweavers.com>

Signed-off-by: Torge Matthies <tmatthies@codeweavers.com>

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54557

Signed-off-by: Marcus Meissner <marcus@jet.franken.de>

Introduced by commit a97fd9f2

Signed-off-by: Tingzhong Luo <luotingzhong@uniontech.com>

We don't have to reset pos and the sortkey state for every iteration of
the for-loop. In most cases the previous iteration's values are still
valid, and can be re-used, skipping a lot of duplicate work.
Signed-off-by: Torge Matthies <tmatthies@codeweavers.com>

If I'm interpreting this code correctly, once either of these two
if-conditions are true once, they will also be true at some point
during all of the remaining iterations of the for-loop. Thus, we can
just stop the for-loop here.
Signed-off-by: Torge Matthies <tmatthies@codeweavers.com>

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53176