Michael D. Ober wrote:

If you don't have SETISpy set to restart the client, you can use the
"CloseSETIDriver" program to shutdown SETI Driver and the CLI.  Go to
http://www.wakeassoc.com/setidriver/additions_and_companions.htm to
download.

Mike Ober.

Mike,

Thanks for the info on the "CloseSETIDriver" program.  I've downloaded it
and will check it out.

One of the members on the Seti message boards pointed me to a program that
will close SetiSpy, which in turn closes down the client and SetiDriver.  I
now have a command file that my UPS runs at 1 minute on battery power that
gracefully stops Seti, so hopefully that will solve the corruption problem
I've encountered when the server shuts down due to a power failure.  (The
server shuts down fine when Seti isn't running - my thought is with Seti
taking a lot of CPU time; something might get upset during the shutdown
phase of Windows 2K server.)

Also, I want to thank you for all the work on SetiDriver - it's been a great
addition to my Seti crunching, using it to cache work units and handle
communication problems.  SetiDriver has been a "set it and forget it" type
of program for me; the only time I check it is when Berkeley is having
issues, or if my DSL line is down.

Regards,
Bob.