- Wine-Devel - list.winehq.org

Re: Fix crash in dsound test
by Ferenc Wagner Aug. 8, 2004

Aug. 8, 2004

Paul Millar <paulm(a)astro.gla.ac.uk> writes: > The build failed. It looks like there's a bug in CVS. Both > CLSID_DirectSoundPrivate and DSPROPSETID_DirectSoundDevice defined multiple > times (the wine-version of mingw libraries and in the source). Yes, there was a short discussion about this on 23-24 July on wine-devel. It reached no conclusion, though, and I didn't try the various MinGW libraries recommended there. The abundance of MinGW packages always confused me, and at the moment I don't even know where I got mine from. But it can't compile the dsound tests, that's for sure. Comments welcome. -- Feri.

2 1

Re: patch: shell32.dll - SHELL_ArgifyW expands env-vars
by Steven Edwards Aug. 8, 2004

Aug. 8, 2004

Hi Jens, --- Jens Collin <jens.collin(a)lakhei.com> wrote: > * lookup of envoronment-vars in SHELL_ArgifyW in shell32.dll added. > (Such as %SystemRoot%). Do you think you could write some test cases for the shellexecute functions using the wine regression tests? I would like to try and merge the rest of shell32 in to ReactOS but am worried that we may overwrite fixes Martin made in the ReactOS tree. Thanks Steven __________________________________ Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. http://messenger.yahoo.com

2 1

Wine's OLE/COM doesn't work, and I can no longer use native COM
by David D. Hagood Aug. 8, 2004

Aug. 8, 2004

