[Home]

[Projects]

[Links]

[Guestbook]

[About me]

KSetiSaver user manual

Aha! I assume you were clever enough to get KSetiSaver compiled & installed. If you got KSetiSaver compiled, you shoud also be able to configure it, but perhaps this is to easy for you, so I'll write a sentence or two about it ;-)
After a succesful install, you should have a "KSetiSaver" entry in your screensaver KControlcenter module (see this screenshot). After pressing configure you see KSetiSavers configuration dialog.

The "General" tab


The Seti@home data location field is for the path to your seti@home client working directory. This is the path where all the *.sah files reside. You may either enter the path manually or pop up a filedialog by pressing the "..." button.



The Seti@home client location field is for the path to your seti@home client. This is the path were your "setiathome" executable resides. You may either enter the path manually or pop up a filedialog by pressing the "..." button. On most installations this is the same as the data location path above, so you may just want to check the Client and data are in the same directory box.

If you check Use Ksetiwatch directories KSetiSaver tries to locate and parse the configuration file from Ksetiwatch. In this mode KSetiSaver cycles through all directories entered in KSetiwatch. Only in Ksetiwatch mode KsetiSaver is able to monitor more than one client! When this option is checked, the Lauch the client when the screensaver starts option gets unavailable. If you use an advanced monitor programm like KSetwatch, I assume that you also use a the more advanced methods of this program to start & stop the clients ;-)

Now let's come to one of KSetiSavers key features ;-) The Launch the client when the screensaver starts option. When this option is checked, KSetiSaver behaves exactly like the Windows screensaver version of seti: When the screensaver starts up, it launches the seti@home client.
Note: This feature was broken in earlier versions of KSetiSaver. Most likely it doesn't work correctly in version prior to 0.3 (it fails to shutdown the client).

When the screensaver finishes, it shuts down the client. That means seti@home is only active when the screensaver is. This way you don't loose a single processor cycle or a byte of ram, while working.

Please note that it may take up to 1 min after the screensaver finished to shutdown the setiathome process!

Before KSetiSaver can lauch a freshly installed seti@home client, you have to start the client one time per hand on a console, because the client will ask you a few question (Setting up an account..). In short: KSetiSaver can launch the client if there is a user_info.sah file in the seti directory.

Important: The seti@home program is started with the permissions of the user who ran the screensaver, so you have to make sure that every file in the seti@home directory is writable for everyone. To make this type into a console (make sure to replace /opt/seti with the path to your seti@home directory)
$ chmod -R -v ugo+rw /opt/seti



The Play sound effects does exactly what you thinking it does: It activates some sound effects. Before activating the sound a little requester pops up, asking you whether you are sure to activate sound, since I don't know if the samples are copyrighted by someone.

The "Advanced" tab


Normally you shouldn't use any of the settings in the advanced tab, however there might be some situations where using some of this optiion becomes neccessary.
With the controls in the Font config box you can override the default fonts. From the beginnig KSetiSaver was developed using hardcoded fonts in the source and was carefully optimized to these fonts. That means every text position in the sourcecode is hardcoded and there no thing like layout managment. Therefore it is better to leave these settings untouched. Unfortunately some people reported that the default fonts looked very ugly or were extraordinarily huge on there computers. If this is the case on your system you might achieve a better display if you tweak the font settings in this dialog. The hardcoded defaults are:

  • Headerfont: Helvetica 32, bold
  • Mediumfont: Helvetica 18
  • Smallfont: Hellvetica 14
You'll only achieve acceptable result if you choose similar fontsizes for your custom fonts!

The Manual positioning" is another config tweak that isn't neccessary for 99,9% of the systems. KSetiSaver always uses a fixed resolution of 1024x768. If your monitor is set to a higher resolution the KSetiSaver graphics will be centered. As far as I know this works fine with most systems, but if you have a dual headed setup you might end up with a splitted KSetiSaver view (one half on each monitor) since KSetiSaver can't detect this. Let's assume you have a dual headed setup with both monitors set to 1024x768 and KSetiSaver displays one half of the graphics on the left screen and one half on the right screen. In this case you should enable the manual positioning option and set the x and y values to 0. Doing this, KSetiSaver will only (but complete) be displayed on the left screen

The "Manual transfer" tab

This functionality is not yet implemented. Prepare for new cool updates

Errors while running

error If a needed file doesn't exist, or if there is no seti@home client running, or when a parsing error of some sort occurs KSetiSaver displays a error message.

If there are any questions remaining, try the FAQ

Back to KSetiSaver mainpage

Murphy was an optimist.

This site is copyright © by Sebastian Schildt
Last modified: around 2003, this pages are just up for archaeological purposes

Frozenlight logo