March 2014 - Wine-Devel - list.winehq.org

Re: how to build wine with USB support ?

by Hin-Tak Leung

------------------------------ On Tue, Mar 18, 2014 1:56 PM GMT Alois Schlögl wrote: >On 2014-03-17 17:22, Uwe Bonnes wrote: >> "Alois" == Alois Schlögl <alois.schloegl(a)gmail.com> writes: > > Alois> In one case, HKLM\System\CurrentControlSet\Services\<driver name> > Alois> points to system32\Driver\hidusb.sys; > > Can you show the exports of hidusb.sys? Maybe it is also a good candidate for > a replacement dll. > > Bye > > > >I'm not sure how to export that information. nm does not work because >its a sys file. >pefile gives quite some information but no export section. grep Hint >pefile_output lists this: > >ntoskrnl.exe.ExFreePool Hint[77] >ntoskrnl.exe.ExAllocatePoolWithTag Hint[65] >ntoskrnl.exe.KeSetEvent Hint[598] >ntoskrnl.exe.IofCallDriver Hint[482] >ntoskrnl.exe.KeWaitForSingleObject Hint[621] >ntoskrnl.exe.MmMapLockedPages Hint[687] >ntoskrnl.exe.InterlockedDecrement Hint[278] >ntoskrnl.exe.IoBuildDeviceIoControlRequest Hint[302] >ntoskrnl.exe.InterlockedIncrement Hint[281] >ntoskrnl.exe.KeResetEvent Hint[588] >ntoskrnl.exe.InterlockedExchange Hint[279] >ntoskrnl.exe.IoInvalidateDeviceState Hint[385] >ntoskrnl.exe.IoQueueWorkItem Hint[401] >ntoskrnl.exe.InterlockedCompareExchange Hint[277] >ntoskrnl.exe.IoAllocateWorkItem Hint[294] >ntoskrnl.exe.IoCancelIrp Hint[307] >ntoskrnl.exe.KeTickCount Hint[614] >ntoskrnl.exe.KeBugCheckEx Hint[502] >ntoskrnl.exe.PoCallDriver Hint[822] >ntoskrnl.exe.KeInitializeSpinLock Hint[542] >ntoskrnl.exe.KeInitializeEvent Hint[536] >ntoskrnl.exe.IoFreeWorkItem Hint[355] >ntoskrnl.exe.IofCompleteRequest Hint[483] >HIDCLASS.SYS.HidRegisterMinidriver Hint[3] >USBD.SYS.USBD_ParseConfigurationDescriptorEx Hint[22] >USBD.SYS.USBD_CreateConfigurationRequestEx Hint[6] > > >-- Alois > >

March 18, 2014

Re: how to build wine with USB support ?

by Uwe Bonnes

>>>>> "Alois" == Alois Schlögl <alois.schloegl(a)gmail.com> writes: Alois> On 2014-03-17 17:22, Uwe Bonnes wrote: >>>>>>> "Alois" == Alois Schlögl <alois.schloegl(a)gmail.com> writes: >> Alois> In one case, HKLM\System\CurrentControlSet\Services\<driver name> Alois> points to system32\Driver\hidusb.sys; >> >> Can you show the exports of hidusb.sys? Maybe it is also a good >> candidate for a replacement dll. >> >> Bye >> Alois> I'm not sure how to export that information. nm does not work Alois> because its a sys file. pefile gives quite some information but Alois> no export section. grep Hint pefile_output lists this: ... Alois> ntoskrnl.exe.IofCompleteRequest Hint[483] Alois> HIDCLASS.SYS.HidRegisterMinidriver Hint[3] Alois> USBD.SYS.USBD_ParseConfigurationDescriptorEx Hint[22] ... It looks like hidusb.sys only exports some way to register another (mini) driver. Probably this minidriver creates some device. How does the application talk to that device. Probably another dll is involved or access happens with Read|WriteFile() to that device. But I am only guessing, I have no experience with HID. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

March 18, 2014

Re: gdi32/tests: Mark Win8.1 behaviour for johab charset as broken

by Akihiro Sagawa

On Tue, 18 Mar 2014 00:21:19 +0100, André Hentschel wrote: > Thx for clarification, after testing a lot i finally removed it: > https://source.winehq.org/patches/data/103264 > > After hours of testing, this is the best solution i found. > > On Windows with fonts that support johab charset, GetCharABCWidthsA fails for > > characters >= 0xff > > I see no need to replicate that in Wine and with this behavior there's nothing to test... I agree with you. I confrmed the bahavior, too. Thanks, Akihiro Sagawa

March 18, 2014

