RhoXS
12-15-01, 03:25 PM
Thanks to 13oots2 and Cy I just discovered the Command Line Version. I feel really stupid because I have processed almost 1600 WU's using the GUI with a blank screen saver. Its very frustrating to think how many more WU's this could have been if I simply took the time to look.
I have some questions I would appreciate help with.
I noticed that when the CLC runs my machine gets noticably sluggish. A nice feature of the GUI version was that it did not at all intrude into my work when the blank screen saver was not active. Is there any way to similarly automatically stop and keep the CLC completely at bay unless I am not using my computer? I saw some parameters in SetiSpy and SetiDriver that might accomplish this but I would rather make known changes than experiment and unnecessarily slow the WU times.
I have a very reliable DSL connection. It happens but is rare that I am unable to connect with Seti to get a new WU. When it does happen it is almost invariably because the SETI server is down. This being the case, is SETIDriver needed?
Again, thanks to 13oots2 and Cy for opening my eyes.
I have some questions I would appreciate help with.
I noticed that when the CLC runs my machine gets noticably sluggish. A nice feature of the GUI version was that it did not at all intrude into my work when the blank screen saver was not active. Is there any way to similarly automatically stop and keep the CLC completely at bay unless I am not using my computer? I saw some parameters in SetiSpy and SetiDriver that might accomplish this but I would rather make known changes than experiment and unnecessarily slow the WU times.
I have a very reliable DSL connection. It happens but is rare that I am unable to connect with Seti to get a new WU. When it does happen it is almost invariably because the SETI server is down. This being the case, is SETIDriver needed?
Again, thanks to 13oots2 and Cy for opening my eyes.