- Wine-Devel - list.winehq.org

Re: OLE clipping
by Mike Hearn May 29, 2003

May 29, 2003

Hmmm, as a follow up, changing if ((flags & DCX_CLIPCHILDREN) && (mode != ClipByChildren)) to if (flags & DCX_CLIPCHILDREN) in get_visible_region fixes it. I assume altering the assignment in GetDC would have the same effect. I think this is what you were talking about earlier with Wine vs X11 clipping.... it seems in this case leaving it up to X doesn't work. I don't understand enough about this area to submit a proper patch though, so I just thought I'd let you know what change fixed the problem. thanks -mike On Fri, 2003-05-16 at 16:10, Mike Hearn wrote: > > Yes I know what you talking about. Here is a patch for this. When I > > presented it to Alexandre a while ago he said that it's not necessary > > because X will take care of the clipping for us. He said we don't need > > to do it. > > Thanks for the patch. I applied it, but other than the Google "I'm > feeling lucky" buttons now appearing when i mouse over them, not much > changed (clip_children is being called now though). > > Here's an excerpt from a trace: > > trace:x11drv:X11DRV_Expose win 0x10025 (4000009) 227,463 365x91 > trace:x11drv:X11DRV_Expose win 0x1002d (400002a) 227,0 365x40 > trace:x11drv:X11DRV_CreateBitmap (0xc18) 365x91 24 bpp > trace:x11drv:X11DRV_GetDC visible=1 > trace:x11drv:clip_children called for parent=1002d, last=0 > trace:x11drv:get_visible_region top=0x1002a, win->hwndSelf=0x1002d > trace:x11drv:get_visible_region WS_CLIPSIBLINGS for child > trace:x11drv:clip_children called for parent=1002a, last=1002d > trace:x11drv:clip_children one > trace:x11drv:clip_children two > trace:x11drv:get_visible_region WS_CLIPSIBLINGS for child > trace:x11drv:clip_children called for parent=10029, last=1002a > trace:x11drv:clip_children one > trace:x11drv:clip_children two > > And the window tree looks like this: > > 10025 (main window - java renders buttons etc direct to it) > |-10029 (start of IE embedding?) > |- 1002A > |- 1002D (this seems to be the IE rendering area) > |-10026 (not sure what this is) > > So, As you can see Expose events are sent to the main window and the > embedded IE window, which makes sense. I can see the clip_children call > seemingly chaining up the window tree - it starts at 1002D and ends up > at 10029 near the top, BUT for some reason clip_children is never called > with a parent of 10025. > > I'm pretty lost in this code, I'm not sure how Java is even drawing - I > switched off the blitting code and it mangled most Wine graphics in > other apps, but Java was just like normal. But I think maybe > clip_children should be called for the top level window? > > thanks a lot for you help Ulrich, it's appreciated! > -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

2 7

Wine folks interested in a CHM spec?
by Pabs3 May 29, 2003

May 29, 2003

Hi wine peeps, Just wondering if Wine folks are implementing a chm viewer and if you would be interested in a specification on the internal files of CHMs and even relicencing some of the code for my chm decompiler. all at http://bonedaddy.net/pabs3/hhm/ BTW; please cc me in replies since, while i'm subscribed i don't want to get heaps of other wine discussion & so i've turned off mail delivery. Bye, Pabs ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

13 24

Wine + Ventrilo (speech communication)
by Kristoffer Ericson May 29, 2003

May 29, 2003

Greetings, Just wanted to point out that Ventrilo (www.ventrilo.com) works in wine with abit of work. Although it requires 3 files (gsm 6.10 codec among other things). The bug i'm left with currently is that when 2 people speak (at same time), it freezes up. Ventrilo will probobly make a linux version but wanted you all to know. Best wishes ps. Tribes still works =) _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus

2 1

d3d merges
by Ann and Jason Edmeades May 28, 2003

May 28, 2003

Thanks Raphael for doing that, as I hadnt had chance to merge in your changes. BTW Did I read right that Alexander is away for 3 weeks...! He'll have a nice workload when he gets back :-) Jason

2 1

Working a bit with installers
by Carlos Lozano May 28, 2003

