• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

linux and wine

ElFenix

ElFenix

Elite Member
Super Moderator
so i pop mandrake on my system just now with the intent of trying it out. happily it can read my windows partition just fine. so i think, hey, i could use wine to run setidriver. so i go get wine. i install the rpm. and then i try to make it go by double clicking. then i RTFM. i try the find command to find wine's path. it doesn't return anything. so now i'm in the happy windows land again. booooooo. try again tomorrow.
 


<< and then i try to make it go by double clicking. then i RTFM. >>

Well, that's your problem. RTFM must be done first, or it won't work 😉

But seriously, Wine didn't return anything when you tried to run it (e.g., $ wine /mnt/windows/seti/seti driver.exe)?
 
Hello.

I haven't succeeded with getting SetiDriver to work in Linux.
Only one thing did get my attention..
I first ran the CMD-client made for linux.. It did a wu in almost the
same time as it should take on my Windows machine.
Here is the weird part:

I wanted to run SetiDriver with Wine on my PC..
It didn't work..
Then I just wanted the Windows CMD-client to run on my Linux machin
with help from Wine.
I succeeded..
Only, one WU took more then 3 ours less then the same client with Windows!!!
Usually on my Celeron (Dual) it takes about 13 ours..
With the windows client under Linux it took almost less then 10 ours!!
Weird, isn't it 😉

Greetings!
 
You need to edit your wine.conf or wine.reg file and tell it where your seti stuff is..

eg. You could give it a drive name of G: and put the path in there.....

I'm at work now so I haven't got an example file to show you, Poof might jump in and help....

cheers,

Col
 
I've never been able to get Setidriver (or the new Setiqueue) to work with WINE yet either (and that's with having the SETI exectuable in the same directory as Setidriver), although I expect that getting Setidriver to run might be easier than Setiqueue. Something to work with Mike Ober on...
 
no no.... i can't even find wine with the find command. using the syntax from the help site, like find / -name "wine" -type f -pref +111 or something like that.
 
Ahhh.... so you've lost the executable, eh? Poor ElFenix! 😛

