March 2012 - Wine-Devel - list.winehq.org

Re: mscoree: Better support RUNTIME_INFO_UPGRADE_VERSION in, GetRequestedRuntimeInfo (try 4)
by Marvin March 13, 2012

March 13, 2012

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=17320 Your paranoid android. === WVISTAADM (32 bit mscoree) === mscoree.c:154: Test failed: version is L"v2.0.50727" , expected L"v1.1.4322" === W2K8SE (32 bit mscoree) === mscoree.c:154: Test failed: version is L"v2.0.50727" , expected L"v1.1.4322" === W7PRO (32 bit mscoree) === mscoree.c:154: Test failed: version is L"v2.0.50727" , expected L"v1.1.4322" === W7PROX64 (32 bit mscoree) === mscoree.c:154: Test failed: version is L"v2.0.50727" , expected L"v1.1.4322" === TEST64_W7SP1 (32 bit mscoree) === mscoree.c:154: Test failed: version is L"v2.0.50727" , expected L"v1.1.4322" === W7PROX64 (64 bit mscoree) === mscoree.c:154: Test failed: version is L"v2.0.50727" , expected L"v1.1.4322" === TEST64_W7SP1 (64 bit mscoree) === mscoree.c:154: Test failed: version is L"v2.0.50727" , expected L"v1.1.4322"

1 0

Re: mscoree: Better support RUNTIME_INFO_UPGRADE_VERSION in, GetRequestedRuntimeInfo (try 3)
by Vincent Povirk March 13, 2012

March 13, 2012

- FIXME("Unrecognized version %s\n", debugstr_w(pwzVersion)); + WARN("Unrecognized version %s\n", debugstr_w(pwzVersion)); I'm not so sure about this. I think GetRuntime is still incomplete, so I'd still like to know when it fails. You will get a useless FIXME in the case where RUNTIME_INFO_UPGRADE_VERSION is specified, but I think a program that makes that specifies a version number and that flag is doing it wrong. Anyway, we shouldn't be spammed with fixme's, right?

2 1

Re: kernel32: Make CreateFile called with creation == 0 work when opening a vxd in win9x mode.
by Saulius Krasuckas March 12, 2012

March 12, 2012

* On Sun, 11 Mar 2012, Dmitry Timoshkov wrote: > > A widely used approach to open/load device drivers under win9x is > > /* Check if already loaded in system.ini */ > hvxd = CreateFile("\\\\.\\mydevice", 0, 0, 0, 0, 0, 0); > if (hvxd == INVALID_HANDLE_VALUE) > /* Load dynamically from PATH */ > hvxd = CreateFile("\\\\.\\path\\to\\mydevice.vxd", 0, 0, 0, CREATE_NEW, FILE_FLAG_DELETE_ON_CLOSE, 0); > > First call never succeeds under Wine, and some device drivers refuse to > load more than once. Are there any proof one can see? What application does behave like this? Where has this source excerpt come from? S.

1 0

GSoC 2011 - introduction
by Józef Kucia March 12, 2012

March 12, 2012

Hi, My name is Józef Kucia. I'm a Masters student in Computer Science at Wrocław University of Technology in Poland. I would like to apply for Google Summer of Code this year. I have a good knowledge of C and OpenGL. I also have limited experience with Direct3D and win32 programming. With regard to the Wine project, I'm familiar with the project from user perspective. I used to run some applications in Wine on my Gentoo Linux box, mostly games to be exact. Unfortunately, I haven't made any previous contributions to the Wine project, except submitting two small patches recently. I have read your project ideas for GSoC, and I am primarily interested in projects related to Direct3D. Nevertheless, I'm open to other projects. I would appreciate any suggestions or comments. Thanks, Józef Kucia

3 2

Re: [PATCH 4/5] msxml3: Added partial XMLView IPersistMoniker_Load implementation
by Alexandre Julliard March 12, 2012

March 12, 2012

Piotr Caban <piotr(a)codeweavers.com> writes: > --- > dlls/msxml3/xmlview.c | 908 > ++++++++++++++++++++++++++++++++++++++++++++++++- > 1 files changed, 904 insertions(+), 4 deletions(-) This doesn't build without libxml (missing domdoc functions). -- Alexandre Julliard julliard(a)winehq.org

2 1

Instructions for using JACK with with Wine's ALSA output on wiki: reverted twice
by Alex Bradbury March 12, 2012

March 12, 2012

