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

Re: [PATCH] Fix 16 bit StringFromGUID2 to not use wide characters
by Dmitry Timoshkov May 20, 2008

May 20, 2008

"Michael Karcher" <wine(a)mkarcher.dialup.fu-berlin.de> wrote: > +INT WINAPI StringFromGUID2_16(REFGUID id, LPSTR str, INT cmax) > +{ > + char xguid[80]; > + int len; > + > + if (WINE_StringFromCLSID( id, xguid )) > + return 0; > + > + len = strlen( xguid ) + 1; /* The terminating zero counts */ > + if (len > cmax) > + return 0; > + > + strcpy( str, xguid ); > + return len; > +} This is not an equivalent of the old implementation, is it really supposed to fail if the buffer length is shorter than the guid? -- Dmitry.

2 4

Re: Bug in dlls/user32/edit.c
by Juan Lang May 20, 2008

May 20, 2008

Hi Bob, could you open a bug at bugs.winehq.org, and put everything you wrote in your email in the description? You might have more luck getting followup that way. Thanks, --Juan

2 1

Spec OpenGL benchmarks
by Dan Kegel May 19, 2008

May 19, 2008

On a whim, I tried the oldest SPEC OpenGL benchmark, SPECviewperf 6. SPECViewperf 6.1.2 lives here: http://www.spec.org/gwpg/pastissues/Feb2_02/opc.static/opcview.htm It's also downloadable from ftp://spec.it.miami.edu/dist/gpc/opc/viewperf/specviewperf612is01.exe So far, the two tests I've tried seem to run ok, though I don't know if the rendering is correct. On one machine, $ cd ".wine/drive_c/Program Files/SPECopc/SPECviewperf 6.1.2" $ wine cmd /c RunLight04.bat produced a proud 3 frames per second, woot! This is pretty slow compared to the published results from 2002, http://www.spec.org/gwpg/pastissues/Feb2_02/opc.data/summary.html even without thinking about how much faster today's CPUs are. Still, it's nice that it runs. Perhaps we can take some baseline data and start looking for bottlenecks one of these days. - Dan

4 4

New winetricks-20080519: add synonym mfc42, show package descriptions in zenity
by Dan Kegel May 19, 2008

May 19, 2008

Another week, another winetricks. Changes since last week's annoucement: - gnome users now see nice package descriptions - mfc42 is now listed as a synonym for vcrun6 Online as always at http://kegel.com/wine/winetricks or http://winezeug.googlecode.com

1 0

Wine forums page links
by Ian Macfarlane May 19, 2008

May 19, 2008

The page http://www.winehq.org/site/forums needs to link to the new forums at http://forum.winehq.org/ (it does, but just in the site-wide sidebar not the page body). Regards, Ian

1 0

Can someone get a Maximizer 8 trial CD for me?
by Dan Kegel May 19, 2008

May 19, 2008

http://www.cabc.co.uk/maximizer8/trial_personal.htm free cd, but only for people in the EU. I'm interested because http://www.mindstab.net/wordpress/archives/292 is a recent report some this being one of the two "must have" apps for someone's dad. Thanks, Dan

2 1

Right way to cope with user error in make test?
by Jeremy White May 19, 2008

May 19, 2008

So...turns out that in this flood of new reporting, that one of the errors only happened to me, and it further turns out to be entirely user error; I didn't have libxslt. So, the obvious first solution is for me to actually read my configure results and deal with it. But I think I serve nicely as an example of the sort of incompetent user for whom it would still be nice to have make test work cleanly. I didn't see any obvious standard way of coping with this situation. Did I miss it? I imagined that maybe we'd skip these cases, but I didn't see evidence of that. I could also imagine a facility whereby we note that the configure was not clean, and then refuse to run make test (or at least refuse to run the full winetest battery). Should we make libxslt non optional (or at least require an explicit --without-libxslt in order to build without it)? Cheers, Jeremy

11 19

