August 2002 - Wine-Devel - list.winehq.org

rpcrt / epmapper / scm

by juergen.schmied＠debitel.net

Hi! Some time ago I did send the rpcrt patches from ove ported to the cvs. It didn't got included. Are there any special reasons? The epmapper was implemented in the wineserver. Should it be a standalone server? 1) If it would be a win32 process we would need 2 context changes for every call. If it would be a server like the wine-server there would only be 1 context change per call. 2) What IPC should we use locally? We could implement LPC like reactos. 3) We need a process for managing services and COM out-of-process servers (the SCM). Any ideas how to do this? To many questions for one mail? ;-) juergen

Aug. 2, 2002

Wine Debugger

by Narayan Pavgi

Hello all, I going through the msc.c file of the wine(20020710)-debugger (which interprets PDB and COFF); but I could not figure out if it is able to obtain local-variables from the PDB file. Does it? Fisbo __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com

Aug. 2, 2002

Re: [breakage] Set the correct permissions on the PE image sections.

by Uwe Bonnes

>>>>> "Eric" == Eric Pouech <eric.pouech(a)wanadoo.fr> writes: >> Info segments doesn't tell about a range including 0x00467390, info >> maps tells about VirtualQueryEx Unsupported . Eric> there's a hacky implemntation for VQEx floating around... if you Eric> need it grab it from: Eric> http://www.winehq.com/hypermail/wine-devel/2002/07/0235.html What is so "hacky" about this patch? -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Aug. 2, 2002

Re: [breakage] Set the correct permissions on the PE image sections.

by Uwe Bonnes

>>>>> "Alexandre" == Alexandre Julliard <julliard(a)winehq.com> writes: Alexandre> Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: >> PROPSHEET_CreatePage writes to ppshpage->u.pResource when >> PSP_DLGINDIRECT is set. MSDN also tells that applications will break >> if pResource is not writable. It seems that above patch maps the >> resource section write protected. Alexandre> Actually it should be read-only, and the default exception Alexandre> handler is supposed to unprotect it to hide bugs in broken Alexandre> apps. But writing to resources is a bug in any case, and that Alexandre> propsheet code needs to be fixed. In fact there's already a Alexandre> hack in there to avoid the same issue with builtin resources; Alexandre> I guess it's really time to fix it properly. Yes, I forget to note that it works with (NT) native commctrl and so the protection seems right... Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Aug. 2, 2002

Re: AutoCAD2000 again and CreateFiber

by Matts

Hi! Does this mean that AutoCad 2000 works good in wine, if I set window version to win95 (which I dont see a problem with right now)? Regards Matts >Well, after the patch-hack-or whatever on VirtualQuery, AutoCAD2000 >began >coming alive ! Some problems yet, but one wonders me in particular : >setting window version as win98 or winnt40, app shows an exception >stating >that CreateFiber function is not implemented; setting as win95 the apps >starts quite well. >Any idea ? Is there some plan to implement xxxxxFiber functions, or >it's too >difficult ? >BTW, looking for help on the net, i haven't really understood the >difference >between a regular thread and a fiber (only caught that use of fibers >instead >of threads is somehow discouraged...) >Regards >Max _____________________________________________________________ Want a new web-based email account ? ---> http://www.firstlinux.net _____________________________________________________________ Promote your group and strengthen ties to your members with email(a)yourgroup.org by Everyone.net http://www.everyone.net/?btn=tag

Aug. 2, 2002

problem with destroy window

by Juergen Schmied

