OK... If I wanted to manually install BOINC what files are REQUIRED.

I was going to adapt the script originally used for SETI@home classic for remote install. I was able to use the MSI installer to extract the install files and plan to ONLY install as a system service. The remote GUI is not needed, as BOINCview is a much easier way to manage large groups of computers.


The following files are extracted to the BOINC directory:

boinc.exe

boincmgr.exe

boinc.dll
dbghelp.dll
msvcp71.dll
msvcr71.dll
boinc_dll.pdb
boinc_exe.pdb
boincmgr.pdb


Obviously I need the boinc.exe file and I don’t need the boincmgr.exe file if I don’t want the GUI. After that I quite know what needs to be there and what doesn’t.

Any help. I think the client works with just the boinc.exe file in the directory but under a limited capacity. If it does not require the other files under a system service mode then I obviously will not need to copy them over.

Any help is greatly appreciated.

---

<a href="http://www.boincstats.com/stats/boinc_user_graph.php?id=877f93559fda9f7c5a65f974a8763090"><img src="http://www.boincstats.com/stats/banner.php?cpid=877f93559fda9f7c5a65f974a8763090"></a>

How do you want to add (new) projects to be crunched by BOINC, when all you have is boinc.exe running as a service? I doubt BOINCView can do that already, or can it?

So even though you don't want the manager, you may need it to add the projects.

---

> How do you want to add (new) projects to be crunched by BOINC, when all you
> have is boinc.exe running as a service? I doubt BOINCView can do that already,
> or can it?
>
> So even though you don't want the manager, you may need it to add the
> projects.
>
Adding projects can be accomplished by copying the account*.xml files to the target computer's BOINC directory and restarting the client.

---

BOINC WIKI

BOINCing since 2002/12/8

Some of the alpha-builds didn't install all the files to correct directory, this lead to the service refused to start and complained about missing *.dll

So, appart from boinc.exe would include all the *.dll-files, to be on the safe side. :)

> Adding projects can be accomplished by copying the account*.xml files to the
> target computer's BOINC directory and restarting the client.
>
That's nice for existing projects on that computer, but what if he wants to add a new one, one he hasn't yet got an account*.xml file of? ;)

You'd still need the manager then, as I doubt you can add a startup string to the service.

---

> > Adding projects can be accomplished by copying the account*.xml files to
> the
> > target computer's BOINC directory and restarting the client.
> >
> That's nice for existing projects on that computer, but what if he
> wants to add a new one, one he hasn't yet got an account*.xml file of? ;)
>
> You'd still need the manager then, as I doubt you can add a startup string to
> the service.
>


BOINCview will add projects quite nicely. So do it once, at your workstation say, then copy to all the network computers, NET STOP and NET START and away you go.

---

So I guess my original question went unanswered.

I know it is possible to attach to projects through both BOINCview and copying the account xml file. My question was: What files are REQUIRED to be in the BOINC directory?

I was hoping someone would have a general idea what each file was used for and if it is important. If they are all needed then I understand, I was mainly wondering for my own curiosity considering the fewer files that need to be copied over the network for an install the faster it will run. This is only a concern due to the fact it may be installed on 30 or more computers at a time and the difference of a MB is about 2 minutes.

Thanks

---

<a href="http://www.boincstats.com/stats/boinc_user_graph.php?id=877f93559fda9f7c5a65f974a8763090"><img src="http://www.boincstats.com/stats/banner.php?cpid=877f93559fda9f7c5a65f974a8763090"></a>

I don't think you need the debug files, but they sure are handy for debugging...
If you don't need the manager you can leave out boincmgr.pdb and boincmgr.exe

boinc.dll is generally used for keylogging (screensaver and off/on based on activity) you would probably like to keep that one around as well as the msvc files (which are needed by the exe)

Use UPX to pack the dll and exe files if filesize is important. Dont pack project files/executables with it - these are md5 tagged and will fail to load...