- wine-devel - winehq.org

Re: msvcrt switching from builtin to native
by Alexandre Julliard 11 Jul '01

11 Jul '01

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > _ismbcdigit is unimplemented. The log looks like wine starts to think with > that call that msvcrt is a native dll. Implementing a semi stub for that > gives the same behaviour at the next unimplemented msvcrt function. This should fix it: Index: loader/pe_image.c =================================================================== RCS file: /opt/cvs-commit/wine/loader/pe_image.c,v retrieving revision 1.94 diff -u -r1.94 pe_image.c --- loader/pe_image.c 2001/05/24 18:43:16 1.94 +++ loader/pe_image.c 2001/07/11 20:50:37 @@ -655,7 +655,7 @@ return NULL; } - if (pe_export) + if (!builtin && pe_export) SNOOP_RegisterDLL( hModule, wm->modname, pe_export->Base, pe_export->NumberOfFunctions ); /* Send DLL load event */ -- Alexandre Julliard julliard(a)winehq.com

1 0

msvcrt switching from builtin to native
by Uwe Bonnes 11 Jul '01

11 Jul '01

Hallo, trying to run msdev.exe with builtin msvcrt, at some point thins strange +snoop,+relay log appears: 08066950:Call msvcrt._strdup(4040b294 "Microsoft Visual C++") ret=5f416652 08066950:Call kernel32.HeapAlloc(40390000,00000000,00000015) ret=4063d846 08066950:Ret kernel32.HeapAlloc() retval=4041c338 ret=4063d846 08066950:Ret msvcrt._strdup() retval=4041c338 ret=5f416652 08066950:Call msvcrt._mbsinc(5f49d450 "%d") ret=5f4160fb 08066950:Ret msvcrt._mbsinc() retval=5f49d451 ret=5f4160fb 08066950:Call msvcrt.atoi(5f49d451 "d") ret=5f41614d 08066950:Ret msvcrt.atoi() retval=00000000 ret=5f41614d 08066950:CALL msvcrt.292: _ismbcdigit(<unknown, check return>) ret=5f416161 ^^^^ 08066950:Call ntdll.RtlRaiseException(406064e0) ret=40631056 08066950:CALL msvcrt.74: __CxxFrameHandler(<unknown, check return>) ret=4006ac97 08066950:Call ntdll.RtlRaiseException(406061d0) ret=40631056 08066950:CALL msvcrt.74: __CxxFrameHandler(<unknown, check return>) ret=4006ac97 _ismbcdigit is unimplemented. The log looks like wine starts to think with that call that msvcrt is a native dll. Implementing a semi stub for that gives the same behaviour at the next unimplemented msvcrt function. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

2 1

Early crash with msdev.exe
by Uwe Bonnes 11 Jul '01

11 Jul '01

