I just installed the program. I have it set NOT to startup when I turn on my PC. The \"select computer...\" thing has nothing to choose. I put in \"localhost\" but that did not work. I have tried with my firewall off as well, still no dice.

Guess what I need is info on how the heck I get started, have not really been able to find anyone having my issues.

---

\'Select computer\' is for people with lots of computers, and to use it with the \'fill ins\', you need two extra files.

To use it with a single computer, you click OK, with the 2 fields left blank.
This will select \'localhost\', the computer you are using.
If this is successful, it will say \'Connected to localhost\' on the right hand side of the bottom blue bar of the Manager (gui).

What this means, is that the 2 parts of BOINC are talking to each other. One is the Manager, and the other is the worker, or child process.
However, this connection should happen automatically when you run boincmgr.exe

Before you try to attach your computer, go to your account page and create a password. Remember this password!

To get to the Oxford site, you use \'Attach to project\', under Projects in the menu. The url is http://climateprediction.net, which you should have received in an email.
The password is the one that you\'ve just created.

You should now be in business. If not, ask again.

It wont let me select a project. When I try that it tells me \"Bionic is not connected to the client.\" All I did was download the Bionic app and install it, after making an account. Just does not seem to want to work and the help in the program is pretty much useless for that issue.

---

In the menu, click Select computer.
Then click OK, with the 2 fields left blank.

If this is successful, it will say \'Connected to localhost\' on the right hand side of the bottom blue bar of the Manager (gui).

If it doesn\'t, then your firewall is blocking the connection between boincmgr.exe, and boinc.exe
They \'talk\' via port 80.

You\'ll have to tell it to allow these two access. (They may have a different name in the BBC version.)

\'Select computer\' is for people with lots of computers, and to use it with the \'fill ins\', you need two extra files.

To use it with a single computer, you click OK, with the 2 fields left blank.
This will select \'localhost\', the computer you are using.
If this is successful, it will say \'Connected to localhost\' on the right hand side of the bottom blue bar of the Manager (gui).

What this means, is that the 2 parts of BOINC are talking to each other. One is the Manager, and the other is the worker, or child process.
However, this connection should happen automatically when you run boincmgr.exe

Before you try to attach your computer, go to your account page and create a password. Remember this password!

To get to the Oxford site, you use \'Attach to project\', under Projects in the menu. The url is http://climateprediction.net, which you should have received in an email.
The password is the one that you\'ve just created.

You should now be in business. If not, ask again.

Ok I got it to work, my WinXP firewall was not allowing the Bionic app to communicate. Once I set that up it worked.

---

How this thing works doesn\'t seem to be being very well explained. I have the same problem as Zoomer. The Boinc manager doesn\'t allow you to add a project because, it says, it can\'t do that as it\'s not currently connected to a \"client\" (therefore please do a select computer etc.). When I select localhost to connect to, it replies that it is unable to.

It\'s not actually obvious from the documentation or advice on the forum that Boinc is in two halves (a \"manager\" and a \"client\"). It certainly doesn\'t spell this out when it\'s installing. I know the manager is running - because I can see it - but how do I know if there is a client running? How does it start? What is the process name? Does it have any visible aspects?

What, exactly, is the password that it requests when I do try to connect to localhost? I\'ve tried the account code, my XP login, and some random passwords and no password for good measure. None of them work. Is this because they are all wrong or is it because the client (whatever it is - see above) isn\'t actually running?

Just to note - I was running the climatechange program happily for a couple of weeks and then it stopped and the vanilla Boinc screensaver took over from the climate visualization. Perhaps a Windows update decided it was malicious software? In any case, I\'d like to continue donating the electricity and cpu cycles but currently it\'s at a frustrating brick wall.

Cheers,
Martin

\'Select computer\' is for people with lots of computers, and to use it with the \'fill ins\', you need two extra files.

To use it with a single computer, you click OK, with the 2 fields left blank.
This will select \'localhost\', the computer you are using.
If this is successful, it will say \'Connected to localhost\' on the right hand side of the bottom blue bar of the Manager (gui).

What this means, is that the 2 parts of BOINC are talking to each other. One is the Manager, and the other is the worker, or child process.
However, this connection should happen automatically when you run boincmgr.exe

Before you try to attach your computer, go to your account page and create a password. Remember this password!

To get to the Oxford site, you use \'Attach to project\', under Projects in the menu. The url is http://climateprediction.net, which you should have received in an email.
The password is the one that you\'ve just created.

You should now be in business. If not, ask again.

---

The connection is supposed to be transparent to the user.
The manager starts, and this starts the \'worker process\'. (Also called: \'child process\', and \'worker daemon\'.)
However, some people have a lot of programs in their startup folder, and the managers attempts to get it\'s worker going are delay by Windows starting all of the other programs. So the manager thinks that the worker has failed in some way, and times out.

You can fix this by removing unneeded programs from the startup folder, and running them manually as and when required, or by removing the BOINC shortcut from the startup folder, and starting it manually when windows has settled down.

The trick with using \'Attach computer\', is to specify the computer that you are using, i.e. localhost. To do this, click OK without anything in the 2 entries.
\'Attach computer\' is normally used by people with lots of computers, (a \'farm\'), who need to look at one of them remotely. The \'computer name\' and \'password\' is the one associated with one of these computers.
And you need extra files to make this work.

You can see the 2 parts of BOINC in Window\'s Task Manager.
The manager is: boincmgr.exe, and the worker is: boinc.exe

Does this help? If not ask again.

I would infer from this response that boincmgr actually starts boinc.

If this is the case, I should be able to run boincmgr any time and I\'d expect it to start boinc. This would be completely independent of anything going on at startup time since it can be done when the computer is up and running and relatively idle.

I see no such attempt by boincmgr to start the client. Also, in case I\'m meant to infer that boinc.exe is also in the startup folder, it certainly isn\'t in my installation.

To confirm, however, the problem was simply that the client was not running. If I start boinc.exe manually then the manager connects without any issues.

The open question, then, is why the client is not starting automatically - and achieving the transparency referred to.

Zoomer - in the mean time, you should be able to go to the Program Files\\Boinc folder and run boinc.exe from there. Then try doing the connect to local host (or leaving the dialog box fields blank). You should see, as I just did, that the connection starts and you can attach to the project.

Cheers,
Martin

The connection is supposed to be transparent to the user.
The manager starts, and this starts the \'worker process\'. (Also called: \'child process\', and \'worker daemon\'.)
However, some people have a lot of programs in their startup folder, and the managers attempts to get it\'s worker going are delay by Windows starting all of the other programs. So the manager thinks that the worker has failed in some way, and times out.

You can fix this by removing unneeded programs from the startup folder, and running them manually as and when required, or by removing the BOINC shortcut from the startup folder, and starting it manually when windows has settled down.

The trick with using \'Attach computer\', is to specify the computer that you are using, i.e. localhost. To do this, click OK without anything in the 2 entries.
\'Attach computer\' is normally used by people with lots of computers, (a \'farm\'), who need to look at one of them remotely. The \'computer name\' and \'password\' is the one associated with one of these computers.
And you need extra files to make this work.

You can see the 2 parts of BOINC in Window\'s Task Manager.
The manager is: boincmgr.exe, and the worker is: boinc.exe

Does this help? If not ask again.

---