A much cleaner result (written by hand) that we can reuse where needed later (_i.e._ `GetNumaProcessorNode` which also crashes with [a similar MAV](https://gist.github.com/wasertech/f894ce8d6250e72a01a861c0e4eb6064) on multi-node systems).
Took me a while to understand where I should put everything, not even sure I got it right. Let me know.
I thought I was going to need `FileNumaNodeInformation` but turns out it's not really needed. I can remove it if you want.
This is what I see when I try to get a node count read:
```log
0024:fixme:ntdll:init_numa_info node affinity; using node 0.
GetNumaHighestNodeNumber: 1
```
I only see this fixme if I try to access `FILE_NUMA_NODE_INFORMATION`. I would really prefer such a behavior for our compatibility layer on any multi-node system.
A big thanks to @besentv and @zfigura for their invaluable feedback on this.
--
v8: ntdll: improve error handling in NtQuerySystemInformationEx
https://gitlab.winehq.org/wine/wine/-/merge_requests/8995
This patchset is just to correct the parameter passed to ShowWindow.
--
v2: wordpad: Correct show parameter passed to ShowWindow
cryptui: Correct show parameter passed to ShowWindow
comdlg32: Correct show parameter passed to ShowWindow
https://gitlab.winehq.org/wine/wine/-/merge_requests/9005