Looks like a window what is in destruction gets the focus from WINPOS_ActivateOtherWindow and don't like it... juergen 08073ff8:Call user32.DestroyWindow(00010022) ret=5d34c141 trace:win:DestroyWindow (10022) 08073ff8:Call x11drv.ResetSelectionOwner(00010022,00000000) ret=4069f640 08073ff8:Ret x11drv.ResetSelectionOwner() retval=02800003 ret=4069f640 08073ff8:Call x11drv.ShowWindow(00010022,00000000) ret=406a4127 08073ff8:Ret x11drv.ShowWindow() retval=00000000 ret=406a4127 trace:win:DestroyWindow (10024) 08073ff8:Call x11drv.ResetSelectionOwner(00010024,00000000) ret=4069f640 08073ff8:Ret x11drv.ResetSelectionOwner() retval=02800007 ret=4069f640 08073ff8:Call x11drv.ShowWindow(00010024,00000000) ret=406a4127 08073ff8:Ret x11drv.ShowWindow() retval=00000000 ret=406a4127 trace:win:WINPOS_SetActiveWindow (10022, 0, 1) trace:win:WINPOS_SetActiveWindow no current active window. 08073ff8:Call window proc 0x5d34c6f6 (hwnd=00010022,msg=WM_QUERYNEWPALETTE,wp=00000000,lp=00000000) 08073ff8:Call user32.GetWindow(00010025,00000005) ret=5d30c073 08073ff8:Ret user32.GetWindow() retval=00000000 ret=5d30c073 08073ff8:Call user32.SendMessageA(00010025,0000030f,00000000,00000000) ret=5d30c0be 08073ff8:Call window proc 0x5d34dfc9 (hwnd=00010025,msg=WM_QUERYNEWPALETTE,wp=00000000,lp=00000000) 08073ff8:Call user32.DefWindowProcW(00010025,0000030f,00000000,00000000) ret=5d34e274 08073ff8:Ret user32.DefWindowProcW() retval=00000000 ret=5d34e274 08073ff8:Ret window proc 0x5d34dfc9 (hwnd=00010025,msg=WM_QUERYNEWPALETTE,wp=00000000,lp=00000000) retval=00000000 08073ff8:Ret user32.SendMessageA() retval=00000000 ret=5d30c0be 08073ff8:Call user32.DefWindowProcA(00010022,0000030f,00000000,00000000) ret=5d34c99a 08073ff8:Ret user32.DefWindowProcA() retval=00000000 ret=5d34c99a 08073ff8:Ret window proc 0x5d34c6f6 (hwnd=00010022,msg=WM_QUERYNEWPALETTE,wp=00000000,lp=00000000) retval=00000000 08073ff8:Call window proc 0x42f35c40 (hwnd=00010024,msg=WM_ACTIVATEAPP,wp=00000001,lp=00000000) 08073ff8:Call user32.GetWindowLongA(00010024,00000000) ret=42f35c91 08073ff8:Ret user32.GetWindowLongA() retval=42ff0408 ret=42f35c91 08073ff8:Call user32.DefWindowProcA(00010024,0000001c,00000001,00000000) ret=42f36426 08073ff8:Ret user32.DefWindowProcA() retval=00000000 ret=42f36426 08073ff8:Ret window proc 0x42f35c40 (hwnd=00010024,msg=WM_ACTIVATEAPP,wp=00000001,lp=00000000) retval=00000000 08073ff8:Call window proc 0x5d34c6f6 (hwnd=00010022,msg=WM_ACTIVATEAPP,wp=00000001,lp=00000000) 08073ff8:Call user32.DefWindowProcA(00010022,0000001c,00000001,00000000) ret=5d34c99a 08073ff8:Ret user32.DefWindowProcA() retval=00000000 ret=5d34c99a 08073ff8:Ret window proc 0x5d34c6f6 (hwnd=00010022,msg=WM_ACTIVATEAPP,wp=00000001,lp=00000000) retval=00000000 08073ff8:Call window proc 0x77a67048 (hwnd=00010021,msg=WM_ACTIVATEAPP,wp=00000001,lp=00000000) 08073ff8:Call user32.DefWindowProcW(00010021,0000001c,00000001,00000000) ret=77a67087 08073ff8:Ret user32.DefWindowProcW() retval=00000000 ret=77a67087 08073ff8:Ret window proc 0x77a67048 (hwnd=00010021,msg=WM_ACTIVATEAPP,wp=00000001,lp=00000000) retval=00000000 08073ff8:Call window proc 0x5d34c6f6 (hwnd=00010022,msg=WM_NCACTIVATE,wp=00000001,lp=00000000) 08073ff8:Call user32.DefWindowProcA(00010022,00000086,00000001,00000000) ret=5d34c99a 08073ff8:Ret user32.DefWindowProcA() retval=00000001 ret=5d34c99a 08073ff8:Ret window proc 0x5d34c6f6 (hwnd=00010022,msg=WM_NCACTIVATE,wp=00000001,lp=00000000) retval=00000001 08073ff8:Call window proc 0x5d34c6f6 (hwnd=00010022,msg=WM_ACTIVATE,wp=00000001,lp=00000000) 08073ff8:Call kernel32.GetLastError() ret=00402238 08073ff8:Ret kernel32.GetLastError() retval=00000578 ret=00402238 08073ff8:Call kernel32.TlsGetValue(00000000) ret=00402246 08073ff8:Ret kernel32.TlsGetValue() retval=429e0100 ret=00402246 08073ff8:Call kernel32.SetLastError(00000578) ret=0040229a 08073ff8:Ret kernel32.SetLastError() retval=00000578 ret=0040229a 08073ff8:Call kernel32.UnhandledExceptionFilter(40464900) ret=0040172a =>0 0x5d30bf01 (HHCTRL.OCX..text+0xaf01 in C:\WINNT\SYSTEM32\HHCTRL.OCX) (ebp=40575064) 1 0x5d34c7b2 (HHCTRL.OCX.DllGetClassObject+0x22159 in C:\WINNT\SYSTEM32\HHCTRL.OCX) (ebp=405760fc) 2 0x406a54db (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=40576120) 3 0x406a557e (WINPROC_CallWndProc+0x8e(proc=0x5d34c6f6, hwnd=0x10022, msg=0x6, wParam=0x1, lParam=0x0) [winproc.c:183] in user32.dll.so) (ebp=40576150) 4 0x406ab84b (CallWindowProcA+0x3b(func=0x5d34c6f6, hwnd=0x10022, msg=0x6, wParam=0x1, lParam=0x0) [winproc.c:2779] in user32.dll.so) (ebp=40576178) 5 0x406bb830 (call_window_proc+0x100(hwnd=0x10022, msg=0x6, wparam=0x1, lparam=0x0, unicode=0x0) [message.c:1372] in user32.dll.so) (ebp=405761c8) 6 0x406bc4f8 (SendMessageTimeoutA+0xe8(hwnd=0x10022, msg=0x6, wparam=0x1, lparam=0x0, flags=0x0, timeout=0xffffffff, res_ptr=0x40576250, hwnd=0x10022) [message.c:1784] in user32.dll.so) (ebp=40576220) 7 0x406bc679 (SendMessageA+0x39(hwnd=0x10022, msg=0x6, wparam=0x1, lparam=0x0) [message.c:1829] in user32.dll.so) (ebp=40576254) 8 0x406a4a96 (WINPOS_SetActiveWindow+0x476(hWnd=0x10022, fMouse=0x0, fChangeFocus=0x1) [winpos.c:1359] in user32.dll.so) (ebp=405762a0) 9 0x406a39c1 (SetActiveWindow+0xd1(hwnd=0x10022) [winpos.c:723] in user32.dll.so) (ebp=405762d0) 10 0x406a4cfd (WINPOS_ActivateOtherWindow+0x13d(hwnd=0x10024) [winpos.c:1463] in user32.dll.so) (ebp=405762f0) 11 0x4069f6f6 (DestroyWindow+0x1f6(hwnd=0x10024) [win.c:1504] in user32.dll.so) (ebp=4057630c) 12 0x4069f6b6 (DestroyWindow+0x1b6(hwnd=0x10022) [win.c:1492] in user32.dll.so) (ebp=40576328) 13 0x5d34c141 (HHCTRL.OCX.DllGetClassObject+0x21ae8 in C:\WINNT\SYSTEM32\HHCTRL.OCX) (ebp=4057690c)

