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

Re: dxdiagn: Added properties for hardware acceleration capabilities

by Markus Weiland

Is this implementation ok? On 14-03-23 07:20 PM, Stefan Dösinger wrote: > Am 23.03.2014 um 04:18 schrieb Markus Weiland <mw(a)graph-ix.net>: > >> This patch addresses bug http://bugs.winehq.org/show_bug.cgi?id=11114 I filed four years ago. It hardcodes the b3DAccelerationExists, b3DAccelerationEnabled, and bDDAccelerationEnabled properties to TRUE. > IDirect3D9::GetDeviceCaps with D3DDEVTYPE_HAL should do. If the call suceeds you have hardware acceleration. >

March 24, 2014

Re: Regarding GSoC

by Austin English

On Fri, Mar 21, 2014 at 2:22 AM, Ashwani Agarwal <ashwani.q(a)gmail.com>wrote: > Hello, > I've submitted my proposal for GSoC 2014 on Tools - Winetest Graphical > User Interface. > Can someone review it, so if there is any changes to make, can be done. > > and also can I know who is the potential mentor for this project? > So I can contact him and proceed further. > Hello Ashwani, Reviews will happen on melange, watch your inbox for melange notifications. -- -Austin

March 24, 2014

Re: dxdiagn: Added properties for hardware acceleration capabilities

by Stefan Dösinger

Am 23.03.2014 um 04:18 schrieb Markus Weiland <mw(a)graph-ix.net>: > This patch addresses bug http://bugs.winehq.org/show_bug.cgi?id=11114 I filed four years ago. It hardcodes the b3DAccelerationExists, b3DAccelerationEnabled, and bDDAccelerationEnabled properties to TRUE. IDirect3D9::GetDeviceCaps with D3DDEVTYPE_HAL should do. If the call suceeds you have hardware acceleration.

March 23, 2014

Re: Mass effect 2 - Bink movies freezes game

by Stefan Dösinger

Am 21.03.2014 um 22:11 schrieb Tomas Gustavsson <tomplast(a)gmail.com>: > Have tried for a while to get Mass Effect 2 working through Wine and though it's very playable for me it has a large drawback, I have to disable all movie playbacks with the -nomoviestartup argument. If I don't, the game freezes up and I can hear the sound stuck in a loop - it does not unfreeze itself. > > By looking through AppDB it seems that there are a large group of people that doesn't have this problem. I assume it's either related to my processor (AMD A10-6700) or GPU (HD5770, Catalyst driver)? I have tried to several Wine versions but it didn't help. I think I know the problem you describe, although I have not re-tested this to be sure. ME2 likes to get stuck during the initial startup, before the main menu is shown. I think there’s a race condition somewhere in the game code. If you run in windowed mode and make the game window bigger it is quite likely to lock up. The problem might affect just window resizes or exposing parts of the window, or all message handling. Again, this is just a theory. I never have investigated it in detail, it hasn’t bothered me enough when I was hunting other ME2 bugs.

March 23, 2014

Re: [PATCH] ntdll: test also FullDirectoryInformation (2nd)

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 https://newtestbot.winehq.org/JobDetails.pl?Key=5880 Your paranoid android. === w2000pro (32 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === wxppro (32 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === wvista (32 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === wvistau64 (32 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === w2008s64 (32 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === w7pro64 (32 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === w8 (32 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === wvistau64 (64 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === w2008s64 (64 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory === w7pro64 (64 bit directory) === directory.c:250: Test failed: not enough data in directory directory.c:250: Test failed: not enough data in directory

March 23, 2014

Re: [PATCH] kernel32: implemented "Basic" mode of findfirstfilex

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 https://newtestbot.winehq.org/JobDetails.pl?Key=5879 Your paranoid android. === w2000pro (32 bit file) === file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed === wxppro (32 bit file) === file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed === wvista (32 bit file) === file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed === wvistau64 (32 bit file) === file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed === w2008s64 (32 bit file) === file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed === wvistau64 (64 bit file) === file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed === w2008s64 (64 bit file) === file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed file.c:2630: Test failed: FindFirstFile failed (err=87) file.c:2631: Test failed: First entry should be '.', is file2 file.c:2635: Test failed: Fetching second file failed file.c:2636: Test failed: Second entry should be '..' is file2 file.c:2638: Test failed: Fetching third file failed file.c:2652: Test failed: Fetching fourth file failed file.c:2655: Test failed: Fetching fifth file failed

March 23, 2014

Re: [PATCH] ntdll: test also FullDirectoryInformation

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 https://newtestbot.winehq.org/JobDetails.pl?Key=5878 Your paranoid android. === w2000pro (32 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === wxppro (32 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === wvista (32 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === wvistau64 (32 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === w2008s64 (32 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === w7pro64 (32 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === w8 (32 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === wvistau64 (64 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === w2008s64 (64 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory === w7pro64 (64 bit directory) === directory.c:248: Test failed: not enough data in directory directory.c:248: Test failed: not enough data in directory

March 23, 2014

Re: [mshtml] add text/jscript as valid mime type for javascript files

by Jacek Caban

Hi Vijay, On 03/22/14 11:39, Vijay Kiran Kamuju wrote: > This is identified by Focht in bug #35827, patch fixes it. > > Changelog: > add text/jscript as valid mime type for javascript files > fixes bug# 35827 Please add a test case. Something like setting type on script element in exectest.html should be enough. Thanks, Jacek

March 23, 2014

Re: gdiplus: skip some tests if Arial is not installed

by Dmitry Timoshkov

Austin English <austinenglish(a)gmail.com> wrote: > font.c:784<https://source.winehq.org/git/wine.git/?a=blob;f=dlls/gdiplus/tests/font.c;…>: > Test failed: wrong face name Liberation Sans > font.c:794<https://source.winehq.org/git/wine.git/?a=blob;f=dlls/gdiplus/tests/font.c;…>: > Test failed: wrong face name Liberation Sans > > 784 ok(!lstrcmpA(lf.lfFaceName, "Arial"), "wrong face name %s\n", > lf.lfFaceName); > ... > 794 ok(!lstrcmpA(lf.lfFaceName, "Arial"), "wrong face name %s\n", > lf.lfFaceName); That's a gdi32 breakage (it shouldn't return "Liberation Sans"), nothing to do with gdiplus tests. -- Dmitry.

March 23, 2014

Re: gdiplus: skip some tests if Arial is not installed

by Austin English

On Sat, Mar 22, 2014 at 6:09 PM, Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > Austin English <austinenglish(a)gmail.com> wrote: > > > + status = GdipCreateFontFamilyFromName(Arial, NULL, &family); > > + if (status == FontFamilyNotFound) > > + { > > + skip("Arial not installed\n"); > > + return; > > + } > > Why do you need this? This test doesn't depend on Arial font presence. > > -- > Dmitry. > dlls/gdiplus/tests/font.c font.c:784<https://source.winehq.org/git/wine.git/?a=blob;f=dlls/gdiplus/tests/font.c;…>: Test failed: wrong face name Liberation Sans font.c:794<https://source.winehq.org/git/wine.git/?a=blob;f=dlls/gdiplus/tests/font.c;…>: Test failed: wrong face name Liberation Sans 784 ok(!lstrcmpA(lf.lfFaceName, "Arial"), "wrong face name %s\n", lf.lfFaceName); ... 794 ok(!lstrcmpA(lf.lfFaceName, "Arial"), "wrong face name %s\n", lf.lfFaceName); -- -Austin

March 23, 2014