Hallo, trying msdev.exe from Microsoft Visual C in a demonstration at Linuxtag, I was astonished how far wine proceeds. Only when trying to create a template, wine crashed. Trying to debug with snoop, however the crash happens much earlier. I tried to look hard at snoop.c, but couldn't find where this error may originate from. Has anybody some idea? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- 08066950:RET msvcrt.658: malloc() retval = 40b01f20 ret=50043066 tid=08066950 08066950:CALL msvcrt.272: _initterm() ret=50043090 08066950:CALL devshl.1603: @(00000700,00000081,00000000,40605ad4,4060576c) ret=50301f0a 08066950:RET devshl.1603: @() retval = 00000000 ret=50301f0a tid=08066950 08066950:CALL mfc42.6374: @(<unknown, check return>) ret=50301f51 08066950:CALL mfc42.5163: @(<unknown, check return>) ret=5f401aff 08066950:CALL msvcrt.67: _EH_prolog(4101007d,00000081,00000000,40605ad4,40605728,40b06da0,00000000,40605748,41010064,00000081,00000000,40605ad4,40b06da0,40b06da0,40605764,50301f1f, ...) ret=5f401b2b 08066950:RET msvcrt.67: _EH_prolog() retval = 41010096 ret=5f401b2b tid=08066950 08066950:CALL msvcrt.74: __CxxFrameHandler(<unknown, check return>) ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 08066950:CALL msvcrt.74: __CxxFrameHandler() ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 tid=08066950 08066950:CALL msvcrt.74: __CxxFrameHandler() ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 tid=08066950 08066950:CALL msvcrt.74: __CxxFrameHandler() ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 tid=08066950 08066950:CALL msvcrt.74: __CxxFrameHandler() ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 tid=08066950 08066950:CALL msvcrt.74: __CxxFrameHandler() ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 tid=08066950 08066950:CALL msvcrt.74: __CxxFrameHandler() ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 tid=08066950 08066950:CALL msvcrt.74: __CxxFrameHandler() ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 tid=08066950 08066950:CALL msvcrt.74: __CxxFrameHandler() ret=4006ac97 08066950:RET msvcrt.74: __CxxFrameHandler() retval = 00000001 ret=4006ac97 tid=08066950 08066950:CALL msvcrt.203: _except_handler3(<unknown, check return>) ret=4006ac97 08066950:CALL msvcrt.73: _XcptFilter(<unknown, check return>) ret=0040175d fixme:pthread_kill_other_threads_np FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock Could not stat /home/bon/ikda/vol2 (No such file or directory), ignoring drive Y: FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock Could not stat /home/bon/ikda/sys (No such file or directory), ignoring drive Z: WineDbg starting... on pid 80683b0 No debug information in 32bit DLL '<Debugged process>' (0x00400000) Loaded debug information from ELF 'wine' (0x00000000) Breakpoint 1 at 0x4000da00 (_end+0x37fc1284) Loaded debug information from ELF '/spare/bon/wine/dlls/libntdll.so' (0x40026000) Loaded debug information from ELF '/spare/bon/wine/libwine.so' (0x40127000) Loaded debug information from ELF '/spare/bon/wine/libwine_unicode.so' (0x4013d000) Loaded debug information from ELF '/lib/libncurses.so.5' (0x40205000) Loaded debug information from ELF '/lib/libm.so.6' (0x4024f000) No debug information in ELF '/lib/libutil.so.1' (0x4026d000) No debug information in ELF '/lib/libdl.so.2' (0x40270000) Loaded debug information from ELF '/lib/libc.so.6' (0x40273000) Loaded debug information from ELF '/lib/ld-linux.so.2' (0x40000000) Loaded debug information from ELF '/spare/bon/wine/dlls/libkernel32.so' (0x40617000) Loaded debug information from ELF '/spare/bon/wine/dlls/libgdi32.so' (0x406b4000) Loaded debug information from ELF '/spare/bon/wine/dlls/libadvapi32.so' (0x40723000) Loaded debug information from ELF '/spare/bon/wine/dlls/libuser32.so' (0x40762000) Loaded debug information from ELF '/spare/bon/wine/dlls/libshell32.so' (0x40882000) Loaded debug information from ELF '/spare/bon/wine/dlls/libshlwapi.so' (0x408e8000) Loaded debug information from ELF '/spare/bon/wine/dlls/libcomctl32.so' (0x40923000) Loaded debug information from ELF '/spare/bon/wine/dlls/libx11drv.so' (0x40c00000) Loaded debug information from ELF '/spare/bon/wine/libwine_tsx11.so' (0x40741000) No debug information in ELF '/usr/X11R6/lib/libSM.so.6' (0x40019000) No debug information in ELF '/usr/X11R6/lib/libICE.so.6' (0x40c4d000) No debug information in ELF '/usr/X11R6/lib/libXpm.so.4' (0x40c65000) No debug information in ELF '/usr/X11R6/lib/libXxf86dga.so.1' (0x40387000) No debug information in ELF '/usr/X11R6/lib/libXxf86vm.so.1' (0x404e5000) No debug information in ELF '/usr/X11R6/lib/libXv.so.1' (0x404ea000) No debug information in ELF '/usr/X11R6/lib/libXext.so.6' (0x40752000) No debug information in ELF '/usr/X11R6/lib/libX11.so.6' (0x40c74000) No debug information in ELF '/usr/lib/gconv/ISO8859-1.so' (0x4038d000) Loaded debug information from ELF '/spare/bon/wine/dlls/libversion.so' (0x404d3000) Loaded debug information from ELF '/spare/bon/wine/dlls/liblz32.so' (0x40695000) No debug information in 32bit DLL 'NTDLL.DLL' (0x40060000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVCRT.DLL' (0x78000000) No debug information in 32bit DLL 'ADVAPI32.DLL' (0x40731000) No debug information in 32bit DLL 'GDI32.DLL' (0x406d0000) No debug information in 32bit DLL 'USER32.DLL' (0x40790000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MFC42.DLL' (0x5f400000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x7ff20000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEAUT32.DLL' (0x7fe80000) No debug information in 32bit DLL 'SHLWAPI.DLL' (0x408fd000) No debug information in 32bit DLL 'COMCTL32.DLL' (0x4092f000) No debug information in 32bit DLL 'SHELL32.DLL' (0x4089c000) No debug information in 32bit DLL 'K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVSHL.DLL' (0x50000000) No debug information in 32bit DLL 'X11DRV.DLL' (0x40c11000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MFC42LOC.DLL' (0x7baf0000) No debug information in 32bit DLL 'LZ32.DLL' (0x40698000) No debug information in 32bit DLL 'VERSION.DLL' (0x404d6000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x7fb90000) No debug information in 32bit DLL 'K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVEDIT.PKG' (0x50800000) No debug information in 32bit DLL 'K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVPRJ.PKG' (0x50300000) 08066950:RET msvcrt.73: _XcptFilter() retval = 00000000 ret=0040175d 08066950:RET msvcrt.203: _except_handler3() retval = 00000001 ret=4006ac97 Unhandled exception: page fault on read access to 0x0000000f in 32-bit code (0x5f401ead). In 32-bit mode. 0x5f401ead (MFC42.DLL.1145+0x10 in C:\WINDOWS\SYSTEM\MFC42.DLL): cmpl $0,0x10(%ebx) Wine-dbg>bt Backtrace: =>0 0x5f401ead (MFC42.DLL.1145+0x10 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=40605684) 1 0x5f401c94 (MFC42.DLL.5163+0x173 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=4060570c) 2 0x4101007d (_end+0x3c3255) (ebp=4060572c) 3 0x41010064 (_end+0x3c323c) (ebp=40605748) 4 0x50301f1f (DEVPRJ.PKG..text+0xf1f in K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVPRJ.PKG) (ebp=40605764) 5 0x5f401a88 (MFC42.DLL.1109+0x74 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=406057c4) 6 0x5f401a10 (MFC42.DLL.1578+0x2a in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=406057e0) 7 0x5f4019cf (MFC42.DLL.1579+0x39 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=4060580c) 8 0x40803b87 (WINPROC_wrapper+0x17 in libuser32.so) (ebp=40605830) 9 0x40803c06 (WINPROC_CallWndProc+0x76(proc=0x5f401996, hwnd=0x700, msg=0x81, wParam=0x0, lParam=0x40605ad4) [winproc.c:171] in libuser32.so) (ebp=4060585c) 10 0x408097f8 (CallWindowProcA+0x88(func=0x40d70dbc, hwnd=0x700, msg=0x81, wParam=0x0, lParam=0x40605ad4) [winproc.c:2589] in libuser32.so) (ebp=40605884) 11 0x407ea1a3 (MSG_SendMessage+0x3b3(hwnd=0x700, msg=0x81, wParam=0x0, lParam=0x40605ad4, timeout=0xffffffff, type=0x2, pRes=0x406058ec) [message.c:1733] in libuser32.so) (ebp=406058bc) 12 0x407ea2a2 (SendMessageA+0x32(hwnd=0x700, msg=0x81, wParam=0x0, lParam=0x40605ad4) [message.c:1772] in libuser32.so) (ebp=406058f0) 13 0x40c15014 (X11DRV_CreateWindow+0x184(hwnd=0x700, cs=0x40605ad4, unicode=0x0) [window.c:871] in libx11drv.so) (ebp=40605938) 14 0x407fce51 (WIN_CreateWindowEx+0x6d1(cs=0x40605ad4, classAtom=0xc066, type=0x2) [win.c:865] in libuser32.so) (ebp=406059b0) 15 0x407fd2fb (CreateWindowExA+0x14b(exStyle=0x0, className=0x403fcebc, windowName=0x0, style=0x42000001, x=0x0, y=0x0, width=0x0, height=0x0, parent=0x2b4, menu=0x7310, instance=0x400000, data=0x40605be0) [win.c:1030] in libuser32.so) (ebp=40605b04) 16 0x5f40c211 (MFC42.DLL.2152+0x9a in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=40605b74) 17 0x5f40aaa5 (MFC42.DLL.2124+0x46 in C:\WINDOWS\SYSTEM\MFC42.DLL) (ebp=40605bb0) 18 0x4101004b (_end+0x3c3223) (ebp=40605c04) 19 0x50311b41 (DEVPRJ.PKG.InitPackage+0x4b5 in K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVPRJ.PKG) (ebp=40605c2c) 20 0x50310336 (DEVPRJ.PKG.EntryPoint+0xb5e in K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVPRJ.PKG) (ebp=40605c58) 21 0x50311a22 (DEVPRJ.PKG.InitPackage+0x396 in K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVPRJ.PKG) (ebp=40605c84) 22 0x50311760 (DEVPRJ.PKG.InitPackage+0xd4 in K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVPRJ.PKG) (ebp=406060c0) 23 0x50036fa3 (DEVSHL.DLL.3467+0x9a in K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVSHL.DLL) (ebp=40606664) 24 0x500344be (DEVSHL.DLL.3219+0x53d in K:\USR\LOCAL\SPARE\BON\NT4SP5G\PROGRAMME\MICROSOFT VISUAL STUDIO\COMMON\MSDEV98\BIN\DEVSHL.DLL) (ebp=40606e0c) 25 0x41010019 (_end+0x3c31f1) (ebp=40606ecc) 26 0x400dbf23 (start_process+0x1a3 [process.c:391] in libntdll.so) (ebp=40606f30) 27 0x400dfaa1 (SYSDEPS_DoCallOnStack+0x21(func=0x400dbd80, arg=0x0) [sysdeps.c:173] in libntdll.so) (ebp=40606ff0) 28 0x400dfb43 (SYSDEPS_CallOnStack+0x2f in libntdll.so) (ebp=bffff5f0) 29 0x400dfbfa (SYSDEPS_SwitchToThreadStack+0x9a(func=0x400dbd80) [sysdeps.c:236] in libntdll.so) (ebp=bffff62c) 30 0x400dc2be (PROCESS_InitWine+0x1ce(argc=0x4, argv=0xbffff6c4, win16_exe_name=0x804c660, win16_exe_file=0x804c764) [process.c:519] in libntdll.so) (ebp=bffff644) 31 0x0804b20a (Letext [main.c] in wine) (ebp=bffff65c) 32 0x4028fbaf (__libc_start_main+0xcf in libc.so.6) (ebp=bffff698) 33 0x08049021 (_start+0x21 in wine) (ebp=00000000) Wine-dbg>quit WineDbg terminated on pid 80683b0

1 0

Re: PATCH: include mess up
by Francois Gouget 11 Jul '01

11 Jul '01

On Tue, 10 Jul 2001, Marcus Meissner wrote: > Hi, > > There is some bad recursion when including objbase.h in non-WINE programs. > This fixes that problem, by using winbase.h instead of windows.h. Yes but rpc.h is supposed to include 'windows.h', not 'winbase.h'. The correct fix must be elsewhere. What is the recursion that happens and which include statement (in your application) triggers it? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux: the choice of a GNU generation

2 1

Re: implement overlapped completion routines
by Alexandre Julliard 10 Jul '01

10 Jul '01

Mike McCormack <mike_mccormack(a)start.com.au> writes: > This patch implements overlapped completion routines, and fixes up a > small problem with the overlapped implementation. According to ms > docs, the transfer count should not be stored in the overlapped > structure. Shouldn't you queue an APC instead of calling the completion routine directly? -- Alexandre Julliard julliard(a)winehq.com

1 0

Joysiick under Wine
by David Hagood 10 Jul '01

10 Jul '01

I've seen a couple of messages about getting USB joysticks working under Wine, but do regular (i.e. gameport) sticks work? I've confirmed that my stick is being read by Linux, and that it is reporting events correctly. Now, how do I get Wine to pass them along? I've confirmed: 1) that I have read/write permissions to /dev/js0 2) that Wine tries to read /dev/js0 3) that Wine indeed does read from /dev/js0, but that 4) Wine shortly thereafter closes /dev/js0, never to read it again. Do I need to have the X Window system joystick driver loaded? Or do I need to add something to the system.ini or .wine/config files. This is a Windowless install, under RH6.1, with 2.4.6, and a CVS pull of Wine from a few days ago. I'm trying to get HalfLife running under Wine. I have the GL working, I have sound working, but I am one of those strange fellows that likes to move with a stick, and look with a mouse. Are there any Windows/Wine tools that I can run to try to troubleshoot this?

2 1

Re: some rasapi32 stubs
by Marcus Meissner 10 Jul '01

10 Jul '01

On Tue, Jul 10, 2001 at 10:10:17PM +1000, Mike McCormack wrote: > > ChangeLog: > * dlls/rasapi32/rasapi.c, dlls/rasapi32/rasapi32.spec > Stub some rasapi functions. If you know arguments are strings you can use 'str' instead of 'ptr' in the .spec file, and relay debugging will print strings ;) Also you can use the return value of debugstr_a(a) for string output. Ciao, Marcus

1 0

Re: wv{sn,ns}printf[AW]
by Alexandre Julliard 09 Jul '01

09 Jul '01

Peter Hunnisett <hunnise(a)yahoo.com> writes: > 2) Can wvnsprintf be moved from user32 into shlwapi? This would cause > user32 to have to import shlwapi (because wsprintfA and friends use it > in their implementation) and I don't know if that's legal because user32 > seems to only import gdi32 and kernel32. If not, what's the solution? > Reimplement everything in user32 to not use wvnsprintf and move the > implementation over or just keep the existing situation and rename > wvnsprintf to wvnsprintf and forward the shlwapi calls to user32? user32 cannot import shlwapi, since this would create a circular dependency. Since the functions are needed both in user32 and shlwapi, they have to be implemented in user32 and forwarded from shlwapi to user32 (the alternative is to have two complete wsprintf implementations, which is a bit of a pain). I guess you could also rename the user32 ones, but this is not strictly necessary (and the current name has the advantage of following the C library naming of vsnprintf). -- Alexandre Julliard julliard(a)winehq.com

