September 2007 - Wine-Devel

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

by Dan Kegel

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. As usual, it's at http://kegel.com/wine/winetricks - Dan revision 1.33 date: 2007/09/30 02:47:13; author: dank; state: Exp; lines: +18 -0 Added volnum verb to work around bug 5351 ---------------------------- revision 1.32 date: 2007/09/30 02:30:33; author: dank; state: Exp; lines: +15 -12 Minor janitorial cleanup ---------------------------- revision 1.31 date: 2007/09/30 02:26:40; author: dank; state: Exp; lines: +11 -9 Detlef Riekenberg reported that gecko was using old version. This fixes it. ---------------------------- revision 1.30 date: 2007/09/30 00:03:03; author: dank; state: Exp; lines: +14 -0 Sanity checking by Lei ---------------------------- revision 1.29 date: 2007/09/30 00:00:55; author: dank; state: Exp; lines: +1 -1 Fix typo introduced by last change ---------------------------- revision 1.28 date: 2007/09/29 23:21:33; author: dank; state: Exp; lines: +19 -38 Localized paths cleanup from Detlef Riekenberg -- Wine for Windows ISVs: http://kegel.com/wine/isv

Sept. 30, 2007

Re: The Spouse Test

by Jesse Allen

On 9/23/07, Dan Kegel <dank(a)kegel.com> wrote: > When will Wine be good enough for the average person to use? > One test is, "Is it good enough to let your spouse migrate to Linux > from Windows?". > My wife's must-have app list is roughly > > Microsoft Office '97 > Adobe Photoshop Elements 1 > Ulead PhotoImpact > Macromedia Dreamweaver 8 > Musicmatch Jukebox 8 > FamilyTreeMaker 2006 > > And you know what? All of those basically work > except for Photoshop Elements. They need some > cosmetic work, and a native DLL or two, and probably a few > obscure bugfixes, but I think that's it. > (I didn't test Office '97, since I expect she'll be using Crossover > for that, as Codeweavers tests that app pretty well.) > > It's possible that by this time next year Wine will pass this test for me. > - Dan > > > I suppose this past week Wine has passed the "poor student test" for me. I needed to make circuit diagrams and have a windows 95 program called circuit maker provided by the school. Well I had a backup of my git tree on my laptop from a few weeks ago, compiled it, ran wineprefixcreate, installed the program, and created the circuit diagram all without leaving the library! I've already used it again to simulate a circuit and do another report. Now if only I could get a better internet connection. Jesse

Sept. 30, 2007

Re: Broken patches since 0.9.45 (problem with missing binary files)

by Victor

On Saturday 29 September 2007 17:36:37 you wrote: > The patches are fine, but they are in git format, so you need to use > git-apply instead of patch to apply the binary changes properly. Thanks for your reply. I've fixed the script, now everything works without problems. Sorry for the "false alarm". -- With best regards, Victor Eremin (ErV2005(a)rambler.ru)

Sept. 30, 2007

Re: Wine application compatibility

by Rob

I understand there are many apps that need more sophisticated tweaking than the average wine user, even a contributor to the appdb, would be able to do. There are also quite a number of far less sophisticated tweaks, like needing to be run in win2k and not winXP for example, that are equally critical to getting application Y to run. Why not have them all in the same place? The open source model: I'll add what I know and can, you add what you know and can, and together hopefully all of us will be able to add enough that it's a complete list of tweaks. There's always the question of dealing with fools and malicious people, and I believe that's what you were getting at when you spoke of 'filtering' the repository. Wouldn't the wiki model should work for that? - you have to register to update, and you'll be banned if you hurt the project. It seems to me that there are enough contributors to appdb to support a system like this, do you agree? Rob Roderick Colenbrander wrote: >> This sounds like the kind of thing that the devs should work to provide >> the functionality for, but >> that the user base should actually maintain. For example, appdb could >> become a place where users >> could suggest, test, and finalize said tweaks for each application. There >> would then be a way for >> wine to use a small 'database' of that information which could be packed >> with each release or >> downloaded from the appdb site (both would seem the best way to go with >> that). The devs aren't >> responsible for maintaining the list of tweaks (that's a waste of their >> time), but the users can >> still benefit from it. >> >> Rob > > It could be maintained at lets say appdb but the problem is filtering on what should be in the database and what not. Just a setting to get a program running or a dll override isn't. It is for programs which really need fixups like the ones I described. Not everyone can maintain such a list. > > Roderick

