Hi!
magnus(a)itkonsult-olsen.com wrote:
Hi
The commit 25758 are complete wrong, more I looking at more foualt I found
we are not longer windows comptable with the keyboard with this commit.
it mean win32k syscall does not longer working as it should do in windows.
and it also fuckup loading process of the keyboard.
We are trying to make it compatible.
example ntoskrnl is setting which defualt keyboard
that should be in use and so
on. in current change it does ignore ntoskrnl setting. and when ntoskrnl trying
set it will mess up the keyboard loading.
the protype for NtUserLoadKeyboardLayoutEx look like this what I can figout
HKL STDCALL NtUserLoadKeyboardLayoutEx( IN HANDLE Handle, x2, x3, x4, IN HWINSTA
pProcessWindowStation, x6, IN INT Flags);
That proto is B.S. Need to do your research better. Start using root Hooks to
figure
out what is being sent. I spent the whole last part of the summer figuring this keyboard
loading thingy. I had everything done but that offset arg. Looking through the Api logs,
there it is. The api monitors I use are trash and my hook crashes just about every
10 mins with out a log being made. Seeing this mail thread make me sick.
Simply! I did the research already!
But x2 and x6 are not in use.
I have not figout x3,x4 yet
I worked last night and part of the day,,,, watching this all from work!
Amazing!
James