December 2005 - Wine-Devel - list.winehq.org

[RESEND] riched20: register ListBox & ComboBox classes
by Cihan Altinay Dec. 4, 2005

Dec. 4, 2005

Another attempt to get some feedback for this patch... Hi, > This patch partially implements the undocumented REExtendedRegisterClass() > function by registering the two missing classes. That way MS Office 2003 and > probably other programs that rely on these classes display dialogs > completely which were empty before. > > Changelog: > Cihan Altinay <cihan(a)uq.edu.au> > Partially implement REExtendedRegisterClass() to register missing window > classes so that applications relying on them don't get confused. > It seems this patch was ignored and I would appreciate some comments because I haven't done much wine development yet (and probably made a lot of mistakes). Basically, I did some reverse engineering to see what is going on under Windows and implemented the (de)registration of the two classes accordingly. The effect of the patch can be seen in the attached screenshots which is the Options dialog of MS PowerPoint 2003. I agree that a patch that makes the controls actually work would be better :-) Cheers, Cihan

2 2

make errors in $WINE/dlls/wininet/netconnection.c
by Colin Wright Dec. 4, 2005

Dec. 4, 2005

After a clean and cvs -PAd I get the following errors during make netconnection.c: In function `sock_get_error': netconnection.c:205: error: `EINTR' undeclared (first use in this function) netconnection.c:205: error: (Each undeclared identifier is reported only once netconnection.c:205: error: for each function it appears in.) netconnection.c:206: error: `EBADF' undeclared (first use in this function) netconnection.c:207: error: `EPERM' undeclared (first use in this function) netconnection.c:208: error: `EACCES' undeclared (first use in this function) netconnection.c:209: error: `EFAULT' undeclared (first use in this function) netconnection.c:210: error: `EINVAL' undeclared (first use in this function) netconnection.c:211: error: `EMFILE' undeclared (first use in this function) netconnection.c:212: error: `EWOULDBLOCK' undeclared (first use in this function) netconnection.c:213: error: `EINPROGRESS' undeclared (first use in this function) netconnection.c:214: error: `EALREADY' undeclared (first use in this function) netconnection.c:215: error: `ENOTSOCK' undeclared (first use in this function) netconnection.c:216: error: `EDESTADDRREQ' undeclared (first use in this function) netconnection.c:217: error: `EMSGSIZE' undeclared (first use in this function) netconnection.c:218: error: `EPROTOTYPE' undeclared (first use in this function) netconnection.c:219: error: `ENOPROTOOPT' undeclared (first use in this function) netconnection.c:220: error: `EPROTONOSUPPORT' undeclared (first use in this function) netconnection.c:221: error: `ESOCKTNOSUPPORT' undeclared (first use in this function) netconnection.c:222: error: `EOPNOTSUPP' undeclared (first use in this function) netconnection.c:223: error: `EPFNOSUPPORT' undeclared (first use in this function) netconnection.c:224: error: `EAFNOSUPPORT' undeclared (first use in this function) netconnection.c:225: error: `EADDRINUSE' undeclared (first use in this function) netconnection.c:226: error: `EADDRNOTAVAIL' undeclared (first use in this function) netconnection.c:227: error: `ENETDOWN' undeclared (first use in this function) netconnection.c:228: error: `ENETUNREACH' undeclared (first use in this function) netconnection.c:229: error: `ENETRESET' undeclared (first use in this function) netconnection.c:230: error: `ECONNABORTED' undeclared (first use in this function) netconnection.c:231: error: `EPIPE' undeclared (first use in this function) netconnection.c:232: error: `ECONNRESET' undeclared (first use in this function) netconnection.c:233: error: `ENOBUFS' undeclared (first use in this function) netconnection.c:234: error: `EISCONN' undeclared (first use in this function) netconnection.c:235: error: `ENOTCONN' undeclared (first use in this function) netconnection.c:236: error: `ESHUTDOWN' undeclared (first use in this function) netconnection.c:237: error: `ETOOMANYREFS' undeclared (first use in this function) netconnection.c:238: error: `ETIMEDOUT' undeclared (first use in this function) netconnection.c:239: error: `ECONNREFUSED' undeclared (first use in this function) netconnection.c:240: error: `ELOOP' undeclared (first use in this function) netconnection.c:241: error: `ENAMETOOLONG' undeclared (first use in this function) netconnection.c:242: error: `EHOSTDOWN' undeclared (first use in this function) netconnection.c:243: error: `EHOSTUNREACH' undeclared (first use in this function) netconnection.c:244: error: `ENOTEMPTY' undeclared (first use in this function) netconnection.c:260: error: `errno' undeclared (first use in this function) netconnection.c:260: warning: implicit declaration of function `perror' netconnection.c: In function `NETCON_create': netconnection.c:279: error: `errno' undeclared (first use in this function) netconnection.c: In function `NETCON_close': netconnection.c:315: error: `errno' undeclared (first use in this function) netconnection.c: At top level: netconnection.c:321: error: syntax error before '*' token netconnection.c: In function `NETCON_connect': netconnection.c:436: error: `errno' undeclared (first use in this function) netconnection.c: In function `NETCON_send': netconnection.c:461: error: `errno' undeclared (first use in this function) netconnection.c: In function `NETCON_recv': netconnection.c:495: error: `errno' undeclared (first use in this function) netconnection.c: In function `NETCON_getNextLine': netconnection.c:585: error: `errno' undeclared (first use in this function) netconnection.c: At top level: netconnection.c:322: warning: `check_hostname' defined but not used Although I've probably wasting my time and there's simply a missing header file or netconnection.c shouldn't even be there I've found that the constants EINTR, EBADF, EPERM, EACCES, EFAULT, EINVAL, EMFILE, EPIPE, ENAMETOOLONG and ENOTEMPTY are all defined in $WINE/include/msvcrt/errno.h and the rest only have WSA\1 constants in $WINE/include/winsock.h. -- Colin Wright cdonline(a)tesco.net

