Hello all.

Having a mare installing any version of BOINC ( attached to Rosetta )

I have tried the "old" ( version 5.10 ) version with the lazy slugs method of the MST

I have tried the new 6.x installer

I can get both to install , yet neither to install via a service.

Using either method - they both run when a user logs in - however they stop when the user logs out.

---

Isn't there something about installing it for all users, not the one that happens to be on while setting it up?

Is it possible you now have BOINC installed more then once? Once as a service and once as normal?

I haven't heard installing as a service as being a problem for people. So am thinking there must be something simple here.

---

Rosetta Moderator: Mod.Sense

Isn't there something about installing it for all users, not the one that happens to be on while setting it up?

Is it possible you now have BOINC installed more then once? Once as a service and once as normal?

I haven't heard installing as a service as being a problem for people. So am thinking there must be something simple here.

It will be something simple - probably the user :)

I definatly DO NOT have boinc > 1

I have had a good dig around for install it for all users , but I want it to start regardless of who is logged on.

---

Strange.

Just been to all the machines , none have hte service install done.

If i reinstall with the same MSI , acccept all the options , it installs the service fine ..

---

Just thought I would drop a line in here : I got it working.

I created a new virtual XP machine , disabled all the autoupdates ( so the install process wasnt interuppted )

I joined the machine to the domain

I logged on as a domain administrator

I downloaded WinInstall LE 9.5 ( a free download from : http://www.softpile.com/Utilities/Miscellaneous/Review_16745_index.html here

I installed Wininstalle LE 9.5 , and ran the capture

Installed BOINC , set all the preferences as required ( inc service install - or elevated as its known in verison 6 )

** CRITICAL BIT *

restart the machine , run services.msc , change the boinc service by right clicking on it , log on bit to local service , start the service.

Restart the machine

recapture , and then you can deploy the MSI as needed.

I had a couple of machines that failed to start the service , they require a further reboot once deployed via policy. If it still doesnt start type the following in a cmd window

sc \machinename start "boinc"


Job Jobbed.

---