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

Re: Internet Explorer 6 Installer script

by Adam Babcock

Adam Babcock wrote: > Hajime Segawa wrote: > >>I wrote a tiny shell script that can install IE6sp1 and WMP7. >>I hope this script can help you. >>RealPlayer 10, MSN Messenger 6.4, Yahoo!Japan Messenger seem to work >>with this configuration. >>http://sidenet.ddo.jp/winetips/config.html >> >>I took some screenshots. >>http://sidenet.ddo.jp/winetips/files/ >> >> > > > Interesting work, however it is failing on the 'which wine' > > Ignore that message, I didn't intend on sending already, I solved that, stupid mistake on my end.

Nov. 26, 2004

Re: Internet Explorer 6 Installer script

by Adam Babcock

Hajime Segawa wrote: > I wrote a tiny shell script that can install IE6sp1 and WMP7. > I hope this script can help you. > RealPlayer 10, MSN Messenger 6.4, Yahoo!Japan Messenger seem to work > with this configuration. > http://sidenet.ddo.jp/winetips/config.html > > I took some screenshots. > http://sidenet.ddo.jp/winetips/files/ > > Interesting work, however it is failing on the 'which wine'

Nov. 26, 2004

Re: dlls/mscms/profile.c breakage

by Gerald Pfeifer

On Thu, 25 Nov 2004, Hans Leidekker wrote: >> lcms 1.09 as standard, you can't require to update it for all users if >> the replacement version (1.13 or so) is not the standard one for that >> distro. > No, I'm not requiring or forcing users to upgrade. I'm asking packagers > (specifically those that target multiple distro's/OS'es or versions with > a single package) to build with the most recent headers. Because that > will result in the most functional Wine if recent lcms is available on > a users' system. I actually think we are in violent agreement, even if it might not seem so at first sight. ;-) There seem to be two issues here: 1) You argue that packagers should use a recent version if possible, and I believe nobody objected. 2) On the other hand, there are also people compiling a FreeBSD port by themselves, or just using CVS Wine. For these, ALSA approach that Francois suggested seems to be a nice solution: if test -z "$ALSALIBS" then echo "*** Alsa not detected. The winealsa.drv.so driver will be a dummy." fi I certainly do not have a problem updating to a later version of lcms. However, I'm also getting support inquiries from those users described under item 2) above; that's why I'd appreciate a more gracious failure mode. ;-) > [FreeBSD Ports Collection] > Don't they automatically fetch the latest version in that case? Or is > the ports collection versioned and tied to the FreeBSD main version? No, users won't automatically fetch the latest version of everything. The Ports Collection itself is not tied to the FreeBSD main version, but a surprisingly large number of users still does not seem to have cheap/reliable Internet access and the use of CD-ROMs (which contain the version of the Ports Collection at the time of the FreeBSD release) is wide spread. Users might update to a more recent version of a specific port like Wine, but not necessarily their whole collection of ports. Gerald

Nov. 25, 2004

Re: profiling GTA4. question about polling

by Raphael

