Wine - Linux - Seti help

[OhioDude]

OK, I suck.

I've got Redhat 7.2 on a dual PII 400 that's been crunching Seti with the Linux client for quite a while now. (15hr wu times! :disgust: Like I said, I suck.) I want to start using Wine and the I386 CLI. Can somebody outline the steps I need to do to configure Wine and run Seti? I've already installed Wine (CodeWeaver 20020411-6.i386). Just need a little (or a big) shove in the right direction.

I'm too busy (or lazy) right now to research it myself...

Thanks!

 

[RaySun2Be]

Calling Poof, calling Poof!

Sorry ODude, can't help ya, I'm Linux illiterate.

 

[Electrode]

as it comes right out of the package, it should be well enough configured to run seti-win32cli.

1. Unpack the cleint somewhere in your homedir. dropping it in wherever you had the linux client will be good enough.
2. run: wine --debugmsg -all -- ./seti.exe -proxy addy.of.queue from the seti client directory.
3. that's all there is to it.

 

[OhioDude]

That's simple enough... Like I said, I suck.

I kept trying to run it through a telnet session from a client and it kept telling me it couldn't open the display... Ran it from the Linux system console and it worked fine. Doh!!!

Thanks, Electrode.

BTW - I'm using the "--winver nt40" option and also nice'ing -15 to keep everyone else on the server off my back...

 

[steell]

I am running two seti clients (i686libc) using ksetiwatch, on a dual P-II 450/1meg Xeon box, and it is averaging 12 hours per wu.
I am also running Seti on a single XP1800+. When I used wine to run the win client, it took an extra 30 min per wu (running in a console window in KDE). Is there some specific way that you have to run the wine/win client to get it to run faster?

I did notice that seti was 55% of cpu and winserver was 45%. Seems to me that I have messed up something, but I can't figure out what.