Hi, Which of the various Wine downloads on the download page should I get for PCLinuxOS? Thanks. Stephen Carter
Hi, If PCLinuxOS is still building their work off of Mandriva, then you could probably get away with using the Mandriva 2008 binary. No guarantees there, but if its still the case, it *should* work. However, also building and installing from source would work. -Zac stevecarter wrote:> Hi, > > Which of the various Wine downloads on the download page should I get for PCLinuxOS? > > Thanks. > > Stephen Carter > > > > >
Zac Brown wrote:> > > However, also building and installing from source would work. > >Zac, Thanks for your speedy reply. However, for a very newcomer to Linux, I have to confess that I would not have the foggiest how to build and install anything from source. I am not even sure I understand what all that means! :( Peace and all good, Stephen Carter
Zac Brown wrote:> > In this case, to play it safe, it looks like PCLinuxOS has their own version of > wine built and ready. It won't be the most recent version but it'll be a working > version of wine that you can install with minimal friction.Zac, Yes indeed. Their version is 0.9.58 and, as far as I can tell, there is no support for Windows programs that need .NET framework present. This was the (unstated) reason behind my original request. Hey, ho - you can't win 'em all! 8) Peace and all good. Stephen Carter
Zac Brown wrote:> If this is what you're interested in, I would be willing to detail that process > by installing and building wine myself and then writing a howto for it. > > Let me know if that suits you better and I'll work on that later today. > >Zac, That is a tremendous gift that you are offering, and I would be thrilled to receive it. Thank you. Best regards, Stephen Carter
> If this is what you're interested in, I would be willing to detail that process > by installing and building wine myself and then writing a howto for it. > > ... > > -Zac >Zac, I'd be interested in that, too. I think lots of people would be. Are you thinking of building, and a Howto, for Stephen and PCLinuxOS? Or is building from source more or less the same for every distribution? I use Debian Etch, but more or less in the same position as Stephen. I looked at the Wine page talking about building from source, but was put off by the number of separate things that it talked about checking first - and, as he says, didn't really know what I might be looking at. I'd certainly like to try rc4 - I've hit problems running Office 97 with VBA under 0.9.58, and even with rc2 - but rc2 is the latest Debian build I've been able to find. ('Ovek' built that and posted it on his website). Echoing what Stephen already said, I think your offer is really helpful, and I'd like to try your Howto for PCLinuxOS and see how far I can get on Debian with it. I'll certainly post back some experience. regards, Island
Zac: I don't know about Steve, but since I haven't found a version newer than 0.9.53 for the Tiger (Mac OSX) platform, I'd be interested in a how-to on compiling a newer version.... :-) On 6/11/08 wine-users-request at winehq.org wrote:> Message: 2 > Date: Wed, 11 Jun 2008 09:42:06 -0700 > From: Zac Brown <zac at zacbrown.org> > Subject: Re: [Wine] Which Wine Download? > To: wine-users at winehq.org > Message-ID: <4850005E.8020700 at zacbrown.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > If this is what you're interested in, I would be willing to detail that process > by installing and building wine myself and then writing a howto for it. > > Let me know if that suits you better and I'll work on that later today. > > -Zac > > > stevecarter wrote: > >> > Zac Brown wrote: >> >>> >> In this case, to play it safe, it looks like PCLinuxOS has their own version of >>> >> wine built and ready. It won't be the most recent version but it'll be a working >>> >> version of wine that you can install with minimal friction. >>> >> > >> > >> > Zac, >> > >> > Yes indeed. Their version is 0.9.58 and, as far as I can tell, there is no support for Windows programs that need .NET framework present. >> > >> > This was the (unstated) reason behind my original request. >> > >> > Hey, ho - you can't win 'em all! 8) >> > >> > Peace and all good. >> > >> > Stephen Carter
Zac Brown wrote:> > You can try one of Dan's scripts. Even though they're for Ubuntu, it might work. > > For Debian Etch, you'll probably want something like Dan's Dapper script, found here: http://kegel.com/wine/dapper.sh > > I give no guarantees that it will work, but its worth a shot. > >I'd missed that work, hadn't realised Dan had done these scripts. Perfect starting point and, hopefully, not too dissimilar. I'll post back some experience. Zac, thanks for the link. Zac Brown wrote:> > If you're willing to wait a bit, I will put Debian Etch/Lenny/Sid on my list of distros to build a dependency script for. > >Zac, that really would be great, and popular, too, I'll bet. I'm up for just trying anyway, using that Dapper script as a guide. I thought I might cross-check what it does (if I can deduce that) with the guidance in the Wine notes page. You just learn more, having a go, even when it ends in tears. And when it does, I'll have a second shot, with your scripts. Actually, I'd like to run them anyway if you do them, and let you know how straightforward it seemed. I've two machines I can try it on, so I'll leave one untouched for now. Thanks again for the suggestions. And what a useful thread, all down to Stephen for asking in the first place. regards, Island
Zac, Thanks for your message and for all your skill so willingly shared. I followed the instructions that came with the script and let the machine chug on for what seemed like ages, downloading a lot of stuff etc. and then working with it to build files etc. When it eventually finished, I am not sure that anything is different. :( wine --version still says it is 0.9.58 as before. I did delete the .wine folder of the original installation before starting the script; should I have done more? Here's hoping I have forgotten something simple. Best regards, Stephen Carter
Zac, Done all that and wine --version now says 1.0-rc4 However (showing my ignorance) there are no items in the PCLinuxOS menus, so I don't know how to configure it. Once again, have I missed something important? Peace and all good. Stephen Carter
Zac, Found winecfg before you replied. About the menu thing; that's cool - I'll see what happens when I install a program. I'll also try the MS .NET framework stuff to see if that will now work. Thanks again. Best regards. Stephen Carter
Hi Zac, I'm back again with ongoing problems. I have successfully installed the 1.0-rc4 version of Wine according to your script. I have installed a simple Windows program (no .NET of anything like that) and the icon is in the menu and on the Desktop. However, when I try to launch it the "Eggtimer" rotates for a short while but then nothing else happens. How do I find out what has gone wrong? Thanks Stephen Carter PS - Do I need to change the subject heading?
Hi Zac, It is a genealogy program called Brother's Keeper, and you can get it here: http://www.bkwin.org/bksetupE.EXE Best regards, Stephen Carter
stevecarter wrote:> Hi Zac, > > I'm back again with ongoing problems. > > I have successfully installed the 1.0-rc4 version of Wine according to your script. > > I have installed a simple Windows program (no .NET of anything like that) and the icon is in the menu and on the Desktop. > > However, when I try to launch it the "Eggtimer" rotates for a short while but then nothing else happens. > > How do I find out what has gone wrong? > > Thanks > > Stephen Carter > > PS - Do I need to change the subject heading?Hi Stephen, This means the installer worked fine, but the application itself is having problems running under Wine. To know what error messages it sends, you must cd to the directory which you installed it, probably "~/.wine/drive_c/Program Files/some folder" and then run the program via the command line as "wine filename.exe" without the quotes. The error messages will be seen in the console. To Zac Brown, My laptop uses Mandriva 2008, and although there are builds for it, I would like to experience how to compile Wine on it. I am more of a Linux user than a dev so these things are not yet within my skill level. If it isn't too much of a bother for you I would love it if you could write me a script like what you did for Stephen. Regards, Bamm
austin987 wrote:> $ wget kegel.com/wine/winetricks > $ sh winetricks vb6runThe full VB6 runtime is overkill. For almost all VB6 programs, you simply copy msvbvm60.dll into the system32 folder and it will work. http://www.dll-files.com/dllindex/dll-files.shtml?msvbvm60
Zac Brown wrote:> Hi Bamm, > > If you can wait till Monday, I'll put it on my list of things to do. I don't > have access to a machine I can run Mandriva on to find the proper packages etc. > > Cheers, > > ZacThanks, Monday will be fine. My daughter will be having her 1st bday party on Sunday so I will not have time to play with Wine on that day. :)
Zac, Bamm and others, Thanks for the advice about the Visual Basic runtime files. It worked! :D What an absolutely superb forum this is; I only wish I had something to give back. Peace and all good. Stephen Carter
stevecarter wrote:> Zac, Bamm and others, > > Thanks for the advice about the Visual Basic runtime files. > > It worked! :D > > What an absolutely superb forum this is; I only wish I had something to give back. > > Peace and all good. > > Stephen Carter > > > > >Triaging is always welcome. So are bug reports :). We always need people to test wine and find the bugs for us. -Zac
Zac, thanks for your guidance. I tried a couple of times to compile &
install on Debian Etch. I tried (more or less) following Dan Kegel's
'dapper script', and your PCLinuxOS script, reaching 'Permission
denied' using either approach. I also tried following the instructions in
the 'readme' file in rc5, and hit the same result.
Just after you posted your suggestions, rc5 was released and so I decided to try
to follow your advice, but with the rc5 release. Downloaded the rc5.bz2 to a
drive with plenty of room, /mnt/hda3, unpacked it into '/wine-1.0.rc5'
(I used this as a sub for the 'cur_wine' value in your script). I
commented out some of your script, and adapted the second part, starting at the
'cd cur_wine' line, and saved it as 'islandwinebuild'.
Here's the output:
island at islandinthesun:/mnt/hda3$ sh islandwinebuild.sh
islandwinebuild.sh: ./configure: /bin/sh: bad interpreter: Permission denied
make: *** No rule to make target `depend'. Stop.
make: *** No rule to make target `install'. Stop.
Done installing, wine is now located in ${INSTALL_PATH}.
The permissions on all the directories and files on /mnt/hda3 are rwx,rwx,rwx,
fully recursively, though I notice that the non-executable files like text docs
are only rw-,rw-,rw-. I used KDE's Konqueror to set these permissions, so
perhaps it decides whether some things are executable or not.
Eager for a really difficult time, I looked at the readme in rc5! Very easy
read, in fact, and makes compiling sound simple. So gave it a try. It advises
running ./tools/wineinstall, Here's the output:
island at islandinthesun:/mnt/hda3$ cd wine-1.0-rc5
island at islandinthesun:/mnt/hda3/wine-1.0-rc5$ ./tools/wineinstall
bash: ./tools/wineinstall: /bin/bash: bad interpreter: Permission denied
island at islandinthesun:/mnt/hda3/wine-1.0-rc5$
Having realised that the readme is not at all ferocious, I plucked up the
courage to read further. It says:
"Run programs as "wine program". For more information and
problem
resolution, read the rest of this file, the Wine man page, and
especially the wealth of information found at http://www.winehq.org."
I did read the rest of the file, but it didn't seem to help with the
permission denied thing. I wondered if the comment meant that, to avoid
'permission denied' problems, I had to log on as 'wine program'
before I could run the ./tools/wineinstall or the ./configure lines etc in your
script. At the moment there is only 'root' and 'island' as
users on this machine.
Nevertheless, I've learnt a lot, and certainly feel confident about having a
another go at compiling. Much thanks to you, though, because your script sets
out the basic sequence we have to go through, and the readme adds useful
details.
regards, Island
Island wrote:> > island at islandinthesun:/mnt/hda3$ sh islandwinebuild.sh > islandwinebuild.sh: ./configure: /bin/sh: bad interpreter: Permission deniedWhat filesystem is that /mnt/hda1? How is it mounted? With what options? Just post output of: Code: mount | grep hda1