An install (or update) to vista-64 or windows 7-64 creates the following at

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run]
"boincmgr"="C:\Program Files\BOINC\boincmgr.exe\" /a /s"
"boinctray"="C:\\Program Files\BOINC\boinctray.exe\"

It would be nice if the user could [x] an option to allow remote control (doing away with automatic install of boincmgr and tray) to get something like the following:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run]
"boinc"="C:\Program Files\BOINC\boinc.exe\" --detach --allow_remote_gui_rpc"

In addition, subsequent installs would default to having the [x] checked or not depending on what the user did on the previous install.

There is also the question of why the install goes to Wow6432 in the first place for 64bit programs.

But here's the thing: you never ever have to run boinc.exe!
So it's unintuitive to run a boinc.exe with commands from the registry, especially since you run boincmgr.exe already. And we both know what happens when you run BOINC twice. In normal circumstances it'll only run once.

So what you would want then is for the attribute commands to be enabled through BOINC Manager. Now, I don't know if you ever tried to run boincmgr.exe from a commandline with the following command: boincmgr -h, but those options shown there are the active ones. You may want to try any of them behind the boincmgr.exe line in the registry.

The /b option (boincargs)allows you to give direct commands from the client. So yours would be "boincmgr"="C:\Program Files\BOINC\boincmgr.exe\" /a /s /b --allow_remote_gui_rpc"

---

Ageless: boincmgr --help shows the /b option will pass commands to boinc but I was never able to get it to work. I downloaded the source code and looked at the module that does the parsing and the command arg parser would not validate --allow_remote_gui_rpc because it was not one of the command args to boincmgr. I tried putting quotes about the args to "/b" but that generated an error. The args to "-b" or "/b" are not forwarded to boinc.exe as AFAICT they fail the "rules" for boincmgr. It was simply ignored. That was two years ago and I remember a developer posting, about that time, that he thought that command "-b" had been removed long ago as it no longer worked. If it is now working, that is news to me.

Also, I have a farm of PC's and use boinctasks for monitoring instead of boincmgr.

I tried it again and got the same error message I got 2 years ago

Ok, then that doesn't work and you may want to ask the developers to make it work. Starting the client from the registry is never going to be done, though if you want to do it for yourself, then that's fine. Just saying it isn't going to be a public option because of permission problems and security trouble, amongst other things.

---