A recent patch included a change to the error code returned from NtQueryInformationToken, and it seems to have upset an application I was running.
From looking at a --debugmsg +ntdll trace, it appears that the application called the function first with a zero-length buffer in order to findout how big a buffer was needed. After the error code was changed, the application called the function one time and then exited.
This trivial patch reverts that function back to the way it was.
-ajp
ChangeLog: - Fix buffer length error code for NtQueryInformationToken
Index: dlls/ntdll/nt.c
===================================================================
RCS file: /home/wine/wine/dlls/ntdll/nt.c,v
retrieving revision 1.59
diff -u -r1.59 nt.c
--- dlls/ntdll/nt.c 30 Sep 2003 01:04:19 -0000 1.59
+++ dlls/ntdll/nt.c 5 Oct 2003 21:22:53 -0000
@@ -225,7 +225,7 @@
*retlen = len;
if (tokeninfolength < len)
- return STATUS_INFO_LENGTH_MISMATCH;
+ return STATUS_BUFFER_TOO_SMALL;
switch (tokeninfoclass)
{
