September 2006 - Wine-Devel

Note and patch about strange UDP packets
by Florian Echtler Sept. 15, 2006

Sept. 15, 2006

Hi everybody, we are using a certain tracking software from Advanced Realtime Tracking. This is a windows software, but we decided yesterday that it would be more flexible to be able to use it under Linux, too, so I gave it a try with Wine. As this software communicates with customized (expensive) cameras via UDP, I noted a strange bug in the Wine debug channel "winsock": the software was sending UDP packets to IP _254_.255.255.255 (note the first octet). After some experimentation, I noticed that while Windows just sends this as a broadcast packet, Linux rejects this address, because the corresponding RFC states that the network 240.0.0.0/4 is reserved and should not be used. I therefore build a small patch which checks for these strange adresses and replaces them by broadcast adresses. This enabled our software to work. However, the question now is whether it makes sense to include this patch into Wine? On the one hand, it increases the similarity between Wine's behaviour and Windows's, OTOH it decreases Wine's RFC compliance.. Comments? Thanks, Yours, Florian

2 1

Re: [PATCH] PATCH: kernel 2.6 in README.de
by n0dalus Sept. 15, 2006

Sept. 15, 2006

On Wed Sep 13 10:57:33 2006 +0200, Marcus Meissner <marcus(a)beiboot.franken.de> wrote: > Mention kernel 2.6. > > --- > > documentation/README.de | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > 10857c3dbb8429ea599288ac93f4cecd8ffeff59 > diff --git a/documentation/README.de b/documentation/README.de > index c4a1324..680e077 100644 > --- a/documentation/README.de > +++ b/documentation/README.de > @@ -45,7 +45,7 @@ Linux-Info: > Obwohl Linux 2.2.x immer noch funktionieren sollte und Linux 2.0.x > vielleicht auch noch funktioniert (ältere 2.0.x-Versionen verzeichneten > Abstürze im Zusammenhang mit Threads), sollte man am besten einen > - aktuellen Kernel wie 2.4.x verwenden. > + aktuellen Kernel wie 2.4.x oder 2.6.x verwenden. > > FreeBSD-Info: > Stellen Sie sicher, dass Sie die Optionen USER_LDT, SYSVSHM, SYSVSEM und > -- > 1.2.4 > > > Hi, A few of the emails you've sent to the wine-patches mailing list lately have not had 'To:' headers. Many people have their mail clients configured to filter emails into folders based on 'To:' fields, so it would be great if you could sort that out (your last few ones, such as this one, ended up in my inbox instead of my wine folder). It probably means that whatever program you are using to send these emails is broken slightly. I hope you are able to work it out, n0dalus.

5 5

Troubles using current wine (wine-0.9.21)
by Louis. Lenders Sept. 15, 2006

Sept. 15, 2006

Hi, i'm having lots of troubles running games with current git. First of all i get these messages running every application i try: "err:wgl:has_opengl glx_version as 1.3 and GLX_SGIX_fbconfig extension is unsupported. Expect problems." Is it really that bad to not have glx_version 1.3? I have Ati radeon 9600 and i do not know if this is supported on my card anyway. Further, games that used to work now crash, for example Serious Sam I. The problem seems to be: 000f:Call gdi32.ChoosePixelFormat(000004f0,0033fc38) ret=004c70b9 000f:Call winex11.drv.ChoosePixelFormat(001aab78,0033fc38) ret=605c1358 trace:seh:raise_exception code=c0000005 flags=0 addr=(nil) --> crash Any hints on this? --------------------------------- Try the all-new Yahoo! Mail . "The New Version is radically easier to use" The Wall Street Journal

4 3

Re: advapi32, msi, rsaenh: MD4_CTX and MD5_CTX have the same elements, declare them in the same order.
by Hans Leidekker Sept. 15, 2006

Sept. 15, 2006

On Thursday 14 September 2006 11:13, Kai Blin wrote: > MD4_CTX and MD5_CTX have the same elements, declare them in the same order. Tell Microsoft about it ;-) Your patch breaks the md5 test on Windows because it depends on the struct layout: crypt_md5.c:90: Test failed: invalid initialization crypt_md5.c:93: Test failed: update doesn't work correctly crypt_md5.c:96: Test failed: update doesn't work correctly crypt_md5: 5 tests executed, 0 marked as todo, 3 failures. -Hans

