June 2004 - Wine-Devel - list.winehq.org

Re: docu update
by Ivan June 19, 2004

June 19, 2004

> (a) and (b) can be solved by WineHQ providing its own distro-neutral, run > anywhere binary packages. This isn't easy to do, and it means you have to A) Leave out some features (mime types, menus, that most distros handle in a different way) or B) package menu/mime stuff for all distros, meaning the user downloads a big binary but will only need part of it. Also, it means we have it compiled for only one architecture. But not all distros use the same one. For example, all software on Mandrake linux is built for i586, and I don't see why that should change. Also how can you have one binary work on platforms that are so different? For example, some users will still use (and want to use) systems that use glibc 2.2, so what do you do, ship 2 binaries for the different versions of glibc? Also, lots of users like to install software using the native packaging system of their distro, infect CodeWeavers now provides native Debs and RPMs of crossover, or at least it did at some point (Not sure if this is still true). Now, if wine was shipped on a CD (Could be done for 1.0 that won't change for some time), we could just have an installer that detected the distro, and installed the appropriate files, but if users have to download (Remember many users still use 56k modems, and that will stay true for quite some time) they only want to have what they really need. I think we won't be able to have a single binary that works on all distros, they are all just to different, for example wine currently doesn't work on FC2 at all, but works perfectly on other distros. Also some distros are built for i386, others for i586 and others for i686, how can you have one binary for all, force them to all use i386 (That will be about 30% slower that a i586 build)? Sure, it may be possible to build one binary and run it anywhere, but in most cases it wouldn't run as well (and as fast) as a build done natively on the distro. Ivan.

2 1

Yum repository for wine
by Leonardo Quijano Vincenzi June 19, 2004

June 19, 2004

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I can't help but notice that there's no Yum repository for Wine. Or at least I haven't found it yet ;). So, would it be too hard to setup one? In case anyone needs instructions, there is a tutorial here: http://fedoranews.org/alex/tutorial/yum/ Leonardo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFA1JEnnuk7PwJlZIURArRtAKC0tlERDAHam+J5TbOTclwSZS/aXgCgsQl0 3IwAd4mFH4JLFx4aOcEy7pk= =Cwf0 -----END PGP SIGNATURE-----

2 1

Investigating a crash at startup
by Phil Krylov June 19, 2004

June 19, 2004

Hello, I have a program here (IBM Translation Manager v.6.0.4) which crashes wine at startup. The program loads a DLL, and Wine starts importing this DLL's imports from kernel32.dll. It crashes on the first import in dlls/ntdll/loader.c:453, which says: thunk_list->u1.Function = (PDWORD)find_named_export( imp_mod, exports, exp_size, pe_name->Name, pe_name->Hint ); This causes an exception because thunk_list happens to be located in .rdata section of the DLL, which is readonly. Currently I have hacked this around by making all PE sections read-write in map_image() in dlls/ntdll/virtual.c, and the program works. If a Wine guru would like to investigate this problem, I can give any support (e.g., ssh access to my computer with the program). If not - I will be using this hacked version of Wine. -- Best regards, Phil mailto:phil(a)newstar.rinet.ru

2 4

Fax Message Received
by Twickline June 19, 2004

June 19, 2004

1 0

Re: Thanks :)
by Twickline June 18, 2004

June 18, 2004

1 0

Forum notify
by Johane June 18, 2004

June 18, 2004

1 0

Where does richedit20.dll fit in the to-do list?
by Dan Kegel June 18, 2004

June 18, 2004

I keep running into apps that won't run without richedit20.dll, yet I can't see any mention of that DLL in the wine 0.9 or wine 1.0 tasklists. Surely it's important enough to merit at least a mention in the wine 1.0 tasklist? - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

3 3

font problems with "Hello" application
by Matt Beaumont June 18, 2004

June 18, 2004

There is a font that displays _extremely_ poorly in the tooltips for the "Hello" photo-sharing application (<http://www.hello.com/>, harmless(?) registration required for download). I'm running the 6/15 wine source package, installed with "make install". Hello wants riched20.dll before it will do anything useful; this can be acquired at <http://www.dll-files.com/dllindex/dll-files.shtml?riched20>. The problem can be reproduced by bringing up a tooltip for one of the checkboxes on the login screen; it shows a completely unreadable string. I've been looking at the output from the font and tooltip WINEDEBUG channels, and haven't found anything screamingly obvious. Does anybody have a suggestion for other channels to look at, or places to look in the source? Thanks, Matt

2 3

Re: docu update
by Ivan June 18, 2004

June 18, 2004

> I want to be able to say to a user who reported a bug "please try latest CVS > and confirm that it is fixed" without having to tell them about > configure or LD_LIBRARY_PATH or whatever If they've reported a bug, and you've told them to try the CVS, then it's not a configuration problem, so configure has been run and LD_LIBRARY_PATH is set correctly. Apart from this, all this sort of stuff can be done in the build system anyway. Also removing wineinstall is on the todo, and it does nothing that can't be handled (more transparently) elsewhere. Ivan.

1 0

Re: docu update
by Ivan June 18, 2004

June 18, 2004

> wineinstall is not out of date, it still works fine, I don't see any > reason to remove it from the doc. I see no reason to leave it, it's now as if it did anything essential for wine. Usually things are first removed from wine, and then from the documentation, this causes an afoul lot of confusion, because people tend to really trust the docs. So it would be a good idea to remove the docs about wineinstall before we remove wineinstall, and as wine can be built and run perfectly well without it I don't see why we should keep it in the docs. Also the documentation about the config will have to be re-written, as soon everything will be done with winecfg of regedit, and as that will take a non trivial amount of time, it's a good idea to start well in advance, so the docs aren't behind wine when the switch is done. Ivan.

1 0