Well, if this is a new install and you're using Codeweaver's WINE, then there's a little installation thing that you're supposed to go through (graphical), that lets you configure WINE. The final settings are then kept in your /home/$yourusername/.wine directory (note that the actual settings directory is a "dot" directory - ".wine". Again - this is assuming the use of Codeweaver's.

When in doubt if looking for executables, check in /usr/bin or /usr/sbin... Sometimes /usr/local/bin or /usr/local/sbin.

🙂

[EDIT: Let me add that you might want to check your windowing environment (either KDE or GNOME or whatever) because after you put that RPM there, there just might be an option in the menu to run the installer for WINE now. 🙂]
 
ah okay cool.

i was also told that i needed to update the index for the find command somehow, though i couldn't see how to do that in the man pages for it.
 
Well, Since I am unable to get the setiathome to run from cron on linux I might as well maximize the speed.

anyone have simple instructions on how to set up the setiathome client with wine?

currently my machine is crunching at around 4.5 hrs if I can get it down to 3 that would be great.

PM me if you like.

AlricTheMad
 
Alric - how are you trying to start SETI from cron? Were you looking to have it check every hour or something to make sure it was running or were you trying to have it run SETI only during certain hours?

Also regarding WINE - if you already have it installed and have WINE corrrectly configured to point to either native or "fake" win32 system files, you can open a terminal and try (this is based on using WINE's -nt40 parameter, which runs faster than the default -win95 or -win98):

wine --winver nt40 -- setiexecutablename.exe -{parameters}

where "setiexecutablename.exe" is whatever you use for the CLI name (most people shorten it to something like "seti.exe"), and "-{parameters}" are whatever parameters you would normally use for the CLI, eg., "-proxy {blah}" if you have to use a proxy server or send the WUs to Setiqueue.

Note that you can actually nice the above WINE server process if you need to. I think by default, the above runs ~ nice -15.

I was checking out Sukhoi's Help thread and I guess we do need a FAQ on this. However, 2 things would need to be described - the first being installing WINE and the 2nd, running SETI (or anything else) with WINE.
 
Poof, I added a line that was suggested by Darkone in another thread. I placed it in cron.tab,
Tho now I wonder if RH doesn't have it's own crontab (found one like anacrontab or similar).
I restarted crond after I made the changes.

wine I have(had?) installed. took it off because it wasn't doing what I wanted. I'll put it back & try with this.

Still doing about 5+WUs/day.

Thanks

AlricTheMad
 
Alric - there are sortof 2 crons - the crontab file in /etc that can be edited directly (specifying the user who has permission to run the job) and the cron files that each user can create for themselves, by running crontab -e and editing cron jobs that way... It could be that what the Darkone suggested was the info that is listed in the readem on running SETI as a cron job (the readme comes with the *nix SETI clients).

With respect to WINE times vs Linux times... I found that on average, WINE (or the corresponding CLI run on windoze) ran the bench WU about 30 minutes faster than the i686 dynamic linux client.... something that still gets me ranting and raving... :|

 
FYI. I have S@H on RH7.2 on a dual processor 850Mhz machine running in SMP.

Same work units tested on both i686-pc-linux-gnu-libc6-dynamic (or whatever its called 🙂 ) and i386-winnt-cmdline.exe under wine.

The winnt-cmdline client running under wine, completed the work unit in 8hours 15 minutes and a few seconds.... the same work unit under the linux client completed in slightly over 10 hours..... .So.. suprisingly despite the client running in an emulator, which i would expect would produce slower results... it was actually faster 🙂

D
 


<< So.. suprisingly despite the client running in an emulator, which i would expect would produce slower results... it was actually faster >>



Wine Is Not an Emulator

🙂😉

Col
 
So.. suprisingly despite the client running in an emulator, which i would expect would produce slower results... it was actually faster 🙂

Well that's because the libraries that were developed for WINE are more efficient than the native windoze ones... Plus you don't have all that overhead that the win32 interface (explorer.exe) adds, despite most people starting up WINE in a graphical mode, which often involves the use of a window manager, on top of a windowing environment, all being on top of X.

The CLI itself is faster than the corresponding *nix clients, having been compiled with the Intel compiler, as opposed to the linux client having been compiled with gcc. There is now an Intel compiler for linux, but it remains to be seen whether the porter will be permitted to recompile the client to make this *nix client more efficient... :disgust:

Also, you'll find that the i686 linux clients will run about 5 minutes faster than the i386 versions, and the i686/i386 dynamics will run about 30 minutes faster than the corresponding statics.
 
despite most people starting up WINE in a graphical mode, which often involves the use of a window manager, on top of a windowing environment, all being on top of X.

So How do you start it up without the graphical mode. Would the teminal command posted by Darkone work?
I was crunching at around 4.5 hrs/WU I will need to figure out the times under Wine.

The CLI itself is faster than the corresponding *nix clients, having been compiled with the Intel compiler, as opposed to the linux client having been compiled with gcc. There is now an Intel compiler for linux, but it remains to be seen whether the porter will be permitted to recompile the client to make this *nix client more efficient... :disgust:

I hope it becomes possible. As I have said I would much rather the Seti client run completely in the background and not require someone to be logged in.


Alric
 
So How do you start it up without the graphical mode. Would the teminal command posted by Darkone work?

There were a couple of ways that I've seen people post to do it - one of which involved the use of the frame buffer. But someone here had another way which seemed much easier.... Geez... I forgot who it was! 🙁

Maybe Kilowatt might know off hand. I'm sure the message where it was suggested is probably archived off the site by now...

[EDIT: I may try to do a search anyway... ]
 
Looks like wine is the way to go, so I'm wondering if I could get it on my floppy Linuxes. I don't imagine it could fit on a floppy; but is there any chance all the necessary parts could fit in, say, 16mb? Or is it the size of a full Windoze install?
 
linux and wine

I'm a DOS and beer kinda guy.
rolleye.gif



 
NWM - Since it's Friday, I'm sure you want a cold one right about now! 😛

ken - WINE is pretty big mainly because it's made to really be run in X + some window manager. I have heard of some people who were able to putz with it and have it run in a tty console (maybe JHutch???), but I don't know if it would fit on a floppy distro...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top