I was alerted by a friend to the problem who doesn't have time himself to write. Installing the boinc CLI as a service (since it is supposed to keep running on machines that have to be on, but not logged in) works, the service is installed and started. HOWEVER: the moment the user logs off, the service stops. logging back on, same or different user, the service remains stopped.

I have tried several things:
1) forcefully setting the permissions for network service to the boinc directories. no fix
2) installing boinc on an XP system that has no file system permissions (fat32 drives). no fix
3) changing the service type logon to SYSTEM SERVICE (local sstem account) as it is installed as network service by default. no fix

In all cases, upon a user log-off, the service stops. This practically nullifies the use of boinc as a system service...

Is there a fix for this? Is there a workaround?

This is supposed to be fixed in 3.20 which is out on the alpha and predictor sites. Http://setiboinc.ssl.berkeley.edu/boinc_alpha/ or http://predictor.scripps.edu/.

OK, well I'd best wait for it to be in release then.

> This is supposed to be fixed in 3.20 which is out on the alpha and predictor
> sites.

> OK, well I'd best wait for it to be in release then.
>
> > This is supposed to be fixed in 3.20 which is out on the alpha and
> predictor
> > sites.
>
If you really want it now, you can get it at either http://predictor.scripps.edu/ or http://setiboinc.ssl.berkeley.edu/boinc_alpha/. The only warning is that you will be doing some of the early testing.