Re: Mismatch Between win32syscalls.h and Windows System Call Numbers

thank you

On Thu, Jun 5, 2025 at 3:11 PM Stefan Dösinger <[email protected]>
wrote:

>
>
> > Am 05.06.2025 um 06:18 schrieb zhengxianwei <[email protected]>:
> >
> > The APIs and call numbers in win32syscalls.h don't seem to match those
> in the Windows system.
> >
> > NtGdiAlphaBlend is listed as 4 in win32syscalls.h, but in reality, it's
> 0x1075 in win32u.dll on Windows 11.
> >
> > So are these values user-defined?
>
> Afaiu we don't need them to match up, and they differ between Windows
> versions too. On paper, applications aren't supposed to call syscalls
> directly at all. Those that do usually parse the syscall thunks in the DLLs
> to extract the syscall numbers.
>
> If you have an application that does depend on a particular syscall having
> a particular number, and the application works on a reasonable number of
> Windows versions, then that would be a reason for us to follow a particular
> Windows version.
>
>
>