When the "Communicating with Client popup displays, BOINC quits processing. No matter whether I hit Exit, Cancel, or close the popup, BOINC processing goes blank. If I shut down BOINC and restart it will not connect to the local host. The BOINC window stays blank. I have to reboot to get BOINC to work. I have an HP Pavilion a6750f with an AMD quad core processor, 8Gb ram, Windows Vista Home Premium 64 bit.

---

What I forgot to say in my prior post was that I'm using BOINC 6.6.36.

What is the solution to this problem?

---

Sounds like the BOINC Manager on your PC is having trouble interfacing with the BOINC core client on your PC. And that is why it can't restart as well.

It's using localhost to talk to, well, itself... well except for apparently Vista is stopping it from doing so.

Here is a thread I found with a similar problem a couple years ago:
http://boinc.berkeley.edu/dev/forum_thread.php?id=1592

---

Rosetta Moderator: Mod.Sense

Sounds like the BOINC Manager on your PC is having trouble interfacing with the BOINC core client on your PC. And that is why it can't restart as well.

It's using localhost to talk to, well, itself... well except for apparently Vista is stopping it from doing so.

Here is a thread I found with a similar problem a couple years ago:
http://boinc.berkeley.edu/dev/forum_thread.php?id=1592

---

Sounds like the BOINC Manager on your PC is having trouble interfacing with the BOINC core client on your PC. And that is why it can't restart as well.

It's using localhost to talk to, well, itself... well except for apparently Vista is stopping it from doing so.

Here is a thread I found with a similar problem a couple years ago:
http://boinc.berkeley.edu/dev/forum_thread.php?id=1592

BOINC will connect and run properly at startup. It's just that at some point during the evening the Communicating popup will popup and that's when the trouble begins. I'm not using the Vista firewall. I have Zone Alarm. I didn't have this problem prior to upgrading to 6.6.36.

---

As you say, then the issue is with BOINC and not Rosetta. BOINC handles all normal network traffic. The only exception to this would be when a Rosetta work unit tries to dump a stack trace after a failure. The error handling tries to use the network directly to process the symbol tables.

To pose your BOINC question, you should post to the BOINC boards:
http://boinc.berkeley.edu/dev/

---

Rosetta Moderator: Mod.Sense