Wine and Linux questions.
17 Aug 2005 4:05:04 UTC
Topic 189704
(moderation:
I have been searching around here on the topic of running Boinc under Wine. I was curious what distros people were having success with when they do this.
I am using Linspire 5.0, and was able to get Boinc 4.19 to install and attach to Einstein, but it keeps going away after about five minutes of crunching.
There are no messages of any sort, it just disappears. To get it going again, I have to rerun the setup and then it takes up where it left off. It did not create a C:/Program Files/BOINC folder, because this isn't really Windows, and I am too dumb to figure out where the heck it put the projects, slots etc. Oops, there it went again. :( Maybe Linspire can't handle Wine and Boinc is crashing because of that. Is there a Beer I can try?
Pam the Baffled Boincer
Wine and Linux questions.
)
I've been using Wine on SuSE 9.2 and Ubuntu 5 (basically Debian), though not much with BOINC. Wine usually creates a fake Windows C: in ~/.wine/fake_windows/ , you should find your BOINC installation in
~/.wine/fake_windows/Program\ Files/BOINC
BM
BM
RE: I've been using Wine on
)
Thanks, I will look for that folder.
RE: RE: I've been using
)
I use gentoo. Are you trying to run the graphical client with wine, or just the command line client? If you are doing the former, I suggest trying just running the windows command line client under wine, thats what worked best for me.
such things just should not be writ so please destroy this if you wish to live 'tis better in ignorance to dwell than to go screaming into the abyss worse than hell
RE: Are you trying to run
)
I don't know how to work the command line client in Windows and don't see how to do it in the WIKI. I found the hidden fake windows files and can only open Boinc Manager, version 4.45 or Boinc gui 4.19 with WINE. Version 4.45 won't attach. Tonight boinc 4.19 is only exiting with zero finished file and advising me to reset.
Thanks for your responses. Maybe before long, they will make Linux better for Einstein.
Pam
RE: I don't know how to
)
For me if you look under ~/.wine/drive_c/Program Files/BOINC, you will see a boinc_cli.exe file. To run just do this
wine boinc_cli.exe
Easy as that!
such things just should not be writ so please destroy this if you wish to live 'tis better in ignorance to dwell than to go screaming into the abyss worse than hell
I'm using SuSe/Novell 9.2 and
)
I'm using SuSe/Novell 9.2 and I just have to open my console (in KDE), and type in (once it's typed in you can ofcourse always recycle it afterwards):
wine /home/[user]/.wine/drive_c/'Program Files'/BOINC/boinc_gui.exe
NB: The [user]-part needs to be replaced by your username ofcourse.
Then, I minimize the console, that's delivering all sort of strange messages, I look at the messages, I switch tabs to 'Work', and I minimze the boinc-gui. If I don't minimize either of them, it doesn't take long before BOINC quits.
Thanks, Jordan and copycat.
)
Thanks, Jordan and copycat. When I try to run it in Konsole, as command line, wine exits with return code 1.
However, minimizing the gui after I get it going seems to work, it hasn't gone off yet. We'll see if it is done when I get up tomorrow morning.
Thanks for all your help.
Pam
:)
Well, it finished in 25643
)
Well, it finished in 25643 sec and was granted credit. It had over an hour on it when I went to bed, and when I checked on it after I got up over six hours later, it said it had two hours to go. So it really had to take more like 9 or ten hours to finish. Now it's acting like it can finish the next one in under five hours. I am not sure the boinc gui can count under wine.
Another computer, with same mb and processor Athlon 64 2800+ averages 32845 sec with linux 2.6.10.
You have to realize the time
)
You have to realize the time it's showing is CPU-time, meaning the time it would take if it had 100% of the CPU at its disposal 100% of the time. At least, that's what I think it is. I've noticed sometimes 1 sec real life
RE: You have to realize the
)
It makes me wonder what else was going on to take up cpu time. It looks good "on paper" at 7 hours, but I know it took way more than 8, which is about what I would get just running the native linux client. Perhaps the windows emulation is what is so cumbersome.