September 2007 - Wine-Devel

Re: Wine application compatibility

by TheBlunderbuss

Roderick Colenbrander wrote: >> On Saturday 29 September 2007 10:34:19 am Roderick Colenbrander wrote: >> >>> Hi, >>> >>> Every Wine release more and more programs start to work on Wine. A >>> >> serious >> >>> problem is that not all programs can work out of the box. Some games for >>> instance need the windows version to be set to Windows 95 or it will >>> >> crash. >> >>> Other games like Medal of Honour need their OpenGL extension string >>> >> trimmed >> >>> to get it to work on cards which support a lot of OpenGL extensions. >>> >> There >> >>> are dozens of more examples like that. >>> >> The majority of Wine's options are settable via the registry and can be >> given >> app-specific overrides. So how about wineprefixcreate creates registry >> entries for specific apps that are known to need special settings? >> >> Just need to be really really careful that an app needs the change, and >> that >> it's not due to a bug in Wine or something. >> > > Yep wineprefixcreate should handle this and I think in combination with winecfg. One issue that I see is that an executable name is not unique. In case of games if multiple ones are using 'game.exe' then there is a problem. For AppDefaults you can type the whole path but you don't know that in advance. > > I fear that for executable some sort of md5sum needs to be stored (there might be something like that already in the app in the form of a product code or so) for purposes like this. We should check how microsoft handles this. Anyway I think that support in the wine loader is needed. > > Roderick > I agree on the checksum. There could be multiple versions of the same program, even, as with Steam's case. How would the registry fix work with wineprefixcreate? Would the user checksum the target program, and then pass as an argument to wineprefixcreate? I think it would be best to have a GUI element using winecfg, to tell the user if there are fixes to be applied.

Sept. 30, 2007

[PATCH] Fix Ugly borders around undecorated windows in Gnome

by Matthew D'Asaro

This is my first attempt at submitting a patch to WINE, so please excuse me if I have broken any conventions or am going through the wrong channel. As it currently stands, wine is setting the 'MWM_DECOR_BORDER' hint on managed but undecorated windows, such as iTunes, or Winamp. This does not cause problems in KDE, but in Gnome it puts a gray border around such windows. Not setting this hint does not seem to cause problems in KDE and fixes the problem in Gnome. A patch to do just that is attached. Comments? -Matthew D'Asaro

Sept. 30, 2007

Re: New winetricks: 'volnum' command to work around bug 5351, new gecko

by Dan Kegel

On 9/30/07, Hans Leidekker <hans(a)it.vu.nl> wrote: > Renaming drive_c is more intrusive, I wouldn't do it while Wine is > running. Absolutely. I suppose I should put in a warning to that effect.

Sept. 30, 2007

Re: New winetricks: 'volnum' command to work around bug 5351, new gecko

by Hans Leidekker

On Sunday 30 September 2007 17:00:38 Dan Kegel wrote: > > All installers I have seen that require the special volume name also > > have a workaround in the form of a command line switch /x which allows > > you to specify a destination folder for extraction. Look at the msxml4 > > verb for an example. > > Good point, and I've updated the comments in the volnum verb. > Renaming drive_c is more convenient than using /x sometimes, so > the volnum verb should probably stay. Renaming drive_c is more intrusive, I wouldn't do it while Wine is running. And running wineserver -k beforehand precludes some useful testing scenarios. -Hans

Sept. 30, 2007

Weekly Newsletter

by EA Durbin

Who maintains the weekly newsletter? I noticed it hasn't been updated since May. _________________________________________________________________ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx…

Sept. 30, 2007

Re: New winetricks: 'volnum' command to work around bug 5351, new gecko

by Dan Kegel

On 9/30/07, Hans Leidekker <hans(a)it.vu.nl> wrote: > Hold on a sec... > > All installers I have seen that require the special volume name also > have a workaround in the form of a command line switch /x which allows > you to specify a destination folder for extraction. Look at the msxml4 > verb for an example. Good point, and I've updated the comments in the volnum verb. Renaming drive_c is more convenient than using /x sometimes, so the volnum verb should probably stay. > Attached patch fixes a 404 in the liberation verb. Applied, thanks. Updated winetricks at the usual place, http://kegel.com/wine/winetricks - Dan

