If you're using a modern client, like the recommended v7.6.22, the easiest way to update configurations is to use the Event Log Options tool (Ctrl+Shift+F) - make a trivial change and click 'OK'. That creates a template cc_config.xml file with every possible tag present, and all spelled correctly :-) Then just modify 0 to 1, or whatever, for the tag you need. Did I say I restarted the primary client after making that change? It feels like one which would only take effect at startup, rather than through 'read config files' like some others.

You are very close, but your cc_config.xml is not formatted correctly. See http://boinc.berkeley.edu/wiki/Client_configuration
You are missing some tags.

OK, as I suspected, curiosity got the better of me. I created the two batch files BobCat13 suggested in the message I'm replying to.

And it failed. Watching the changes in the second data directory, I saw a file stderrdae.txt being created, with the contents

05-May-2016 15:50:59 Another instance of BOINC is running.
GLE: Cannot create a file when that file already exists.

 (0xb7)

Armed with that information, I edited the cc_config.xml file for the first (originally running) instance, with the

<allow_multiple_clients>1</allow_multiple_clients>

option, and restarted the first client. After that, everything worked as advertised. Two different clients running (two instances of boinc.exe in Task Manager), two different instances of boincmgr.exe in Task Manager as well, two different displays on screen with different project lists, etc. etc.

@Erich, what firewall do you use, and did you add boinc.exe and boincmgr.exe to it? If just the Windows firewall, what are the settings used?

[quote] They considered using BOINC a few years ago, but couldn't make it fly. However, it does give us another useful option in situations like the present.

[quote] They considered using BOINC a few years ago, but couldn't make it fly. However, it does give us another useful option in situations like the present.

Ah OK, but if he's already having trouble connecting two BOINC Managers, he may as well have trouble connecting boinccmd to the right directory.

There is very little GPUGrid work at the moment anyway, so it could be much ado about nothing.

Maybe I mentioned this elsewhere, but at the risk of repetition: In comparable situations, I just do Folding on the GPU, and use BOINC for the CPU projects. They get along together fine in most cases, except when a VirtualBox project is involved, in which case Folding can crash.

When you then start the first BOINC, it will no longer be attached to GPUGRID, but when you start the second instance, it will be.

You can also attach the first BOINC to GPUGRID, then move the account_*.xml file over to the second BOINC instance's data directory. ...

You did stop/start the client, correct?

...But that assumes that the second client is running, that it's listening on the correct port, etc. etc. etc. I think you get the same "incorrect password" error message whichever part of your configuration is wrong.

The best was to do it is to have both data directory folders open and drag from the first client to the second client choosing the Copy option.

For the second BOINC instance, use 'localhost' or '127.0.0.1' (you'll have to experiment), and use the "computername:port" format as described for the boinccmd tool.

The alternative BOINCTasks manager is apparently much easier to get working with a second client.