Re: kernel32: Add a few traces to help debug test failures [RESEND]
by Dmitry Timoshkov May 19, 2008

May 19, 2008

"James Hawkins" <jhawkins(a)codeweavers.com> wrote: > if(detailed_info->lpRootManifestPath) > ok(!lstrcmpiW(detailed_info->lpRootManifestPath, exinfo->root_manifest_path), > - "unexpected detailed_info->lpRootManifestPath\n"); > + "unexpected detailed_info->lpRootManifestPath: %s %s\n", > + strw(detailed_info->lpRootManifestPath), strw(exinfo->root_manifest_path)); As far as I can see strw() uses static buffer and is not able to handle more than one string at once. -- Dmitry.

1 0

Re: Right way to cope with user error in make test?
by Rolf Kalbermatter May 19, 2008

May 19, 2008

Please both calm down a bit. <dmitry(a)codeweavers.com> wrote: >"Steven Edwards" <winehacker(a)gmail.com> wrote: >><dmitry(a)codeweavers.com> wrote: >>> Not everyone supposed to run the Wine tests, only those do who >>> *really* can comprehend the results and able to do something with them. >> >> NO. Everyone that builds Wine from source should run make test. > >Why? Does it magically make something useful? Again, what about other >packages built from source? To limit running of the test frame work only to those that know exactly what they are doing is a to strict limitation IMHO. You should not forget that acceptance of a patch is based on the criteria that it runs make test. Which in may case has been always a limited make test in the directory itself only, since a whole make test seldom or never even got so far as to run for the component I was working at. While sending patches is of course the right thing to do, it has been and still is rather discouraging to get wine sources, building them on ones own box and finally run a make test and find that there are many areas where it simply reports failures or crashes altogether especially in areas I do not have the knowledge to do anything about and not the time to dig into much deeper. The fact that I couldn't get the whole make test to run out of the box on my system without bad crashes and/or numerous test failures has not only made me not run it anymore except in tree for the component I attempted to create a fix for, but has actually discouraged me in the past from working on more bug fixes or improvements other than what I have found strictly necessary to make a specific app working. >> It should pass 100% for everyone everywhere. If does not then there is >> something wrong. It does the world not 1 damn bit of good if passes on >> your system and no one elses. > >If the test doesn't pass for you, go ahead and fix it. I can't do that >for you if the test passes for me. But isn't that the crux of why this discussion started? Someone finding that a soft dependency of Wine on a library should not create a failure but a skip when that dependency was not satisifed and this was detectable in a sane way. And getting shot down that this system should be considerd broken. If the missing soft dependency should be considered a broken system then the dependency should be not soft and vice versa. I personally don't mind a test failure in a library that depends on something I know I don't use and consequently don't have installed but if it's possible to skip the tests for that why not do it? The test framework should not only help avoiding regressions for the VERY active developers but allow anyone working on Wine in one way or the other to have some confidence that he got it to build right. It's what I usually do when installing any source package to see if I missed something. Getting a long list of errors and sometimes crashes out of the box really leaves a bad taste and also makes it much harder to verify that my own modifications to it later on didn't break it in some ways. Rolf Kalbermatter

3 3

is run-time path translation standard
by Roumen Petrov May 18, 2008

May 18, 2008

Dear Wine developers, Starting from version 2.x the libtool would like the create an environment where user to be able to run win32 programs. The former version 1.5x has this capability, but with some limitation in case of cross-compilation environment. The current libtool HEAD revision contain code that create binary executable (C-wrapper). This wrapper executable setup environment and run the real executable. The development in case of cygwin/msys native environment is finished and now on the road is cross-compilation. Lest see recent libtool 2x discussion started here: http://lists.gnu.org/archive/html/libtool-patches/2008-05/msg00044.html The question if about translation at run time of items in PATH environment variable. My test show that we can add absolute paths from build system to the PATH and at run time those paths are translated to the paths in emulated environment. Is this translation documented, i.e. standard or it is just a "side-effect"? If translation is non-standard, could Wine team confirm that will keep it ? Note that Charles may is not subscribed to the list and please CC to him. Roumen P.S. Also, please consider a minor issue with winepath: http://bugs.winehq.org/show_bug.cgi?id=13265