Hi On Thursday 25 November 2004 20:43, Brian Gunlogson wrote: > The patch you gave me is too incomplete to run GTA :( :( > I can start a game, but once the loading screen says it is done, the game > crashes. Looked at the console, it says, "fixme:drawStridedFast TODO". Well the only way to have this TODO its when your card support vertex blending (and i'm happy to found people who have cards that support this extension :) ) > The crash happens at the end of drawStridedFast(), inside glDrawElements(). Really strange, and when you export WINED3D_VBO_DISABLE=1 it crash ? > Your patch will really speed things up when it is finished. Yes, its work on progress But i have a very strange problem who i can't understand at all :( > In a fresh CVS tree, I disabled drawStridedSlow and applied 2 polling > patches submitted to wine-patches. > The game works almost as fast as in Windows!! Good news :) > Brian G. > Regards, Raphael

Nov. 25, 2004

Re: Major Winelib Problems

by Steven Edwards

Hi Sam, --- Sam Lauber <sam124(a)operamail.com> wrote: > I followed the tutorial for Winelib on my Linux system, building > notepad. I examined the file "./notepad2" with readelf, and it said > "Not an ELF file", and I do not have an a.out system. I opened it > with my text editor (attached is the text I saw) and I was > disappointed. Instead of a real "port", it was just a shell script > that launches wine on a Windows program encapsulated in a ELF shared > object file. I'm not happy. Thats the way it works. The idea of Winelib is that you can use it as a step to port your application to Linux. Now that you have a the app as a ELF binary you can use dlopen and friends to open Unix libs and replace parts of Linux toolkits. Winelib allows you to do this in steps by starting with things like use Unix sockets vs Winsock or start to replace filedialogs with GTK filedialogs. Thanks Steven __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com

Nov. 25, 2004

Re: Major Winelib Problems

by Vincent Béron

Le jeu 25/11/2004 à 14:34, Dimitrie O. Paun a écrit : > On Thu, Nov 25, 2004 at 08:04:48PM +0100, Sam Lauber wrote: > > I followed the tutorial for Winelib on my Linux system, building notepad. I examined the file "./notepad2" with readelf, and it said "Not an ELF file", and I do not have an a.out system. I opened it with my text editor (attached is the text I saw) and I was disappointed. Instead of a real "port", it was just a shell script that launches wine on a Windows program encapsulated in a ELF shared object file. I'm not happy. > > Sorry, but that's how things are. It is pretty much a "real" port (whatever > that means), even though it's launched through a script. It's not pretty, > but because of the different binary env in Linux and Windows, that's the > way it has to be. I just discussed this on IRC with Mike, and the direction we briefly looked at involved transforming wineapplauncher to a C program which could then be the entry point for .exe.so files produced via winegcc, the same way libc.so can be executed (and gives basic info on the included libs, copyright info, etc.). That leaves winewrapper to take care of (to launch from the Wine source tree). I guess mucking around the .exe.so while "make install" is out of the question? :) Vincent

Nov. 25, 2004

Re: profiling GTA4. question about polling

by Brian Gunlogson

The patch you gave me is too incomplete to run GTA :( I can start a game, but once the loading screen says it is done, the game crashes. Looked at the console, it says, "fixme:drawStridedFast TODO". The crash happens at the end of drawStridedFast(), inside glDrawElements(). Your patch will really speed things up when it is finished. In a fresh CVS tree, I disabled drawStridedSlow and applied 2 polling patches submitted to wine-patches. The game works almost as fast as in Windows!! Brian G. --- Raphael <fenix(a)club-internet.fr> wrote: > Here is it. > > But i have some problems with hardware vertex buffers (using vbo extension) > i have some 'transparent" objects (ie graphics bugs) > Anyway, If you encounter same problems you can uncomment this line: > //useSoft |= (0 != (Usage & D3DUSAGE_WRITEONLY)); > (dls/d3d8/vertexbuffer.c at line 71) __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail

Nov. 25, 2004

Re: Major Winelib Problems

by Dimitrie O. Paun

On Thu, Nov 25, 2004 at 07:24:08PM +0000, Mike Hearn wrote: > I think what you mean is, you wanted to be able to type: > > ./my-program > > and have it launch like a "normal" app. Which is exactly what the current Winelib toolchain gives you. -- Dimi.

Nov. 25, 2004

Re: Major Winelib Problems

by Dimitrie O. Paun

On Thu, Nov 25, 2004 at 08:04:48PM +0100, Sam Lauber wrote: > I followed the tutorial for Winelib on my Linux system, building notepad. I examined the file "./notepad2" with readelf, and it said "Not an ELF file", and I do not have an a.out system. I opened it with my text editor (attached is the text I saw) and I was disappointed. Instead of a real "port", it was just a shell script that launches wine on a Windows program encapsulated in a ELF shared object file. I'm not happy. Sorry, but that's how things are. It is pretty much a "real" port (whatever that means), even though it's launched through a script. It's not pretty, but because of the different binary env in Linux and Windows, that's the way it has to be. -- Dimi.

Nov. 25, 2004

Re: Major Winelib Problems

by Mike Hearn

On Thu, 25 Nov 2004 20:04:48 +0100, Sam Lauber wrote: > I followed the tutorial for Winelib on my Linux system, building > notepad. I examined the file "./notepad2" with readelf, and it said "Not > an ELF file", and I do not have an a.out system. I opened it with my > text editor (attached is the text I saw) and I was disappointed. Instead > of a real "port", it was just a shell script that launches wine on a > Windows program encapsulated in a ELF shared object file. I'm not happy. What did you expect? Winelib can't magically make a Windows program a non Windows program. It still needs CreateWindowEx and friends to be present. I think what you mean is, you wanted to be able to type: ./my-program and have it launch like a "normal" app. You don't like the aesthetics of running "wine my-program.exe.so". This is natural, I think most people go through it (me too) but it's done for sound technical reasons and there's really no disadvantage. The reason to do a Winelib app is to either: a) Port to another CPU arch b) Allow usage of native ELF APIs c) Both I'm afraid whichever way you cut it, if a program is using Win32 it will need Wine to be present. thanks -mike

Nov. 25, 2004