May 28, 2003

Hello, I have been playing a bit with a installer what the background appears above of the window what you must press "NEXT>>", what you can't select. It worked only using "Managed" = "No". Changing the line: dlls/x11drv/windows.c inline static BOOL is_window_managed( WND *win ) { if (!managed_mode) return FALSE; /* tray window is always managed */ if (win->dwExStyle & WS_EX_TRAYWINDOW) return TRUE; /* child windows are not managed */ if (win->dwStyle & WS_CHILD) return FALSE; /* tool windows are not managed */ if (win->dwExStyle & WS_EX_TOOLWINDOW) return FALSE; /* windows with caption or thick frame are managed */ if ((win->dwStyle & WS_CAPTION) == WS_CAPTION) return TRUE; if (win->dwStyle & WS_THICKFRAME) return TRUE; /* default: not managed */ return FALSE; ^^^^^^^^^^^^^^ with return TRUE; It is possible install (at least in my case) the program even in managed mode. Regards, Carlos. -- ___ _ \ | / Consulting | . |._ _ _| | ___ ___ ___ http://www.andago.com | || ' |/ . |<_> |/ . |/ . \__ GNU/Linux |_|_||_|_|\___|<___|\_. |\___/ _ \ __|\ \ / Carlos A. Lozano <___'/ | \ -_) __/\__ \ > < -_) [ carlos.lozano(a)andago.com ]\___|_| ____/ _/\_\___| [ calb(a)epsxe.com ] http://www.ePSXe.com

1 1

Agent crashes when sending article
by Gerhard W. Gruber May 28, 2003

May 28, 2003