1 0

Re: WineD3D: workaround for lack of depth/stencil
by Stefan Dösinger May 18, 2008

May 18, 2008

Am Sonntag, 18. Mai 2008 18:11:35 schrieb Roderick Colenbrander: > Hi, > > This patch is a workaround for a severe WineD3D issue which is too much > work and to risky to fix properly during the code freeze. It fixes drawing > issues in GTR2, Suppreme Commander, Call of Duty 2 Call of Duty 4 and > likely dozens of other games. Wouldn't it be better to write the FIXME only if the app requests a depth stencil format != D24S8?

1 0

What graphics cards do the d3d9 tests pass on?
by Dan Kegel May 18, 2008

May 18, 2008

Anyone know how to get the d3d9 tests to pass? Are there a set of graphic cards that are known to work with them? Right now, nobody who's reported test results under wine is seeing them pass: http://test.winehq.org/data/2470b0b31605133ec046330dd79fdccaa7ba33fe/#group… And, come to think of it, ditto for Windows: http://test.winehq.org/data/200804161000/#group_XP:d3d9:visual (though the data's pretty thin there). All the apparant successes are really just skipped tests. - Dan

6 6

Configure question about Wine / HAL
by Kris Moore May 17, 2008

May 17, 2008

I'm trying to get Wine to compile with HAL support on FreeBSD, and running into this error: > checking dbus/dbus.h usability... yes > checking dbus/dbus.h presence... yes > checking for dbus/dbus.h... yes > checking hal/libhal.h usability... yes > checking hal/libhal.h presence... yes > checking for hal/libhal.h... yes > checking for dbus_connection_close in -ldbus-1... no > configure: error: libhal development files not found, no dynamic device > support. > This is an error since --with-hal was requested. What exactly is -ldbus-1? Is there a way around this? Configure is finding the dbus and hal headers properly, and they both work properly on the system. -- Kris Moore PC-BSD Software http://www.pcbsd.com

4 11

curious failure and messages running a well-known installer
by Hin-Tak Leung May 17, 2008

May 17, 2008

I install the win32 version of ghostscript quite routinely under wine; just taken the old one off and put the new one in with wine rc1, the first time it bombed out with: err:module:map_image Could not map section _winzip_, file probably truncated err:module:map_image Could not map section _winzip_, file probably truncated wine: could not load L"H:\\mirror.cs.wisc.edu\\pub\\mirrors\\ghost\\GPL\\current\\gs862w32.exe": Bad EXE format for and 2nd/3rd time it went to completion. This is the first time ever I have a failure installing ghostscript. There are some messages which I don't remember seeing before also: fixme:shell:IShellLinkA_fnGetPath (0x14a980): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkA_fnGetPath (0x14aae8): WIN32_FIND_DATA is not yet filled. I seem to recall the _winzip_ thing is a known and fixed problem? anyway, the installer is at http://mirror.cs.wisc.edu/pub/mirrors/ghost/GPL/current/gs862w32.exe and I'd be interested to hear if somebody else the _winzip_ failure message. __________________________________________________________ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

3 2

Re: WIKI: Add forum link to wiki site
by Dimi Paun May 17, 2008

May 17, 2008

On Sat, 2008-05-17 at 10:26 +0200, Rico Schüller wrote: > Hi, > > this patch adds the Wine Forum link to the WineHQ Menu in the wiki. Thanks! Now I'm just on my way out to New York, I'll get back in 3 days, I'll look at it when I get back. [If I don't commit it in 3-4 days, please ping me again, in case it felt through the cracks] -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

1 0

Search data seems to show that each new product seems to raise Wine's profile a bit
by Dan Kegel May 17, 2008

May 17, 2008

