Thread 'Creating 32-bit BOINC Installer in Inno Setup'

Author	Message
JJS Send message Joined: 30 Mar 14 Posts: 8	Message 53456 - Posted: 1 Apr 2014, 11:05:31 UTC Last modified: 1 Apr 2014, 11:08:45 UTC When creating an installer for BOINC, I thought it would be simply 1) Copy the program files into C:\Program Files (x86)\BOINC (109 files total in 32bit version) 2) Copy the few other files into ProgramData\BOINC And that would be it. However, I am getting this error message: "You currently are not authorized to manage the client. Please contact your administrator to add you to the 'boinc_users' local user group." What am I missing? I am using Inno Setup to create the installer as I do not have a full version of InstallShield. ID: 53456 ·

ChristianB Volunteer developer Volunteer tester Send message Joined: 4 Jul 12 Posts: 321	Message 53461 - Posted: 1 Apr 2014, 13:46:42 UTC The BOINC Installer does some more things than just copying files. Why do you want to create your own Installer? Is there some functionality missing? ID: 53461 ·

JJS Send message Joined: 30 Mar 14 Posts: 8	Message 53470 - Posted: 2 Apr 2014, 0:12:05 UTC - in response to Message 53461. Last modified: 2 Apr 2014, 0:13:10 UTC Why do you want to create your own Installer? Is there some functionality missing? A friend made a customized version of the manager and I have the source for it, wanted to package it into an installer. I don't think it's better or anything, it just looks different. The BOINC Installer does some more things than just copying files. How do I find out what those things are? ID: 53470 ·

ChristianB Volunteer developer Volunteer tester Send message Joined: 4 Jul 12 Posts: 321	Message 53474 - Posted: 2 Apr 2014, 8:57:56 UTC You can find some rather old (but mainly still valid) documentation here: ClientSetupWinSix and the implementation notes here: ClientSetupLogicWinSix For the actual logic you have to look in win_build/installerv2 and inspect the InstallShield files. If those changes to the Manager are generic and could benefit other volunteers you should send them to the developers so this could be incorporated into the original source. ID: 53474 ·

JJS Send message Joined: 30 Mar 14 Posts: 8	Message 53476 - Posted: 2 Apr 2014, 12:12:10 UTC - in response to Message 53474. Last modified: 2 Apr 2014, 12:12:37 UTC Okay great, I'll make sure I test it out first. Would this whole process be simpler if I found someone with a full version of InstallShield? I feel I am just making things harder on myself, trying to use Inno. ID: 53476 ·

ChristianB Volunteer developer Volunteer tester Send message Joined: 4 Jul 12 Posts: 321	Message 53477 - Posted: 2 Apr 2014, 12:22:14 UTC Sure, this would be easier using the same tools as Berkeley. ID: 53477 ·

Rom Walton Project developer Send message Joined: 26 Aug 05 Posts: 164	Message 53507 - Posted: 3 Apr 2014, 16:23:43 UTC It sounds as though your installer needs to setup two registry values: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup] "INSTALLDIR"="C:\\Program Files\\BOINC\\" "DATADIR"="C:\\ProgramData\\BOINC\\" DATADIR needs to point to a place that the installing user can read/write to/from. ----- Rom BOINC Development Team, U.C. Berkeley My Blog ID: 53507 ·

Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.