Some time ago I posted that Agent crashes when sending an email. At this time the crash was sometimes quite frequently and sometimes it worked well for an extended period of time. Now I found a scenario which will cause this crash rather reliably (it failed only one time for me when I tested it). Compose an article with a non-existent newsgroup., messagetext and subjectline doesn't matter I think, and then send this article with <ALT>-S (for Send-Now). When the crash occurs ebx contains a pointer that is pointing to some invalid address (actually it is a string instead of a pointer) which is subsequently referenced. On each crash the pointer and it's content is the same. I already run agent with "wine -debugmsg +all" and got a rather huge trace (about 500MB) so if you need any info I can extract it from this. I tried to anlyze the problem but I have problems interpreting the trace so it doesn't tell me much. I would investigate this myself but I need some input how the best way to approach this. winedbg is not much help to me for now. Or can you set memory access breakpoints like in Softice? Backtrace: =>0 0x005b507b (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x202cd in D:\home\agent\agent.exe) (ebp=406b1cd8) 1 0x0046cd45 (agent.exe.(a)ENUMERATEACTIVEWNDS$QP6HWND__P9TENUMINFO+0x39175 in D:\home\agent\agent.exe) (ebp=406b1f60) 2 0x0040e1ba (agent.exe.__GetExceptDLLinfo+0xd14c in D:\home\agent\agent.exe) (ebp=406b1f74) 3 0x0058e5c3 (agent.exe.(a)WinTimerStatics@Func$qp6HWND__uiuiul+0xe35b in D:\home\agent\agent.exe) (ebp=406b1f88) 4 0x00531d64 (agent.exe.(a)MyDdeCallback$quiuip7HCONV__p5HSZ__t4p10HDDEDATA__ulul+0x17d5c in D:\home\agent\agent.exe) (ebp=406b1fd8) 5 0x004dacf4 (agent.exe.(a)PropdlgKbdProc$qiuil+0x261fc in D:\home\agent\agent.exe) (ebp=406b2024) 6 0x00598543 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x3795 in D:\home\agent\agent.exe) (ebp=406b207c) 7 0x005985a0 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x37f2 in D:\home\agent\agent.exe) (ebp=406b20b0) 8 0x0059865f (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x38b1 in D:\home\agent\agent.exe) (ebp=406b20f8) 9 0x005985c8 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x381a in D:\home\agent\agent.exe) (ebp=406b2110) 10 0x408141fb (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=406b2134) 11 0x4081429f (WINPROC_CallWndProc+0x8f(proc=0x416b1fb8, hwnd=0x10025, msg=0x411, wParam=0x100, lParam=0x4199cac8) [winproc.c:184] in user32.dll.so) (ebp=406b2164) 12 0x4081a6e8 (CallWindowProcA+0x88(func=0x413b0848, hwnd=0x10025, msg=0x411, wParam=0x100, lParam=0x4199cac8) [winproc.c:2854] in user32.dll.so) (ebp=406b218c) 13 0x407fc1da (DispatchMessageA+0x12a(msg=0x406b222c) [message.c:794] in user32.dll.so) (ebp=406b21d0) 14 0x407dc9f9 (MENU_TrackMenu+0x5e9(hmenu=0x0, wFlags=0x80000000, x=0x0, y=0x0, hwnd=0x10025, lprect=0x0) [menu.c:2891] in user32.dll.so) (ebp=406b2248) 15 0x407dce67 (MENU_TrackKbdMenuBar+0x147(hwnd=0x10025, wParam=0xf100, vkey=0x0) [menu.c:3049] in user32.dll.so) (ebp=406b2278) 16 0x40801266 (NC_HandleSysCommand+0x266(hwnd=0x10025, wParam=0xf100, lParam=0x0) [nonclient.c:2194] in user32.dll.so) (ebp=406b22a0) 17 0x407f0aee (DEFWND_DefWinProc+0x74e(hwnd=0x10025, msg=0x112, wParam=0xf100, lParam=0x0) [defwnd.c:534] in user32.dll.so) (ebp=406b2330) 18 0x407f1517 (DefWindowProcA+0x3a7(hwnd=0x10025, msg=0x112, wParam=0xf100, lParam=0x0) [defwnd.c:863] in user32.dll.so) (ebp=406b2364) 19 0x407f9daf (DefFrameProcA+0xff(hwnd=0x10025, hwndMDIClient=0x10026, message=0x112, wParam=0xf100, lParam=0x0) [mdi.c:1492] in user32.dll.so) (ebp=406b2388) 20 0x005a1dea (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0xd03c in D:\home\agent\agent.exe) (ebp=406b23a4) 21 0x0059c206 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x7458 in D:\home\agent\agent.exe) (ebp=406b23c4) 22 0x00598556 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x37a8 in D:\home\agent\agent.exe) (ebp=406b241c) 23 0x005985a0 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x37f2 in D:\home\agent\agent.exe) (ebp=406b2450) 24 0x0059865f (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x38b1 in D:\home\agent\agent.exe) (ebp=406b2498) 25 0x005985c8 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x381a in D:\home\agent\agent.exe) (ebp=406b24b0) 26 0x408141fb (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=406b24d4) 27 0x4081429f (WINPROC_CallWndProc+0x8f(proc=0x416b1fb8, hwnd=0x10025, msg=0x112, wParam=0xf100, lParam=0x0) [winproc.c:184] in user32.dll.so) (ebp=406b2504) 28 0x4081a246 (WINPROC_CallProc32WTo32A+0xc6(func=0x416b1fb8, hwnd=0x10025, msg=0x112, wParam=0xf100, lParam=0x0) [winproc.c:2676] in user32.dll.so) (ebp=406b2530) 29 0x4081a7c8 (CallWindowProcW+0x88(func=0x413b0856, hwnd=0x10025, msg=0x112, wParam=0xf100, lParam=0x0) [winproc.c:2890] in user32.dll.so) (ebp=406b2558) 30 0x4082dc00 (call_window_proc+0xd0(hwnd=0x10025, msg=0x112, wparam=0xf100, lparam=0x0, unicode=0x1, same_thread=0x1) [message.c:1401] in user32.dll.so) (ebp=406b25a8) 31 0x4082e85f (SendMessageTimeoutW+0xdf(hwnd=0x10025, msg=0x112, wparam=0xf100, lparam=0x0, flags=0x0, timeout=0xffffffff, res_ptr=0x406b2630) [message.c:1791] in user32.dll.so) (ebp=406b2600) 32 0x4082eae9 (SendMessageW+0x39(hwnd=0x10025, msg=0x112, wparam=0xf100, lparam=0x0) [message.c:1873] in user32.dll.so) (ebp=406b2634) 33 0x407f0c03 (DEFWND_DefWinProc+0x863(hwnd=0x1003e, msg=0x105, wParam=0x12, lParam=0xc0380001) [defwnd.c:571] in user32.dll.so) (ebp=406b26c8) 34 0x407f1517 (DefWindowProcA+0x3a7(hwnd=0x1003e, msg=0x105, wParam=0x12, lParam=0xc0380001) [defwnd.c:863] in user32.dll.so) (ebp=406b26fc) 35 0x408141fb (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=406b2720) 36 0x4081429f (WINPROC_CallWndProc+0x8f(proc=0x407f1170, hwnd=0x1003e, msg=0x105, wParam=0x12, lParam=0xc0380001) [winproc.c:184] in user32.dll.so) (ebp=406b2750) 37 0x4081a69b (CallWindowProcA+0x3b(func=0x407f1170, hwnd=0x1003e, msg=0x105, wParam=0x12, lParam=0xc0380001) [winproc.c:2839] in user32.dll.so) (ebp=406b2778) 38 0x005982ed (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x353f in D:\home\agent\agent.exe) (ebp=406b279c) 39 0x00598556 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x37a8 in D:\home\agent\agent.exe) (ebp=406b27f4) 40 0x005985a0 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x37f2 in D:\home\agent\agent.exe) (ebp=406b2828) 41 0x0059865f (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x38b1 in D:\home\agent\agent.exe) (ebp=406b2870) 42 0x005985c8 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x381a in D:\home\agent\agent.exe) (ebp=406b2888) 43 0x408141fb (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=406b28ac) 44 0x4081429f (WINPROC_CallWndProc+0x8f(proc=0x41998408, hwnd=0x1003e, msg=0x105, wParam=0x12, lParam=0xc0380001) [winproc.c:184] in user32.dll.so) (ebp=406b28dc) 45 0x4081a6e8 (CallWindowProcA+0x88(func=0x413b0db8, hwnd=0x1003e, msg=0x105, wParam=0x12, lParam=0xc0380001) [winproc.c:2854] in user32.dll.so) (ebp=406b2904) 46 0x407fc1da (DispatchMessageA+0x12a(msg=0x406b2980) [message.c:794] in user32.dll.so) (ebp=406b2948) 47 0x004db200 (agent.exe.(a)PropdlgKbdProc$qiuil+0x26708 in D:\home\agent\agent.exe) (ebp=406b299c) 48 0x004db4c3 (agent.exe.(a)PropdlgKbdProc$qiuil+0x269cb in D:\home\agent\agent.exe) (ebp=406b29ec) 49 0x004dadbb (agent.exe.(a)PropdlgKbdProc$qiuil+0x262c3 in D:\home\agent\agent.exe) (ebp=406b2a54) 50 0x0040fd3b (agent.exe.__GetExceptDLLinfo+0xeccd in D:\home\agent\agent.exe) (ebp=406b2e18) 51 0x005a54d4 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x10726 in D:\home\agent\agent.exe) (ebp=406b2e5c) 52 0x005b40b5 (agent.exe.(a)InitWndProc$qp6HWND__uiuil+0x1f307 in D:\home\agent\agent.exe) (ebp=406b2e8c) Register dump: CS:0023 SS:002b DS:002b ES:002b FS:008f GS:005f EIP:005b507b ESP:406b1cb4 EBP:406b1cd8 EFLAGS:00210206( R- 00 I - -P1 ) EAX:2d746e65 EBX:4199cacc ECX:4199c268 EDX:406b1d48 ESI:00000000 EDI:4199cac8 -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)