It's a small effect, and it's not really surprising, but if you look at a graph of the relative search volume for the phrases linux wine linux photoshop linux warcraft linux steam it seems that each time a new big app starts working on Linux enough for people to start searching for it (photoshop, warcraft, steam), the number of queries for linux wine goes up a little bit. http://www.google.com/trends?q=linux+wine%2Clinux+photoshop%2C+linux+warcra… I'm just pleased to see that the effect is measurable, and not lost in the noise...

2 1

Re: [PATCH 2/3] shell32: implement make new folder UI changes.
by Jeff Latimer May 17, 2008

May 17, 2008

Lei Zhang wrote: > Hi, > > This implements the treeview UI changes to show users the newly created folder. > > ------------------------------------------------------------------------ > > I can't apply the patch. Is there one missing? Jeff Latimer

2 1

Wine 1.0 release status: 27 bugs left
by Dan Kegel May 17, 2008

May 17, 2008

Clickable copy at http://kegel.com/wine/countdown.html Wine Release Status Wine 1.0rc1 released on May 9. 6 days to second release candidate. wine-1.0rc1 was released on Friday, May 9th, 2008. Wine is now in a code freeze in preparation for the 1.0 release. According to http://wiki.winehq.org/WineReleasePlan, wine-1.0.0-rc2 will be due out Friday, May 23rd, 2008. It will be something like be the next to last release candidate for 1.0. Alexandre is on vacation, so git is a bit stale. In particular, Photoshop CS2 and DNS 9 don't install properly due to a regression introduced just before his vacation started; here's the fix. Some effort has been put into making it easy for people to automatically report "make test" failures; see MakeTestFailures for info and results. Bug Status There are 27 open 1.0 bugs as of 16 May. Most of these will simply be rolled over to be fixed for a later release; we only have time to fix a few, and much as we'd like to fix the rest, most are not showstoppers. Changes since last week (with category and votes): New (!): 8783 ntdll 15 USB serial ports do not work 13168 -unknown 0 Update the README before the 1.0 release Fixed: 3270 gdi32 16 Problem with minimized top-level windows 5844 -unknown 16 tray minimize 5926 programs 1 Wine does not provide an implementation of winhlp32.exe 5948 -unknown 2 Star Trek: Armada does not install 8898 shdocvw 1 Run Time Error "445": Object doesn't support this action in Europa Knowledgebase 11742 shlwapi 9 Small .net 1.1 app (FastMD5 1.3) fails to start up 12263 opengl 3 Sketchup Cannot initialize OpenGL - ChoosePixelFormat fails Abandoned: 664 user32 8 The help menu functionality inside programs is broken (messaging problem) Here's the full list of current bugs: 2493 comctl32 2 Multi-select listview: Shift-arrow up only selects top two items 11509 crypt32 0 Wordviewer 2003 is unable to open documents encrypted with AES 5535 directx- 21 Planescape:Torment doesn't work 9916 directx- 7 "make test" usually fails 11584 directx- 4 Multiple games crash with stack overflow error 12246 directx- 2 "make test" gives different results with and without warn+heap 12730 gdi32 1 gdi32: some tests fail when X is run in 16 bit mode, but not 32 bit 6519 gdi32 7 Wine blacks out rotated font bitmap 9771 gdi32 47 Steam Friends doesn't work (fails to render correctly or refresh) 5024 kernel32 6 Thief: Deadly Shadows crashes:page fault on read access to 0x0000040c 10147 msi 2 Word Viewer 2003 - Tab behavior differs from Windows 8783 ntdll 15 USB serial ports do not work 10288 programs 0 wine_gecko download hangs sometimes 13071 quartz 0 Flashplayer crashes in a quartz bug 5163 setupapi 15 Office XP 2002 crashes on installation 6095 shdocvw 17 MOTD in counter-strike 1.6 and counter-strike source does not render 8439 shell32 10 Visual Studio .NET (7) install fails 12074 testcase 3 The conformance tests fail on Windows 5402 -unknown 0 Trying to run PhotoStitch 3.1 7404 -unknown 3 ShowWindow(SW_MINIMIZE) should not generate a WM_PAINT message 11281 -unknown 5 CJK input many issues 12097 -unknown 3 Wine 1.0 should not ship out-of-sync resource translations 13168 -unknown 0 Update the README before the 1.0 release 3023 user32 6 Orcad - "Place Part" never tries to put down a part 124 wineserv 2 Review of Wine Server Protocol 9787 winsock 67 Warcraft3 Battle.net Doesn't work (Needs AcceptEx) 12005 wintab32 2 Regression in pressure sensitivity with wizardpen tablet driver and Photoshop 7