1 0

wv{sn,ns}printf[AW]
by Peter Hunnisett 09 Jul '01

09 Jul '01

Hi, it appears that we have a bit of a hack in the wine code. Presently we export wvsnprintf[AW] from user32. - These two functions do not appear to be in the real user32.dll and the comments in the code seem to back it up. - Windows does have wvnsprintf[AW] (note the transposed "sn") exported from shlwapi.dll So my questions are: 1) Was the user32 a bit of a hack because those routines just weren't noticed or was it because of something from before shlwapi? 2) Can wvnsprintf be moved from user32 into shlwapi? This would cause user32 to have to import shlwapi (because wsprintfA and friends use it in their implementation) and I don't know if that's legal because user32 seems to only import gdi32 and kernel32. If not, what's the solution? Reimplement everything in user32 to not use wvnsprintf and move the implementation over or just keep the existing situation and rename wvnsprintf to wvnsprintf and forward the shlwapi calls to user32? Thanks, Peter hunnise(a)yahoo.com _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

Re: Are these the ordinal names?
by Alexandre Julliard 08 Jul '01

08 Jul '01

Peter Hunnisett <hunnise(a)yahoo.com> writes: > Howdy, > I have a couple of questions about the following error messages > > err:win32:fixup_imports No implementation for > SHLWAPI.dll.281(wvnsprintfA) imported from > C:\windows\system\shdocvw.dll, setting to 0xdeadbeef > err:win32:fixup_imports No implementation for > SHLWAPI.dll.282(wvnsprintfW) imported from > C:\windows\system\shdocvw.dll, setting to 0xdeadbeef > err:win32:fixup_imports No implementation for > SHLWAPI.dll.240(StrRetToStrW) imported from > C:\windows\system\shdocvw.dll, setting to 0xdeadbeef > > 1) Do these messages mean that 281 is named wvnsprintfA and so on? If > so, why does the SHLWAPI.240 name not seem to jive with the existing > implementation? If a name is specified, the ordinal is only a hint, so it's OK for it to be different. What this means is that in some version of shlwapi StrRetToStrW is at ordinal 240, but it can be at other ordinals in other versions since it is looked up by name. In our builtin version, ordinal 240 is something else (which is fine), and StrRetToStrW is not implemented at all (which is the cause of your problem). You can either implement it, or use the native shlwapi. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: sharing windows between processes
by Alexandre Julliard 08 Jul '01

08 Jul '01

"Bill Medland" <medbi01(a)accpac.com> writes: > Some time ago I raised the issue of the fact that windows handles cannot be > shared between processes on the same server and was told that it was a > known significant issue. > > Is anyone doing anything about it? Sure, that's the main reason behind all the recent window management and messaging changes. So yes, it is being worked on. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Mouse events
by Alexandre Julliard 08 Jul '01

08 Jul '01

Duane Clark <dclark(a)akamail.com> writes: > I assume some problem led to its removal. I regularly try out Myst (the > 32 bit version) as a test, running locally on a 700MHz Athlon, so this > can't be blamed on a slow ethernet connection or slow machine. When > dragging the slide controls in the "planetarium", they used to follow > the mouse just fine. With this patch, if you grab the control, move the > mouse and release it, the control does not keep up with the mouse but > just moves at a moderately slow pace until it reaches the point where > the mouse was released (a few seconds to travel from one end to the > other). At that point everything returns to normal. The new hardware event handling does not yet attempt to merge mouse motion events, so this is probably the reason for the problem. This should be fixed soon. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: printing docu
by Duane Clark 08 Jul '01

08 Jul '01

Andreas Mohr wrote: > Hi all, > > while trying to configure Wine for printing in order to be able to use > Windows Acrobat Reader instead of Linux acroread which is crashing on certain > PDF files, I remembered that the printing docu is everything but perfect. > > Updated printing docu a bit. > > ... > - <sect3> > <title>Spooling</title> > <para> > Spooling is rather primitive. The [spooler] section of > @@ -82,13 +82,14 @@ > example the following lines > </para> > <screen> > -"LPT1:" = "foo.ps" "LPT2:" = "|lpr" > +"LPT1:" = "foo.ps" > +"LPT2:" = "|lpr" > </screen> > <para> > map <systemitem>LPT1:</systemitem> to file <filename>foo.ps</filename> > and <systemitem>LPT2:</systemitem> to the <command>lpr</command> > - command. If a job is sent to an unlisted port then a file is created > - with that port's name e.g. for <systemitem>LPT3:</systemitem> a file > + command. If a job is sent to an unlisted port, then a file is created > + with that port's name; e.g. for <systemitem>LPT3:</systemitem> a file > called <systemitem>LPT3:</systemitem> would be created. > </para> > <para> While it used to work that way, for me at least, the part about - a job that is sent to an unlisted port will create a file with the port's name - stopped working a few months ago. And I just tested it a few minutes ago and it still does not work (for me). I don't know where the data goes, but it does not appear to be written to a file anywhere. Actually, I think that is probably a good thing. In most cases, the print dialog should have a "Print to file" button. And if there is no way to specify a file name, then the ~/.wine/config entry "FILE:" = "foo.ps" will control where it is written, and in this case it will in fact be correctly written to the indicated file name. Duane

1 0

Half-Life/CS under WINE
by David Bronaugh 08 Jul '01

08 Jul '01

Just as a follow-up to my previous email.. if you want a quick response from me, email me off the list - I'm getting the digest, as I don't want to massively clutter up my inbox. David Bronaugh

1 0

Problems running WINE with Half-Life with CounterStrike
by David Bronaugh 08 Jul '01

08 Jul '01

Hey all, I'm having some interesting issues with Half-Life running under WINE... I'm guessing these are due to it running under WINE (they are strange enough). #1 problem: I can't type normally in the Half-Life console (the keyboard is mapped to a completely nonsensical map). I believe this is because they implemented their own custom key handler. Is there any workaround in software/with config for this? Note that this is only in the game when the game engine is initialized, otherwise the keyboard works great (Kudos to the WINE people that my dvorak-mapped QWERTY keyboard works as it should in dvorak). #2 problem: I can't get to the Half-Life console without going through some convolutions... This in itself is useless to tell you people. How I do get into the game is by the following method: I join a game or whatever, and the "Loading" screen pops up. At this point.. it will sit there for hours (I'm guessing this is a locking issue with pthreads?). What I do that appears to relieve the deadlock is to click the "Done" button that is invisible (but I know where it is, so I click it). Then the game loads normally, and runs decently enough (performance isn't great, but playable... huge kudos to the Wine crew for that). Note that the only button that does this is the "Done" button, the rest do nothing out of the ordinary. Again, this may be due to some peculiarity with Half-Life or with my config.. I'm betting on a peculiarity with Half-Life interacting with some unimplemented feauture or bug in WINE. If anyone has suggestions re these two, send em to me.. I'm more than happy to spend a few hours to help resolve this. David Bronaugh

1 0

