From BOINC

Contents 1 Release notes for version 6.12 1.1 New features 1.1.1 Notices 1.1.2 VirtualBox Detection 1.2 BOINC 6 incompatible with Domain Controllers 1.3 Installing BOINC 1.3.1 Windows 1.3.2 Linux 1.3.3 Mac OSX 1.4 Uninstalling BOINC 1.5 Known Issues (Linux) 1.6 Known Issues (Windows) 1.6.1 Error 1069: Service cannot be started because of a faulty login

Release notes for version 6.12

New features

Notices

Project updates can now be displayed within BOINC Manager by way of notices. You'll know the latest and greatest about what is going on with a project without ever having to open a web browser.

VirtualBox Detection

BOINC can now detect what version of VirtualBox is installed on your machine.

For a full list of changes, please see the version history.

BOINC 6 incompatible with Domain Controllers

The present range of BOINC 6 is incompatible with Domain Controllers, meaning that you cannot install it on your system if it is a DC. This is because the developers used the Local Account API's instead of the Global Account API's.

Install BOINC 5.10.45 instead, even though this doesn't support GPUs or multi-threading applications.

BOINC 5.10.45 32bit version
BOINC 5.10.45 64bit version

Installing BOINC

Windows

You can set install options by clicking the "Advanced" button on the configuration screen. The options are:

• Program directory - where BOINC's program files will be stored.
• Data directory - where BOINC's data files will be stored.
• Use BOINC screensaver - Use the BOINC screensaver for the current user.
• Protected application execution - Run project applications under an unprivileged account. This provides increased protection against faulty applications, but it may cause graphics to not work with older applications. Do not install BOINC in protected application execution mode on Windows Vista and Windows 7 if you plan to use a GPU for doing calculations. These OSes run the drivers and user accounts in different sessions, so BOINC will not be able to detect your GPU. This is a security measure by Microsoft, it isn't something BOINC can fix.
• Allow all users on this computer to control BOINC - If selected (public mode), all users can control BOINC (attach/detach projects, etc.). If not selected (private mode), the only users who can control BOINC are: the installing user, members of the Administrator group, and members of the 'boinc_users' group. When other users run the BOINC Manager, they'll be shown a dialog saying to contact the administrator to add them to the 'boinc_users' group.

To run BOINC invisibly, choose the "Protected application execution" option, then delete the BOINC shortcut from the Start/Programs/BOINC and Start/Programs/Startup menus (locate BOINC in each menu, right-click, select Delete). You can still run the BOINC Manager by going to C:\Program Files\BOINC and double-clicking on boincmgr.exe

Linux

Main article: Installing on Linux

Mac OSX

Main article: Installing on Mac OS X

Uninstalling BOINC

Main article: Uninstalling BOINC

Known Issues (Linux)

Due to a problem with incompatible wxWidget build options BOINC 6.12 will not work on Fedora 14 & 15. This will be fixed as soon as possible. (last not working: 6.12.33)

Known Issues (Windows)

Error 1069: Service cannot be started because of a faulty login

This happens after something has removed the "Logon as a Service" from the "boinc_master" user account that was created during setup.

Known reasons for why this might happen:

• The administrator for your network has specified which accounts are allowed to "Logon as a Service" via Group Policy. Any account not on that list is stripped of that user right.

---

From my point of view the problem is because the install program by default decided to install the program files and program data files in folders which are only accessible with administrator privileges.

It installs program files in the correct place (C:\Program files\BOINC), where only admins can access it. It installs data files in the correct place (C:\Documents and settings\All users\Application data\BOINC) and sets permissions so that only boinc_master (an account created by the installed) can access it. That's all the way it should be.

Also it doesn't help that whenever the boinc manager starts automatically it starts as a service of the current user and therefore doesn't have enough privileges to do anything so you have to shut it down and restart it as with administrator privileges.

It never starts as a service under the current user account. That's not how services work. Services always start under the same account, no matter who is logged in. In fact, they start before anyone logs in.

Why can't the program be set to run always as an administrator level service that is available to all users?

Because that would be insecure, and it's completely irrelevant to the problem here anyway. --Nicolas (talk) 23:34, 16 March 2009 (UTC).