December 2010 - Wine-Devel - list.winehq.org

Re: New winetricks 20101222: new verbs icodecs, msnasn1, opensymbol, wmi, xmllite; removed obsolete verbs audioio, dcom98, eadm, urlmon

by Dan Kegel

Roseanne wrote: > Urlmon is needed to work around bugs 25492 and 25494. Jacek suggests installing ie7 (and possibly limiting overrides to just urlmon). He warns that the old ie6-era urlmon winetricks was using would cause more and more problems as he continues moving wine over to ie7-style infrastructure. A new urlmon verb that installs an ie7-era urlmon would be logical, but I haven't needed it myself yet. If anyone else needs it and feels like coding it up, I'd be happy to test and commit. - Dan

Dec. 22, 2010

Re: New winetricks 20101222: new verbs icodecs, msnasn1, opensymbol, wmi, xmllite; removed obsolete verbs audioio, dcom98, eadm, urlmon

by Rosanne DiMesio

On Wed, 22 Dec 2010 11:41:13 -0800 Dan Kegel <dank(a)kegel.com> wrote: > the audioio, dcom98, eadm, and urlmon verbs are gone, let > me know if you really need those! > Urlmon is needed to work around bugs 25492 and 25494. -- Rosanne DiMesio <dimesio(a)earthlink.net>

Dec. 22, 2010

New winetricks 20101222: new verbs icodecs, msnasn1, opensymbol, wmi, xmllite; removed obsolete verbs audioio, dcom98, eadm, urlmon

by Dan Kegel

Another month, another Winetricks. Online as always at http://kegel.com/wine/winetricks or http://winezeug.googlecode.com (Bug reports to the issue tracker at the above URL, please.) Changes: Lots of bugfixes. wsh57 now works with vb scripts. The code has undergone some spring cleaning, so watch out for regressions. (We've fixed a few already.) In particular, the audioio, dcom98, eadm, and urlmon verbs are gone, let me know if you really need those! There's a new --optin commandline option that will tells winetricks to phone home after each run with info about which verbs really get used. Please consider using this, it will help future winetricks development. (You only have to give that option once, it sticks. You can turn it off with the --optout option, or by removing ~/.cache/winetricks.) Longer Changelog: Detlef Riekenberg: wmi: new verb Andrew Nguyen: steam: install corefonts first gfw: Avoid extracting the entire Win2k SP4 redist for msasn1.dll Austin English: Always use quiet and overwrite options for unzip. (issue 196) Lots of win64 fixes audioio: removed cmake: support silent install d3dx9_xx: only extract the desired dll (faster) dotnet11: work around wine bug 25120 eadm: remove, it's useless and its sha1sum changes way too often ie6: get rid of ie6 online installer, rename ie6_full to ie6 (which works around the inseng bug), support quiet installs mono28: bump to mono 2.8.1 mono28: remove mono registry keys, they are set by default in Wine since 1.2 msxml3: fix install opensymbol: added font set_psm: should set PixelShaderMode, not RenderTargetLockMode. (Issue 197) unset_winver: wine changed version setting, so make this a synonym for winver xp vcrun2003: use the correct programfiles directory. Fixes win64 install. w_call: if the subshell fails, exit immediately, otherwise w_die() is useless winver: update how setting a windows version works. w_warn: should return 0 in case of no-gui xact: fix for WINEPREFIXes with spaces/special characters Dan Kegel: Many small changes to start obeying new coding convention. Fix a few bugs found when running on windows Fix places where paths weren't quoted (bug 179). Thanks to Roberto Neri. Add --option, --optout options to control experimental opt-in usage tracking. crypt32: it was really broken, but works now. dcom98: it's obsolete, and causes problems, so removed. dotnet30: have to set XP mode now for install to work dotnet35: improved recipe per Louis, good enough to let some apps start icodecs: brought back, thanks to Alan Alberghini for the new URL. msasn1: new verb. urlmon: remove for now wsh57: improve so wscript hello.vbs works xmllite: new verb. (Hangs at end unless you give -q)

Dec. 22, 2010

Re: The Windows version of the "octave --version" command exposes an uncommon X network transparency issue for wine

by Hin-Tak Leung

Alan W. Irwin wrote: <snipped> > wineconsole --backend=curses MinGW/msys/1.0/bin/bash.exe > > Under that bash if I set the PATH to include the bin directory where > octave.exe resides and run > > octave --version > > directly (i.e., not from an X-terminal) I get a good result which > consists of the usual GNU octave version message. If I do > the same thing from my X-terminal (where all X applications like the > xterm where the wineconsole command is executed are running on a > remote machine over the office LAN and a local X server on the > X-terminal box transparently handles the X display, keyboard, and > mouse), then I get the following errors (subject to rewrapping) > > bash.exe-3.1$ octave --version > X Error of failed request: BadMatch (invalid parameter attributes) > Major opcode of failed request: 1 (X_CreateWindow) > > Serial number of failed request: 208 > Current serial number in output stream: 210 <snipped> I am still not quite sure about the two different execution environments you have, but if it is DRI-related, you could try also running Xvfb and setting DISPLAY to the Xvfb virtual display to see if either of your execution environments continue to work. AFAIK Xvfb is totally software-based and since "octave --version" doesn't use X display at all, using Xvfb should be no effect what so ever.