Are these the ordinal names?
by Peter Hunnisett 08 Jul '01

08 Jul '01

Howdy, I have a couple of questions about the following error messages err:win32:fixup_imports No implementation for SHLWAPI.dll.281(wvnsprintfA) imported from C:\windows\system\shdocvw.dll, setting to 0xdeadbeef err:win32:fixup_imports No implementation for SHLWAPI.dll.282(wvnsprintfW) imported from C:\windows\system\shdocvw.dll, setting to 0xdeadbeef err:win32:fixup_imports No implementation for SHLWAPI.dll.240(StrRetToStrW) imported from C:\windows\system\shdocvw.dll, setting to 0xdeadbeef 1) Do these messages mean that 281 is named wvnsprintfA and so on? If so, why does the SHLWAPI.240 name not seem to jive with the existing implementation? 2) Why would I be getting the error for SHLWAPI.dll.240(StrRetToStrW) given the fact that the shlwapi.spec file contains the following line and there does seem to be an implementation in ordinal.c? 240 stdcall @(long long long long) SHLWAPI_240 Ciao, Peter Hunnisett hunnise(a)yahoo.com _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

Re: Win16 problems
by Gerard Patel 07 Jul '01

07 Jul '01

At 10:43 PM 03/07/2001 +0200, you wrote: <snip> >winmine fails to draw, whereas freecell runs just fine Yes, I see the problem with winmine; but is it really a 16-bits problem ? What I see is an app creating its main window iconic (minimized), then showing it using ShowWindow. Current Wine code does not take this particular behaviour (completely absurd, granted) in account - When the window is created the 'client' window is not mapped (since it's iconic, nothing surprising here), but in ShowWindow the iconic flag (WS_MINIMIZED) is cleared, and when SetWindowPos is called by ShowWindow, X11DRV_sync_client_window_position cleverly detects that the window is already mapped ;-) and decides that it's not necessary to do anything more. This seems more a Winmine specific problem than otherwise. BTW, I can't see any problem with sol.exe (win3.11 version) This patch : --- window.c.orig Wed Jun 27 03:03:36 2001 +++ window.c Sat Jul 7 23:19:03 2001 @@ -596,7 +596,7 @@ if (was_mapped && !is_client_window_mapped( win )) XUnmapWindow( display, data->client_window ); XConfigureWindow( display, data->client_window, mask, &changes ); - if (!was_mapped && is_client_window_mapped( win )) + if (is_client_window_mapped( win )) XMapWindow( display, data->client_window ); wine_tsx11_unlock(); } works around this particular problem. Gerard

1 0

Windows .lnk file parsing
by J. Henning Schwentner 07 Jul '01

07 Jul '01

Hi Wine developers, I am planning to write a little tool "lnk2desktop" which converts Windows LNK links into KDE/Gnome .desktop links, which you could use then to integrate your Windows start menu into your K menu. When I searched through the wine news archive I found a message about library that parses .lnk files and returns the command to execute, the icon etc. My question is now, does such a library exist and what other ways do exist for finding out such infomations? Regards, Henning Schwentner Lanthan Software KG P.S.: Please CC me, since I am not subscribed to the list.

1 0

sharing windows between processes
by Bill Medland 06 Jul '01

06 Jul '01

Some time ago I raised the issue of the fact that windows handles cannot be shared between processes on the same server and was told that it was a known significant issue. Is anyone doing anything about it? It seems to me that what has to be done is to have wineserver coordinate the allocation of handles. Any comments? Bill

1 0

Confusing SHGetFolderPath
by nog 06 Jul '01

06 Jul '01

Hi, While I was looking through some of the wine dlls' code I found that the function SHGetFolderPath is in the shell32 dll and the shfolder dll. Is this ment to be like this? Because the docs that I read says that the function is meant to be in shfolder. Anyway are the two functions meant to do the same thing? If so then why is the one in shell32 implemented and working and the one on shfolder doesn't eaven appear to give a fixme message? Nog

4 3

Help with nonclient Windows 95 frame
by Bill Medland 06 Jul '01

06 Jul '01

I'd appreciate some advice here before I mess things up for everyone else. In the longer term I am fixing a border issue with the edit control, but before doing so I am fixing up the nonclient frame drawing code (i.e. NC_DoNCPaint95). The code contains quite a bit of calculation based upon the system metrics. The code seems to reflect the Windows documentation. However it should come as no surprise that there are disagreements between that documentation and what I see on my Win95 computer! For example a frame with WS_THICKEDGE but no WS_BORDER nor WS_DLGFRAME nor WS_EX_DLGMODALFRAME on my computer is only 3 pixels wide, not 4 (although one of those pixels is the COLOR_WINDOW associated with the WS_THICKEDGE) Is there a way to adjust the size of the borders on the Win95 to be able to see what affects what? Bill

1 1

Mouse events
by Duane Clark 03 Jul '01

03 Jul '01

Howdy, Just tried the most recent CVS. I found that the patch from 6/25 to windows/x11drv/event.c has led to mildly annoying mouse behavior in certain (admittedly very limited) cases. Here is the change that did it: @@ -292,21 +291,8 @@ case ButtonRelease: EVENT_ButtonRelease( hWnd, (XButtonEvent*)event ); break; case MotionNotify: - /* Wine between two fast machines across the overloaded campus - ethernet gets very boged down in MotionEvents. The following - simply finds the last motion event in the queue and drops - the rest. On a good link events are servered before they build - up so this doesn't take place. On a slow link this may cause - problems if the event order is important. I'm not yet seen - of any problems. Jon 7/6/96. - */ - if ((current_input_type == X11DRV_INPUT_ABSOLUTE) && - (in_transition == FALSE)) - /* Only cumulate events if in absolute mode */ - while (TSXCheckTypedWindowEvent(display,((XAnyEvent *)event)->;window, - MotionNotify, event)); EVENT_MotionNotify( hWnd, (XMotionEvent*)event ); break; I assume some problem led to its removal. I regularly try out Myst (the 32 bit version) as a test, running locally on a 700MHz Athlon, so this can't be blamed on a slow ethernet connection or slow machine. When dragging the slide controls in the "planetarium", they used to follow the mouse just fine. With this patch, if you grab the control, move the mouse and release it, the control does not keep up with the mouse but just moves at a moderately slow pace until it reaches the point where the mouse was released (a few seconds to travel from one end to the other). At that point everything returns to normal. Other similar slide controls, such as the musical slide controls in the space ship, work fine with the patch, however. Perhaps it is possible that the code above was masking some other problem causing the control to move too slowly to follow the mouse? Duane

1 0

Win16 problems
by Ove Kaaven 03 Jul '01

03 Jul '01

Is it just me, or does no Win16 GUI apps work in the current Wine CVS? If Wine is compiled with --enable-opengl, then we get BadMatch errors in X_CreateWindow (some kind of visual mismatch), If I disable the OpenGL visual, then the windows are created and seem to exist, but they're never drawn. Win32 apps work fine, of course. I could probably look into the OpenGL problem if that was the only problem, but why are Win16 windows never drawn anyway? (Unfortunately, I don't have sol.exe here, I tested with MS Word Viewer 16-bit, but DOS apps like Monkey Island gets the same issues in my tree)

2 2

Mixed mode CD's and volume label
by David Hagood 03 Jul '01

03 Jul '01

I was trying to get Half-Life running under Wine last night, and ran into a problem with getting the CD label under Wine. Since the HL CD is a mixed mode data/audio disk (as are most game disks nowadays) Wine complained with a We don't have a way of determining the label of a mixed mode CD - Linux doesn't allow raw access ! However, Xcdroast was easily able to access the data. As an experiment, I disabled this check in misc/cdrom.c, and it worked quite happily. Perhaps this check is out of date. Perhaps it is my system setup: 2.4.6-pre7, Samsung CD-Writer/DVD reader on IDE, ide-scsi module loaded, Wine configured to use the /dev/scd0 link. Now, if I could just work out why the OpenGL is flashing...

2 1

Window painting problem
by Glenn Schrader 03 Jul '01

03 Jul '01

