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

how to build wine with USB support ?
by Alois Schlögl 18 Mar '14

18 Mar '14

Hi I'm trying to use USB devices for Data acquisition on wine. The recording software is proprietary, but runs on wine. (It IgorPro with some binary called FPulse, and MultiClamp Commander 700B). The problem occurs only when trying to connect to the recording device through USB. I've already found the page [1] and trying to build wine with the recommended patch. Unfortunately, the current patches [2] do not apply cleanly to the most recent version of wine-git. Therefore, I'm asking what the recommended approach is ? Is there a more recent set up patches ? The once from [2] have been updated last in Jun 2012 ? Or would you recommend using the sources of wine from that date ? Kind regards, Alois [1] http://wiki.winehq.org/USB [2] ftp://ftp.etersoft.ru/pub/people/amorozov/usb/current/

3 7

Re: how to build wine with USB support ?
by Hin-Tak Leung 18 Mar '14

18 Mar '14

------------------------------ 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 > >

1 0

Re: gdi32/tests: Mark Win8.1 behaviour for johab charset as broken
by Akihiro Sagawa 18 Mar '14

18 Mar '14

On Sat, 15 Mar 2014 00:15:54 +0100, André Hentschel wrote: > - {JOHAB_CHARSET, 0x8446, 0x3135, > + {JOHAB_CHARSET, 0x8446, 0x3135, TRUE /* Win8.1 */, > {TRUE, TRUE, FALSE, FALSE, TRUE, FALSE, FALSE, FALSE, FALSE, FALSE, FALSE, TRUE}}, (snip) > + ok((pGetCharABCWidthsA(hdc, c[i].a, c[i].a + 1, a) && > + pGetCharABCWidthsW(hdc, c[i].w, c[i].w + 1, w) && > + memcmp(a, w, sizeof a) == 0) || broken(c[i].broken), > "GetCharABCWidthsA and GetCharABCWidthsW should return same widths. charset = %u\n", c[i].cs); Regarding this test about Johab charset, you are missing the point. Which version of Windows does succeed in? I suspect that the test is broken. Don't you think? As far as I know, other wine testbots just skip the test due to missing Johab (=130) charset font. Moreover, my Windows 7 with Arial Unicode MS or YOzFont[1] doesn't pass because GetCharABCWidthsA returns 0. But I've not tested on Korean version Windows. If you have further information, please let me know. [1] YOzFont apparently supports Johab charset. It's available from http://yozvox.web.fc2.com/446F776E6C6F6164.html Regards, Akihiro Sagawa

2 2

Re: vbscript: Allow creating RegExp object by new expression.
by Marvin 18 Mar '14

18 Mar '14

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

1 0

Re: mshtml: Fixed tests on old IEs and improved results on IE11.
by Marvin 18 Mar '14

18 Mar '14

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

1 0

Re: [PATCH] scrrun: Implement WriteLine/Write for ITextStream (try2)
by Dmitry Timoshkov 18 Mar '14

18 Mar '14

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.

2 1

Re: user32/tests: Use BOOL type where appropriate
by Marvin 18 Mar '14

18 Mar '14

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

1 0

Re: rpcrt4/tests: Add a couple of tests for marshalling an array of strings. Take 2.
by Marvin 18 Mar '14

18 Mar '14

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=5736 Your paranoid android. === 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

2 1

Re: [PATCH] scrrun: Implement WriteLine/Write for ITextStream
by Marvin 18 Mar '14

18 Mar '14

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=5734 Your paranoid android. === wvista (32 bit filesystem) === filesystem.c:1342: Test failed: got L"\feffC:\\Users\\winetest\\AppData\\Local\\Temp\\scrrun\\test.txt\r\nT\f8a8\"\186e\7630", expected L"\feffC:\\Users\\winetest\\AppData\\Local\\Temp\\scrrun\\test.txt\r\n" === wvistau64 (32 bit filesystem) === filesystem.c:1342: Test failed: got L"\feffC:\\Users\\winetest\\AppData\\Local\\Temp\\scrrun\\test.txt\r\n\008d\f8a8'\186e\7550", expected L"\feffC:\\Users\\winetest\\AppData\\Local\\Temp\\scrrun\\test.txt\r\n" === w2008s64 (32 bit filesystem) === filesystem.c:1342: Test failed: got L"\feffC:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\scrrun\\test.txt\r\nu\f8a8'\186e\75af", expected L"\feffC:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\scrrun\\test.txt\r\n" === w7pro64 (32 bit filesystem) === filesystem.c:1342: Test failed: got L"\feffC:\\Users\\winetest\\AppData\\Local\\Temp\\scrrun\\test.txt\r\n\008c\f8a8(\625c\761f", expected L"\feffC:\\Users\\winetest\\AppData\\Local\\Temp\\scrrun\\test.txt\r\n" === w8 (32 bit filesystem) === filesystem.c:1342: Test failed: got L"\feffC:\\Users\\winetest\\AppData\\Local\\Temp\\scrrun\\test.txt\r\n\0129\019c", expected L"\feffC:\\Users\\winetest\\AppData\\Local\\Temp\\scrrun\\test.txt\r\n"

1 0

Re: gdi32/tests: GetCharABCWidthsA is broken for johab charset on windows
by Marvin 17 Mar '14

17 Mar '14

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=5730 Your paranoid android. === w8 (32 bit font) === font.c:3609: Test failed: W: tmLastChar for Nirmala UI Semilight got a839 expected 262c font.c:3609: Test failed: W: tmLastChar for Nirmala UI got a839 expected 262c font.c:4297: Test failed: 104 100

1 0