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

Re: Wine passes WGA test

by Andreas Mohr

Hi, On Fri, Aug 05, 2005 at 12:18:32PM +0200, Francois Gouget wrote: > On Fri, 5 Aug 2005, Ivan Leo Puoti wrote: > [...] > >Also the anti wine checks appear to be disabled as the tool works in both > >windows 2000 and windows 98 mode, however the wine registry key string is > >still in the binary, maybe it's just disabled. > > IIRC it's checking the location of the old Wine config registry key. > This has all moved as part of the config file removal (and as was > planned long before WPA came around). WGA! ("Windows Genuine Disadvantage", not XP's "Windows Product Activation") > No doubt they will update their WPA checks at some point... Hmm, let's hope they know what to do or not do, also in light of the EU investigation reports, then... Andreas Mohr -- No programming skills!? Why not help translate many Linux applications! https://launchpad.ubuntu.com/rosetta

Aug. 5, 2005

Re: msxml3: protect DOMElement implementation with HAVE_LIBXML2

by Mike McCormack

Michael Jung wrote: > This fixes msxml3 compilation on debian sarge, if libxml2-dev headers are not > installed. I've imitated Mike's scheme from domdoc.c. Thanks for fixing this. > +HRESULT DOMElement_create( IXMLDOMElement** DOMElement, void* xmldoc ) You shouldn't need this stub, because the function will only be used if HAVE_LIBXML2 is defined in domdoc.c Mike

Aug. 5, 2005

Re: Wine passes WGA test

by Francois Gouget

On Fri, 5 Aug 2005, Ivan Leo Puoti wrote: [...] > Also the anti wine checks appear to be disabled as the tool works in both > windows 2000 and windows 98 mode, however the wine registry key string is > still in the binary, maybe it's just disabled. IIRC it's checking the location of the old Wine config registry key. This has all moved as part of the config file removal (and as was planned long before WPA came around). No doubt they will update their WPA checks at some point... -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Dieu dit: "M-x Lumière". Et la lumière fut.

Aug. 5, 2005

Wine passes WGA test

by Ivan Leo Puoti

You can now validate for WGA downloads using wine and the Microsoft WGA validation tool, and you'll get a thank you message from Microsoft for using Microsoft genuine downloads. Also the anti wine checks appear to be disabled as the tool works in both windows 2000 and windows 98 mode, however the wine registry key string is still in the binary, maybe it's just disabled. In any case some EU officials have already expressed an interest in these checks, so if they enable them someone may end up getting another super fine. Ivan.

Aug. 5, 2005

Re: [DSHOW] Beginning of winestrmbase lib (resend)

by Christian Costa

Dimi Paun wrote: >From: "Christian Costa" <titan.costa(a)wanadoo.fr> > > >>Well, I chose this name because the Direct Show SDK provides the >>strmbase.lib library. >>The purpose is quite the same so I kept the same name and prefixed it >>since it's wine specific. >> >> > >But if that's the case, shouldn't we just name it strmbase >and make it compatible? > > > strmbase contains mostly C++ classes...

Aug. 5, 2005

Re: test case demonstrating PeekMessage give up timeslices

by Oliver Mössinger

We changed our program to avoid the needless polling (only two PeekMessage are needet then). We add also the PM_NOYIELD. This gives back the reaction of the program if some other process consumes process time. But the speed is more reduced than windows. Your patch works for our program. It seems it is faster than before. So now our program works, not fine but it works. If you can find a better fix, it would be fine... > Jeremy White <jwhite(a)codeweavers.com> writes: > > However, this makes it clear to me that the yield > > in message.c is largely moot; you need to remove both > > that one and the one in ntdll/sync.c to have > > any material effect on Wine timing with messages. > > Actually it should be enough to not yield in MsgWaitForMultipleObjects > when we are only checking for X events, and that would be correct IMO > since the check for X events is always in addition to the normal > behavior. Something like this should do it: > > Index: dlls/x11drv/event.c > =================================================================== > RCS file: /opt/cvs-commit/wine/dlls/x11drv/event.c,v > retrieving revision 1.56 > diff -u -p -r1.56 event.c > --- dlls/x11drv/event.c 25 Jul 2005 11:08:43 -0000 1.56 > +++ dlls/x11drv/event.c 3 Aug 2005 08:28:52 -0000 > @@ -295,12 +295,13 @@ DWORD X11DRV_MsgWaitForMultipleObjectsEx > > data->process_event_count++; > if (process_events( data->display, mask )) ret = count; > - else > + else if (count || timeout) > { > ret = WaitForMultipleObjectsEx( count+1, new_handles, flags & > MWMO_WAITALL, timeout, flags & MWMO_ALERTABLE ); if (ret == count) > process_events( data->display, mask ); > } > + else ret = WAIT_TIMEOUT; > data->process_event_count--; > return ret; > }

Aug. 5, 2005

Re: [Bug 3148] Mouse: multi-file "selection" & drag behavior broken

by Andreas Mohr