I've been tracking down a window painting problem and I think that I know whats happening but I'd like to get some opinions on the 'right' way to fix it. The symptom is that (in some cases) any change to a window will cause the entire window to be repainted. For instance, using the mouse to select a single character causes the whole window to update rather than just the small region which needs to be highlighted. This doesn't happen on most applications. In fact, the only one where i've seen this effect is RoAClient (a really good MUD client). Even so, its really annoying and makes the window flash so much that the app is effectively useless. The problem appears to be in BeginPaint. There is a test which checks to see if the window has the CS_PARENTDC flag set. If so then then the update region is discarded and the window is painted. This has the side effect of making the whole window repaint every time anything in the window changes. According to the windows docs that i've looked at, the CS_PARENTDC should just make the window paint using its parent's device context. There isn't any mention of also removing the invalid region clipping so i'm pretty sure that what BeginPaint is doing isn't right. In my hacking around, I disabled the branch of the test which removes the clipping region and things appear to work a lot better. The screen updating is definitely smoother. What I'm not sure of is whether this is good enough or whether the CS_PARENTDC case really should be slightly different. Normally the clipping region is offset relative to the window thats being drawn but with CS_PARENTDC should the offset be done relative to the parent window instead? Are there any other subtle things that CS_PARENTDC affects? Any insight would be appreciated... Thanks much, G. Schrader

2 1

Re: Window painting problem
by r.maurizzi＠gvs.it 03 Jul '01

03 Jul '01

Glenn Schrader <gschrad(a)ll.mit.edu> wrote: > The symptom is that (in some cases) any change to a > window will cause the entire window to be repainted. > (...) > This doesn't happen on most applications. > In fact, the only one where i've seen this effect is > RoAClient (a really good MUD client). Even so, its > really annoying and makes the window flash so much > that the app is effectively useless. Just for info, Lotus Notes v 4.6x has the same problem. Ciao, Roberto.

1 0

Re: Win16 problems
by Gerard Patel 03 Jul '01

03 Jul '01

At 02:58 AM 03/07/2001 +0200, you wrote: >Is it just me, or does no Win16 GUI apps work in the current Wine CVS? If >Wine is compiled with --enable-opengl, then we get BadMatch errors in >X_CreateWindow (some kind of visual mismatch), If I disable the OpenGL >visual, then the windows are created and seem to exist, but they're never >drawn. > >Win32 apps work fine, of course. For me Win16 apps have not more problems than Win32 ones. Word viewer 16 bits has one regression with current Cvs vs say one month ago, a focus problem that is occuring only in managed mode. Other than that, it is starting and loading files, either on my old computer with Xfree 3.3 and on my newer one with Xfree 4 (compiled with --enable-opengl) I still run most of my test apps on the old computer, but none of them crashes and the new redrawing problems are less than what you say. IMO Wine behaviour depends more now on the specific X server and window manager. I use Kde on both computers, btw (1.1.1 and 2.1 respectively) Gerard

1 0

Re: dead lock
by Alexandre Julliard 03 Jul '01

03 Jul '01

eric pouech <eric.pouech(a)wanadoo.fr> writes: > let's assume fixing it is now on Alexandre's TODO list ;-) Yes, I'll fix it, thanks for the report. You'll have to wait a bit though, as I will be away most of the week. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: PATCH: setsockopt differences for winsock/winsock2
by Alexandre Julliard 03 Jul '01

03 Jul '01

Marcus Meissner <marcus(a)jet.franken.de> writes: > That was the time that I spotted that the #defines for the IP_* > stuff _differs_ between winsock and winsock2. So I had to split up > the IPPROTO_IP handling. I tried to keep code duplication to a minimum. > > I am not sure whether the forwarders are good style. They are not IMHO. I'd suggest writing a ws1-to-ws2 conversion function instead, and use it (by duplicating its code) both for the 16-bit functions in ws2_32 and for the version 1 functions in wsock32. A little code duplication is better than adding entry points. An even better alternative that would avoid the duplication could be to have the 16-bit functions implemented in wsock32 instead of ws2_32, but this is probably a lot more work. -- Alexandre Julliard julliard(a)winehq.com

1 0

tray icon creation problem
by Adriaan Moors 03 Jul '01

03 Jul '01

hi, earlier, i reported a problem with create_icon_window. It doesn't crash anymore with today's cvs (it says an error occurred when initing the tray icon). The application (winmx) continues to load, but it keeps moving downwards. This only occurs when using enlightenment, with window maker it stays still :-) Maybe it's a bug in enlightenment? regards adriaan moors -- Have you ever noticed that the people who are always trying to tell you, "There's a time for work and a time for play," never find the time for play?

1 0

Request for feature
by David Ronis 02 Jul '01

02 Jul '01