Aug. 2, 2002

Re: [breakage] Set the correct permissions on the PE image sections.

by Eric Pouech

> Info segments doesn't tell about a range including 0x00467390, info maps > tells about VirtualQueryEx Unsupported . there's a hacky implemntation for VQEx floating around... if you need it grab it from: http://www.winehq.com/hypermail/wine-devel/2002/07/0235.html

Aug. 2, 2002

Re: [breakage] Set the correct permissions on the PE image sections.

by Alexandre Julliard

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > PROPSHEET_CreatePage writes to ppshpage->u.pResource when PSP_DLGINDIRECT is > set. MSDN also tells that applications will break if pResource is not > writable. It seems that above patch maps the resource section write > protected. Actually it should be read-only, and the default exception handler is supposed to unprotect it to hide bugs in broken apps. But writing to resources is a bug in any case, and that propsheet code needs to be fixed. In fact there's already a hack in there to avoid the same issue with builtin resources; I guess it's really time to fix it properly. -- Alexandre Julliard julliard(a)winehq.com

Aug. 2, 2002

Re: DTR/DSR vs RTS/CTS - followup

by Raul Dias

Oi Miguel, I had similar problems with serial printers and wine. However, I think it is not related to signaling. The printers are Itautec fiscal printers. Which one are you using? I don't think it is related to signaling because it used to work with wine. Until sometime around 20001026 the printer worked fine. After this there was a major serial recoding in wine which broke the serial support (for the printer at least). I do use wine-20001026 and it works great with the windows driver (printing from a windows application). I put an rpm wine in http://www.dias.com.br/RPMS/wine/wine-20001026-1cl.i386.rpm It is from an old Conectiva Linux, but should be compatible with any distribution. Just make sure no other wine is installed in the system. Can you test this wine version (or build the on from the sources if you wish) ? If it works, then there might be a chance for the wine serial support to get revised :D What I really miss from the current tree is the client side fonts, as the fonts looks really awful in that program with 20001026. Regards, Raul Dias <lists(a)vmn.com.br> wrote: >Hello All, > >Last week I sent an email about a problem with a serial printer that >used DTS/DTR hardware flow control. >I later understood that DTS/DTR was not supported in linux , and >therefore not in wine. Linux [and wine] support RTS/CTS hardware flow control. > >Since the protocols are similar, an ideia that I received was to construct a >cable that made the computer think it was using RTS/CTS and the printer think it >was using DTR/DTS. > >Today, I received the cable from the printer manufacturer and the initial tests >with wine/linux worked. > >**************************** >RTS - Ready To Send >CTS - Clear To Send > >DTR - Data Terminal Ready >DSR - Data Set Ready > >**************************** >Here is a snippet of mytestapp --debugmsg +comm > >trace:comm:COMM_Init COM1 = /dev/ttyS0 >trace:comm:COMM_Init LPT1 = /dev/lp0 >trace:comm:COMM_Init COM2 = /dev/ttyS1 >trace:comm:COMM_Init COM3 = /dev/ttyS2 >trace:comm:COMM_Init COM4 = /dev/modem >trace:comm:BuildCommDCBAndTimeoutsA (COM2:9600,N,8,1,0x4002af48,(nil)) >trace:comm:COMM_BuildOldCommDCB (COM2:9600,N,8,1), ptr 0x4002af48 >trace:comm:COMM_BuildOldCommDCB baudrate (9600) >trace:comm:COMM_BuildOldCommDCB parity (N) >trace:comm:COMM_BuildOldCommDCB charsize (8) >trace:comm:COMM_BuildOldCommDCB stopbits (1) >trace:comm:SetCommState handle 52, ptr 0x4002af48 >trace:comm:SetCommState bytesize 8 baudrate 9600 fParity 0 Parity 0 stopbits 1 >trace:comm:SetCommState ~IXON ~IXOFF >trace:comm:SetCommState CRTSCTS >trace:comm:SetCommMask handle 52, mask 10 > > >Thanks every one from wine-devel for all the prompt answers I received. > >Miguel Feitosa > >------------------------------------------------- >This mail sent through IMP: webmail.vmn.com.br >

Aug. 2, 2002

Re: Compilation error with newer CVS on glibc -2.1.3

by Alexandre Julliard

Martin Cracauer <cracauer(a)cons.org> writes: > The offending _GNU_SOURCE is in here for some time. > 1.18 (julliard 07-Jan-02): #define _GNU_SOURCE /* for pread/pwrite */ > > I think the julliard 22-Jul-02 commits to this file triggered the > error. Yes, I see it now. We should probably avoid _GNU_SOURCE here, but this would be a bit of work. And since we don't really need that struct user at all I have simply removed it. Thanks for looking into this. -- Alexandre Julliard julliard(a)winehq.com

Aug. 2, 2002