Hi, On Thu, Aug 04, 2005 at 10:23:23PM -0700, Hiji wrote: > Looks like someone else is having this problem. I've > tried looking at listview.c and the treeview > equivalent as well, but I can't made heads or tails of > it. I have no experience with C. > > Anybody on this list make any changes to listview or > treeview in the last few months? I wouldn't even find it hard to believe that they already forgot about it... If you want hard, definitive data, then I I cannot find any reason why you wouldn't want to look at ChangeLog... Andreas Mohr

Aug. 5, 2005

winedebug/gdb crashes

by Simon Kissane

Hi Using latest wine CVS (checked out today), trying to debug the PackageForTheWeb self-extracting EXE that MS uses to distribute MSDE 2000.... The EXE works fine (albeit with some visual bugs) when running under plain wine instead of winedebug.... Anyone have any idea what might be wrong? (I am very new to wine, although I've been following the wine-devel archives for a while...) Cheers Simon Kissane ===== winedebug window ====== > winedbg --gdb --no-start z:/home/skissane/downloads/MSDE2000A.exe 0000001b:0000001c: create process 'Z:\home\skissane\downloads\MSDE2000A.exe'/0x7fff003c @0040ce00 (0<0>) 0000001b:0000001c: create thread I @0040ce00 target remote localhost:32815 0000001b:0000001c: loads DLL c:\windows\system\ntdll.dll @00840000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\kernel32.dll @00e50000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\advapi32.dll @00770000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\gdi32.dll @00370000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\user32.dll @00270000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\comctl32.dll @00430000 (0<0>) fixme:dbghelp:elf_new_wine_thunks Duplicate in comctl32<elf>: refDataPropName<004b4d60-00000020> subclasses<4b4d60-00000000> 0000001b:0000001c: loads DLL c:\windows\system\iphlpapi.dll @00b00000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\rpcrt4.dll @004e0000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\ole32.dll @006b0000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\shlwapi.dll @00d90000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\shell32.dll @00550000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\lz32.dll @003e0000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\winex11.drv @00ca0000 (0<0>) 0000001b:0000001c: loads DLL c:\windows\system\imm32.dll @00710000 (0<0>) 0000001b:0000001c: exception code=0x80000003 wine-pthread: gdbproxy.c:1984: extract_packets: Assertion `i == gdbctx->out_len' failed. wine: Unhandled exception (thread 001d), starting debugger... WineDbg starting on pid 0x1e Unhandled exception: assertion failed in 32-bit code (0x595a97e2). In 32 bit mode. Register dump: CS:0073 SS:007b DS:007b ES:007b FS:1007 GS:0033 EIP:595a97e2 ESP:7fcbf38c EBP:7fcbf3a0 EFLAGS:00000202( - 00 - - I1) EAX:00000000 EBX:00004e8c ECX:00004e8c EDX:00000006 ESI:00000000 EDI:2014fff4 Stack dump: 0x7fcbf38c: 200521f8 00004e8c 2014fff4 00000000 0x7fcbf39c: b7efe9e0 7fcbf4cc 20053948 00000006 0x7fcbf3ac: 7fcbf440 00000000 00000060 7d00bf80 0x7fcbf3bc: 00000068 00000000 2008bae7 7fcbf404 0x7fcbf3cc: 7d00bf88 7d00bfec 7fcbf4dc 2014fff4 0x7fcbf3dc: 00000059 0000005a 7fcbf4b0 20086515 0200: sel=1007 base=b7f04000 limit=00001f97 32-bit rw- Backtrace: =>1 0x595a97e2 (0x7fcbf3a0) 2 0x20053948 (0x7fcbf4cc) 3 0x2004b38e (0x7fcbf510) 4 0x75ff7e2f gdb_remote+0xaab(flags=0x1) [/home/skissane/osdevel/wine/programs/winedbg/gdbproxy.c:1981] in winedbg (0x7fcbfddc) 5 0x76002b9b main+0x473(argc=0x2, argv=0x7fee04a8) [/home/skissane/osdevel/wine/programs/winedbg/winedbg.c:1285] in winedbg (0x7fcbfeac) 6 0x75fef26f __wine_exe_main+0x176 in winedbg (0x7fcbff2c) 7 0x4bdbe9e2 start_process+0xb6(arg=0x0) [/home/skissane/osdevel/wine/dlls/kernel/process.c:996] in kernel32 (0x7fcbfff4) 8 0x20004935 wine_switch_to_stack+0x11 in libwine.so.1 (0x00000000) 0x595a97e2: ret Modules: Module Address Debug info Name (21 modules) ELF 0x0051b000-00537000 Deferred ld-linux.so.2 ELF 0x00539000-00663000 Deferred libc.so.6 ELF 0x00665000-00669000 Deferred libdl.so.2 ELF 0x0066b000-0068f000 Deferred libm.so.6 ELF 0x00a05000-00a17000 Deferred libpthread.so.0 ELF 0x20000000-20018000 DIA libwine.so.1 ELF 0x20154000-201c6000 Deferred ntdll<elf> \-PE 0x20170000-201c6000 \ ntdll ELF 0x201ea000-201f5000 Deferred libnss_files.so.2 ELF 0x201f5000-2020b000 Deferred psapi<elf> \-PE 0x20200000-2020b000 \ psapi ELF 0x39fc3000-39fff000 Deferred advapi32<elf> \-PE 0x39fd0000-39fff000 \ advapi32 ELF 0x45dc6000-45e01000 Deferred dbghelp<elf> \-PE 0x45dd0000-45e01000 \ dbghelp ELF 0x4bd54000-4be4f000 Stabs kernel32<elf> \-PE 0x4bd80000-4be4f000 \ kernel32 ELF 0x6be33000-6bf28000 Deferred libwine_unicode.so.1 ELF 0x75fd7000-76019000 Stabs winedbg<elf> \-PE 0x75fe0000-76019000 \ winedbg ELF 0x7bf00000-7bf03000 Deferred <wine-loader> Threads: process tid prio (all id:s are in hex) 0000001b 0000001c 0 0000001e (D) c:\windows\system\winedbg.exe 0000001d 0 <== 0000000e 0000000f 0 0000000a 0000000b 0 WineDbg terminated on pid 0x1e ===== gdb window ====== > gdb GNU gdb Red Hat Linux (6.3.0.0-1.21rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu". (gdb) target remote localhost:32815 Remote debugging using localhost:32815 Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Couldn't establish connection to remote target Malformed response to offset query, timeout (gdb)

Aug. 5, 2005

Re: Patch to fix GetCommState "Invalid Argument" errors with Linux usbserial devices

by James Liggett

On Fri, 2005-08-05 at 14:28 +0900, Mike McCormack wrote: > James Liggett wrote: > > > This patch fixes an "Invalid Argument" error in GetCommState when a > > program tries to get information about a usbserial device. With this > > patch, Wine provides a "fake" serial device control block to a Windows > > program requesting it, such that the program believes that it's > > interfacing with an actual serial port, since usbserial devices don't > > currently acknowledge traditional DCBs via tcgetattr/tcsetattr. Using > > this patch I was able to synchronize a serial-based Palm PDA with Palm > > Desktop on Wine with a pl2303 USB-serial converter. I'm also told that > > this patch also works with FTDI devices. > > Hi James, > > I don't think this is quite right. The pl2303 is a standard USB-serial > converter, and it should have a selectable baud rate (according to the > Linux kernel's driver for it). It has a db-9 connector on one end, and > a usb connector on the other, right? Yes, that's right. And yes, pl2303 does have mechanisms to set DCB info. However, AFAIK there's no way to set this information from userspace. Greg Kroah-Hartman told me that the usbserial drivers must be modified to work with tcgetattr/tcsetattr. pl2303 doesn't acknowledge any ioctl that would allow this to be set either. Honestly, I wasn't sure this was 100% correct either, but it does work. If you have a better way of doing this, please let me know. ;-) > > I'm also pretty sure that all serial ports are ttys in Linux, so your > if(isatty()) check will always succeed. Sure, it probably would. I did this only to be safe. pilot-link and many others do it, so I thought I would do it too to be thorough. And besides, what if the comm symlink we were looking at wasn't a tty, but some other kind of device? (user setup error) In that case the comm functions would go crazy without any kind of sanity checking on the given port node. > > Have you tried writing a small test program that does GetCommState and > SetCommState on that serial device in Windows? If it fails to set the > baud rate perhaps there's an error code returned? I didn't write my own program, but I know that Windows programs don't have a problem with this device. I did quite a bit of testing of Palm Desktop on both Windows and WINE, and Hotsync worked well with this device on windows, so I know we're not getting an error here. I think the problem I'm trying to solve here is related to usbserial drivers specifically. Why exactly this is I really can't say. Thanks for the feedback. :) > > Mike > James

Aug. 5, 2005

Re: Patch to fix GetCommState "Invalid Argument" errors with Linux usbserial devices

by Mike McCormack

James Liggett wrote: > This patch fixes an "Invalid Argument" error in GetCommState when a > program tries to get information about a usbserial device. With this > patch, Wine provides a "fake" serial device control block to a Windows > program requesting it, such that the program believes that it's > interfacing with an actual serial port, since usbserial devices don't > currently acknowledge traditional DCBs via tcgetattr/tcsetattr. Using > this patch I was able to synchronize a serial-based Palm PDA with Palm > Desktop on Wine with a pl2303 USB-serial converter. I'm also told that > this patch also works with FTDI devices. Hi James, I don't think this is quite right. The pl2303 is a standard USB-serial converter, and it should have a selectable baud rate (according to the Linux kernel's driver for it). It has a db-9 connector on one end, and a usb connector on the other, right? I'm also pretty sure that all serial ports are ttys in Linux, so your if(isatty()) check will always succeed. Have you tried writing a small test program that does GetCommState and SetCommState on that serial device in Windows? If it fails to set the baud rate perhaps there's an error code returned? Mike

Aug. 5, 2005