2 2

Re: CVSROOT/. loginfo
by Ron Jensen Dec. 4, 2005

Dec. 4, 2005

Alexandre, Can we get the Module name and/or modified files added back to the subject line for CVS? IHMO, this is much more useful than knowing who submitted the patch. Thankyou, Ron Jensen On Fri, 2005-12-02 at 09:43 -0600, Alexandre Julliard wrote: > ChangeSet ID: 21634 > CVSROOT: /opt/cvs-commit > Module name: CVSROOT > Changes by: julliard(a)winehq.org 2005/12/02 09:43:52 > > Modified files: > . : loginfo > > Log message: > Don't send mail to wine-cvs for the wine module, this will be done > from the git repository. > > Patch: http://cvs.winehq.org/patch.py?id=21634 > > Old revision New revision Changes Path > 1.50 1.51 +2 -1 CVSROOT/loginfo > > Index: CVSROOT/loginfo > diff -u -p CVSROOT/loginfo:1.50 CVSROOT/loginfo:1.51 > --- CVSROOT/loginfo:1.50 2 Dec 2005 15:43:52 -0000 > +++ CVSROOT/loginfo 2 Dec 2005 15:43:52 -0000 > @@ -28,7 +28,8 @@ > # Use this for testing > ^test /usr/bin/perl $CVSROOT/CVSROOT/log_accum -m testing(a)winehq.org -f $CVSROOT/CVSROOT/commitlog -S -s %p %s > > +^wine /usr/bin/perl $CVSROOT/CVSROOT/log_accum -f $CVSROOT/CVSROOT/commitlog -S -s %p %s > + > # All others go to wine-cvs > -^wine /usr/bin/perl $CVSROOT/CVSROOT/log_accum -m wine-cvs(a)winehq.org -f $CVSROOT/CVSROOT/commitlog -L 200 -p -S -s %p %s > DEFAULT /usr/bin/perl $CVSROOT/CVSROOT/log_accum -m wine-cvs(a)winehq.org -f $CVSROOT/CVSROOT/commitlog -P winehq -L 200 -p -c -S -s %p %s > > >

5 6

Make check failure
by Dustin Navea Dec. 4, 2005

Dec. 4, 2005

