Distributed Setting up CLI Seti

Here's how I setup the CLI version of seti.

------

Seti CLI for windows
ftp://alien.ssl.berkeley.edu/pub/setiathome-3.08.i386-winnt-cmdline.exe

Setistash
http://www.hereintown.net/~wink/programs/setistash2_1.zip

------

Extract the Setistash .zip file to C:\program files\setistash\.
Copy setiathome-3.08.i386-winnt-cmdline.exe into C:\program files\setistash\.
Rename the setiathome-3.08.i386-winnt-cmdline.exe to seti.exe (very important)
Start setistash.
When prompted for Username or E-mail enter them. (this will be in the CLI window, setistash is a seperate program) You may be prompted more than once.

In the setistash program click the third button. (setup)
Select "start processing at startup," "start minimized in system tray," and "hide CLI window"
Add cashes if desired, I find that for dialup more is better, but a minimum of 2 is recomended (max 50)

------

"Process WUs" starts to process the WUs
"Transfer WUs" transfers the completed units, and recieves new ones
"Setup" Advanced options*
"Hide" Makes the program run as a tray icon.
"Process all workunits" should be selected. (it will only process the selected WUs if not)

*Advanced options
"Invisible tray icon" will make it difficult to transferr the workunits manually by hiding the setistash icon.
"Auto-transfer complete WUs" best for a broadband or always connected system.
"Verbose" will cause the CLI window to display the current calculation's result but may slow down the processing. (try it for yourself)

"Cashes" number of locally stored WUs (1-50)
"CPU Number" is only useful in a multi proccessor system. (0-99)

The other buttons and options should be self explanitory.

------

Note that the auto-transfer feature and invisible tray icon feature are best used on an always connected or broadband system, where you do not want to be bothered by seti at all.

------

Admins or Mods please make this a sticky for easy reference.

/EDIT Setistash may be a bugger and want to be put in a dir other than "C:\program files\setistash\" IF THIS HAPPENS PUT seti.exe IN THE SAME FOLDER.

 

1398342003 - Just followed your guide to the letter and it doesn't work. When I start setisplash the CLI window does not appear. If I start the renamed seti.exe it does ask me for my username and if I then start setisplash I get an error say "seti.exe could not be found / run".

 

Sorry, my mistake. Put the SETI.exe in the setistash folder, where ever that is. (F3 for setistash)

 

Ok maybe it's just me but I'm still a little confused. As when I start Setisplash I'm still not prompted for username only when I start the CL client seti.exe.

Whenever I hit the transfer WUs button in setisplash I get the following error:



In which program am I suppose to hit F3 and what does it do?

Sorry for all the questions.

 

I'm a little confused too. Explain your way of starting seti. (the whole thing)

 

When you start seti, only start Setistash, the cli window will pop up automatically

 

Ok I start Setisplash and the CLI window appears but is blank. It doesn't prompt me for a username. It just shows as being idle.

 

I'm not repeating that.

 

1398342003 -

 

Stop, please your showing off me stoopit side. Lakk fo caffine.

I can only get that type of error when seti.exe is not in the setistash folder.

 

Seti.exe is in the same folder as setistash



I've tried unzipping everything into different folders, program files etc but still get the same error.

 

Is your computer set to hide the file extensions? If it is, then seti.exe is being called seti.exe.exe.

But do realize that I'm grasping at straws. I can think of nothing else.

*1398 crosses his fingers

 

Got it working now thanks mate! Wonder by how much my seti times will be reduced.

 

So what was the problem then -H- ?

 

He had named the Seti CLI seti.exe.exe due to windows hiding the file extension. It should be called seti.exe.

The worst decrease I've seen is 50% of the GUI time. The best I've seen is 33%.

 

Actually it wasn't that. I had the old standard Seti Client installed (not running) and for some reason it was casuing problems with the new one.

BTW this new client rocks! It's soo fast!

Edit/ 2 questions:

1. I tried using the Verbose option on the CLI to progress but nothing happens?

2. After it completes a work unit I still have to tell it process the next one despite having ticked transfer all units and process all units.

 

When you choose to use verbose you must stop and restart processing.

Does yours look like this?

 

Ah right dude. Yeah that's how it looks.

 

Which is better, the ones you guys are using or Seti Driver and Set Spy?