http://bugs.winehq.org/show_bug.cgi?id=9685
--- Comment #52 from Anastasius Focht focht@gmx.net 2007-09-30 09:36:00 --- Created an attachment (id=8311) --> (http://bugs.winehq.org/attachment.cgi?id=8311) pb trace with ioctl handling problem in wineserver
Hello,
the game PB servers seem to behave differently. Some of them kick early for "unknown windows api xxx" and others get much further.
The "good" ones assign you PB player GUID (message) and the PB "B" service actually tries to talk to kernel driver. The bad news is: the ioctl request is never delivered to kernel driver itself (IRP). Somewhere in wine server the request fails. Attached is trace of this case. I added some debug trace in ntdll ("server_ioctl_file") to see where it fails.
tid 0x41 is device driver context tid 0x2f is "B" service context
--- snip trace --- .. 002f:trace:ntdll:NtDeviceIoControlFile (0x64,(nil),(nil),(nil),0x61762854,0x002261c0,0x51bf44,0x00000008,0x41b228,0x00000010) 002f:trace:ntdll:server_ioctl_file server_ioctl_file begin: 0x64, 2261c0 002f:trace:ntdll:server_ioctl_file server_ioctl_file end: 0x64, 2261c0, c0000022 002f:trace:ntdll:server_ioctl_file server_ioctl_file end wait: 0x64, 2261c0, c0000022 .. --- snip trace ---
ioctl code 0x2261c0 decodes as follows: device_type=0x22, func=0x870, access=FILE_READ_ACCESS, method=METHOD_BUFFERED
Returned status code 0xc0000022 is actually STATUS_ACCESS_DENIED.
The driver symbolic link handle is valid so it must be something different. I remember app <-> kernel driver device i/o control stuff has worked several months ago. Probably some parts in wineserver have been changed/rewritten over the months.
Regards