Sept. 30, 2007

Re: Wine application compatibility

by Roderick Colenbrander

> On Saturday 29 September 2007 10:34:19 am Roderick Colenbrander wrote: > > Hi, > > > > Every Wine release more and more programs start to work on Wine. A > serious > > problem is that not all programs can work out of the box. Some games for > > instance need the windows version to be set to Windows 95 or it will > crash. > > Other games like Medal of Honour need their OpenGL extension string > trimmed > > to get it to work on cards which support a lot of OpenGL extensions. > There > > are dozens of more examples like that. > > The majority of Wine's options are settable via the registry and can be > given > app-specific overrides. So how about wineprefixcreate creates registry > entries for specific apps that are known to need special settings? > > Just need to be really really careful that an app needs the change, and > that > it's not due to a bug in Wine or something. Yep wineprefixcreate should handle this and I think in combination with winecfg. One issue that I see is that an executable name is not unique. In case of games if multiple ones are using 'game.exe' then there is a problem. For AppDefaults you can type the whole path but you don't know that in advance. I fear that for executable some sort of md5sum needs to be stored (there might be something like that already in the app in the form of a product code or so) for purposes like this. We should check how microsoft handles this. Anyway I think that support in the wine loader is needed. Roderick -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

Sept. 30, 2007

Re: winex11.drv: possible fix for thick border around utility window in DatePicker

by Dmitry Timoshkov

<a_villacis(a)palosanto.com> wrote: > It seems that, when presented with a combination of WS_POPUP and WS_BORDER > without any extended style, the window is supposed to be shown with a thin > border (a 1px border in Windows). I still have not found a window style that > makes a X window show a thin border, and the nearest thing in looks is no > border at all. Please comment on this patch, as I don't think it is exactly > sane. > > Changelog: > * Deactivate WS_BORDER when present with WS_POPUP > - else if (style & WS_BORDER) mwm_hints.decorations |= MWM_DECOR_BORDER; > + else if ((style & WS_BORDER) && !(style & WS_POPUP)) mwm_hints.decorations |= MWM_DECOR_BORDER; This looks like a bug in Metacity, I don't see why it adds "(disabled) decorations" when only asked for MWM_DECOR_BORDER. On the other hand we already check for WS_CHILD|WS_POPUP and don't add MWM_DECOR_BORDER if any of that styles present, so perhaps your change is in that direction, and should be made to also check for both WS_CHILD|WS_POPUP. Probably it's also worth to file a bug to metacity bugzilla. -- Dmitry.

Sept. 30, 2007

Re: New winetricks: 'volnum' command to work around bug 5351, new gecko

by Hans Leidekker

On Sunday 30 September 2007 04:53:56 Dan Kegel wrote: > Another month, another winetricks. This updates the gecko installed > by winetricks to 0.1.0, and adds a 'volnum' verb to let you run installers > that complain "Unable to find a volume for file extraction." And it > has a few other cleanups. Hold on a sec... All installers I have seen that require the special volume name also have a workaround in the form of a command line switch /x which allows you to specify a destination folder for extraction. Look at the msxml4 verb for an example. Attached patch fixes a 404 in the liberation verb. -Hans

Sept. 30, 2007

Re: Wine application compatibility

by Chris Robinson

On Saturday 29 September 2007 10:34:19 am Roderick Colenbrander wrote: > Hi, > > Every Wine release more and more programs start to work on Wine. A serious > problem is that not all programs can work out of the box. Some games for > instance need the windows version to be set to Windows 95 or it will crash. > Other games like Medal of Honour need their OpenGL extension string trimmed > to get it to work on cards which support a lot of OpenGL extensions. There > are dozens of more examples like that. The majority of Wine's options are settable via the registry and can be given app-specific overrides. So how about wineprefixcreate creates registry entries for specific apps that are known to need special settings? Just need to be really really careful that an app needs the change, and that it's not due to a bug in Wine or something.

Sept. 30, 2007