May 2010 - Wine-devel - list.winehq.org

Re: [PATCH 4/4] wined3d: use stretch_rect_fbo for swapchainless blits
by Henri Verbeet 23 Jun '10

23 Jun '10

On 28 April 2010 14:29, Roderick Colenbrander <thunderbird2k(a)gmail.com> wrote: > + /* Early sort out of cases where no render target is used */ > + if (!dstSwapchain && !srcSwapchain > + && src_surface != device->render_targets[0] > + && dst_surface != device->render_targets[0]) > + { > + if (fbo_blit_supported(&device->adapter->gl_info, BLIT_OP_BLIT, > + &src_rect, src_surface->resource.usage, src_surface->resource.pool, src_surface->resource.format_desc, > + &dst_rect, dst_surface->resource.usage, dst_surface->resource.pool, dst_surface->resource.format_desc)) > + { > + stretch_rect_fbo(device, src_surface, &src_rect, dst_surface, &dst_rect, Filter); > + return WINED3D_OK; > + } > + > + TRACE("No surface is render target, not using hardware blit.\n"); > + return WINED3DERR_INVALIDCALL; > + } > + You might as well try FBO blits first, before doing most of the other checks. That's how it's eventually supposed to work anyway, and you could remove the other strecth_rect_fbo() calls in that case. That does depend on fbo_blit_supported() working properly, of course.

2 4

Re: [PATCH] ntdll: Show one-time ERR if NOFILE limit is reached.
by Octavian Voicu 10 Jun '10

10 Jun '10

Forgot to mention, this fixes http://bugs.winehq.org/show_bug.cgi?id=19861. Octavian

2 3

Call for translators
by Paul Vriens 09 Jun '10

09 Jun '10

Hi, The code freeze for Wine-1.2 has started and we are now in a weekly release candidate cycle. This is an ideal moment for translation work. The current translations status page http://source.winehq.org/transl/index.php shows four (4) languages at a 100%. Please help us have more fully translated languages for Wine-1.2. Also fixing the errors in the translations (21 languages affected) would be greatly appreciated. Most translators are not programmers and are probably intimidated by Wine's translation system. If you are comfortable editing resource file than please go ahead, create patches and sent them to wine-patches. The wiki-page http://wiki.winehq.org/Translating gives some more background information if needed. If you like to help out Wine but don't want to touch any of these resource files we can help you out. Please sent us an email with the language you'd like to translate Wine into and we will sent you the more familiar po files. These files show all the translatable strings from a resource file but in a less intriguing format. Once translated, you can sent these files back and we will turn them into the proper resource files. 'We' for now are Michael Stefaniuc and Paul Vriens but I guess others will chime in if needed. -- Cheers, Paul.

7 21

Release plans
by Alexandre Julliard 06 Jun '10

06 Jun '10

Folks, The 64-bit support is now more or less complete, and we have most of the fancy new icons, so it's time to think about the next stable release. Unless some major problems come up, 1.1.44 will be the last of the 1.1.x series. The next release will be 1.2-rc1, which will mark the beginning of the code freeze. This should result in a 1.2 final sometime in June. As usual the code freeze will become more and more drastic as we get closer to release, so if you have major changes to make, now is pretty much the last minute. I'd encourage everyone to look through the list of nominated 1.2 bugs, and also to check the regression reports for anything that might be in your area. We should strive to have as few regressions from 1.0 as possible, so regressions fixes will have priority during code freeze. And of course changes that don't impact the code, like translations or test fixes, can go in until quite late. -- Alexandre Julliard julliard(a)winehq.org

14 26

bricscad goes native
by Dan Kegel 02 Jun '10

02 Jun '10

I've long predicted that companies might use Wine for a while to ship Linux-compatible products, and later switch to a native build once they know they have users. Well, now we have at least one example of this: Bricscad (see http://www.bricsys.com ). This is a *good* thing, and validates somewhat the idea that Wine is a catalyst to enable a global shift from Windows to Linux.

6 10

AppDB 64 bit flag?
by André Hentschel 01 Jun '10

01 Jun '10

Hi, what about an AppDB input in test reports to mention if the test were made with the 32 or 64 bit version of the app? -- Best Regards, André Hentschel

3 2

kernel32 nls file codepage conversion
by Frédéric Delanoy 01 Jun '10

01 Jun '10