Recently user 'falktx' posted instructions on the Sound wiki page on how to set up an ALSA to JACK bridge that would work with Wine. He did this at the suggestion of aeikum: 14:45 <@aeikum> okay. so it is possible to get this working correctly. that's good to know 14:46 < falktx> I can make a small package with my setup scripts 14:47 <@aeikum> that might be handy to put up on the sound wiki page http://wiki.winehq.org/Sound If you look at the page edit history, you'll see the content has been reverted twice by Vitaliy without comment: http://wiki.winehq.org/Sound?action=info Please can you (wine developers) clarify your position on this. It seems to be useful content for the wiki that will benefit a number of users and I can see no justification for deleting it. It could be argued it clutters up the Sound wiki page, in which case it should be moved to a separate page linked to from there. Thank you, Alex

3 4

Re: advapi32: Correct tests under WOW64 (try 2)
by Vitaliy Margolen March 12, 2012

March 12, 2012

On 03/10/2012 12:36 AM, Alistair Leslie-Hughes wrote: > Hi, > Marked test as broken if it returns true. > > + /* WoW64 return TRUE with the LastError set */ > + ok((!ret && GetLastError() == ERROR_INSUFFICIENT_BUFFER) || broken(ret), > "%d with error %d\n", ret, GetLastError()); This is incorrect. You can check or report result of GetLastError(). But not both at the same time. You have to store the result in additional variable. Then compare and report it. Vitaliy

3 4

Re: mscoree: Better support RUNTIME_INFO_UPGRADE_VERSION in, GetRequestedRuntimeInfo (try 2)
by Vincent Povirk March 12, 2012

March 12, 2012

I suspect that RUNTIME_INFO_UPGRADE_VERSION will actually use the newest non-4.0 version when it doesn't find an exact match, which is why I asked you to add that test. I'm not sure whether Marvin's results prove that or not. If that's the case, get_runtime_info should probably be checking the result of CLRMetaHost_GetRuntime, and proceeding to the RUNTIME_INFO_UPGRADE_VERSION check if it fails.

1 0

Re: mscoree: Better support RUNTIME_INFO_UPGRADE_VERSION in, GetRequestedRuntimeInfo (try 2)
by Marvin March 12, 2012

March 12, 2012

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=17280 Your paranoid android. === WVISTAADM (32 bit mscoree) === mscoree.c:157: Test failed: version is L"v2.0.50727" , expected L"v2.0.50727" === W2K8SE (32 bit mscoree) === mscoree.c:157: Test failed: version is L"v2.0.50727" , expected L"v2.0.50727" === W7PRO (32 bit mscoree) === mscoree.c:157: Test failed: version is L"v2.0.50727" , expected L"v2.0.50727" === W7PROX64 (32 bit mscoree) === mscoree.c:157: Test failed: version is L"v2.0.50727" , expected L"v2.0.50727" === TEST64_W7SP1 (32 bit mscoree) === mscoree.c:157: Test failed: version is L"v2.0.50727" , expected L"v2.0.50727" === W7PROX64 (64 bit mscoree) === mscoree.c:157: Test failed: version is L"v2.0.50727" , expected L"v2.0.50727" === TEST64_W7SP1 (64 bit mscoree) === mscoree.c:157: Test failed: version is L"v2.0.50727" , expected L"v2.0.50727"

1 0

Re: Are we the reason Apple isn't helping us?
by Ralph Little March 11, 2012

March 11, 2012

Hi, Well, I'm a general lurker and small contributer in my own way. I'm looking at one bug and have requested help from wine-devel in the past. So, in a nutshell, I consider myself an outsider of the general crew. Therefore, I'm going to be a bit more forthright about my response to this post. The Wine developers know nothing about me and my experience. I have attempted to demonstrate that, although I lack much time, I am prepared to put some effort into helping where I can in my small way. There are many like me. In have tried to be cordial and respectful on wine-devel. In return I have had nothing but courtesy, helpful assistance and general goodwill in answer. There is a right way of entering into these things and a wrong way. The Wine crew, as far as I know, know nothing of this supposed Apple developer. He has not demonstrated his experience or trustworthyness or knowledge of the Wine product to any level. Jeremy expects that as a stranger the Wine team should take his word at face value that he submitted a needed fix and that it sufficiently corrected the problem without doing even the *minimum* of effort to convince them. I have read the bug issue in question, and from the outset, he was disrespectful and downright combative and dismissive of all of the Wine teams procedures. Despite that, the responses on the bug tracker from the Wine team where measured and non-escalatory. A slightly different approach would have yielded a substantially different result. A humble request for assistance in knowing the proper channel and aid in getting the change properly submitted would, I feel, have had a far greater acceptance of what he was after. I agree that sometimes the responses on the bug tracker can be curt to the point of rudeness, but mostly that is down to the impersonal nature of the medium. Jeremy obviously thought that the change was important enough that he should take the time to submit it in the first place. A little bit of natural humility and expressing a more willing sentiment would have gone a long way to helping his cause. Cheers, Ralph

1 0