Sept. 29, 2007

Re: Wine application compatibility

by Rob

This sounds like the kind of thing that the devs should work to provide the functionality for, but that the user base should actually maintain. For example, appdb could become a place where users could suggest, test, and finalize said tweaks for each application. There would then be a way for wine to use a small 'database' of that information which could be packed with each release or downloaded from the appdb site (both would seem the best way to go with that). The devs aren't responsible for maintaining the list of tweaks (that's a waste of their time), but the users can still benefit from it. Rob 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. > > Microsoft is having similar troubles and since Windows 2000 they provide appcompat stuff for windows (in WinXP/Vista it is a default feature). It basically works on a database which is used somehow at program startup and which then applies 'fixes' like 'setting the windows version', patching function calls and more. See for instance > http://technet.microsoft.com/en-us/library/bb457032.aspx for more info and pay attention to http://technet.microsoft.com/en-us/library/bb457032.apcpxp06_big(en-us,tech… which shows a part of the list and the scope of it. > > I think we have reached a point in Wine where we might need something similar :( Our compatibility seems to be bigger than XP/Vista so we might not need much. Perhaps we need to maintain some file which applies really needed fixups. It should be merged into the registry using wineprefixcreate and the database can be checked using winecfg. It would use normal AppDefaults. > > What do you guys think about such a thing? I don't like it at all but I fear it is really needed. If we would add such I'm not sure if we are allowed to dump microsoft their database, looking at it might be something differently. > > It might be a good topic for WineConf. > > Regards, > Roderick Colenbrander

Sept. 29, 2007

Re: Wine application compatibility

by Roderick Colenbrander

> This sounds like the kind of thing that the devs should work to provide > the functionality for, but > that the user base should actually maintain. For example, appdb could > become a place where users > could suggest, test, and finalize said tweaks for each application. There > would then be a way for > wine to use a small 'database' of that information which could be packed > with each release or > downloaded from the appdb site (both would seem the best way to go with > that). The devs aren't > responsible for maintaining the list of tweaks (that's a waste of their > time), but the users can > still benefit from it. > > Rob It could be maintained at lets say appdb but the problem is filtering on what should be in the database and what not. Just a setting to get a program running or a dll override isn't. It is for programs which really need fixups like the ones I described. Not everyone can maintain such a list. Roderick -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

Sept. 29, 2007

Wine application compatibility

by Roderick Colenbrander

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. Microsoft is having similar troubles and since Windows 2000 they provide appcompat stuff for windows (in WinXP/Vista it is a default feature). It basically works on a database which is used somehow at program startup and which then applies 'fixes' like 'setting the windows version', patching function calls and more. See for instance http://technet.microsoft.com/en-us/library/bb457032.aspx for more info and pay attention to http://technet.microsoft.com/en-us/library/bb457032.apcpxp06_big(en-us,tech… which shows a part of the list and the scope of it. I think we have reached a point in Wine where we might need something similar :( Our compatibility seems to be bigger than XP/Vista so we might not need much. Perhaps we need to maintain some file which applies really needed fixups. It should be merged into the registry using wineprefixcreate and the database can be checked using winecfg. It would use normal AppDefaults. What do you guys think about such a thing? I don't like it at all but I fear it is really needed. If we would add such I'm not sure if we are allowed to dump microsoft their database, looking at it might be something differently. It might be a good topic for WineConf. Regards, Roderick Colenbrander -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

Sept. 29, 2007

Re: version resource for ole2nls.dll

by Dmitry Timoshkov

"Stefan Leichter" <Stefan.Leichter(a)camline.com> wrote: > Ok, looks like i picked a bad example from the wine tree. > +#define WINE_FILEVERSION 2,1,3050,1 > #define WINE_FILEVERSION_STR "2.10.3050.1" Shouldn't it be 2,10,3050,1 ? Also, could you please also fix the place(s) which you took as an example? -- Dmitry.