2 11

Problem with compobj.dll.COSETSTATE
by Peter Barth May 28, 2003

May 28, 2003

Hi, I try to run a French-learning software called Decouvertes. Multiple problems I have, hopefully sombodey answers and can help: o as a starting point I used the ODBC dlls delivered by the program, The DB stuff works, but I would like to know, how to implement the wine-builtin ODBC support and which driver this would be then o once the program comes up, it generates a Win16Mutex timed out - message. After a while it allows input and runs quiet good as it seems o issueing an other task - dictionary - leedss to an exception related to: unimplemented function compobj.dll.COSETSTATE called in32-bit mode in ole32.dll.so There is a OLE2.DLL deliverd with the program, which has such a function built in. Question is, as a newbie to wine, how to tell wine, not to use ole32.dll.so builtin but ole2.dll native. Rename ole32.dll.so, reconfigure and recompile? I would need assistance badly, probably somebody had a similar problem before. The purpose for this is, that we try to establish Solaris based system at a school environment whithout involving Win2k/Citrix on a seperate Application-Server. It would help tremendously if somebody becomes involved with this. Thank you very much best regards Peter Barth

2 1

little WWN problem
by Dimitrie O. Paun May 28, 2003

May 28, 2003

Hi folks, How come "The top 5 posters of the week" are almost always screwed up: 1. 28 posts in 68K by Alexandre Julliard 2. 35 posts in 89K by Dimitrie O. Paun 3. 18 posts in 41K by Gerhard W. Gruber 4. 11 posts in 91K by Mike Hearn 5. 1 posts in 3K by Shachar Shemesh -- Dimi.

