I'm running Windows 2000. I *was* running the CLI version of S@H Classic, but was shocked to see that there is not a CLI-mode version of SetiBOINC available for download (although you can download the source and compile it yourself... Fat lot of good that does someone w/o a compiler!) I do realize that there is not as much need for a CLI version since the new client will "dock" itself into the system tray and all but disappear. However, it would be nice to have a CLI version as well.

Second -- When will SAH be working again? Currently when I try to join the "full release" version of SAH, I get a message that the server has software problems. Yesterday I couldn't connect because the server was down for maintenance. What gives? When is this thing going to be "ready for primetime"???

The CLI is partly working. It is supposed to be working completely sometime before S@H1 is stopped. It is in your BOINC directory, but there are problems. Rights management and stopping when the active user logs out are two of them. What I believe is supposed to happen (don't hold me to this, I am not quite certain) is that the CLI is installed to do the control of the WU processing apps, and the GUI is also installed, and talks to the CLI to allow for easier control. The CLI is supposed to allow the option of remote control from a GUI on a different machine. This setup also allows for a replacement UI of somesort to be written.

> The CLI is partly working. It is supposed to be working completely sometime
> before S@H1 is stopped. It is in your BOINC directory, but there are
> problems. Rights management and stopping when the active user logs out are two
> of them. What I believe is supposed to happen (don't hold me to this, I am
> not quite certain) is that the CLI is installed to do the control of the WU
> processing apps, and the GUI is also installed, and talks to the CLI to allow
> for easier control. The CLI is supposed to allow the option of remote control
> from a GUI on a different machine. This setup also allows for a replacement
> UI of somesort to be written.
>
Thanks, John...
The way it was posted in the download section it sounded like the only way to have a CLI client was to compile your own, something most people aren't capable of doing in a Microsoft environment... :-) Now a *nix environment, that's a different story... but then we already have a pre-comipled cli client for *nix. ;-)

'Preciate the explanation...now if only S@H2's server would come back up... *sigh*