Sept. 29, 2007

Re: Broken patches since 0.9.45 (problem with missing binary files)

by Alexandre Julliard

Victor <ErV2005(a)rambler.ru> writes: > Can someone fix this problem? (It looks like problem is related to binary > files) It would be great if both patches were fixed and re-uploaded. The patches are fine, but they are in git format, so you need to use git-apply instead of patch to apply the binary changes properly. -- Alexandre Julliard julliard(a)winehq.org

Sept. 29, 2007

Broken patches since 0.9.45 (problem with missing binary files)

by Victor

Hello! It looks like last two patches - wine-0.9.45.diff.bz2 and wine-0.9.46-diff.bz2 are broken. It is not possible to compile wine-0.9.45 (if sources were created by patching 0.9.44 with wine-0.9.45.diff.bz2) due to missing notepad.ico :) : --- make[2]: Leaving directory `/home/erv/distr/wine/wine-0.9.45/programs/net' make[2]: Entering directory `/home/erv/distr/wine/wine-0.9.45/programs/notepad' ../../tools/makedep -C. -S../.. -T../.. -I../../include/msvcrt dialog.c main.c rsrc.rc notepad.ico: No such file or directory notepad.ico was first included from rsrc.rc:47 make[2]: [Makefile] Error 1 (ignored) ../../tools/makedep -C. -S../.. -T../.. -I../../include/msvcrt dialog.c main.c rsrc.rc notepad.ico: No such file or directory notepad.ico was first included from rsrc.rc:47 make[2]: *** [depend] Error 1 make[2]: Leaving directory `/home/erv/distr/wine/wine-0.9.45/programs/notepad' make[1]: *** [notepad/__depend__] Error 2 make[1]: Leaving directory `/home/erv/distr/wine/wine-0.9.45/programs' make: *** [programs/__depend__] Error 2 Compilation failed, aborting install. --- and it isn't possible to compile wine-0.9.46 (created by patching complete 0.9.45 sources with wine-0.9.46.diff.bz2) due to missing c1.bmp in cards.dll: --- make[2]: Leaving directory `/home/erv/distr/wine/wine-0.9.46/dlls/capi2032' make[2]: Entering directory `/home/erv/distr/wine/wine-0.9.46/dlls/cards' ../../tools/makedep -C. -S../.. -T../.. cards.c cards.rc c1.bmp: No such file or directory c1.bmp was first included from cards.rc:23 make[2]: [Makefile] Error 1 (ignored) ../../tools/makedep -C. -S../.. -T../.. cards.c cards.rc c1.bmp: No such file or directory c1.bmp was first included from cards.rc:23 make[2]: *** [depend] Error 1 make[2]: Leaving directory `/home/erv/distr/wine/wine-0.9.46/dlls/cards' make[1]: *** [cards/__depend__] Error 2 make[1]: Leaving directory `/home/erv/distr/wine/wine-0.9.46/dlls' make: *** [dlls/__depend__] Error 2 Compilation failed, aborting install. --- And here is a script I've been using to unpack patches (it should be placed in dir containing wine-0.9.30.tar.bz2 and patches (0.9.31, 0.9.32, etc) in *.diff.bz2 format : --- #!/bin/sh echo unpacking wine BUILD=30 BASE=$BUILD WINE='wine-0.9' tar -xvvjf $WINE.$BUILD.tar.bz2 && cd $WINE BUILD=$(($BUILD+1)) cd "$WINE.$BASE" while [ -f ../$WINE.$BUILD.diff.bz2 ]; do echo $WINE.$BUILD bzcat ../$WINE.$BUILD.diff.bz2|patch -p1 && BUILD=$(($BUILD+1)) done cd .. mv $WINE.$BASE $WINE.$(($BUILD-1)) --- Can someone fix this problem? (It looks like problem is related to binary files) It would be great if both patches were fixed and re-uploaded. Thanks. -- Victor Eremin (ErV2005(a)rambler.ru)

Sept. 29, 2007