One of the few Windows programs I use is Delorme's MapNGo (versions 4 and 6). Under older versions of Wine wherein I could use the native Windows OLE/COM implementation it worked fairly well, but with the new Wine it does not. The symptoms are that the program cannot create the initial document object - this ususally is an indication that the DLLS implementing the COM classes for the MapNGo object are not registered correctly with the system. However, I have taken a system running an older version of Wine that could successfully run Mng6 and upgraded it to the latest CVS of Wine, and it broke the app. Not being a wiz at COM, I am not sure where to go from here, other than to report the results of tracing the run: WINDEBUG=+ole,+com wine ./Mng6 fixme:ole:CoRegisterMessageFilter stub err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 0x1003a! [wowbaggr(a)surfer AAAMNG6]$ [wowbaggr(a)surfer AAAMNG6]$ WINDEBUG=+ole,+com wine ./Mng6.mdb wine: cannot determine executable type for L"D:\\AAAMNG6\\Mng6.mdb" [wowbaggr(a)surfer AAAMNG6]$ WINDEBUG=+ole,+com wine ./mng mng6.cnt mng6.exe mng6.hlp mngfeat.hlp [wowbaggr(a)surfer AAAMNG6]$ WINDEBUG=+ole,+com wine ./mng6.exe fixme:ole:CoRegisterMessageFilter stub err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 0x1003a! [wowbaggr(a)surfer AAAMNG6]$ [wowbaggr(a)surfer AAAMNG6]$ WINDEBUG=+all wine ./mng6.exe fixme:ole:CoRegisterMessageFilter stub err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 0x1003a! [wowbaggr(a)surfer AAAMNG6]$ [wowbaggr(a)surfer AAAMNG6]$ WINEDEBUG=+ole,+com wine ./mng6.exe trace:ole:DllMain 0x40c00000 0x1 0x1 trace:ole:DllMain (0x40e30000,1,0x1) trace:ole:CoInitializeEx ((nil), 2) trace:ole:CoInitializeEx () - Initializing the COM libraries trace:ole:RunningObjectTableImpl_Initialize () trace:ole:OleInitialize ((nil)) trace:ole:CoInitializeEx ((nil), 2) trace:ole:OleInitialize () - Initializing the OLE libraries trace:ole:OLEClipbrd_Initialize () fixme:ole:CoRegisterMessageFilter stub trace:ole:WINE_StringFromCLSID 0x49d964->{F4B4E540-7F32-11CE-AC56-0000C0496D91} trace:ole:WINE_StringFromCLSID 0x487530->{D97A6266-C342-11D2-A562-A313798CEB30} trace:ole:WINE_StringFromCLSID 0x4071f3bc->{D97A6266-C342-11D2-A562-A313798CEB30} trace:ole:CoGetClassObject CLSID: {d97a6266-c342-11d2-a562-a313798ceb30}, IID: {b196b28f-bab4-101a-b69c-00aa00341d07} trace:ole:COMPOBJ_DLLList_Add trace:ole:CoInitializeEx ((nil), 2) trace:ole:WINE_StringFromCLSID 0x5f8a41b8->{00025E15-0000-0000-C000-000000000046} trace:ole:CoGetClassObject CLSID: {00025e15-0000-0000-c000-000000000046}, IID: {b196b28f-bab4-101a-b69c-00aa00341d07} trace:ole:COMPOBJ_DLLList_Add trace:ole:CreateErrorInfo (0x4071f38c): stub: trace:ole:IErrorInfoImpl_QueryInterface (0x40252658)->( IID: {22f03340-547d-101b-8e65-08002b2bd119},0x4071f38c) trace:ole:ICreateErrorInfoImpl_AddRef (0x40252658) trace:ole:IErrorInfoImpl_AddRef (0x40252658)->(count=1) trace:ole:IErrorInfoImpl_QueryInterface -- Interface: (0x4071f38c)->(0x4025265c)trace:ole:IErrorInfoImpl_Release (0x40252658)->(count=2) trace:ole:ICreateErrorInfoImpl_QueryInterface (0x40252658) trace:ole:IErrorInfoImpl_QueryInterface (0x40252658)->( IID: {1cf2b120-547d-101b-8e65-08002b2bd119},0x4071f390) trace:ole:IErrorInfoImpl_AddRef (0x40252658)->(count=1) trace:ole:IErrorInfoImpl_QueryInterface -- Interface: (0x4071f390)->(0x40252658)trace:ole:ICreateErrorInfoImpl_SetGUID (0x40252658)->({00000000-0000-0000-0000-000000000000}) trace:ole:ICreateErrorInfoImpl_SetSource (0x40252658) trace:ole:ICreateErrorInfoImpl_SetDescription (0x40252658) trace:ole:ICreateErrorInfoImpl_SetHelpContext (0x40252658) trace:ole:SetErrorInfo (0, 0x40252658) trace:ole:IErrorInfoImpl_AddRef (0x40252658)->(count=2) trace:ole:IErrorInfoImpl_Release (0x40252658)->(count=3) trace:ole:ICreateErrorInfoImpl_Release (0x40252658) trace:ole:IErrorInfoImpl_Release (0x40252658)->(count=2) err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 0x1003a! (this last message usually happens when Mng tries to show an error dialog at startup.) When I've tried re-installing Mng6, I get messages from Wine about "Registering a non-oleautomation interface" - I do not know if this is significant or not. So, any pointers on where to go from here?

2 5

Problem with ITypeInfo
by jack Aug. 8, 2004

Aug. 8, 2004

Hi. I've tryed to run game Project Entropia and I got segmentation fault because of a bug in OLE. I've hacked code and I found two bugs: 1. ITypeInfo has back pointer to ITypeLib, but it's possible (and happened) that ITypeLib is destroyed and later ITypeInfo calls its function. I've solve this problem by call ITypeLib_AddRef while creating ITypeInfo (and ITypeLib_Release while destroying ITypeInfo). 2. ITypeInfo_Invoke doesn't support optional parameters. I've added support for cParamsOpt>0. MSDN says that optional parameter is when VARTYPE equals VT_EMPTY, but in my case it was a VT_BYREF | VT_VARIANT type but the pointer was NULL. When I treated it as VT_EMPTY, it was OK. I enclose my patch. My knownlage about OLE is sparse so I'm not able to test this. Thanks, Jacek

3 4

Re: Take monospace fonts into account in default font selectionalgorithm.
by Alexandre Julliard Aug. 7, 2004

Aug. 7, 2004