Dec. 22, 2010

Re: Death to win9x?

by Jacek Caban

On 12/22/10 5:52 PM, Joerg-Cyril.Hoehle(a)t-systems.com wrote: > Hi, > > André Hentschel wrote: >> actually we just always need to do something like skip() or broken() >> and that's nothing else as ignoring the test results of 9x > Well, I could sympathize with the idea of removing all broken(/*win9x*/) > and leave only skip() such that the tests don't crash prematurely. > > Does test.winehq.org refuse win9x test data since 2010-12-17? Yes, see my patch: http://www.winehq.org/pipermail/wine-patches/2010-December/096908.html > This is not a good idea at all. > We had a couple of real machines that were submitting results, e.g. Saulius's machines. > Even when test failures on win9x are not a criteria for rejecting patches, that > must not mean that we become blind on what happens on the win9x side. It was said already a few times: dropping win9x tests has nothing to do with dropping win9x support. These test results weren't helpful nor useful anyways. Jacek

Dec. 22, 2010

Death to win9x?

by Joerg-Cyril.Hoehle＠t-systems.com

Hi, André Hentschel wrote: >actually we just always need to do something like skip() or broken() > and that's nothing else as ignoring the test results of 9x Well, I could sympathize with the idea of removing all broken(/*win9x*/) and leave only skip() such that the tests don't crash prematurely. Does test.winehq.org refuse win9x test data since 2010-12-17? This is not a good idea at all. We had a couple of real machines that were submitting results, e.g. Saulius's machines. Even when test failures on win9x are not a criteria for rejecting patches, that must not mean that we become blind on what happens on the win9x side. What seems to happen now is overshooting. + Don't let testbot run patches against win9x anymore -- ok which is quite different from ignoring win9x test failures. + Still have them alive for developers -- great - Drop win9x data from test.winehq.org -- WTF? People are still using many apps written in the win9x era and not all of those have platinum rating. We still need to know how those old systems behaved differently. Regards, Jörg Höhle

Dec. 22, 2010

Re: [PATCH 4/6] urlmon: Add some error handling to the http protocol.

by jacek＠codeweavers.com

On 12/22/10 2:17 PM, David Hedberg wrote: > Hi Jacek, > On Wed, Dec 22, 2010 at 13:07, Jacek Caban<jacek(a)codeweavers.com> wrote: >>> + if(security_problem) { >>> + hres = IUnknown_QueryService((IUnknown*)This->base.protocol_sink, >> You shouldn't need the cast here. > I get warnings if I leave the casts out though, and I can't see any obvious problem with the declarations. Any ideas? I've read your patch wrongly, sorry. Please avoid using IUnknown_QueryService. It's an ugly named helper function and it causes confusions like mine. Explicitly QIing for IServiceProvider and calling QueryService on it is the way to go. Cheers, Jacek

Dec. 22, 2010

Re: [PATCH 2/2] shell32: Add IInputObject stub to IExplorerBrowser.

by Alexandre Julliard

David Hedberg <david.hedberg(a)gmail.com> writes: > + WPARAM supported_key_accels[] = { /* Win7 */ > + VK_RETURN, VK_PRIOR, VK_NEXT, VK_END, VK_HOME, VK_LEFT, VK_UP, VK_RIGHT, > + VK_DOWN, VK_F10, 0 }; > + MSG msg_a = { > + hwnd, > + supported_key_accels[1], This doesn't make sense, you should be passing a keyboard message here. -- Alexandre Julliard julliard(a)winehq.org

Dec. 22, 2010

Re: [PATCH 4/6] urlmon: Add some error handling to the http protocol.

by David Hedberg

Hi Jacek, On Wed, Dec 22, 2010 at 13:07, Jacek Caban <jacek(a)codeweavers.com> wrote: >> + if(security_problem) { >> + hres = IUnknown_QueryService((IUnknown*)This->base.protocol_sink, > > You shouldn't need the cast here. > I get warnings if I leave the casts out though, and I can't see any obvious problem with the declarations. Any ideas? > Please add some real tests. At least a connection to an invalid certificate > should be easy to achieve. > I'll look into adding some better tests. Thanks, David

Dec. 22, 2010

Shell.Application

by Alexander Morozov

Some Windows programs use Shell.Application object (sample: http://bugs.winehq.org/show_bug.cgi?id=8987) This object has IShellDispatch, IShellDispatch2, IShellDispatch3, ... interfaces (http://www.com.it-berater.org/COM/windows_shell/interfaces/IShellDispatch.h…) If IShellDispatch is sufficient for some application and I am going to add its declaration should I add IShellDispatch2, 3, ..., 5 in addition?

Dec. 22, 2010