• blah
  • blah

How to get SetiSpy, SetiLog and the CL client to work together and keep the client hidden

First put Setilog and Setspy in the same directory as the client. Now make a shortcut to Setilog in the same directory. 

To make a shortcut, for those of you who are unsure, left click once on the SetiLog icon to select it, then right click the icon, this will bring up a menu.  Select Create Shortcut, and a shortcut will be made in the same directory.

You can now rename it to a shorter name, this will help you later.  If you are unsure how to rename, left click on the shortcut icon and then right click, which will bring up the menu again.  Now select Rename from the list and type in the new name for the shortcut, in my case I renamed the shortcut to SETI but you can call it what you like, just try to keep it to 8 chars and no spaces, less complicated.

Now edit the properties of the shortcut, same as before but select Properties from the bottom of the menu:

You need to add the following to the end of the target line (outside the quote marks):

-cpu 1 -proxy 200.200.200.1:5512 /ssetiathome1.exe /Q /h

The first two are switches for the client (setilog passes them on for you), the last three are Setilog switches. The first "/s" points to the client (if you have renamed it like me), second "/q" says start quietly no startup screen and the last "/h" says hide the client from the taskbar.

(The above is a screenshot from Windows 2000, if you are using Win95/98 then “Run in separate memory space”, “Run as different user” and “Comment”  will not be there, but the rest of the screen will be same.)

Now go into Setispy and go to the client page.

Now click on the Configure button.

In the client path line add the path to the link you generated earlier, mine is:

D:\Documents and Settings\Jon\Desktop\Seti Processor 1\seti.lnk

(you can use long or short filenames)
Leave the client parameters line empty. If you want Setispy to restart the client if it bombs out for some reason, type in the name of the client (make sure it is the same as the name you typed after the /s switch in the Setilog shortcut).

In the keep alive section, click both of the tick boxes and set the time Setispy waits before restarting the client.

In the client control section, click the hide and restore tick boxes. (Not sure if you need the hide, but it doesn't cause any problems with the ticked)

Now click OK and try (Re)starting the client. This will start SetiLog, which will start the client, and now you should have both Setilog logging you WU completion details and Setispy watching you WU processing status.

If you want to see if they are all running, press CONTROL-ALT-DELETE and SetiSpy, Setilog and the client should be listed in the list of active running processes.

If you are using Win9x don’t try and unhide the client as it will crash, and the only way to get it going again is to use the End Task button, when the client is highlighted, and then restart the client. -JonT