5 Jun
2025
5 Jun
'25
9:06 a.m.
Thanks, it looks like this syscall number was automatically generated by some tool. I think I have a general idea now. On Thu, Jun 5, 2025 at 3:59 PM Biswapriyo Nath <nathbappai(a)gmail.com> wrote:
On Thu, Jun 5, 2025 at 8:49 AM zhengxianwei <baikaishiuc(a)gmail.com> wrote:
NtGdiAlphaBlend is listed as 4 in win32syscalls.h, but in reality, it's 0x1075 in win32u.dll on Windows 11.
The syscall number differs across major Windows versions and Windows 10/11 revisions too. For example, * syscall number across Windows 10/11 revisions - https://hfiref0x.github.io/X86_64/NT10_w32ksyscalls.html#:~:text=NtGdiAlphaB... * syscall number across major Windows versions - https://j00ru.vexillium.org/syscalls/win32k/64/#:~:text=NtGdiAlphaBlend