January 2011 - Wine-Devel - list.winehq.org

Re: MapleStory Wine Bug

by James McKenzie

On 1/30/11 10:35 AM, Jack Edmonds wrote: > I recently submitted a bug > (http://bugs.winehq.org/show_bug.cgi?id=25934) I'm not sure if I did a > good job on the submission, but if I did, I was thinking it would be a > good first bug to work on so as to introduce me to the Wine source code. > I was wondering if someone could help me get started on it. > Jack: There is a whole bunch of information on how to develop for Wine on the Wine Wiki. Including Coding Standards and what NOT to do as well as what TO do. I'll defer to those pages. James McKenzie

Jan. 30, 2011

MapleStory Wine Bug

by Jack Edmonds

I recently submitted a bug (http://bugs.winehq.org/show_bug.cgi?id=25934) I'm not sure if I did a good job on the submission, but if I did, I was thinking it would be a good first bug to work on so as to introduce me to the Wine source code. I was wondering if someone could help me get started on it.

Jan. 30, 2011

Re: user32: Replicate Windows behavior of WM_SETTEXT handler regarding WM_CTLCOLOR*

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=8728 Your paranoid android. === WNT4WSSP6 (32 bit msg) === msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0135 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0135 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0138 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0138 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0138 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0138 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0138 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0135 was expected, but got msg 0x0111 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg 0x0111 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 4: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0138 was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg sequence is not complete: expected 8000 - actual 0000 msg.c:5644: Test failed: SETTEXT on a button: 2: the msg 0x0135 was expected, but got msg 0x002b instead msg.c:5644: Test failed: SETTEXT on a button: 3: the msg 0x002b was expected, but got msg 0x8000 instead msg.c:5644: Test failed: SETTEXT on a button: 4: the msg sequence is not complete: expected 8000 - actual 0000 === W7PROX64 (64 bit msg) === Timeout

Jan. 30, 2011

Re: Policy regarding 3rd party "windows" distributions and winetest

by Juan Lang

> I mean, yeah it's not legal, it's bad and what you want but what about if > they provide results that differ from the daily bot results ? So what? You know that the Windows software may have changed, and you can't replicate the results yourself (unless you also feel like breaking the law). > Do you think this 'stripped' version can cause failures that would not > happen on real windows ? > Should we ignore these results ? Perhaps, so yes. --Juan

Jan. 30, 2011

Re: Policy regarding 3rd party "windows" distributions and winetest

by GOUJON Alexandre

On 01/30/2011 04:47 PM, James McKenzie wrote: > On 1/27/11 7:04 PM, Dan Kegel wrote: >> I suspect that we should discourage people from submitting >> winetest results from 3rd party repackagings of Microsoft Windows, >> e.g. http://thepiratebay.org/torrent/4254053/MicroXP_v0.82_-_eXPerience >> >> Agreed? > +1. And that is a pirate version of Windows anyway. I don't see the point ... I mean, yeah it's not legal, it's bad and what you want but what about if they provide results that differ from the daily bot results ? Do you think this 'stripped' version can cause failures that would not happen on real windows ? Should we ignore these results ?

Jan. 30, 2011

Re: Policy regarding 3rd party "windows" distributions and winetest

by James McKenzie

On 1/27/11 7:04 PM, Dan Kegel wrote: > I suspect that we should discourage people from submitting > winetest results from 3rd party repackagings of Microsoft Windows, > e.g. http://thepiratebay.org/torrent/4254053/MicroXP_v0.82_-_eXPerience > > Agreed? +1. And that is a pirate version of Windows anyway. James McKenzie

Jan. 30, 2011

Re: ntoskrnl.exe: unimplemented function ntoskrnl.exe.IoGetDeviceInterfaces

by James McKenzie

On 1/29/11 6:53 AM, Qian Hong wrote: > Dear all, > While test another online bank with wine ActiveX, > I got an unimplemented fuction of ntoskrnl: IoGetDeviceInterfaces, > I found it listed in http://source.winehq.org/WineAPI/ntoskrnl.html as a stup, > so I can't understand this log: > wine: Unimplemented function ntoskrnl.exe.IoGetDeviceInterfaces called > at address 0x7b839552 (thread 0022), starting debugger... > Grateful for any explain! > Qian: I would like to echo Nikolay's comment and add one more: Please search through the Bug Reports before submitting a new one. You might receive more assistance on the Wine User list as well. Most of the developers lurk there. Thank you. James McKenzie

Jan. 30, 2011

Re: [PATCH 1/2] winecoreaudio: Don't use Component Manager on Mac OS 10.6.

by Charles Davis

On 1/29/11 6:40 PM, James McKenzie wrote: > Chip: > > I'm assuming that this has been checked on Tiger/Leopard and it works. I checked that it would work if the AudioComponent header weren't present (which it isn't pre-SL). > > I don't have a Leopard system here and I'm reluctant to try it on one of > the systems I have Tiger installed on (it is a PowerPC Mac.) I can't imagine why... :) Chip

Jan. 30, 2011

Re: Wine FAQ edits

by Vitaliy

On 01/29/2011 12:21 PM, Dan Kegel wrote: > Hi Albert, > http://wiki.winehq.org/FAQ?action=diff&rev2=384&rev1=383 looks > like it was a pretty big edit. > > Try smaller ones, and try to do just one kind of change per edit. That, and the fact that some changes where questionable, and broken: > -cd ~/.wine/drive_c/Program\ Files > +cd .wine/drive_c/Program\ Files This will break if current directory is not $HOME. > - You can also use double quotes, but you need two backslashes instead of one: > - > -{{{ > -wine start "C:\\Games\\Tron\\tron.exe" > -}}} Backslashes still have special meaning inside double quotes. So they should be escaped. > -/bin/sh -c glxgears > +/usr/bin/env glxgears What advantage does "env" has over full featured shell? This is unnecessary. > -@="/bin/sh run_linx_program acroread \"%1\"" > +@="/bin/sh -c \"acroread `wine winepath -u '%1'`\"" Have you actually tested this? This won't work for paths with spaces. If it will work at all. Vitaliy

Jan. 29, 2011

re: Wine FAQ edits

by Dan Kegel

Hi Albert, http://wiki.winehq.org/FAQ?action=diff&rev2=384&rev1=383 looks like it was a pretty big edit. Try smaller ones, and try to do just one kind of change per edit.

Jan. 29, 2011