3 5

rpcrt4 questions
by Damjan Jovanovic Sept. 15, 2006

Sept. 15, 2006

1. I was surprised to discover DCE RPCs (as opposed to DCOM) from wine to Windows do work. Is this documented anywhere? 2. Is there any reason why rpc_transport.c uses native sockets instead of winsock? 3. Would a patch to fix (2) be welcome? With a few more changes, it would also allow an RPC server to run on wine, as opposed to the current case where only clients work. Thank you Damjan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: wine 0.9.21 - World of warcraft appears to be broken on ATI hardware ? crashes with Blizzard critical error
by Nick Law Sept. 15, 2006

Sept. 15, 2006

Vitaliy Margolen wrote: > Nick Law wrote: > >> I'm having the same problems with 0.9.21 here, World of Warcraft is >> broken, no longer runs at all on ATI hardware, (confirmed on two >> separate systems running with ATO 9550. (maybe ok on Nvidia hardware >> although not tried it myself). >> >> > Nick please open a bug in bugzilla, and do proper regression testing. > > Vitaliy. > > ok, I'll see what I can do over the next few days. Nick

1 0

Re: TRY 2: Socket resets randomly
by Vitaliy Margolen Sept. 15, 2006

Sept. 15, 2006

Ryan Miller wrote: > ws2_32: Fixed bug with sockets randomly resetting due to GetLastError being > reset by setsockopt in Windows, but not in Wine. Also included is the > associated test. > > + SetLastError(1); Please use more accepted value of 0xdeadbeef Vitaliy

1 0

wine 0.9.21 - World of warcraft appears to be broken on ATI hardware ? crashes with Blizzard critical error
by Nick Law Sept. 14, 2006

Sept. 14, 2006