Hi folks, I'm intending to convert dlls/kernel32/nls/fr.nls from CP 1252 to CP 65001 (UTF-8), but I've some questions first: - most nls files are non-UTF8... is it intended? or just "legacy"? - can LOCALE_IDEFAULTANSICODEPAGE be set to 65001 or should it be left at its current "1252" value, i.e. is it necessary for compatibility with older win versions where UTF-8 is not the default (correct me if I'm wrong)? - LOCALE_SCURRENCY is set to char code 80 (<80> in vim). What is that exactly? The code for the euro sign in a specific code page? which one? Frédéric

4 10

Assigning bugs, and how new developers can find bugs to work on
by Alexandru Băluț 31 May '10

31 May '10

Hi Paul, I was wondering what is the best way to pick bugs, for a developer aspiring to fix nonspecific Wine bugs. Normally, our hero would look at the unassigned bugs to find one to work on. For some bugs, a fix appeared with no notification that somebody is working on them, for example: http://bugs.winehq.org/show_bug.cgi?id=22263 - julliard@ unexpectedly announced that the bug should be fixed by a specific patch. http://bugs.winehq.org/show_bug.cgi?id=22845 - arethusa26@ unexpectedly mentioned that the bug should be fixed by somebody else's specific patch. Notice both are marked as FIXED, but none of them have been assigned! Let's say our hero picks a bug; should he ask on the bug page whether anybody is already working on it, or ask on wine-devel, or #wine-hackers? Or is it fine to just announce, in the bug page, that you'll work on that bug? See, for example, this comment: http://bugs.winehq.org/show_bug.cgi?id=22264#c9 Any suggestions about improving this process are welcome. I think people will show up, wanting to help, and it would be nice to help them find something to work on fast. ;) In the meanwhile, please assign the bugs, and spare others of spending time on them. As a bonus, it would be nice to see accurate numbers about how many bugs are on nobody's plate vs how many are on somebody's plate. Data! :) At the moment, there are 15 assigned bugs (ignored 11 assigned to wine-bugs@), vs 5580 unconfirmed/new/reopened bugs, for the Wine component. Thanks, Alex On Thu, May 27, 2010 at 20:00, Paul Vriens <paul.vriens.wine(a)gmail.com>wrote: > On 05/27/2010 07:48 PM, belnac wrote: > >> What about dev work, is any available? >> > > Did you ever have a look at our bugzilla ;) > > There is plenty of stuff to do besides fixing bugs of course. What you want > to do depends on many things like skills, interest, the amount of time you > have etc.. > > Remember that we are in code freeze now so looking at bugs and trying to > figure out what could be wrong or even providing information that could lead > to fixing the bugs is welcome. > > -- > Cheers, > > Paul. > > >

3 4

Re: RFC: msvcrt: support dates after year 2038 in mktime64
by testbot＠testbot.winehq.org 31 May '10

31 May '10

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=2394 Your paranoid android. === WINEBUILD (build) === Patch failed

3 4

Re: New wisotool 20100530: new verbs galore
by wylda＠volny.cz 31 May '10

31 May '10

> > Does bioshock install ok manually from .mds for you > with cdemu? Yes, without any problem. I always double check each image, i.e. first i test the image under winxp and when the image is ok, i take it under wine. Bioshock passed both these tests successfully, i.e. installs and runs without originals (just the mounted image, no cracks of course). BTW: if you have a non-working image under winxp (have to work - necessary condition) check your available drive speeds. For SecuROM is recommended: CD medium: Use lowest available speed for DPM DVD medium: use highest available speed for DPM But my personal experience is different. For example DVD F.E.A.R. Extraction Point i succeeded after 4th try in case of highest DPM speed. Then i tried lowest DPM speed even for DVD and succeeded in every test. So since this i use in alcohol120: * 8x (CD-ROM read) * 4x (DVD-ROM read) Those are lowest speeds for my Samsung SH-S223F. It _should_ work setting 1x and the drive should choose lowest possible, but it happened sometimes to me, that max DPM speed was chosen instead. So i set the speeds explicitly. Unfortunately i also have DVD drives which will _never_ be capable of making working image (to name one: Sony/Optiarc AD-5200S). So if you can't succeed with image creation for longer time, send your drive to trash ;) What makes the image successful is .mds file (mdf should be always the same for different tries). So in case you have non-working image, you can ask someone just for .mds (but .mdf must have same size - i.e. same language DVD or gamebox). > > That's a familiar error. We can and should fix that > before you try again. OK :) > > Also how do you handle multi CD games whit this tool? > > I have 8 virtual drives... > The script can handle unmounting the 1st disc and mounting > the 2nd, but maybe we should mount multiple as you suggest. > (That's a bit more complicated to script because we want the > script to run on windows, too). > - Dan I met games, which are hard to persuade even with "wine eject" and also then you usually need to confirm "OK CD2 is in drive". So to me it looks easier to mount all CDs/DVDs before installation begins. (I'm not a programmer so maybe i'm wrong here;)

1 0