- Nov 21, 2001
- 31
- 0
- 0
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!
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!