I'm having the same problems with 0.9.21 here, World of Warcraft is broken, no longer runs at all on ATI hardware, (confirmed on two separate systems running with ATO 9550. (maybe ok on Nvidia hardware although not tried it myself). Upon trying to start WoW, a Blizzard dialog box appears which contains the following ( see my post http://appdb.winehq.org/appview.php?iVersionId=5606) Here's a summary World of WarCraft (build 5595) Exe: C:\Program Files\World of Warcraft\WoW.exe Time: Sep 14, 2006 10:58:59.684 PM User: guest Computer: linux ------------------------------------------------------------------------------ This application has encountered a critical error: ERROR #132 (0x85100084) Fatal Exception Program: C:\Program Files\World of Warcraft\WoW.exe Exception: 0xC0000005 (ACCESS_VIOLATION) at 0073:00000000 The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read". WoWBuild: 5595 ------------------------------------------------------------------------------ ---------------------------------------- x86 Registers ---------------------------------------- EAX=7C093970 EBX=6103A374 ECX=00000003 EDX=610323CE ESI=00000000 EDI=7C340D00 EBP=0034FAF8 ESP=0034FA9C EIP=00000000 FLG=00210297 CS =0073 DS =007B ES =007B SS =007B FS =003B GS =0033 ---------------------------------------- Stack Trace (Manual) ---------------------------------------- Address Frame Logical addr Module 00000000 0034FAF8 0000:00000000 C:\Program Files\World of Warcraft\WoW.exe 61009DC0 0034FB58 0001:00038DC0 c:\windows\system\winex11.drv 6070C1FF 0034FB88 0001:0003B1FF c:\windows\system\gdi32.dll 0058C0DB 0034FC14 0001:0018B0DB C:\Program Files\World of Warcraft\WoW.exe 0058BF2C 0034FC24 0001:0018AF2C C:\Program Files\World of Warcraft\WoW.exe 0058CAA6 0034FC74 0001:0018BAA6 C:\Program Files\World of Warcraft\WoW.exe 00591B75 0034FC80 0001:00190B75 C:\Program Files\World of Warcraft\WoW.exe 0058C801 0034FCA0 0001:0018B801 C:\Program Files\World of Warcraft\WoW.exe 005896D7 0034FCB4 0001:001886D7 C:\Program Files\World of Warcraft\WoW.exe 00639E73 0034FD20 0001:00238E73 C:\Program Files\World of Warcraft\WoW.exe 004027EC 0034FE68 0001:000017EC C:\Program Files\World of Warcraft\WoW.exe 004021E0 0034FE78 0001:000011E0 C:\Program Files\World of Warcraft\WoW.exe 0040410E 0034FF08 0001:0000310E C:\Program Files\World of Warcraft\WoW.exe 603A6B81 0034FFE8 0001:00055B81 c:\windows\system\kernel32.dll ---------------------------------------- Stack Trace (Using DBGHELP.DLL) ---------------------------------------- 61009DC0 winex11.drv X11DRV_DescribePixelFormat+448 (0x001A9110,0x00000001,0x00000028,0x0034FBDC) (opengl.c,1004) 6070C1FF gdi32.dll DescribePixelFormat+175 (0x0000032C,0x00000001,0x00000028,0x0034FBDC) (painting.c,424) 0058C0DB WoW.exe +0 (0x0034FC74,0x00000000,0x0034FC74,0x0058CAA6) 0058BF2C WoW.exe +0 (0x0034FC3C,0x000002E4,0x011D0F30,0x011D0008) 0058CAA6 WoW.exe +0 (0x0034FCCC,0x0034FCA0,0x0058C801,0x0042CFD0) 00591B75 WoW.exe +0 (0x0042CFD0,0x0034FCCC,0x0034FD04,0x0042CFD0) 0058C801 WoW.exe +0 (0x0042CFD0,0x0034FCCC,0x00000000,0x0034FD20) 005896D7 WoW.exe +0 (0x0034FCCC,0x00401000,0x00000000,0x603D9968) 00639E73 WoW.exe +0 (0x00000001,0x6C726F57,0x666F2064,0x72615720) 004027EC WoW.exe +0 (0x00000001,0x00000001,0x0034FF08,0x0040410E) 004021E0 WoW.exe +0 (0x00409990,0x00400000,0x00000000,0x0011646C) 0040410E WoW.exe +0 (0x7FFDF000,0x00000000,0x00000000,0x00000000) 603A6B81 kernel32.dll start_process+209 (0x00000000,0x00000000,0x00000000,0x00000000) (process.c,822) 60020247 wine_switch_to_stack+23 (0x00000000,0x00000000,0x00000000,0x00000000) ---------------------------------------- Loaded Modules ---------------------------------------- 0x00350000 - 0x003E6000 C:\Program Files\World of Warcraft\fmod.dll 0x00400000 - 0x00D05000 C:\Program Files\World of Warcraft\WoW.exe 0x10000000 - 0x10069000 C:\Program Files\World of Warcraft\DivxDecoder.dll 0x60290000 - 0x602F7000 c:\windows\system\ntdll.dll 0x60350000 - 0x60435000 c:\windows\system\kernel32.dll 0x604B0000 - 0x604E3000 c:\windows\system\advapi32.dll 0x604F0000 - 0x60592000 c:\windows\system\comctl32.dll 0x605B0000 - 0x606B4000 c:\windows\system\user32.dll 0x606D0000 - 0x6073C000 c:\windows\system\gdi32.dll 0x60750000 - 0x60819000 c:\windows\system\shell32.dll 0x60830000 - 0x6086B000 c:\windows\system\shlwapi.dll 0x60880000 - 0x608F2000 c:\windows\system\ole32.dll 0x60900000 - 0x6093E000 c:\windows\system\rpcrt4.dll 0x60950000 - 0x6095B000 c:\windows\system\iphlpapi.dll 0x60960000 - 0x60974000 c:\windows\system\wsock32.dll 0x609A0000 - 0x609B7000 c:\windows\system\ws2_32.dll 0x609D0000 - 0x60A29000 c:\windows\system\opengl32.dll 0x60C00000 - 0x60C14000 c:\windows\system\imm32.dll 0x60D70000 - 0x60DDE000 c:\windows\system\winmm.dll 0x60DF0000 - 0x60E02000 c:\windows\system\msacm32.drv 0x60E10000 - 0x60E63000 c:\windows\system\msvcrt.dll 0x60E70000 - 0x60EA4000 c:\windows\system\wininet.dll 0x60EB0000 - 0x60EC3000 c:\windows\system\mpr.dll 0x60FD0000 - 0x61043000 c:\windows\system\winex11.drv 0x6A250000 - 0x6A27A000 c:\windows\system\wineoss.drv 0x6AEC0000 - 0x6AEE4000 c:\windows\system\uxtheme.dll 0x6AFB0000 - 0x6AFBD000 c:\windows\system\midimap.dll 0x6B1F0000 - 0x6B221000 c:\windows\system\dbghelp.dll 0x6B230000 - 0x6B236000 c:\windows\system\psapi.dll ---------------------------------------- Memory Dump ---------------------------------------- Code: 16 bytes starting at (EIP = 00000000) 00000000: Stack: 1024 bytes starting at (ESP = 0034FA9C) * = addr ** * 0034FA90: 60 86 09 7C DC FB 34 00 F8 FA 34 00 54 5F 00 61 `..|..4...4.T_.a 0034FAA0: 70 39 09 7C 00 00 18 00 0B 80 00 00 E4 FA 34 00 p9.|..........4. 0034FAB0: B4 05 1C 60 00 28 27 60 E4 FA 34 00 E0 FA 34 00 ...`.('`..4...4. 0034FAC0: 34 CC 03 61 CE 23 03 61 27 00 00 00 01 00 00 00 4..a.#.a'....... 0034FAD0: 00 00 00 00 40 FB 34 00 01 00 00 00 70 39 09 7C ....(a).4.....p9.| <mailto:....(a).4.....p9.%7C> 0034FAE0: 00 00 00 00 00 00 00 00 43 00 00 00 74 A3 03 61 ........C...t..a 0034FAF0: D4 28 04 61 DC FB 34 00 58 FB 34 00 C0 9D 00 61 .(.a..4.X.4....a 0034FB00: 44 FB 34 00 00 00 00 00 48 FB 34 00 4D 4F 00 00 D.4.....H.4.MO.. 0034FB10: 00 B8 72 60 54 FB 34 00 00 B8 72 60 44 FB 34 00 ..r`T.4...r`D.4. 0034FB20: 00 00 00 00 2C 03 00 00 58 FB 34 00 F0 0B 34 7C ....,...X.4...4| 0034FB30: 2C 03 00 00 FF FF 00 00 58 FB 34 00 C9 29 70 60 ,.......X.4..)p` 0034FB40: 00 00 00 00 B8 8F 1A 00 01 00 00 00 28 3C 72 60 ............(

