Gerry <gerlast2@TAGLIAMIyahoo.it> expounded in 
news:u20Db.209572$hV.8126246@news2.tin.it:

Hello everyone!
I use setiservice under Windows XP, but I'd like to make my processor 
crunch more data during the periods I'm not at the terminal.
This is what I'd like to do:
To start the winNT client when starts the screensaver, (but not actually 
use the screensaver version of seti@home!) and stop it when the 
screensaver stops. So my users could choose any screensaver they want.
Anyone tryed to do something similar?

 (Oops.  Just realized that I accidentally hit the wrong button and emailed 
my reply instead of posting it here.)

 A few thoughts.

 I have my Win98 system set up so that the CLI is started with the 
screensaver, so it may be possible to do some of what you want, but there 
may not be much point in trying to set this up on your system(s) now, since 
the current S@H program will presumably be ending before too long, to be 
replaced by the new BOINC program.

 I don't have WinXP so I don't really know how the "service" thing works, 
but would you really gain anything by running the CLI S@H as a 
"screensaver" instead of a service?

 I have the CLI starting with the screensaver, but it does not stop when 
the screensaver stops and I don't know if that's possible.  Theoretically, 
it's not a problem if S@H keeps running since it runs at low priority, 
unless you're short on RAM or something.

 If you're using some kind of WU caching program (eg. SetiQueue) and it's 
not already running, I don't know if it would be possible for the 
screensaver function to start it as well.  I think I played around a bit 
with trying to start SetiQueue that way, but there was a problem if it was 
already running.  I can't remember for sure.  IAC, I just normally start 
SetiQueue when I start Win98.

 > So my users could choose any screensaver they want.

 I setup the screensaver on my system so that it calls a batch file which 
runs the "blank screen" screensaver and then starts the S@H CLI.  You might 
be able to use some of the other standard Windows screensavers (I could if 
I wanted to), but that might defeat the whole purpose of starting S@H with 
the screensaver.  Some of the standard Windows screensavers, especially the 
"OpenGL" ones on my Win98 system, seem to use quite a bit of CPU power, so 
they would probably slow S@H down.  So I just use the "blank screen" one.

One more thing: is it possible to make the nt client connect (and 
disconnect)automatically when it ends? I have a dial-up connection.

 Depending on how your dial-up connection works, it's certainly possible 
for the S@H client to automatically connect when it needs to.  I'm not so 
sure about auto-disconnecting.  It's just not something I normally do.  
There may be options within Windows or addon programs that you can use.
 Personally, I like having my system setup so that it can't automatically 
dial out to the 'Net.  Then I know that no program can connect to the 'Net 
(using a regular connection) without my intervention.

 It sounds like you're not using a WU caching program.  That might be a 
better alternative.  It can d/l a batch of WU's (eg. several days worth) at 
your convenience and S@H can work on those until you're ready to connect 
again and get another batch.  (That's a simplistic description, but that's 
basically the way it works.)

 James