Mike Hearn <mike(a)navi.cx> writes: > On Sat, 2004-08-07 at 23:16 +0900, Dmitry Timoshkov wrote: >> This can't work because instead of logical boolean results you compare >> binary flags which are different: >> >> #define FT_FACE_FLAG_FIXED_WIDTH ( 1L << 2 ) >> >> #define MONO_FONT 0x08 > > You are right. I will watch out for this in future! Here is a fixed > patch. The correct way to compare booleans in C is to invert them, i.e. instead of (a == b) use (!a == !b). You must not rely on booleans being always 0 or 1. -- Alexandre Julliard julliard(a)winehq.org

1 0

make crosstest fails
by Stefan Leichter Aug. 7, 2004

Aug. 7, 2004

Hello, building cross tests of current cvs fails for me with: i386-mingw32-gcc capture.cross.o ds3d.cross.o dsound.cross.o propset.cross.o testlist.cross.o -o dsound_crosstest.exe -ldsound -lole32 -luser32 -lkernel32 -ldxguid -luuid -ldxerr8 /usr/local/lib/gcc-lib/i386-mingw32/3.2.3/../../../../i386-mingw32/lib/ libdxguid.a(dxguid.o)(.text+0x570):/usr/src/packages/BUILD/mingw-3.2/ w32api-2.5/lib/directx/dxguid.c: multiple definition of `CLSID_DirectSoundPrivate' propset.cross.o(.text+0x0):propset.c: first defined here /usr/local/lib/gcc-lib/i386-mingw32/3.2.3/../../../../i386-mingw32/lib/ libdxguid.a(dxguid.o)(.text+0x580):/usr/src/packages/BUILD/mingw-3.2/ w32api-2.5/lib/directx/dxguid.c: multiple definition of `DSPROPSETID_DirectSoundDevice' propset.cross.o(.text+0x10):propset.c: first defined here make[3]: *** [dsound_crosstest.exe] Fehler 1 make[3]: Leaving directory `/usr/src/wine/wine-mingw/dlls/dsound/tests' make[2]: *** [tests/__crosstest__] Fehler 2 make[2]: Leaving directory `/usr/src/wine/wine-mingw/dlls/dsound' make[1]: *** [dsound/__crosstest__] Fehler 2 make[1]: Leaving directory `/usr/src/wine/wine-mingw/dlls' make: *** [dlls/__crosstest__] Fehler 2 Bye Stefan

4 3

DOOM 3 misses some opengl32 wgl* and Cg functions
by Dr. Uwe Girlich Aug. 7, 2004

Aug. 7, 2004

Hello all! I just tested out DOOM 3 (no-cd-cracked version) with the current Wine (CVS from 1 hour ago) and found the following problems on the game console: Couldn't find proc address for: wglSwapIntervalEXT Couldn't find proc address for: wglGetPixelFormatAttribivARB Couldn't find proc address for: wglGetPixelFormatAttribfvARB Couldn't find proc address for: wglChoosePixelFormatARB Couldn't find proc address for: wglCreatePbufferARB Couldn't find proc address for: wglGetPbufferDCARB Couldn't find proc address for: wglReleasePbufferDCARB Couldn't find proc address for: wglDestroyPbufferARB Couldn't find proc address for: wglQueryPbufferARB Couldn't find proc address for: wglBindTexImageARB Couldn't find proc address for: wglReleaseTexImageARB Couldn't find proc address for: wglSetPbufferAttribARB GL_ARB_texture_non_power_of_two not found GL_ATI_fragment_shader not found (this is expected, I have a nvidia card) Cg not available. Are these wgl* function difficult to implement? Almost all computer terminals in the game show static black & white noise (instead of some animated computer screen image). I suspect, that this has something to do with the missing 'Cg' support in Wine (DOOM3 cannot find cg.dll & cgGL.dll). On the other hand, the rendering paths (r_renderer nv10, nv20, arb, and arb2) are all more or less working (besides the noise and the too bright lighting in nv10). BTW, DOOM 3 crashes at program start in Cedega, you made it better! Bye, Uwe

7 7

Re: Take monospace fonts into account in default font selectionalgorithm.
by Dmitry Timoshkov Aug. 7, 2004

