Installer doesn't act as expected when following along with ClientSetupLogicWinSix

[imsaguy]

I'm on a x64 Vista machine and just installed 6.1.5 from 5.10.30. I had my 5 client running in its own user account for management/security sake and here are my notes from there.

Install

Program directory: c:\Program Files (x86)\BOINC\

Data directory: C:\ProgramData?\BOINC\ /*Wiki states C:\Users\All Users\BOINC Symlinks shouldn't be relied upon, they can be removed in later releases.*/

Unchecked allow all users on this computer to control BOINC /*Wiki states all boxes are off, my protected and all users boxes were checked*/

Post Install

Installing user didn't have access to Program directory or Data directory /*Wiki states Administrators have access, and while a part of the Administrators group, I still didn't have access*/

BOINC service wasn't started. Upon checking the Windows Event Log, these errors were logged: First this:

Faulting application boinc.exe, version 6.1.5.0, time stamp 0x4762d38d, faulting module MSVCR80.dll, version 8.0.50727.762, time stamp 0x45712238, exception code 0xc000000d, fault offset 0x00012280, process id 0xfb8, application start time 0x01c84a3b1821e203.

Then this about 20 seconds later:

The BOINC service terminated unexpectedly.  It has done this 1 time(s).

Three user groups were created: /*Wiki states two user groups are created*/ boinc_admins boinc_projects boinc_users

Two users were created: boinc_master (member of boinc_admins) boinc_project (no membership) /*Wiki states boinc_project should be a member of boinc_projects group*/

[imsaguy]

First error message doesn't show correctly for me. It should be:

Faulting application boinc.exe, version 6.1.5.0, time stamp 0x4762d38d, faulting module MSVCR80.dll, version 8.0.50727.762, time stamp 0x45712238, exception code 0xc000000d, fault offset 0x00012280, process id 0xfb8, application start time 0x01c84a3b1821e203." Then this about 20 seconds later: "The BOINC service terminated unexpectedly. It has done this 1 time(s).

[romw]

Should be fixed in latest editions of the wiki and application.