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
> 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\
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 sayin
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 dr
Ah woops, I misread the message.
-Zac
Juan Lang wrote:
>> 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
> 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 availa
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,
> 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
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
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 wi
10 matches
Mail list logo