I posted this to comp.emulators.ms-windows.wine, but got no reply. I'd been having problems with a windows application that want's to pass off a URL to a browser (netscape). OK I figured out part of my problem. [In short, I have an windows application that spawn netscape with some command-line url]. As was suggested in this thread, I had to install a windows version of netscape (I only had the linux native version installed). The installation set up the registry and things work (well sort of, netscape complains about not being able to write to the tmp directory e: [which is /tmp]). The problem now is that I seem to be on the slippery slope; i.e., most of the plugins/helper applications are absent, so in order to see various file types I have to download more windows versions of things already on my system. None of this would be necessary if there was some way to get wine to first try a native program; e.g., before trying netscape.exe or whatever was in the registry, try netscape using a standard unix system call; only if this failed would wine look for a windows version. Alternately the order could be reversed (I'd be more than willing to remove the windows versions of netscape). The best solution, would be some sort of override capability be added to the config file, for example, similar to the way native vs windows .dll's are chosen. I'm willing to play around with this, but have no experience with the internals of wine. Can somebody point me to the right point of the source code? It'd probably be trivial (and less likely to mess up wine) to first try to fork off a linux command (e.g., by mapping the end of command to something lowercase and less the .exe or .com suffix) and if that failed resort to the windows command. David P.S., I don't subscribe to this list, so please CC me.

1 0

dead lock
by eric pouech 02 Jul '01

02 Jul '01

an app of mine, using two threads, dead locks as follows: thread 1 0 0x40057b1b (RtlpWaitForCriticalSection+0x147(crit=0x40652d48, crit=0x40652d48) [critsection.c:185] in libntdll.so) (ebp=40a96a74) 1 0x40057bf6 (RtlEnterCriticalSection+0x3e(crit=0x40652d48) [critsection.c:241] in libntdll.so) (ebp=40a96a88) 2 0x400ca883 (_EnterSysLevel+0xf7(lock=0x40652d48) [syslevel.c:80] in libntdll.so) (ebp=40a96ab4) 3 0x40639a5f (GDI_AllocObject+0x2f(size=0x34, magic=0x4f4b, handle=0x40a96afc, handle=0x40a96afc) [gdiobj.c:427] in libgdi32.so) (ebp=40a96ad8) 4 0x4062c668 (CreateBitmap+0x78(width=0x20, height=0x20, planes=0x1, bpp=0x18, bits=0x4039fe1c) [bitmap.c:124] in libgdi32.so) (ebp=40a96b00) 5 0x40770f66 (GetIconInfo+0xca(hIcon=0x24e, iconinfo=0x40a96b50) [cursoricon.c:1816] in libuser32.so) (ebp=40a96b30) 6 0x40805a4a (set_icon_hints+0xe6(display=0x8082898, wndPtr=0x4037fe00, hints=0x8083da0, display=0x8082898, win=0x4037fe00, display=0x8082898, win=0x4037fe00) [window.c:263] in libx11drv.so) (ebp=40a96b8c) 7 0x40805ccb (set_wm_hints+0xf3(display=0x8082898, win=0x4037fe00) [window.c:370] in libx11drv.so) (ebp=40a96bbc) 8 0x4080691e (create_whole_window+0x1aa(display=0x8082898, win=0x4037fe00, win=0x4037fe00) [window.c:699] in libx11drv.so) (ebp=40a96c50) 9 0x40806ead (X11DRV_CreateWindow+0xb5(hwnd=0x4ac, cs=0x40a96e2c, unicode=0x0) [window.c:856] in libx11drv.so) (ebp=40a96c90) 10 0x40797831 (WIN_CreateWindowEx+0x6c9(cs=0x40a96e2c, classAtom=0xc014, type=0x2) [win.c:865] in libuser32.so) (ebp=40a96d08) 11 0x40797cca (CreateWindowExA+0x15a(exStyle=0x0, className=0x404c86ce, windowName=0x4049ef3c, style=0xcf0000, x=0x366, y=0x14, width=0x19a, height=0x16f, parent=0x0, menu=0x0, instance=0x4049d000, data=0x0) [win.c:1030] in libuser32.so) (ebp=40a96e5c) 12 0x4049be85 (SInitInstance+0x169(hInstance=0x4049d000, nCmdShow=0x1) [sinit.c:247] in a.so) (ebp=40a96ecc) 13 0x4049911b (ServerThread+0x4b(p=0x405e6e14) [a.c:19] in a.so) (ebp=40a96f1c) 14 0x400cb1ac (THREAD_Start+0x98 [thread.c:273] in libntdll.so) (ebp=40a96f38) 15 0x400ca44e (SYSDEPS_StartThread+0x36(teb=0x40aa7000) [sysdeps.c:73] in libntdll.so) (ebp=40a96ff4) 16 0x4030531a (NTDLL.DLL.memcpy+0x494aa in libc.so.6) (ebp=00000000) thread 2 0 0x40057b1b (RtlpWaitForCriticalSection+0x147(crit=0x40841d10, crit=0x40841d10) [critsection.c:185] in libntdll.so) (ebp=405e6ac0) 1 0x40057bf6 (RtlEnterCriticalSection+0x3e(crit=0x40841d10) [critsection.c:241] in libntdll.so) (ebp=405e6ad4) 2 0x4080b668 (lock_tsx11+0x1c [x11drv_main.c:109] in libx11drv.so) (ebp=405e6ae4) 3 0x4080f595 (X11DRV_StretchBlt+0x39(dcDst=0x4039f710, xDst=0x0, yDst=0x0, widthDst=0xa0, heightDst=0x80, dcSrc=0x4039f4e8, xSrc=0x0, ySrc=0x0, widthSrc=0x190, heightSrc=0x140, rop=0xcc0020) [bitblt.c:1555] in libx11drv.so) (ebp=405e6b10) 4 0x4061bbf2 (StretchBlt+0x102(hdcDst=0xf4, xDst=0x0, yDst=0x0, widthDst=0xa0, heightDst=0x80, hdcSrc=0xf0, xSrc=0x0, ySrc=0x0, widthSrc=0x190, heightSrc=0x140, rop=0xcc0020) [bitblt.c:120] in libgdi32.so) (ebp=405e6b54) 5 0x40499b84 (CInitializeCoolBitmaps+0x36c [cinit.c:229] in a.so) (ebp=405e6bd4) 6 0x4049a265 (CMainWndProc+0x205(hWnd=0x13c, msg=0x590, wParam=0x0, lParam=0x0) [client.c:131] in a.so) (ebp=405e6d24) 7 0x4079e197 (WINPROC_wrapper+0x17 in libuser32.so) (ebp=405e6d48) 8 0x4079e216 (WINPROC_CallWndProc+0x76(proc=0x4049a060, hwnd=0x13c, msg=0x590, wParam=0x0, lParam=0x0) [winproc.c:171] in libuser32.so) (ebp=405e6d74) 9 0x407a3da8 (CallWindowProcA+0x88(func=0x4096054c, hwnd=0x13c, msg=0x590, wParam=0x0, lParam=0x0) [winproc.c:2589] in libuser32.so) (ebp=405e6d9c) 10 0x40785fcc (DispatchMessageA+0xd8(msg=0x405e6e24) [message.c:2359] in libuser32.so) (ebp=405e6de0) 11 0x404991ff (WinMain+0x9b(hInstance=0x4049d000, hPrevInstance=0x0, lpCmdLine=0x40360747, nCmdShow=0x1) [a.c:78] in a.so) (ebp=405e6e40) 12 0x4049e082 (__wine_exe_main+0x82 [a.spec.c:5838] in <Debugged process>) (ebp=405e6ecc) 13 0x400c6d52 (start_process+0x1a6 [process.c:391] in libntdll.so) (ebp=405e6f30) 14 0x400ca559 (SYSDEPS_DoCallOnStack+0x25(func=0x400c6bac, arg=0x0) [sysdeps.c:173] in libntdll.so) (ebp=405e6ff0) 15 0x400ca603 (SYSDEPS_CallOnStack+0x2f in libntdll.so) (ebp=bffff660) 16 0x400ca6ad (SYSDEPS_SwitchToThreadStack+0x95(func=0x400c6bac) [sysdeps.c:236] in libntdll.so) (ebp=bffff69c) 17 0x400c70de (PROCESS_InitWine+0x1ce(argc=0x1, argv=0xbffff734, win16_exe_name=0x804c620, win16_exe_file=0x804c724) [process.c:519] in libntdll.so) (ebp=bffff6b4) 18 0x0804b1ee (Letext [main.c] in wine) (ebp=bffff6cc) 19 0x4027bcbe (NTDLL.DLL.sqrt+0x3262e in libc.so.6) (ebp=bffff708) 20 0x08049021 (_start+0x21 in wine) (ebp=00000000) it (simply) deadlocks because the new window management code (written by Alexandre), (rev 1.5 of dlls/x11drv/window.c, change log entry Create an X window for every window, including children. Fixed non-client rectangle calculations in managed mode. Added support for icon window in managed mode. ) does call GDI functions (here GetIconInfo) while the x11drv critical section is held, which shouldn't be the case let's assume fixing it is now on Alexandre's TODO list ;-) A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

1 0

Re: convert 16bit comm stuff to use handles
by Ove Kaaven 02 Jul '01

02 Jul '01

On Sat, 30 Jun 2001, Mike McCormack wrote: > this is the first step in cleaning up the 16bit comm code. > This patch is untested, so have a look, and give it a go! > - ptr->s_read = SERVICE_AddObject( FILE_DupUnixHandle( ptr->fd, > - GENERIC_READ | SYNCHRONIZE ), > + ptr->s_read = SERVICE_AddObject( ptr->handle, > comm_notification, > (ULONG_PTR)ptr ); Not good... you *must* duplicate the handle (probably with DuplicateHandle) before passing it to SERVICE_AddObject. The SERVICE_Delete will close the handle passed to AddObject, which is bound to cause problems if it's not a duplicate.

2 1

GDI Memory Leak + err:x11drv:X11DRV_SetDeviceClipping Rgn is 0. Please report this.
by adoniz＠hushmail.com 02 Jul '01

02 Jul '01

I got these errors while trying to do something a little uncommon: I have been running Halflife from my windows partiton just fine. But I wanted to remove the huge files and replace them with symlinks to a cdrom, but since I can't do symlinks on fat32 (is there a wine hack for this?? i think it would be a great idea!!), I figured I copy the basic files of HL to my linux partition, and symlink the huge pak files. So, I have /mnt/halflife and under there I have some symlinks. I went ahead and added these to my ~/.wine/config [Drive H] "Path" = "/mnt" "Type" = "hd" "Filesystem" = "vfat" Now, as root try running halflife with: cd /mnt/halflife ; wine hl.exe or wine h:\\halflie\hl.exe (or with all the command line options for opengl, software, etc) I get these errors and a SegFault from wine: /mnt/halflife# wine h:\\halflife\\hl.exe -- -console -toconsole -soft -w 640 -win err:local:LOCAL_GetBlock not enough space in GDI heap 0237 for 108 bytes err:region:CombineRgn Invalid rgn=0000 err:x11drv:X11DRV_SetDeviceClipping Rgn is 0. Please report this. err:region:CombineRgn Invalid rgn=0000 err:region:CombineRgn Invalid rgn=0000 err:region:CombineRgn Invalid rgn=0000 err:region:CombineRgn Invalid rgn=0000 Segmentation fault whatever:/mnt/halflife# err:ntdll:RtlpWaitForCriticalSection Critical section 0x4065da54 wait timed out, retrying (60 sec) fs=0257 Running notepad.exe from /mnt/ works just fine. So something else is happening here... Email me if you need more info thanks Free, encrypted, secure Web-based email at www.hushmail.com

2 1

Re: Re: rebar trouble with WinZip 8.0
by Mike McCormack 02 Jul '01

02 Jul '01

Hi Guy, Yep, that does it. Thanks, Mike Original message from: "Guy L. Albertelli" <galberte(a)neo.lrun.com> > >Hi Mike, > >See if the attached patch fixes your problem. It seems to do it for me. > >Thanks for finding this. > >Guy > >-----Original Message----- >From: Mike McCormack <mike_mccormack(a)start.com.au> >To: wine-devel(a)winehq.com <wine-devel(a)winehq.com> >Date: Thursday, June 28, 2001 10:46 PM >Subject: rebar trouble with WinZip 8.0 > > >>Hi, >> >>WinZip 8.0 has a toolbar. It used to show all the toolbar buttons, but >>it seems to have a problem now, since only the LHS >>button is shown. Some debug output below. >> >>Mike ------------------------------------------ mailto:Mike_McCormack@looksmart.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

1 0

opengl32.dll works, but how about opengl.dll
by adoniz＠hushmail.com 01 Jul '01

01 Jul '01

Another (small I think) problem I noticed is that some braindead Windows apps (yes, 32bit, Windows 9x) are linked against opengl.dll as opposed to opengl32.dll !! But this makes wine refuse to run them because it doesn't "recognize" that the application needs the built-in openGL support. So how would one go about fixing this, so that Wine will use the builtin OpenGL support not just for openg32.dll but also for opengl.dll ? thanks in advance ps. please email me as i am not subscribed to the ML Free, encrypted, secure Web-based email at www.hushmail.com

1 0

Re: rebar trouble with WinZip 8.0
by Guy L. Albertelli 01 Jul '01

01 Jul '01

Hi Mike, See if the attached patch fixes your problem. It seems to do it for me. Thanks for finding this. Guy -----Original Message----- From: Mike McCormack <mike_mccormack(a)start.com.au> To: wine-devel(a)winehq.com <wine-devel(a)winehq.com> Date: Thursday, June 28, 2001 10:46 PM Subject: rebar trouble with WinZip 8.0 >Hi, > >WinZip 8.0 has a toolbar. It used to show all the toolbar buttons, but >it seems to have a problem now, since only the LHS >button is shown. Some debug output below. > >Mike > > >mike@linux:~/c > wine Program\ Files/WinZip/WINZIP32.EXE >Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: >x11drv: Warning: $DISPLAY variable ignored, using ':0.0' specified in >config file >.. >trace:rebar:REBAR_AdjustBands start=0, end=0, max x=550, max y=61 >trace:rebar:REBAR_AdjustBands Phase 1 band 0, (0,0)-(69,61), orig x=0, >xsep=0 >trace:rebar:REBAR_AdjustBands Phase 2 band 0, (0,0)-(69,61), orig x=0, >xsep=0 >err:rebar:REBAR_AdjustBands Serious problem adjusting row 1, start >band 0, end band 0 >trace:rebar:REBAR_AdjustBands start=0, end=0, max x=561, max y=61 >trace:rebar:REBAR_AdjustBands Phase 1 band 0, (0,0)-(69,61), orig x=0, >xsep=0 >trace:rebar:REBAR_AdjustBands Phase 2 band 0, (0,0)-(69,61), orig x=0, >xsep=0 >err:rebar:REBAR_AdjustBands Serious problem adjusting row 1, start >band 0, end band 0 >.. >fixme:shell:SHGetFileInfoA set icon to shell size, stub >fixme:listview:LISTVIEW_SetColumnOrderArray iCount 9 lpiArray >0x405a6a74 >mike@linux:~/c > > > >------------------------------------------ >mailto:Mike_McCormack@looksmart.com.au >ph +82 16 430 0425 > >__________________________________________________________________ >Get your free Australian email account at http://www.Looksmart.com.au > > >

1 0

Re: convert 16bit comm stuff to use handles (fwd)
by lawson_whitney＠juno.com 01 Jul '01

01 Jul '01

OOPS, this was meant for wine-devel, not wine-patches. Sorry! On Sat, 30 Jun 2001, Mike McCormack wrote: > > Hi, > > this is the first step in cleaning up the 16bit comm code. > This patch is untested, so have a look, and give it a go! > > Mike > Good day! Turns out the app will still run with --winver win31 (I swear it worked with --winver nt40 before, I think :-) but with the patch, it can't find the modem with both hands and a flashlight. Seems not to see input. comm trace is attached. Let me know if (which) additional traces would help. Lawson ---blah---

1 0

Re: wine/ ./configure ./configure.in documentation ...
by Uwe Bonnes 29 Jun '01

29 Jun '01

>>>>> "Alexandre" == Alexandre Julliard <julliard(a)winehq.com> writes: Alexandre> ... Alexandre> +0 -0 wine/msdos/ppdev.c ^^^^^ Hallo Alexandre, oops, this is not enough. The patch I submitted was --- /dev/null Tue Feb 20 18:39:20 2001 +++ wine/msdos/ppdev.c Thu Jun 21 14:32:14 2001 @@ -0,0 +1,283 @@ ^^^^ Did I choose wrong arguments to diff? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

2 1

rebar trouble with WinZip 8.0
by Mike McCormack 29 Jun '01

29 Jun '01

Hi, WinZip 8.0 has a toolbar. It used to show all the toolbar buttons, but it seems to have a problem now, since only the LHS button is shown. Some debug output below. Mike mike@linux:~/c > wine Program\ Files/WinZip/WINZIP32.EXE Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: x11drv: Warning: $DISPLAY variable ignored, using ':0.0' specified in config file .. trace:rebar:REBAR_AdjustBands start=0, end=0, max x=550, max y=61 trace:rebar:REBAR_AdjustBands Phase 1 band 0, (0,0)-(69,61), orig x=0, xsep=0 trace:rebar:REBAR_AdjustBands Phase 2 band 0, (0,0)-(69,61), orig x=0, xsep=0 err:rebar:REBAR_AdjustBands Serious problem adjusting row 1, start band 0, end band 0 trace:rebar:REBAR_AdjustBands start=0, end=0, max x=561, max y=61 trace:rebar:REBAR_AdjustBands Phase 1 band 0, (0,0)-(69,61), orig x=0, xsep=0 trace:rebar:REBAR_AdjustBands Phase 2 band 0, (0,0)-(69,61), orig x=0, xsep=0 err:rebar:REBAR_AdjustBands Serious problem adjusting row 1, start band 0, end band 0 .. fixme:shell:SHGetFileInfoA set icon to shell size, stub fixme:listview:LISTVIEW_SetColumnOrderArray iCount 9 lpiArray 0x405a6a74 mike@linux:~/c ------------------------------------------ mailto:Mike_McCormack@looksmart.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

1 0

Re: Support Ordinal forwarding in Dll loading
by Alexandre Julliard 29 Jun '01

29 Jun '01

"Guy L. Albertelli" <galberte(a)neo.lrun.com> writes: > In attempting to use Specmaker to create a forwarding DLL to do testing of > the Rebar and ComboBoxEx controls, I ran into a problem where pe_image.c did > not support forwarding an ordinal only reference. This patch allows that > function to work. The ordinal forward is of the form: > dllname.DLLNAME_nnnn. I don't think Windows supports something like this. I would suggest instead to fix specmaker to not generate a forward in this case. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Proper detection of VM86 support
by Alexandre Julliard 28 Jun '01

28 Jun '01

Patrik Stridvall <ps(a)leissner.se> writes: > Proper detection of VM86 support > on FreeBSD, Linux and Solaris added. I don't think that's useful. Even if we someday support vm86 on other platforms, this is one of these cases where a simple platform check (#ifdef linux) is preferable to complex configure magic IMO. This is how we do the LDT check too, because there simply isn't enough similarity between platforms to justify configure tests. -- Alexandre Julliard julliard(a)winehq.com

1 0

[Problem report] Messages cooked too much ?
by Gerard Patel 27 Jun '01

27 Jun '01

This is a problem of intermittents hangings, when moving the mouse or closing a window (not obvious). I finally realized that the traces in the hanging of Eudora 4 looked very similar, but Eudora 4 hangs reliably ;-) I have found this Eudora crash an infinite loop generated by a mouse move message, cooked to generate a WM_NCMOUSEMOVE, then this last message is obtained repeatedly from the server without being ever removed. It does not seem right to peek a cooked message off the server, not find anything useful to do with it, and just ignore it and asking the server again. The following patch removes the problem, and *seems* to cure the intermittent hangings of other apps. Gerard --- message.c.orig Wed Jun 27 22:14:07 2001 +++ message.c Wed Jun 27 22:13:57 2001 @@ -790,7 +790,11 @@ if (qmsg.kind == RAW_HW_MESSAGE || qmsg.kind == COOKED_HW_MESSAGE) { if (!process_hardware_message( &qmsg, hwnd, first, last, flags & PM_REMOVE )) + { + if (qmsg.kind == COOKED_HW_MESSAGE) + if (!(flags & PM_REMOVE)) QUEUE_FindMsg( hwnd, first, last, TRUE, &qmsg ); goto retry; + } } else {

1 0

Re: docu patch
by Alexandre Julliard 26 Jun '01

26 Jun '01

Andreas Mohr <a.mohr(a)mailto.de> writes: > diff -u -r1.9 DEVELOPERS-HINTS > --- DEVELOPERS-HINTS 2001/01/10 23:59:25 1.9 > +++ DEVELOPERS-HINTS 2001/06/26 23:02:00 > @@ -23,6 +23,7 @@ > > GDI: > > + console/ - handling of text consoles > graphics/ - graphics drivers > x11drv/ - X11 display driver > win16drv/ -> see below > @@ -58,7 +59,7 @@ > msnet/ > msvcrt/ - C runtime library > msvideo/ - 16 bit video manager > - ole32/ - 32 bit OLE 2.0 librairies > + ole32/ - 32 bit OLE 2.0 libraries > oleaut32/ - 32 bit OLE 2.0 automation > olecli/ - 16 bit OLE client > oledlg/ - OLE 2.0 user interface support > @@ -86,12 +87,13 @@ > > Miscellaneous: > > - misc/ - shell, registry, winsock, etc. > + misc/ - misc. wine management, registry, etc. > ipc/ - SysV IPC based interprocess communication > - win32/ - misc Win32 functions > ole/ - OLE code > - nls/ - National Language Support > + nls/ - National Language Support > configuration files > + unicode/ - Unicode (character) support > + win32/ - misc Win32 functions > I have nothing against updating the doc, but I don't think adding wrong information is going to help <g>. console/ is not a GDI directory, and there is no top level nls/ directory. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: configure.in patch
by Marcus Meissner 26 Jun '01

26 Jun '01

On Tue, Jun 26, 2001 at 03:34:23PM +0900, Bang Jun-Young wrote: > * configure.in: > Remove a redundant check for flex. It is not redundant! AC_PROG_LEX does more than just look for the 'lex' binary. Please do not apply. Ciao, Marcus > -AC_PROG_LEX > AC_CHECK_PROGS(XLEX,$LEX flex lex,none) > if test "$XLEX" = "none" > then

3 5

change of style in the edit control
by Bill Medland 26 Jun '01

26 Jun '01

Is anyone working on the edit control's handling of WM_STYLE_CHANGED? Does anyone have any useful information? I intend adding handling of WM_STYLE_CHANGING/ED to controls/edit.c for our application (which uses SetWindowLong to modify the style after creation). 1. Does anyone know why the EDITSTATE.style is not fed back to the pWnd->dwStyle after being modified. 2. Does anyone know of any documentation of the interaction within windows when the styles are incompatible? Bill

1 0

Apps DB round 2
by Jeremy Newman 26 Jun '01

26 Jun '01

The new Application DB (http://wine.codeweavers.com/appdb/) is starting to fill up. But, we still need your help before we totally unleash it on the Wine community. We need as much feedback, comments, and flames [:-)] as possible this week. We need volunteers to take responsibility for updating Apps in the DB. If you would like to help, email the appDB team at appdb(a)codeweavers.com. Areas we need help on: - Add Apps and App Versions. - Comments on Apps - Application Owners (the app db has a privilege system where you can be owner of an app.) - Screenshots (lots of 'em) --- _ _WebGeek/NetAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://jnewman.codeweavers.com | .` / -_) V V / ' \/ _` | ' \ -= mailto:jnewman@codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

9 12

undefined reference to main in _start
by Gilroy Billard 25 Jun '01

25 Jun '01

Hi, I can't link in any version of the WINE libraries after version 20001202 without getting a linker error: undefined reference to main in function _start. I compile WINE with these options: ./configure --without-x --without-curses --disable-debug --disable-trace. Any ideas??? thanks, Gilroy Billard mailto:gilroy@trakonic.com Software Developer Trakonic Inc. PH: 1-902-450-0922 FX: 1-902-450-0939 1-877-419-3887 http://www.trakonic.com

5 6

Re: Win16 calls by Win32 functions
by Alexandre Julliard 25 Jun '01

25 Jun '01

Patrik Stridvall <ps(a)leissner.se> writes: > Sure Win32 calls to Win16 should be eliminated that is > without question. This is how Windows NT does it and > Alexandre has a policy that Wine should doing like > Windows NT does. I fully agree. > > However I'm not positive that replacing Win16 calls to > Win16 with Win32 calls is always good idea. See below. As a rule it is a good idea, but there are of course exceptions. Basically the rule should be that wherever you can choose between a Win16 or Win32 function to do something, you should pick the Win32 function. But in the cases where the Win16 and Win32 functions have different semantics, then of course you have to use the correct one, even if in some cases it means calling Win16 functions from Win32 (like for the GlobalAlloc stuff). -- Alexandre Julliard julliard(a)winehq.com

1 0

RE: Win16 calls by Win32 functions
by Patrik Stridvall 25 Jun '01

25 Jun '01

> "Patrik Stridvall" <ps(a)leissner.se> wrote: > > > Noticing that you (Dimitry) have send in a few patch > > replacing Win16 calls by Win32 ones, I wish to > > point out that winapi_check can detect "illegal" > > calls from Win32 to Win16. > > > > Just do > > winapi_check --cross-call-win32-win16 > > Great! Why didn't you just make a patch and submit it? Well. Because I don't want to blindly do search and replace I haven't got around to do it since it will take some time to analyze each case for correctness. It is on my list of things to do but it has very low priority. But since you seems to be doing it, I might just as well tell you how to easily find many of them. > > Note that some of the fixes in your (Dimitry's) > > patches is not included in the result below > > because they are Win16 functions calling Win16 > > functions. > > > > I do not say this is nessary wrong, but are > > you (Dimitry) really sure this is how it should be? > > Well, as Alexandre already has pointed out, Win16 should be > mostly implemented by using Win32. I agree with him that use > of the 16-bit code should be eliminated as much as possible. > Moreover, until now I just have replaced only obvious places: > 16-bit functions which just thunk up to win32 without any > argument processing. Sure Win32 calls to Win16 should be eliminated that is without question. This is how Windows NT does it and Alexandre has a policy that Wine should doing like Windows NT does. I fully agree. However I'm not positive that replacing Win16 calls to Win16 with Win32 calls is always good idea. See below. > > Sure it probably runs a little faster, but then Win16 > > applications on a modern computer are likely to be > > _very_ fast, so it is really worth risking potential > > compabillity errors because of some probably irrelavant > > speed differences. > > > > Not that functions like DeleteObject are likely to > > have such problems but still... > > I'm not going to blindly replace 16-bit calls by 32-bit. > I look into the code and do think twice before submitting > a patch. Of course you are not, but there might be subtle issues that break the code in the future then the full Win32 semantics is implemented. That requires much more thinking than just casually browsing the code and reading the documentation. Actually just thinking and reading documentation is not enough either Win32 or Win16 might have undocumentation features on Windows not implement by Wine yet. Note that I'm not convinced is a large problem if any at all. I'm just worried and think we need to think this through carefully. So what should we do? Correct me if I'm wrong but because of the DLL separation Win16 to Win16 calls between different DLL:s (or rather different .so files) must not take place. I notice that, for example, user32.spec contains the following lines: ################################################################ # Wine extensions: Win16 functions that are needed by other dlls # @ stdcall CallNextHookEx16(long long long long) CallNextHookEx16 @ stdcall CallWindowProc16(long long long long long) CallWindowProc16 @ stdcall CloseDriver16(long long long) CloseDriver16 @ stdcall CreateDialogIndirectParam16(long ptr long long long) CreateDialogIndirectParam16 @ stdcall DefDriverProc16(long long long long long) DefDriverProc16 @ stdcall DialogBoxIndirectParam16(long long long long long) DialogBoxIndirectParam16 @ stdcall GetDriverModuleHandle16(long) GetDriverModuleHandle16 @ stdcall OpenDriver16(str str long) OpenDriver16 @ stdcall PostAppMessage16(long long long long) PostAppMessage16 @ stdcall SendDriverMessage16(long long long long) SendDriverMessage16 @ stdcall SetWindowsHookEx16(long long long long) SetWindowsHookEx16 @ stdcall UserYield16() UserYield16 and gdi32.spec contains these lines: ################################################################ # Wine extensions: Win16 functions that are needed by other dlls # @ stdcall CreateMetaFile16(str) CreateMetaFile16 @ stdcall CloseMetaFile16(long) CloseMetaFile16 This is what is guess Alexandre wants eliminated not calls like the call in SetDCState16 (Win16 GDI) to DeleteObject16 (Win16 GDI) that you "fixed" in one of your patches. Of course Win32 to Win16 calls should be fixed even within a DLL but that is because of possible different semantics not because of the DLL separation. In short I suggest the following policy 1. No Win32 to Win16 calls: This is because of semantic and speed reasons. 2. No Win16 to Win16 calls between different DLL:s: This is because of the DLL separation. 3. No Win16 to Win32 calls within a DLL (with the exception a function's Win32 counterpart or replacement in the case of obsolete function): This is because of semantic reasons but I'm not sure how hard we must enforce point, because if the the Win32 function generates a non Win16 message or some other non Win16 related stuff I guess we can quite easily can (and perhaps even now does) ignore or filter such things in more fundamental part of the code like in the message dispatching code.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel