I followed the instruction here: http://efmer.com/forum/index.php?topic=856.0

On a Windows XP x86 PC it worked in past.

Now an other PC with Windows 8.1 x64 it don't work.

From the 'log':
BoincTasks version: 1.67
Language ---- User: 1031 (DEU), System: 1031 (DEU), Selected: 1033 (ENU) Used: 1033 (ENU)
Maximum number of computers: Unlimited
Computers ---- BOINC2 , IP: localhost2
Computers ---- blabla , IP: localhost
Start BOINC client ---- The BOINC client started OK
Connect ---- Connected to: Host: blabla, IP: localhost, Port: 31416, BOINC Version: 7.6.22
Logging ---- Start debug mode
Connect, init ---- Host: BOINC2, IP: localhost2, Port: 31426, connection error


What's different between XP and 8.1?

As I installed BOINC v7.6.22, there was during installation something like 'allow BOINC access to folder' or something...
IIRC, this wasn't happen on the XP PC, with an older BOINC version (for 2+ years in past).

Now on the 8.1 PC I need to allow someone the access to the BOINC2 folder?

It's important where the BOINC2 folder is?
Maybe it must be in the C:\ProgramData\ folder?

Maybe I must adjust the Windows Firewall?
Open/allow a port?

It's important how I adjusted the Windows Firewall?
I can chose 'home' and 'guest/public' network.
Which I must chose normally, and/or if I want a 2nd BOINC client?


Thanks.


BTW.
In the BOINC2 folder is:
notices (folder)
all_projects_list.xml
cc_config.xml (with <allow_multiple_clients>1...)
client_state.xml
client_state_prev.xml
coproc_info.xml
daily_xfer_history.xml
gui_rpc_auth.cfg
stderrgpudetect.txt
stdoutgpudetect.txt
time_stats_log