1 0

WM_*UISTATE message implementation in wine
by Vijay Kiran Kamuju Sept. 14, 2006

Sept. 14, 2006

Hi, Has wine an implementation for WM_*UISTATE messages? Can anybody tell me where should it be implemented and how it should be implemented. Does it involve complex coding? Thanks, VJ

1 1

Re: LOSTWAGES: Update the bus information for WineConf
by Eric Pouech Sept. 14, 2006

Sept. 14, 2006

Hi Rob, any news about how to get the keys for the room at Reading U ? haven't seen nothing about it ? TIA 2006/9/14, Robert Shearman <rob(a)codeweavers.com>: > > ChangeLog: > Update the bus information for WineConf. > > -- > Rob Shearman > > > > Index: templates/en/wineconf/travel.template > =================================================================== > RCS file: /home/wine/lostwages/templates/en/wineconf/travel.template,v > retrieving revision 1.18 > diff -u -p -r1.18 travel.template > --- templates/en/wineconf/travel.template 2 Aug 2006 19:03:42 > -0000 1.18 > +++ templates/en/wineconf/travel.template 14 Sep 2006 13:43:45 -0000 > @@ -48,10 +48,11 @@ depending on your quality and travelling > <li><a href="http://www.nationalexpress.com/">National > Express</a></li> > <li><a href="http://www.reading-buses.co.uk/">Reading Buses</a>: > <ul> > - <li>You will want to take the number 12 bus to get to the > + <li>You will want to take the number 18 or 19 bus to get to > the > university from Reading station. Click here for the > - <a href=" > http://www.reading-buses.co.uk/tt_reading_july2005/012MF20.HTML > ">timetable</a>. > - You can ask the bus driver to let you know where to get > off.</li> > + <a href=" > http://www.reading-buses.co.uk/tt_reading_march2006/018MF31.HTML > ">timetable</a>. > + You should get off at the St Joseph's Convent bus stop, as > this > + is the nearest to Windsor Hall.</li> > </ul> > </ul> > <li>Taxi — around £5 - £10 from Reading Station to > the > > > > > > -- Eric Pouech

1 0