Re: vbscript: Allow creating RegExp object by new expression.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5757 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvista (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7pro64 (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found === w7pro64 (64 bit) === No test summary line found

March 18, 2014

Re: how to build wine with USB support ?

by Alois Schlögl

On 2014-03-17 17:22, Uwe Bonnes wrote: >>>>>> "Alois" == Alois Schlögl <alois.schloegl(a)gmail.com> writes: > > Alois> In one case, HKLM\System\CurrentControlSet\Services\<driver name> > Alois> points to system32\Driver\hidusb.sys; > > Can you show the exports of hidusb.sys? Maybe it is also a good candidate for > a replacement dll. > > Bye > I'm not sure how to export that information. nm does not work because its a sys file. pefile gives quite some information but no export section. grep Hint pefile_output lists this: ntoskrnl.exe.ExFreePool Hint[77] ntoskrnl.exe.ExAllocatePoolWithTag Hint[65] ntoskrnl.exe.KeSetEvent Hint[598] ntoskrnl.exe.IofCallDriver Hint[482] ntoskrnl.exe.KeWaitForSingleObject Hint[621] ntoskrnl.exe.MmMapLockedPages Hint[687] ntoskrnl.exe.InterlockedDecrement Hint[278] ntoskrnl.exe.IoBuildDeviceIoControlRequest Hint[302] ntoskrnl.exe.InterlockedIncrement Hint[281] ntoskrnl.exe.KeResetEvent Hint[588] ntoskrnl.exe.InterlockedExchange Hint[279] ntoskrnl.exe.IoInvalidateDeviceState Hint[385] ntoskrnl.exe.IoQueueWorkItem Hint[401] ntoskrnl.exe.InterlockedCompareExchange Hint[277] ntoskrnl.exe.IoAllocateWorkItem Hint[294] ntoskrnl.exe.IoCancelIrp Hint[307] ntoskrnl.exe.KeTickCount Hint[614] ntoskrnl.exe.KeBugCheckEx Hint[502] ntoskrnl.exe.PoCallDriver Hint[822] ntoskrnl.exe.KeInitializeSpinLock Hint[542] ntoskrnl.exe.KeInitializeEvent Hint[536] ntoskrnl.exe.IoFreeWorkItem Hint[355] ntoskrnl.exe.IofCompleteRequest Hint[483] HIDCLASS.SYS.HidRegisterMinidriver Hint[3] USBD.SYS.USBD_ParseConfigurationDescriptorEx Hint[22] USBD.SYS.USBD_CreateConfigurationRequestEx Hint[6] -- Alois

March 18, 2014

Re: mshtml: Fixed tests on old IEs and improved results on IE11.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5749 Your paranoid android. === w8 (32 bit htmldoc) === htmldoc.c:2964: Test failed: unexpected call Exec_ShellDocView_138 htmldoc.c:2964: Test failed: unexpected call Exec_ShellDocView_138 htmldoc.c:5289: Test failed: elem != NULL htmldoc.c:2964: Test failed: unexpected call Exec_ShellDocView_138 htmldoc.c:2861: Test failed: unexpected command 74 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:6012: Test failed: expected Exec_ShellDocView_67 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:6012: Test failed: expected Exec_ShellDocView_67 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:6012: Test failed: expected Exec_ShellDocView_67 htmldoc.c:2989: Test failed: unexpected command 137 htmldoc.c:2989: Test failed: unexpected command 137 htmldoc.c:5946: Test failed: expected Exec_ShellDocView_67 htmldoc.c:2868: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:2868: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:2861: Test failed: unexpected command 74 htmldoc.c:2861: Test failed: unexpected command 74 htmldoc.c:2964: Test failed: unexpected call Exec_ShellDocView_138 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:5946: Test failed: expected Exec_ShellDocView_67 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:5946: Test failed: expected Exec_ShellDocView_67 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:5946: Test failed: expected Exec_ShellDocView_67 htmldoc.c:2989: Test failed: unexpected command 133 htmldoc.c:3433: Test failed: dwFlags = 140 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:6084: Test failed: expected Exec_ShellDocView_67 htmldoc.c:2861: Test failed: unexpected command 74 htmldoc.c:985: Test failed: unexpected id 3000032 htmldoc.c:3300: Test failed: unexpected call {f6d02767-9c80-428d-b974-3f1729453fdb} htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:5946: Test failed: expected Exec_ShellDocView_67 htmldoc.c:2989: Test failed: unexpected command 137 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:5946: Test failed: expected Exec_ShellDocView_67 htmldoc.c:2861: Test failed: unexpected command 74 htmldoc.c:2989: Test failed: unexpected command 133 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:3165: Test failed: unexpected state L"uninitialized", expected 4 htmldoc.c:3165: Test failed: VT_I4(out)=0, expected 4 htmldoc.c:7807: Test failed: expected Exec_ShellDocView_67 htmldoc.c:7811: Test failed: expected Exec_ShellDocView_84

March 18, 2014

Re: [PATCH] scrrun: Implement WriteLine/Write for ITextStream (try2)

by Nikolay Sivov

On 3/18/2014 12:28, Dmitry Timoshkov wrote: > Nikolay Sivov <nsivov(a)codeweavers.com> wrote: > >> +static HRESULT textstream_writestr(struct textstream *stream, BSTR text) >> +{ >> + DWORD written = 0; >> + BOOL ret; >> + >> + if (stream->unicode) { >> + if (stream->first_write) { >> + static const short utf16bom = 0xfeff; > 'WCHAR' instead of 'short' would look more natural IMO, especially since > remaining data is WCHAR based.. I don't think it's really important.

March 18, 2014

Re: [PATCH] scrrun: Implement WriteLine/Write for ITextStream (try2)

by Dmitry Timoshkov

Nikolay Sivov <nsivov(a)codeweavers.com> wrote: > +static HRESULT textstream_writestr(struct textstream *stream, BSTR text) > +{ > + DWORD written = 0; > + BOOL ret; > + > + if (stream->unicode) { > + if (stream->first_write) { > + static const short utf16bom = 0xfeff; 'WCHAR' instead of 'short' would look more natural IMO, especially since remaining data is WCHAR based.. -- Dmitry.

March 18, 2014

Re: user32/tests: Use BOOL type where appropriate

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5739 Your paranoid android. === w2000pro (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 0005009E fg 00020036 in hook HCBT_ACTIVATE win.c:2952: Test failed: GetActiveWindow() = 00000000 win.c:2952: Test failed: GetFocus() = 00000000 win.c:2975: Test failed: GetActiveWindow() = 00000000 win.c:2975: Test failed: GetFocus() = 00000000 win.c:3036: Test failed: GetActiveWindow() = 00000000 win.c:3036: Test failed: GetFocus() = 00000000 === wxppro (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 00030160 fg 00060064 in hook HCBT_ACTIVATE win.c:2952: Test failed: GetActiveWindow() = 00000000 win.c:2952: Test failed: GetFocus() = 00000000 win.c:2975: Test failed: GetActiveWindow() = 00000000 win.c:2975: Test failed: GetFocus() = 00000000 win.c:3036: Test failed: GetActiveWindow() = 00000000 win.c:3036: Test failed: GetFocus() = 00000000 === wvista (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 00040264 fg 00010054 in hook HCBT_ACTIVATE win.c:2952: Test failed: GetActiveWindow() = 00000000 win.c:2952: Test failed: GetFocus() = 00000000 win.c:2975: Test failed: GetActiveWindow() = 00000000 win.c:2975: Test failed: GetFocus() = 00000000 win.c:3036: Test failed: GetActiveWindow() = 00000000 win.c:3036: Test failed: GetFocus() = 00000000 === wvistau64 (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 00040184 fg 0001006C in hook HCBT_ACTIVATE win.c:2952: Test failed: GetActiveWindow() = 00000000 win.c:2952: Test failed: GetFocus() = 00000000 win.c:2975: Test failed: GetActiveWindow() = 00000000 win.c:2975: Test failed: GetFocus() = 00000000 win.c:3036: Test failed: GetActiveWindow() = 00000000 win.c:3036: Test failed: GetFocus() = 00000000 === w8 (32 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 0006019E fg 00010048 in hook HCBT_ACTIVATE win.c:6406: Test failed: 0x80/0x1c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6428: Test failed: 0x80/0x1010000: window rect 0,0-1024,768 win.c:6406: Test failed: 0x80/0x81c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6406: Test failed: 0/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6406: Test failed: 0x40000/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6406: Test failed: 0x80/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6406: Test failed: 0x80/0x1c50000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6428: Test failed: 0x80/0x1050000: window rect 0,0-1024,768 win.c:6406: Test failed: 0x80/0x1c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6428: Test failed: 0x80/0x1410000: window rect 0,0-1024,768 win.c:2952: Test failed: GetActiveWindow() = 00000000 win.c:2952: Test failed: GetFocus() = 00000000 win.c:2975: Test failed: GetActiveWindow() = 00000000 win.c:2975: Test failed: GetFocus() = 00000000 win.c:3036: Test failed: GetActiveWindow() = 00000000 win.c:3036: Test failed: GetFocus() = 00000000 win.c:6189: Test failed: wrong error 31 === wvistau64 (64 bit win) === win.c:892: Test failed: wrong dwWindowStatus: 0001 != 0000 active 0000000000040184 fg 000000000001006C in hook HCBT_ACTIVATE win.c:2952: Test failed: GetActiveWindow() = 0000000000000000 win.c:2952: Test failed: GetFocus() = 0000000000000000 win.c:2975: Test failed: GetActiveWindow() = 0000000000000000 win.c:2975: Test failed: GetFocus() = 0000000000000000 win.c:3036: Test failed: GetActiveWindow() = 0000000000000000 win.c:3036: Test failed: GetFocus() = 0000000000000000

March 18, 2014

Re: rpcrt4/tests: Add a couple of tests for marshalling an array of strings. Take 2.

by Dmitry Timoshkov

Marvin <testbot(a)winehq.org> wrote: > === w8 (32 bit server) === > server.c:984: Test failed: get_ranged_enum() returned 1997012995 instead of RE3 > server.c:984: Test failed: get_ranged_enum() returned -65533 instead of RE3 > server.c:984: Test failed: get_ranged_enum() returned 1997012995 instead of RE3 These failures are not related to my tests. -- Dmitry.

March 18, 2014