make[3]: Entering directory `/home/speeddy/wine/dlls/advapi32/tests' ../../../tools/runtest -q -P wine -M advapi32.dll -T ../../.. -p advapi32_test.exe.so crypt.c && touch crypt.ok crypt.c:710: Test failed: expected 234, got 0 Anyone wanna help me figure out why? Dustin

3 3

ConfigureNotify messages queuing up
by Mikael Lindqvist Dec. 4, 2005

Dec. 4, 2005

Hello dear Wine developers, I was using Flash MX under Wine yesterday and I noticed that when I resize the window, the contents swirl around as resize messages get processed. I thought that maybe this could be avoided if the code in wine that processes ConfigureNotify messages from X and passes them on to the windows application could be made to not forward all the messages, but just the ones that mattered. I had a look at the source where this takes place (in dlls/x11drv/winpos.c) and put the following code in the X11DRV_ConfigureNotify function: XEvent more_events; . . . wine_tsx11_lock(); while(XCheckTypedWindowEvent(event->display,event->window, ConfigureNotify,&more_events)) { event=& (more_events.xconfigure); x = event->x, y = event->y; } wine_tsx11_unlock(); So what it does is that when processing ConfigureNotify messages it checks the message queue if there are more ConfigureNotify messages queued up, and only delivers the last one to the windows application. And actually things ran a bit smoother with this code in place! Maybe there are potential problems with this code, because it might mean that messages gets delivered in the wrong order, but I have some ideas how this could probably be taken care of. And also some other bits and pieces should be fixed for this to work. But what do you think about the idea, is it worth exploring further? In that case I could submit a proper patch for this... -- Mikael

3 3

Debugging winelib apps in Eclipse
by Michael Ost Dec. 4, 2005

Dec. 4, 2005

Does anyone know how to set up Eclipse to debug winelib applications? I tried just replacing 'gdb' with 'winedbg' on the "Debugger" tab on the "Debug" window. After Eclipse says "Launching..." there is an error that says "Process terminated." After reviewing the winelib debug docs, I found that there is a --gdb switch to winedbg so I added that as a "C/C++ Program Argument" on the "Arguments" tab of the same window... a long shot, and it didn't work. This is on Fedora Core 4, with Eclipse 3.1 (yum updated from the 3.1M6 version that comes with FC4), and with the wine 0.99.2 FC4 rpm. Any leads? Thanks ... mo

4 3

iTunes COM problems?
by Thomas Meyer Dec. 3, 2005

Dec. 3, 2005

Hi. iTunes version 6 installation fails. i made a log an my guess is that the problem is here: [snip] trace:ole:TMStubImpl_AddRef (0x7fdcd028)->(ref before=1) trace:ole:stub_manager_int_release after 1 trace:ole:dispatch_rpc Calling apartment thread 0x0000000b... trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0400 trace:ole:TMStubImpl_Invoke ... trace:ole:ITypeLib2_fnAddRef (0x7fd8a348)->ref was 9 trace:ole:ITypeInfo_fnAddRef (0x7fdc8b30)->ref is 3 trace:ole:ITypeInfo_fnGetFuncDesc (0x7fdc8b30) index 0 trace:ole:ITypeInfo_fnGetFuncDesc (0x7fdc8b30) index 1 trace:ole:ITypeInfo_fnGetDocumentation (0x7fdc8b30) memid -1 Name(0x7fbda55c) DocString((nil)) HelpContext((nil)) HelpFile((nil)) trace:ole:ITypeInfo_fnGetNames (0x7fdc8b30) memid=0x60010001 Maxname=10 trace:ole:deserialize_param vt 3 at 0x7fdd193c trace:ole:_invoke Calling 0x4136dc(7ced8370,0000005f,) trace:ole:_invoke returns 00000000 trace:ole:serialize_param (tdesc.vt 3) trace:ole:ITypeInfo_fnRelease (0x7fdc8b30)->(2) trace:ole:ITypeLib2_fnRelease (0x7fd8a348)->(9) trace:ole:TMStubImpl_Invoke returning trace:ole:TMStubImpl_Release (0x7fdcd028)->(ref before=2) trace:ole:apartment_release a0000000b: after = 1 trace:ole:rpc_sendreceive_thread completed with status 0x0 trace:ole:DllMain 0x7f6e0000 0x3 (nil) ole32.dll trace:ole:CoWaitForMultipleHandles -- 0x00000000 trace:ole:RpcChannelBuffer_SendReceive RPC call status: 0x0 trace:ole:RpcChannelBuffer_SendReceive -- 0x00000000 trace:ole:ITypeInfo_fnRelease (0x7fe2e6f0)->(2) trace:ole:ITypeLib2_fnRelease (0x7fdf4758)->(201) Ok. One of the things i did't figured out till now. What does this xCall thing mean? trace:ole:xCall -- 0x00000000 trace:ole:CoMarshalInterface (0x775af1b8, {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, 0x7ce45480, 3, (nil), MSHLFLAGS_TABLESTRONG) trace:ole:CoGetStandardMarshal ({c9ce9778-210c-4cb4-b4f0-f589c3dda00b},0x7ce45480,3,(nil),1,0x7fbde72c) trace:ole:CoMarshalInterface Using standard marshaling trace:ole:CoMarshalInterface Calling IMarshal::MarshalInterace trace:ole:StdMarshalImpl_MarshalInterface (...,{c9ce9778-210c-4cb4-b4f0-f589c3dda00b},...) trace:ole:CoGetPSClsid () riid={c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, pclsid=0x7fbde654 trace:ole:WINE_StringFromCLSID 0x496980->{C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} trace:ole:__CLSIDFromStringA {C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} -> 0x7fbde654 trace:ole:CoGetPSClsid () Returning CLSID={c9ce9778-210c-4cb4-b4f0-f589c3dda00b} trace:ole:get_facbuf_for_iid CoGetPSClsid hr= 0x00000000 trace:ole:CoGetClassObject CLSID: {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, IID: {d5f569d0-593b-101a-b569-08002b2dbf7a} trace:ole:WINE_StringFromCLSID 0x7fbde654->{C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} trace:ole:COMPOBJ_DLLList_Add trace:ole:get_inproc_class_object DllGetClassObject hr= 0x80040111 err:ole:CoGetClassObject no class object {c9ce9778-210c-4cb4-b4f0-f589c3dda00b} could be created for for context 0x1 err:ole:marshal_object couldn't get IPSFactory buffer for interface {c9ce9778-210c-4cb4-b4f0-f589c3dda00b} I guess this is the reason why the installer fails. Maybe i am wrong and this is an error in the application program. but how to determin this? is there a way to explorer all interfaces in an COM object (in the dll file)? err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80040111 err:ole:CoMarshalInterface Failed to marshal the interface {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, 80040111 trace:ole:CoMarshalInterface completed with hr 0x80040111 trace:ole:CreateFileMoniker (L"{872653C6-5DDC-488B-B7C2-CF9E4D9335E5}",0x7fbde880) trace:ole:FileMonikerImpl_Construct (0x775af1b8,L"{872653C6-5DDC-488B-B7C2-CF9E4D9335E5}") trace:ole:FileMonikerImpl_DecomposePath L"{872653C6-5DDC-488B-B7C2-CF9E4D9335E5}", (nil) trace:ole:FileMonikerImpl_QueryInterface (0x775af1b8,{0000000f-0000-0000-c000-000000000046},0x7fbde880) trace:ole:FileMonikerImpl_AddRef (0x775af1b8) trace:ole:CoCreateInstance (rclsid={064cb054-2518-474e-b2e8-200049528c42}, pUnkOuter=(nil), dwClsContext=00000004, riid={a16ab1e1-377d-4df2-8d8a-c9f283857ddc}, ppv=0x7fbde7cc) trace:ole:CoGetClassObject CLSID: {064cb054-2518-474e-b2e8-200049528c42}, IID: {00000001-0000-0000-c000-000000000046} trace:ole:RPC_GetLocalClassObject rclsid={064cb054-2518-474e-b2e8-200049528c42}, iid={00000001-0000-0000-c000-000000000046} trace:ole:WINE_StringFromCLSID 0x480b00->{064CB054-2518-474E-B2E8-200049528C42} trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" trace:ole:WINE_StringFromCLSID 0x480b00->{064CB054-2518-474E-B2E8-200049528C42} trace:ole:create_server activating local server L"c:\\PROG~1F2\\GEME~SR3\\INST~JM1\\Driver\\11\\INTE~MEX\\IDriverT.exe -Embedding" for {064cb054-2518-474e-b2e8-200049528c42} trace:ole:DllMain 0x7f910000 0x3 (nil) ole32.dll trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message __driCreateNewScreen_20050727 - succeeded trace:ole:DllMain 0x7f870000 0x1 0x1 ole32.dll trace:ole:DllMain (0x7f770000,1,0x1) oleaut32.dll trace:ole:DllMain 0x7f870000 0x2 (nil) ole32.dll trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:DllMain 0x7f910000 0x3 (nil) ole32.dll trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 [installer contiunes here. but i did end the program; after a while the installer fails with an error message] by the way: what is an apartment? (i think it has something to do with thread/process, therefore i added the dll names for each Main call) any ideas and remarks are welcome thanks and regards Thomas ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

2 1

[Take 2] Make check error
by Dustin Navea Dec. 3, 2005

Dec. 3, 2005

The last error was caused by linux/capi.h being included, even though it wont compile (checked configure) This one I'm not sure about. ../../../tools/runtest -q -P wine -M gdi32.dll -T ../../.. -p gdi32_test.exe.so metafile.c && touch metafile.ok metafile.c:135: Test failed: pass 0: dx[0] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[1] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[2] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[3] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[4] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[5] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[6] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[7] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[8] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[9] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[10] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[11] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[12] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[13] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[14] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[15] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[16] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[17] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[18] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[19] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[20] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[21] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[22] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[23] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[24] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[25] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[26] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[27] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[28] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[29] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[30] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[31] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[32] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[33] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[34] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[35] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[36] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[37] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[38] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[39] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[40] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[41] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[42] (0) didn't match 4 fixme:dc:GdiIsMetaPrintDC (nil) fixme:dc:GdiIsPlayMetafileDC (nil) fixme:dc:GdiIsMetaPrintDC 0x358 fixme:dc:GdiIsPlayMetafileDC 0x358 fixme:dc:GdiIsMetaPrintDC 0x368 fixme:dc:GdiIsPlayMetafileDC 0x368 make[3]: *** [metafile.ok] Error 43 make[3]: Leaving directory `/home/speeddy/wine/dlls/gdi/tests' make[2]: *** [tests/__test__] Error 2 make[2]: Leaving directory `/home/speeddy/wine/dlls/gdi' make[1]: *** [gdi/__test__] Error 2 make[1]: Leaving directory `/home/speeddy/wine/dlls' make: *** [dlls/__test__] Error 2

1 0

Re: msvcrt incompatibility in Origin 6.0 when saving documents
by Olaf Leidinger Dec. 3, 2005

Dec. 3, 2005

Hello again! Running Origin6.0 with WINEDEBUG="+snoop,+relay" with and without native msvcrt, tailing, cutting and wc-ing and finally diffing the output I found the following: First of all using the native version I get some msvcrt._EH_prolog calls I can't find in the builtin version. all window-procs have such calls: native: ret kernel32.94() retval=00000009 ret=7f6c5a5c call window proc 0x6c231b81 (hwnd=0x1003a,msg=wm_settext,wp=00000000,lp=7fadedd4) call msvcrt._eh_prolog(7f6cf147,0001003a,0000000c,00000000,7fadedd4 "microcal origin - i ret msvcrt._eh_prolog() retval=7db10190 ret=6c231b8b call msvcrt._eh_prolog(6c231b9c,6c23b419,6c231b81,6c231b81,7fadf8ec,6c2c2cfe,ffffffff0009 ret ntdll.rtlentercriticalsection() retval=00000000 ret=7e6563d2 call ntdll.rtlleavecriticalsection(7e69a888) ret=7e656412 ret ntdll.rtlleavecriticalsection() retval=00000000 ret=7e656412 \\mnt\\privat\\origin6\\untitled",7f6ee620,0001003a,0000000c, ...) ret=6c2310b5 ret msvcrt._eh_prolog() retval=7db10190 ret=6c2310b5 call kernel32.tlsgetvalue(00000003) ret=6c231018 ret kernel32.tlsgetvalue() retval=7fdd7a88 ret=6c231018 call msvcrt._eh_prolog(6c23138a,00000000,6c231be9,0001003a,7fadeba8,6c231bba,0001003a,0000000c,00000000,7fadedd4 "microcal origin - i ret msvcrt._eh_prolog() retval=7db10190 ret=6c23112a call kernel32.tlsgetvalue(00000003) ret=6c231018 ret kernel32.tlsgetvalue() retval=7fdd7a88 ret=6c231018 call kernel32.tlsgetvalue(00000003) ret=6c231018 ret kernel32.tlsgetvalue() retval=7fdd7a88 ret=6c231018 call msvcrt._eh_prolog(6c231bfb,7d9366c0,0001003a,0000000c,00000000,7fadedd4 "microcal origin - i ret msvcrt._eh_prolog() retval=7db10190 ret=6c231c09 call kernel32.tlsgetvalue(00000003) ret=6c231018 builtin: call window proc 0x6c231b81 (hwnd=0x1003a,msg=wm_settext,wp=00000000,lp=7fadedd4) call kernel32.tlsgetvalue(00000003) ret=6c231018 This is another example not concerting window procs: native: call kernel32.lstrlena(7fadecc0 "microcal origin") ret=6c2338d7 ret kernel32.lstrlena() retval=0000000f ret=6c2338d7 call msvcrt._eh_prolog(6c2319c6,0000000f,7fadedd0,7fd299fc,6c23393c,0000000f,0000000f,7fadedd0,6c2338f9,0000000f,7fadecc0 "microcal origin",7fadedd0,6c2338e0,0000000f,7fadecc0 "microcal origin",0000000f, ...) ret=6c231aeb ret msvcrt._eh_prolog() retval=7db101a9 ret=6c231aeb call ntdll.rtlentercriticalsection(6c300088) ret=6c231b03 same as builtin: call kernel32.lstrlena(7fadecc0 "microcal origin") ret=6c2338d7 ret kernel32.lstrlena() retval=0000000f ret=6c2338d7 call ntdll.rtlentercriticalsection(6c300088) ret=6c231b03 >From mfc there is also such a call: native: call mfc42.6374(0000000c,00000000,7fadedd4 "microcal origin - i call mfc42.5163(0000000c,00000000,7fadedd4 "microcal origin - i call msvcrt._eh_prolog(7db101db,0000000c,00000000,7fadedd4 "microcal origin - i ret msvcrt._eh_prolog() retval=7db101f4 ret=6c231d16 call ntdll.rtlentercriticalsection(6c300220) ret=6c23178e builtin: call mfc42.6374(0000000c,00000000,7fadedd4 "microcal origin - i call mfc42.5163(0000000c,00000000,7fadedd4 "microcal origin - i call ntdll.rtlentercriticalsection(6c300220) ret=6c23178e Then there is also a difference when calling ftime(): native: (line 16240) call msvcrt.memcpy(7d945558 "untitled",7fe5e27a "untitled",00000008) ret=6c233905 ret msvcrt.memcpy() retval=7d945558 ret=6c233905 ret mfc42.860() retval=7d943dc0 ret=7f81a080 call outl60.labutil_str2date(00000000,00000003,00000000) ret=7f81a0fe call msvcrt._ftime() ret=7f74100d call kernel32.getsystemtimeasfiletime(7fadedf0) ret=78026aad call ntdll.ntquerysystemtime(7fadec80) ret=7fd08e30 ret kernel32.getsystemtimeasfiletime() retval=01c5f531 ret=78026aad ret msvcrt._ftime() retval=438cd1d8 ret=7f74100d call msvcrt.localtime() ret=7f74103e call kernel32.getlasterror() ret=78002699 ret kernel32.getlasterror() retval=00000000 ret=78002699 call kernel32.tlsgetvalue(00000002) ret=780026a7 ret kernel32.tlsgetvalue() retval=7d930088 ret=780026a7 call kernel32.setlasterror(00000000) ret=780026b8 ret kernel32.setlasterror() retval=00000000 ret=780026b8 ret msvcrt.localtime() retval=7d9306f8 ret=7f74103e builtin: (line 16632) call msvcrt.memcpy(7fe7dff8,7fe637e2,00000008) ret=6c233905 ret msvcrt.memcpy() retval=7fe7dff8 ret=6c233905 ret mfc42.860() retval=7fe7aac0 ret=7f81a080 call outl60.labutil_str2date(00000000,00000003,00000000) ret=7f81a0fe call msvcrt._ftime(7f75b778) ret=7f74100d call kernel32.gettimezoneinformation(7fadec9c) ret=7e886be4 call ntdll.rtlquerytimezoneinformation(7fadec9c) ret=7fd09bce ret ntdll.rtlquerytimezoneinformation() retval=00000000 ret=7fd09bce call ntdll.ntquerysystemtime(7fadebc0) ret=7fd08e30 ret kernel32.gettimezoneinformation() retval=00000000 ret=7e886be4 call kernel32.getsystemtimeasfiletime(7faded48) ret=7e886bf3 call ntdll.ntquerysystemtime(7fadebe0) ret=7fd08e30 ret ntdll.ntquerysystemtime() retval=00000000 ret=7fd08e30 ret kernel32.getsystemtimeasfiletime() retval=01c5f530 ret=7e886bf3 ret msvcrt._ftime() retval=00000000 ret=7f74100d call msvcrt.localtime(7f75b748) ret=7f74103e call kernel32.filetimetolocalfiletime(7faded48,7faded40) ret=7e886e9a call ntdll.rtlsystemtimetolocaltime(7fadeba4,7fadebac) ret=7fd09f03 ret ntdll.rtlsystemtimetolocaltime() retval=00000000 ret=7fd09f03 ret kernel32.filetimetolocalfiletime() retval=00000001 ret=7e886e9a call kernel32.filetimetosystemtime(7faded40,7faded30) ret=7e886ea4 call ntdll.rtltimetotimefields(7fadebb0,7fadeba0) ret=7fd09572 ret ntdll.rtltimetotimefields() retval=0000016f ret=7fd09572 ret kernel32.filetimetosystemtime() retval=00000001 ret=7e886ea4 call kernel32.gettimezoneinformation(7fadec84) ret=7e886fd1 call ntdll.rtlquerytimezoneinformation(7fadec84) ret=7fd09bce ret ntdll.rtlquerytimezoneinformation() retval=00000000 ret=7fd09bce call ntdll.ntquerysystemtime(7fadeb98) ret=7fd08e30 ret ntdll.ntquerysystemtime() retval=00000000 ret=7fd08e30 ret kernel32.gettimezoneinformation() retval=00000000 ret=7e886fd1 ret msvcrt.localtime() retval=7e8ae660 ret=7f74103e And the native msvcrt seems to use an internal _ftol native: call msvcrt._cipow() ret=7f82aaf9 ret msvcrt._cipow() retval=40f00020 ret=7f82aaf9 call msvcrt._ftol() ret=7f82a67a ret msvcrt._ftol() retval=00000001 ret=7f82a67a builtin: call msvcrt._cipow() ret=7f82aaf9 ret msvcrt._cipow() retval=00000001 ret=7f82aaf9 call ntdll._ftol() ret=7f82a67a ret ntdll._ftol() retval=0000000000000001 ret=7f82a67a By the way... what is the difference between "retval" and "ret"? It sounds the same. There are still some megs in front of me... Perhaps you could comment my discoveries so far. Personally I think they aren't very important, but I really don't know much about the win32 api, so I can't tell... Ciao, Olaf Leidinger

2 2

wine alsa impelmentation
by Tomas Carnecky Dec. 3, 2005

Dec. 3, 2005

I have a Envy24PT sound chip, without hardware mixing, so I had to setup dmix (in ~/.asoundrc). That works fine when I try to play two sound files with any combination of mplayer, alsaplayer and mpg123). But when I start any of those a then wine, I get this: ALSA lib pcm_dmix.c:788:(snd_pcm_dmix_open) unable to create IPC shm instance and I get no sound. If I start wine first and then mplayer I get this: pcm_params.c:187: snd_pcm_hw_param_get_min: Assertion `!snd_interval_empty(i)' failed. In which way does the wine alsa implementation differ from the one of mplayer, alsaplayer or mpg123? Or what could cause this problem.. Also I get lots of fixme:dsound:DSOUND_MixOne problem with underrun detection (mixlen=16384 < primary_done=21168) err:dsound:DSOUND_MixOne underrun on sound buffer 0x55952bf8 err:wave:wodPlayer_ProcessMessages pcm_pause failed: Input/output error and rarely fixme:wave:ALSA_AddRingMessage two fast messages in the queue!!!! toget = 11(WINE_WM_RESTARTING), tosave=12(UNKNOWN(0x00000000)) messages. How can I improve my sound quality? My asoundrc is in the attachment. thanks tom pcm.!dmix { type dmix ipc_key 5678293 slave { pcm "hw:0,0" period_size 1024 buffer_size 16384 format S32_LE } } pcm.!dsnoop { type dsnoop ipc_key 5778293 slave { pcm "hw:0,0" format S32_LE } } pcm.duplex { type asym playback.pcm "dmix" capture.pcm "dsnoop" } pcm.!default { type plug slave.pcm "duplex" } pcm.default { type plug slave.pcm "duplex" } pcm.!dsp { type plug slave.pcm "duplex" } ctl.!mixer { type hw card 0 }

1 0