Since my tiny little menu patch didn't go in, I figured Alexandre wanted a test. So I tried to compile and run the existing one on Windows XP. It failed for me: lots of menu size tests failed. I checked the test.winehq.org data, and I don't see lots of failures on XP, so... I thought I'd run winetest.exe from Paul Millar's site, just in case the compilation environment had something to do with it.
That locks up my laptop somewhere in the d3d/ddraw tests.
I know some video drivers are so broken we don't want to run on them. I have an ATI Radeon Mobility 250. I thought this was a fairly common card. Is locking up the machine really acceptable here?
How the ^$*@ am I supposed to produce a test when the existing ones fail/crash/burn for me? Grrr... --Juan
As a thought, did you consider just building the tests you needed via mingw32?
I've found John Klehm's script (http://wiki.winehq.org/JohnKlehm at the top) to be useful for that as winetest.exe hard locks my laptop and my desktop... ewww.
-Zac
Juan Lang wrote:
Since my tiny little menu patch didn't go in, I figured Alexandre wanted a test. So I tried to compile and run the existing one on Windows XP. It failed for me: lots of menu size tests failed. I checked the test.winehq.org data, and I don't see lots of failures on XP, so... I thought I'd run winetest.exe from Paul Millar's site, just in case the compilation environment had something to do with it.
That locks up my laptop somewhere in the d3d/ddraw tests.
I know some video drivers are so broken we don't want to run on them. I have an ATI Radeon Mobility 250. I thought this was a fairly common card. Is locking up the machine really acceptable here?
How the ^$*@ am I supposed to produce a test when the existing ones fail/crash/burn for me? Grrr... --Juan
As a thought, did you consider just building the tests you needed via mingw32?
Well, as I said, I did just build the test I needed, with MSVC. It failed. That's why I tried winetest. --Juan
Am Freitag, 30. Mai 2008 16:51:08 schrieb Juan Lang:
I know some video drivers are so broken we don't want to run on them. I have an ATI Radeon Mobility 250. I thought this was a fairly common card. Is locking up the machine really acceptable here?
All we could do is blacklisting certain drivers or card IDs. If the system hard crashes or has a bluescreen it's a driver bug for sure. It is plainly impossible to make sure the tests do not crash anywhere, except by not having any tests at all.
I have never heard the name "ATI Radeon Mobility 250". It could be an ATI Radeon Mobility 9000, which has a rv250 chip in it. I have the same in my old laptop, the tests run without crashing(Some are failing due to clear driver bugs though, and I there aren't any newer laptop drivers available)
I have never heard the name "ATI Radeon Mobility 250". It could be an ATI Radeon Mobility 9000, which has a rv250 chip in it. I have the same in my old laptop, the tests run without crashing(Some are failing due to clear driver bugs though, and I there aren't any newer laptop drivers available)
That's the one. The system doesn't blue screen. The display has a yellow background, with a four-color square in the middle. The mouse pointer is an hourglass. The mouse pointer moves around, but the system doesn't respond to ctrl-alt-del or ctrl-shift-esc or alt-tab, so after half an hour of no change I power cycled.
The d3d9 tests crashed for me, so it was some test after that. I assume it's a some d3d or ddraw test because the screen resolution is different than the default. --Juan
Stefan Dösinger wrote:
Am Freitag, 30. Mai 2008 16:51:08 schrieb Juan Lang:
I know some video drivers are so broken we don't want to run on them. I have an ATI Radeon Mobility 250. I thought this was a fairly common card. Is locking up the machine really acceptable here?
All we could do is blacklisting certain drivers or card IDs. If the system hard crashes or has a bluescreen it's a driver bug for sure. It is plainly impossible to make sure the tests do not crash anywhere, except by not having any tests at all.
I have never heard the name "ATI Radeon Mobility 250". It could be an ATI Radeon Mobility 9000, which has a rv250 chip in it. I have the same in my old laptop, the tests run without crashing(Some are failing due to clear driver bugs though, and I there aren't any newer laptop drivers available)
We now have a bug report for the same issue:
http://bugs.winehq.org/show_bug.cgi?id=13608
From looking at the attached res/report file, it crashes at that same test. I'm not sure if this is the relevant info about his graphics card:
d3d9:visual start dlls/d3d9/tests/visual.c - visual.c:181:Driver string: "ati2dvag.dll" visual.c:182:Description string: "Radeon X1950 Series" visual.c:183:Device name string: "\.\DISPLAY1" visual.c:184:Driver version 6.14.10.6783
It appears that at least 2 users are bitten by this issue. Not something we want to happen I guess, but I have no clue how to fix this.
Juan Lang wrote:
Since my tiny little menu patch didn't go in, I figured Alexandre wanted a test. So I tried to compile and run the existing one on Windows XP. It failed for me: lots of menu size tests failed. I checked the test.winehq.org data, and I don't see lots of failures on XP, so... I thought I'd run winetest.exe from Paul Millar's site, just in case the compilation environment had something to do with it.
That locks up my laptop somewhere in the d3d/ddraw tests.
I know some video drivers are so broken we don't want to run on them. I have an ATI Radeon Mobility 250. I thought this was a fairly common card. Is locking up the machine really acceptable here?
How the ^$*@ am I supposed to produce a test when the existing ones fail/crash/burn for me? Grrr... --Juan
What resolution is your display set to?
On Fri, 30 May 2008, Juan Lang wrote: [...]
I thought I'd run winetest.exe from Paul Millar's site, just in case the compilation environment had something to do with it.
[...]
How the ^$*@ am I supposed to produce a test when the existing ones fail/crash/burn for me? Grrr...
I'm not saying that the it's ok for the tests to crash/freeze your system. But here's a workaround for 'extracting' the test executables from Paul Millar's exe. Start winetest, wait until the first test starts, and then kill winetest.exe (or close the winetest window). Then you can find the test binaries in c:\Windows\Temp\wct (or possibly c:\Documents and Settings\your account\Local Settings\Temp or something like that). Then you can run just the test you want. And yes, it would be nice if the winetest GUI was better and let you do that more cleanly.
here's a workaround for 'extracting' the test executables from Paul Millar's exe. Start winetest, wait until the first test starts, and then kill winetest.exe (or close the winetest window). Then you can find the test binaries in c:\Windows\Temp\wct (or possibly c:\Documents and Settings\your account\Local Settings\Temp or something like that). Then you can run just the test you want.
Thanks, I'll do that! --Juan
-
Francois Gouget -
Juan Lang -
Paul Vriens -
Stefan Dösinger -
Zac Brown