So now time for me to do a service install of BOINC I think
This program is also really easy to install so don't be put off by the long steps mentioned below
Alpha Version

The site is here its still in French but other languages to follow at some point.
BOINC Studio will auto-update to any new versions of the software that are released
The download link seems to include versions for Windows & Linux
Right time for instructions (thanks to all posts from various websites I have seen, this is my version of everyone else's)
1. Download the .rar file from the link
2. Open file and unpack to /Program Files/BOINC Studio (can use http://www.winace.com/)
3. Enter the BOINC Studio file and find Boincstudio.exe right click and send a shortcut to your desktop
4. Next open notepad and add IP addresses or names of computers that will be talking/contacting BOINC
Eg
124.321.25.231
156.247.25.246
etc etc
or you can list a range of IP's if you are on a router
124.321.25.231
124.321.25.232
124.321.25.233
124.321.25.234
(note IP's above made up out of my head)
save the file as remote_hosts.cfg not as remote_hosts.cfg.txt, place the file into \BOINC Studio\clients\bs_current_win32
5. Shut down BOINC

6. Go to the BOINC directory and find gui_rpc_auth.cfg open it with notepad, delete the long line of text and type in a new easier to remember password - Save the file and exit
7. Copy the contents of \BOINC Studio\clients\bs_current_win32 to your BOINC folder, overwrite all files when prompted
8. Start up BOINC again and wait for the benchmarks to runs after they have finished check for this message
(Don't worry if it doesn't say that yet)24/06/2006 18:16:35||Remote control allowed
24/06/2006 18:16:35||Listening on port 31416
9. Start up BOINC Studio from the link you placed on your desktop
10. Click on Computers, then New Host
11. Change the Display Name (to something meaningful to you)
12. Change Host Name to either the IP's or Host Names that you typed into the remote_hosts.cfg file
13. Port - Do not touch

14. Put in the password that you changed in the gui_rpc_auth.cfg
15. Install path - Apparently is not needed but just in-case it is needed C:\Program Files\BOINC (or wherever your BOINC install is located)
16. Right click on the host that has just been created and click connect, if it won't connect restart your computer and see if that helps
17. Optional step - BOINC Studio has a Credits Correction facility you can enable this by going to the relevant host on BOINC Studio and clicking the projects tab (note currently it may produce higher claimed credits than normal, but this is getting fixed)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I am assuming the following steps can also be followed for Linux using the Linux files included but I'm not 100% sure so if anyone wants to test it on Linux let us know how it goes

Note: If you are going to use it for multiple systems then you will have to follow steps 7 - 8 I think, also I think at any new install of BOINC you would have to follow those steps too, dunno on that one yet until I upgrade to a new version. Also can still use BAM.
Right well that's all the steps time to mention a few extras BOINC Studio has a really neat feature built into it, the ability to have a backup project, the ability to trick a project into thinking you have more than 1 CPU & also you can set up hosts to work off various projects.
To set a project as a back-up mode go to the same page mentioned on step 17 the back-up modes option should be there. Not too sure how it works I assume you would suspend all projects except your main project and then choose a back-up project that will then kick in if you run out of work on your main project
The CPU trick is also on the same page as above just click on box and a drop down section comes down, this can be a useful thing to do on projects where you are limited to so many WU's per CPU (eg Einstein)
Setting up projects on multiple hosts means you can for example have 1 host running Einstein and another running SETI and still micro-manage the projects from one location independently from each other.
See this thread for bits of info - I find it hard to read as is a massive post.
If anyone has anything they want to add, hints, tips & support requests just put them all here.
Thread going to be stickied for now
Screenshots