BTW.
As I executed the .bat file with (Fred's example):
"C:\Program Files\BOINC\boinc.exe" --allow_multiple_clients --dir C:\ProgramData\BOINC2 --gui_rpc_port 31426
...a command prompt was open and the 2nd client was connected with BoincTasks.

But, IIRC, the localhost (1st client) wasn't connected with BoincTasks.

Maybe I need now with Win8.1 to start the 2nd client via .bat file?


If I 'install' a 2nd client (execution of the .bat file), BoincTasks and the 1st client can run, or all BOINC stuff need to be stopped/exited?

---

Disregard, I figured it out.

OK. I got it all working, but the only thing I am not sure of is how to make it do AMD tasks on one, and Nvidia on the other since the project still only see's one computer?

I am also trying to run 2 clients on the same computer. I am doing it to get one project to run both an AMD and Nvidia GPU I have installed. I can only get the project to run one right now even though I have a cc-config file with use all gpu's, and I have the preferences set in the project for both. It will only run my AMD.

I am a little lost on the instructions Bobcat gave. The .bat file for instance. How do I go about that? I know I can make it in notepad, but what do I name it and where does it go?

Yesterday late evening, a disruption happened on my system - I could not re-activate the monitor, neither by mouse nor by keyboard :-(
So I had no other choice than pushing the hardware exit button and re-boot the PC. And of course, the RAMDisk was emtpy, BOINC was gone.

This incident was kind of a sign for me to now change to the external USB3 HD (as I had planned it anyway if I can't get the second BOINC client to run).

So, this morning I re-installed BOINC on the external HD, and I do no longer need to care about observing unrealstic disc size requirements when downloading GPUGRID and ATLAS tasks, etc.

Again, many thanks to all of you who put in their time by providing these many hints and suggestions, in order to get my second BOINC to function.

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.

I have never had to do this, but I wonder if that is because the two clients have always run under different user accounts? Currently, client1 is installed as a service, and client2 runs under my account. In the past client1 ran under a restricted account I created specifically for running Boinc, and client2 ran under my account.

When I do Ctrl+Shift+F, a window called "BOINC Diagnostic Log Flags" opens.

That's the one. Make a change, 'OK' it. Go and have a look at cc_config.xml

It should contain everything described in the first two sections of Client configuration - Logging flags and Options.

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.

sorry, I read your post too late. When I do Ctrl+Shift+F, a window called "BOINC Diagnostic Log Flags" opens, rather than what you were describing.
Concerning making changes: in fact, each time I made these in the cc_config.xml, I had closed down BOINC before and then restarted it.

could you please tell me what exactly the cc_config.xml would look like then?
I now have as follows:

<cc_config>
<options>
<allow_multiple_clients>1</allow_multiple_clients>
<allow_remote_gui_rpc>
</options>
</cc_config>

When I open the BOINC manager, I get notices like
Unrecognized tag in cc_config.xml: <allow_remote_gui_rpc>
and
Error in cc_config.xml options
and
Missing end tag in cc_config.xml

I got interrupted by a phone call as I was performing my test, and had to go out for a bit, but I should probably amplify a bit.

Machine is Windows 7/64
BOINC was initially installed in user mode (primary instance runs GPUs). Executable files have been updated with self-built versions from head, as at early March this year. I'm pretty sure that doesn't affect the multiple clients issue - no change in that area from 7.6.22/.23/.29/.32 or wherever we're up to now.
Both program and data directories are located on a clean data drive: neither are in the protected C:\Program Files\ or ProgramData areas.

Having tested that the second Manager instance runs properly when the second client is running, I've tried without launching the client first. Nada - tried (and failed) to connect, no error message. In particular, no message about a bad password. Because this is on a secure private network, I have used BOINC Manager itself, and BoincView, to manage machines remotely for many years with an eight-letter password which is an anagram of wssrpoda - makes it easy to avoid errors in that department.

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.

okay, I guess I found out what you talk about. It now looks like this:

<cc_config>
<options>
<allow_multiple_clients>1</allow_multiple_clients>
</options>
</cc_config>

(again, the various lines are moved to the right, for some reason this cannot be reproduced here in the forum).

However, this did not help, either. The failure must be somewhere else, and I doubt that I'll find out.

Yes the <options> tags were missing.

I don't think BOINC cares about the layout in the cc_config.xml

I think this
<cc_config>
<options>
<allow_multiple_clients>1</allow_multiple_clients>
</options>
</cc_config>
or this

<cc_config>
	<options>
		<allow_multiple_clients>1</allow_multiple_clients>
	</options>
</cc_config>

would be the same.

If the BOINC Manager isn't connecting to the client you can check the stdoutdae.txt in each data directory to make sure each instances started as expected. Something you might want to give a try is either a remote_hosts.cfg or using the <allow_remote_gui_rpc> option in your cc_config.xml.
The <allow_remote_gui_rpc> options allows any BOINC Manger to connect to the client, if the have the right password, and using a remote_hosts.cfg only allows the IPs of the hosts in the file to connect to the client. The <allow_remote_gui_rpc> would be a quick way to test to see if there was a permission issue.

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.

okay, I guess I found out what you talk about. It now looks like this:

<cc_config>
<options>
<allow_multiple_clients>1</allow_multiple_clients>
</options>
</cc_config>

(again, the various lines are moved to the right, for some reason this cannot be reproduced here in the forum).

However, this did not help, either. The failure must be somewhere else, and I doubt that I'll find out.

I now created this cc_config.xml and put it into both BOINCs. Then I restarted the first one, then the second one.
Same failure as before: on the right-hand lower corner (in kind of a "status bar"), the two notices "connecting to 127.0.01" and "disconnected" change in intervals of a few seconds.

Just to be on the safe side, as I am surely not a specialist in creating xml-files. The one I did looks like this:

<cc_config>
<allow_multiple_clients>1</allow_multiple_clients>
</cc_config>

correct?

One one hand, it seems to me that I am just a tiny step away from succeeding, on the other hand, I suspect that for some unknown reason, it simply cannot made work here :-(

So, with the trial period of my RAMDisk ending in a few days, I'll give up the idea of having two BIONCs (one on the RAMDisc, the other one on the internal SSD). I will install it on an external USB3-SSD.

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.

I now created this cc_config.xml and put it into both BOINCs. Then I restarted the first one, then the second one.
Same failure as before: on the right-hand lower corner (in kind of a "status bar"), the two notices "connecting to 127.0.01" and "disconnected" change in intervals of a few seconds.

Just to be on the safe side, as I am surely not a specialist in creating xml-files. The one I did looks like this:

<cc_config>
<allow_multiple_clients>1</allow_multiple_clients>
</cc_config>

correct?

One one hand, it seems to me that I am just a tiny step away from succeeding, on the other hand, I suspect that for some unknown reason, it simply cannot made work here :-(

So, with the trial period of my RAMDisk ending in a few days, I'll give up the idea of having two BIONCs (one on the RAMDisc, the other one on the internal SSD). I will install it on an external USB3-SSD.

P.S. Unfortunately, the cc_config-xml text structure is not shown correctly here. In the second line, the arrow is placed exactly unter the underbar of the text in the first line.

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.

hm, sounds interesting.
However:
- there is no cc_config.xml in the "first" BOINC (in fact, in the "second" not either). But as far as I understand, I would just need to create one.
- the file "stderrdae.txt" here is two days old, and it's empty. No text at all.
So, the behaviour here seems to be different to what you got while testing.

I guess I now just create the cc_config.xml and put it into the first BOINC, right?

I found everything works better if each BOINC instance has a cc_config.xml with <allow_multiple_clients>. Then you will not have issues if you stop and start the instances in a different order.

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.

hm, sounds interesting.
However:
- there is no cc_config.xml in the "first" BOINC (in fact, in the "second" not either). But as far as I understand, I would just need to create one.
- the file "stderrdae.txt" here is two days old, and it's empty. No text at all.
So, the behaviour here seems to be different to what you got while testing.

I guess I now just create the cc_config.xml and put it into the first BOINC, right?

I currently have a dozen machines running 10 instances of BOINC. I have found that BOINC Manager does not connect to the client when more than one instances of the Manager is open. The second instance of BOINC Manager always gives me the message "Another instance of BOINC Manager is already running on this computer. Please select a client to monitor ". Individually I can connect to each BOINC client instance with no problem.

I start the BOINC clients in a single .bat like this:

boinc.exe --gui_rpc_port 31416 --dir %~dp0Data1\ --detach
boinc.exe --gui_rpc_port 31417 --dir %~dp0Data2\ --detach
boinc.exe --gui_rpc_port 31418 --dir %~dp0Data3\ --detach
boinc.exe --gui_rpc_port 31419 --dir %~dp0Data4\ --detach
boinc.exe --gui_rpc_port 31420 --dir %~dp0Data5\ --detach
boinc.exe --gui_rpc_port 31421 --dir %~dp0Data6\ --detach
boinc.exe --gui_rpc_port 31422 --dir %~dp0Data7\ --detach
boinc.exe --gui_rpc_port 31423 --dir %~dp0Data8\ --detach
boinc.exe --gui_rpc_port 31424 --dir %~dp0Data9\ --detach
boinc.exe --gui_rpc_port 31425 --dir %~dp0Data10\ --detach

Then I have a .bat to launch the Manager for each client I want to connect.
start_mgr_client1.bat

start ..\boincmgr.exe /n localhost /p password /g 31416 /m

start_mgr_client2.bat

start ..\boincmgr.exe /n localhost /p password /g 31417 /m

start_mgr_client3.bat

start ..\boincmgr.exe /n localhost /p password /g 31418 /m

I started with BOINC 7.6.22. Then I loaded 7.6.23 to see if it worked differently. The OS is Windows 7 64-bit & Windows XP 32-bit.

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?

I am using Symantec Endpoint Protection. In the chapter "Network Thread Protection" I now opened "configure firewall rules" and added a rule to allow all traffic for boincmgr.exe and boinc.exe
However, this did not help :-(

[quote]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.

But the Manager doesn't connect to a directory - and nor does boinccmd.

I used the wrong name. I was with my head elsewhere -soft pillows, warm covers- when I wrote that. I meant 'the right BOINC instance'.

@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?

---