May 2008 - Wine-Devel - list.winehq.org

Re: Ubuntu Popularity Contest - 37% Wine install base, 10% who use, and 7% who use regularly

by Clarence "Sparr" Risher

This statistic also neglects people who install wine from source without building a package, and I know that is a non-trivial number of people. On Fri, May 30, 2008 at 10:17 AM, Scott Ritchie <scott(a)open-vote.org> wrote: > Doing some division, this means that a rather high 37% of Ubuntu users > have Wine installed, and 10% of all Ubuntu users actually make use of > Wine. 7% use Wine "frequently", however popcon defines that. > > Combine this with other estimates of Ubuntu's user base (about 8 million > last I heard), and you have approximately 800,000 Wine users.

May 30, 2008

Re: Winetest grrr...

by Zac Brown

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

May 30, 2008

Re: Winetest grrr...

by Paul Vriens

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? -- Cheers, Paul.

May 30, 2008

Re: Winetest grrr...

by Juan Lang

> 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

May 30, 2008

Re: README: Few more updates

by Austin English

On Fri, May 30, 2008 at 5:05 AM, Alexandre Julliard <julliard(a)winehq.org> wrote: > "Austin English" <austinenglish(a)gmail.com> writes: > >> Anything wrong with this patch? > > I don't see any need to change all the URLs, the existing ones work just > fine. > > -- > Alexandre Julliard > julliard(a)winehq.org > I was going for consistency, but that's fair enough. Some of urls malform in that case anyway.

May 30, 2008

Re: Winetest grrr...

by Juan Lang

> 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

May 30, 2008

Re: Winetest grrr...

by Stefan Dösinger

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)

May 30, 2008

Re: Winetest grrr...

by Zac Brown

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 > >

May 30, 2008

Winetest grrr...

by Juan Lang

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

May 30, 2008

Re: Double free in direct sound capture

by Maarten Lankhorst

Hi Michael, 2008/5/30 Michael Karcher <wine(a)mkarcher.dialup.fu-berlin.de>: > Am Freitag, den 30.05.2008, 08:59 +0200 schrieb Michael Karcher: >> I was running the testcases with warn+heap, and noted some warnings from >> dsound:capture. They are caused by double free calls, and only happen >> with winealsa.drv, not with wineoss.drv. The following patch happens to >> makes the messages disappear. Could somebody with some knowledge about >> wine's DirectSound implementation please look into this issue and find a >> proper fix? > > OK, status update. I think I understood that bit of code, and already > got an improved version of this improvised patch committed, which seems > clean to me (84fd6e629a05a87cf788cff8bf009fbc94a269e9), I would not mind > any DirectSound experienced Wine programmer to review it. There's no such thing as a DirectSound experienced wine programmer. ;-) Cheers, Maarten.

May 30, 2008