6 7

cvs.diff
by Tom May 28, 2003

May 28, 2003

Then use decent tools => upgrade CVS. Well in my simple point of view I am ! I went and got the latest update for RH 7.3 from : http://www.rpmfind.net//linux/RPM/redhat/updates/7.3/i386/cvs-1.11.1p1-8.7.… I also just looked and RH *9* use's 1.11.2-10 here is the link : http://www.rpmfind.net//linux/RPM/redhat/9/i386/cvs-1.11.2-10.i386.html So im not sure Dimi's suggestion about 1.11.5 will work.........As 1.11.5 is in RH RawHide .. And no one who cares about a stable Box is going to use RawHide Warez.......... http://www.rpmfind.net//linux/RPM/rawhide/1.0/i386/RedHat/RPMS/cvs-1.11.5-1… I say go with -z 0 and let it be !!!!!!!! This also helps on the WineHQ sever on over head. Right ? And as ive said before anyone who has ever used cvs before can still compress to there hearts content.. Tom

2 1

Re: msdos/int21 CREAT special cases
by Andreas Mohr May 28, 2003

May 28, 2003

On Mon, May 26, 2003 at 01:04:49PM +0200, Ferenc Wagner wrote: > Volume label creation should fail, not create a regular file. > Similarly for file names ending in a slash (this is actually > needed for PKSFX Version 2.04g to unpack directory trees). > > Feri. > > Index: msdos/int21.c > =================================================================== > RCS file: /home/wine/wine/msdos/int21.c,v > retrieving revision 1.93 > diff -u -r1.93 int21.c > --- msdos/int21.c 19 May 2003 21:40:05 -0000 1.93 > +++ msdos/int21.c 26 May 2003 10:48:21 -0000 > @@ -474,8 +474,18 @@ > } > static BOOL INT21_CreateFile( CONTEXT86 *context ) > { > - SET_AX( context, _lcreat16( CTX_SEG_OFF_TO_LIN(context, context->SegDs, > - context->Edx ), CX_reg(context) ) ); > + LPCSTR path=CTX_SEG_OFF_TO_LIN(context, context->SegDs, context->Edx); > + > + if (CX_reg(context) == 0x0008) { > + SetLastError( ERROR_ACCESS_DENIED ); > + return TRUE; > + } > + if (path[strlen(path)-1] == '/') > + { > + SetLastError( ERROR_FILE_NOT_FOUND ); > + return TRUE; > + } > + SET_AX( context, _lcreat16( path, CX_reg(context) ) ); > return (AX_reg(context) == (WORD)HFILE_ERROR16); > } Hmm, and is there a reason to not do it in _lcreat16() instead? Or is _lcreat16() really "clever" enough to handle volume labels "properly" if called directly? Somehow I doubt it... ;) Or in fact you could walk further up the chain and maybe find that even _lcreat() should be the function to have that check instead... (or, for that matter, even CreateFileA and thus CreateFileW...) So my rough guess is that this should probably be prevented in CreateFileW instead even. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://mohr.de.tt

2 1