SETI Driver / SETI Spy question...

[saabcaptain]

I just changed from the Windows GUI client to the CLI client with SETI Driver and SETI Spy add ons. I have it all up and working but I have a few questions since this setup is quite different that what I have used before...

1. In my Windows XP Screen Saver dialog box there is no option for "Default Screen Saver" as recommended in the Windows XP directions for CLI/Driver use that you posted in this forum. Do I just set the screen saver to "None"? Do I even use a screen saver if I have the CLI setup?

2. This is the first time I have ever done SETI@Home where it will use up idle clock cycles while I work, having used the GUI version as a screen saver only before. While my computer still feels snappy, and I know the CLI client will only use "idle" cycles there must be *some* performance hit right? It seems almost to good to be true. Do you all turn off the CLI client when running a video game, or other processor intensive task, or is the CLI client *that good* you can trust it to not harm performance.

Thanks!

 

[Ionizer86]

None or Blank are both good. The CLI will have it constantly running, so you don't need to screensaver it.

The performance hit is under 1%. It'll automatically stop using cpu cycles when you game. I noticed after watching a movie that very little extra cpu time was devoted to the seti 3.03. You can trust the CLI

here is a benchmark for Folding@home vs. having it off. SETI@home will perform similarly. The hit seems to be from 0 to 1%.

 

[saabcaptain]

Excellent! The main reason I haven't done too many WU over the last year is problems with the GUI version and some higher priority Tivo server software I use in rare occasions to send photos and MP3s to my Tivo. This CLI version doesn't conflict at all and even better is pretty good at crunching while I do fairly non-intensive tasks like browsing or checking email. I should see, and Team Anandtech should see a big increase in my WU units running on my 2.4 P4.

 

[Smoke]

This is second question today about the "Blank" screen saver in Windows XP.

The sigline instruction set has now been corrected and updated.

 

[saabcaptain]

also so you know all the links to CLI posted today are for the 3.03 version and I saw a CLI 3.08 version (which I got) on the Seti@Home website so that also might need updating.

going to add a P-M (centrino) 1.6Ghz laptop to my P4 2.4 desktop ... the laptop won't run 24/7 but often sees good up time so it will help.

 

[saabcaptain]

one more thing, my WinXP Home installs don't have a "Blank" screen saver setting either. "(None)" is the available setting.

 

[Overkiller]

The 3.08 version fixes a *slight* secrutiy flaw, of which i dont think anyone here frets over b/c it is really that minor. The 3.03 version is about 5-15% faster i belive (going on memory) than v. 3.08..hence why many of us are using 3.03


Welcome aboard with whatever you got and how much you got! every little bit matters!!!

 

[Spacehead]

3.08 security issue explained

Fix for v3.08 security issue



I have noticed playing some games a bit of a slowdown so sometimes i do shut SETI down while playing. Just remember to turn it back on

 

[Overkiller]

When i play games i disable 1 of the services b/c i run 2 instances on my 2.8 HT

works like a charm