I know this has been mentioned before in http://setiweb.ssl.berkeley.edu/forum_thread.php?id=127, but I am unsure of what posters meant when they said that a regedit worked for them in making this option stick whenever the service started. I am not sure of what registry key they are referring to, or what they changed. Simply adding "-allow_remote_gui_rpc" to the end of ImagePath right after "-win_service" doesn't seem to work, and the client starts without this option enabled. Placing "-allow_remote_gui_rpc" in the "Start Parameters" works fine, but this is only a one time thing and doesn't stick when you exit the properties window. I am curious as to how other people got the service to start with this option every time. It would definitely help me because I have many computers running BOINC on my network that it is very inconvenient to physically walk to, and it would be nice to be able to use BoincView to control these clients.

I hate walking. Walking takes energy, and I am not allowed to use energy because it goes against my life principles of absolute laziness.

So you're saying that, in theory, simply adding the option to your ImagePath registry value so that it reads

Q:/Program Files/BOINC/boinc_cli.exe -win_service -allow_remote_gui_rpc

should work? This does not seem to work for me, and I have tried it on three different Windows XP Professional boxes. Any other suggestions?

I know all the slashes are backwards, this forum system doesn't display the correct slash.

!

This program is an add-on for the BOINC project, similar to the SETI@home I tool called SetiWatch. It can watch all BOINC clients throughout a network and lists all informations about these clients. The program can also log BOINC specific results.


BoincView

> Simply adding
> "-allow_remote_gui_rpc" to the end of ImagePath right after "-win_service"
> doesn't seem to work, and the client starts without this option enabled.

FWIW, I know a few people have looked in to fixing it, although I don't think any have provided code yet. The problem is the win service stuff is just very very funky, entirely in a seperate place from the other commandline switches, bypassing all of them.

Rob

This is ther first BOINC thread I have read in which an answer to a problem is given but there is no explanation of what the problem is supposed to be!

What is it you are trying to fix here? Eg, Boinc/Seti seems to work so far as I can see. What am I missing?

> This is the first BOINC thread I have read in which an answer to a problem
> is given

Unfortunately you are not right. No answer with a working solution was given.

> but there is no explanation of what the problem is supposed to be!
> What is it you are trying to fix here? Eg, Boinc/Seti seems to work so far as
> I can see. What am I missing?

Maybe you missed the scroll bar. You can also use the scrolling wheel on your mouse, or PgDn on your keyboard. Scrolling to the bottom of the page before replying is always a good idea. At most threads, you can find the the problem description just at the bottom (reverse ordering).

In this case, starting boinc_cli as service with Remote Gui RPC is being looked for. RPC is needed for monitoring and other tools, such as BoincView.

Well, this is _exactly_ what I (and others) originally did, but although boinc_cli starts as service without problems, it ignores the RPC argument, and can be launched in the RPC mode only manually after entering the -allow_remote_gui_rpc switch into the "Start Parameters".

Others had exactly the same experience with all available boinc versions, so I am little bit sceptical about your claim. I suspect that in BoincView you either use the file sharing (and not RPC), or in the same time had the GUI version of Boinc started with the RPC switch, or did not notice that the RPC communication does not work, since the client works normally even without it, of course.

The advantage of running it as service is aparrent - on many servers there is often no user logged in, so starting it in the user's startup folder is no option. There is also no need having the GUI overkill loaded in memory on PC's where you do not use it (since checking them remotely only).

Thank you all for your suggestions. The method detailed by RichiMeister is what I tried on all three Windows XP Professional systems, to no avail. User Rights is not an issue (I think...) because it runs perfectly fine and crunches away, just without remote gui rpc access. Because running BOINC as a service is a reliatively new feature that has not been used enough to work all the bugs out, I'm sure that its just a little bit "touchy" right now and it will improve over time.

Because it is currently "difficult" to use the remote gui rpc option while running BOINC as a service and doesn't work in many cases, I would like to put a good word in for Firedaemon here. Download at www.firedaemon.com. I have installed this on all the computers on my network to allow BOINC to run as a service and allow remote gui rpc connections. True, I had to physically walk to every one, but now that its installed and running, it works just fine and I can manage them all with BoincView from one computer.

To answer RichiMeister's question about why it is run as a service... I like having BOINC hidden from view from the owners of the other computers becuase they are very curious and have a tendancy to break things and like to keep their computers exactly how they want with no extra "stuff," so they only allowed me to run BOINC on them if it was completely hidden from view and they couldn't tell it was running. The best way to do this was to run it as a service. Also, sometimes their computers sit for hours on end with no logged in users, so running it as a service ensures that this time will not be wasted and that the computers can be crunching at all times.

> an other way to start the boincclient (not as a service)
> is to put it the RUN section of the registery, but you know this surely

I am not familiar with a way to run the client automatically at system startup, other than as a service. I know that it can be started automatically once a user logs on, but it is a requirement in my case to allow the client to run even when there are no logged on users. If there is a way to run the client other than as a service, and have it continue to run at all times when the computer is running, please let me know. In the meantime, firedaemon is working very well for me.

> > This is the first BOINC thread I have read in which an answer to a
> problem
> > is given
>
> Unfortunately you are not right. No answer with a working solution was given.
>
> > but there is no explanation of what the problem is supposed to be!
> > What is it you are trying to fix here? Eg, Boinc/Seti seems to work so
> far as
> > I can see. What am I missing?
>
> Maybe you missed the scroll bar. You can also use the scrolling wheel on your
> mouse, or PgDn on your keyboard. Scrolling to the bottom of the page before
> replying is always a good idea. At most threads, you can find the the problem
> description just at the bottom (reverse ordering).
>
> In this case, starting boinc_cli as service with Remote Gui RPC is being
> looked for. RPC is needed for monitoring and other tools, such as BoincView.
>
>
>
>

Jeez, you dont have to try so HARD to be a smart arse. You're a natural!

Your answer still doesnt make sense.

I do have exactly the same problem as "cheese"...
How can I persuade Win XP to start the BOINC service with that "-allow_remote_gui_rpc" switch all the time (e.g. automatically)?

---

BTW I cannot see any of the comments from "RichiMeister" - why? Were those deleted or what?

---