1 0

Call for help with Wine 1.0 testing
by Jeremy White May 16, 2008

May 16, 2008

Hi Folks, One key goal for Wine 1.0 is that all of its conformance tests run successfully on nearly all systems. We would really like your help in figuring out how close we are to that goal. To that end, if you are comfortable with checking Wine out via git, could you please visit this page: http://wiki.winehq.org/MakeTestFailures and follow the instructions there? (It's really simple; build current git Wine, download + run a script). And, if you're a Wine developer, since Alexandre is away and the code freeze is on, why not look for one of those failures in your own make test results and see if you can fix it? Thanks! Jeremy

6 9

re: Right way to cope with user error in make test?
by Dan Kegel May 16, 2008

May 16, 2008

jwhite wrote: > The attached patch is one approach - skip the tests in this case. > Does this seem like a reasonable approach to folks? I like it. I would also like to see us get a lot tougher about letting people build wine without a full complement of development headers. Maybe our configure should have a sanity check at the end, and abort if something optional but very common is missing; we could add a --no-sanity-check option to enable configuring in that case if it's really intended. - Dan

3 4

Re: Right way to cope with user error in make test?
by Susan Cragin May 16, 2008

May 16, 2008

I have a string of crashes in my maketest. Distro Hardy UbuntuStudio, machine ASUS G1S. Several triaged Ubuntu bugs may be responsible. For instance, my video drivers don't work and I have defaulted to vesa. My soundcard doesn't yet work properly, and there are two open bugs related to this, one to do with my motherboard. HTH.

1 0

A console screen buffer sync problem in kernel32/editline.c
by FENG Yu Ning May 16, 2008

May 16, 2008

I have found a synchronization problem in kernel32/editline.c . The problem appears when read and write operations to the console are in different threads. Detail information is here: http://bugs.winehq.org/show_bug.cgi?id=13188 Solution to it should not be difficult. Could any developers look into this and fix it? Thanks very much!

1 0

Re: ALSA Midi port names
by Dmitry Timoshkov May 16, 2008

May 16, 2008

"Free Ekanayaka" <free(a)64studio.com> wrote: > I attach an amended patch for this bug: > > http://bugs.winehq.org/show_bug.cgi?id=13241 As it's been said the first hunk of your patch looks incorrect and seems not related. Also, please use your real name, Wine doesn't accept anonymous patches. -- Dmitry.

1 0

Re: richedit: empty text should result in a scroll range of 0. Tests for this behavior.
by Eric Pouech May 15, 2008

May 15, 2008

Alex Villacís Lasso a écrit : > Even though the code freeze is still in effect, I post this so that it > will be reviewed. For more information, see bug #12311. > > Changelog: > * richedit: empty text should result in a scroll range of 0. > * Tests for this behavior. > > ------------------------------------------------------------------------ > > what I don't understand is why the height of an empty doc is not zero (I had similar issues with the height of a doc where we systematically get one row too much). I believe this root cause should be fixed instead of the band aid your patch is providing A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)

2 2

regressions running Photoshop?
by Dan Kegel May 15, 2008

May 15, 2008

Hmm. I just tried running Photoshop CS2 trial and Photoshop 5.5 trial, and both failed on current wine. CS2 complained "not enough DOS memory", and 5.5 complained lcms: Error #12288; Too many tags (2025813777) PS6 works, though.

2 3