Aug. 7, 2004

"Mike Hearn" <mike(a)navi.cx> wrote: > + (*insertface)->fixed_width = ft_face->face_flags & FT_FACE_FLAG_FIXED_WIDTH; ... > - if(csi.fs.fsCsb[0] & family->FirstFace->fs.fsCsb[0]) > + if((csi.fs.fsCsb[0] & family->FirstFace->fs.fsCsb[0]) && > + (family->FirstFace->fixed_width == (lf.lfPitchAndFamily & MONO_FONT))) This can't work because instead of logical boolean results you compare binary flags which are different: #define FT_FACE_FLAG_FIXED_WIDTH ( 1L << 2 ) #define MONO_FONT 0x08 -- Dmitry.

1 0

suse patch for wineprefixcreate
by Marcus Meissner Aug. 7, 2004

Aug. 7, 2004

Hi, This is the patch I use at SUSE for wineprefixcreate. Mike wanted to see it ;) $dlldir/config is the sample config file with just minimal local suse changes. Ciao, Marcus Index: wineprefixcreate.in =================================================================== RCS file: /home/wine/wine/tools/wineprefixcreate.in,v retrieving revision 1.4 diff -u -r1.4 wineprefixcreate.in --- wineprefixcreate.in 14 May 2004 00:43:50 -0000 1.4 +++ wineprefixcreate.in 7 Aug 2004 12:40:57 -0000 @@ -86,8 +86,10 @@ if [ -d "$WINEPREFIX" ] || mkdir "$WINEPREFIX"; then : else - echo "Could not create $WINEPREFIX, aborting" - exit 1 +fi + +if [ ! -f "$WINEPREFIX/config" ]; then + cp $dlldir/config "$WINEPREFIX/config" fi WINEPREFIX=`cd "$WINEPREFIX" && pwd` @@ -124,6 +126,35 @@ [ -d "$i" ] || mkdir "$i" done +# Create the drive symlinks +if [ ! -d "$WINEPREFIX/dosdevices" ] +then + mkdir "$WINEPREFIX/dosdevices" + ln -s "../drive_c" "$WINEPREFIX/dosdevices/c:" + ln -s "/" "$WINEPREFIX/dosdevices/z:" + ln -s "/tmp" "$WINEPREFIX/dosdevices/x:" + if [ -d "$HOME" ]; then + ln -s "$HOME" "$WINEPREFIX/dosdevices/y:" + if [ ! -f "$HOME/.windows-label" ]; then + echo "HOME" > "$HOME/.windows-label" + fi + fi + # autodetect CD-ROMS on SUSE. + drive=D + for i in /media/* ; do + bn=`basename $i` + if [ "$i" = "/media/floppy" ]; then + ln -s /media/floppy "$WINEPREFIX/dosdevices/a:" + ln -s /dev/fd0 "$WINEPREFIX/dosdevices/a::" + fi + if echo $bn| grep -E -v "^(sd|usb-storage|floppy)" >/dev/null; then + ln -s /media/$bn "$WINEPREFIX/dosdevices/"`echo $drive|tr "[A-Z]" "[a-z]"`: + ln -s /dev/$bn "$WINEPREFIX/dosdevices/"`echo $drive|tr "[A-Z]" "[a-z]"`:: + drive=`echo $drive|tr "D-L" "E-M"` + fi + done +fi + # Create the application symlinks link_app()

2 1

msvideo 16bit codec question
by Mike Hearn Aug. 7, 2004

Aug. 7, 2004

Hey Mike, I've been trying to make Maxis Marble Drop work in my non-connected spare time in the evenings, and the intro video doesn't render right. Examination of the code revealed that it had been patched to output pixel blocks in the right direction for the 8 bit decoder but the 16 bit decoder hadn't been modified. So, I copied across the changes to the 16 bit decoder as well, unfortunately it doesn't work. Something is going wrong, and the codec trashes the heap arena, so I'm guessing there's something in the maths that is different for 16 bit videos than 8 bit. Got any ideas? thanks -mike

1 0