Posts by Chocolate eater

1) Message boards : Questions and problems : Boinc manager loops when connecting to client (Message 37028)
Posted 26 Feb 2011 by Chocolate eater
Post:
Oook, I figured it out. Hunting for the data directory (which I found out should be under C:\Programdata, which it still wasn't), I reinstalled BOINC and selected to run the installation as administrator. I hate the UAC.... Thanks for your input!
2) Message boards : Questions and problems : Boinc manager loops when connecting to client (Message 37027)
Posted 26 Feb 2011 by Chocolate eater
Post:
I have not yet been able to set up any projects, as this is a clean installation. This happens before I can start adding projects.

Seems no data directory exists. The binary files are in Program Files (x86), and so the data directory should be in the Program files directory?
3) Message boards : Questions and problems : Boinc manager loops when connecting to client (Message 37025)
Posted 26 Feb 2011 by Chocolate eater
Post:
Hi!

Yes, boinc.exe is running. I just watched it for a few secs. Seems every time the manager tries to connect, the memory use for boinc.exe goes to approx 60-75k. Each time the manager stops the connection, the memory use drops to around 30k. At the next connection attempt, the memory use goes up to 60-75k, again.

Hope this gave some meaning :)
4) Message boards : Questions and problems : Boinc manager loops when connecting to client (Message 37023)
Posted 26 Feb 2011 by Chocolate eater
Post:
Hi, all.

I've just installed BOINC on my Win7 x64 machine. I have enabled Boinc manager, client and screen saver through my firewall. When trying to telnet on localhost using the Boinc port, I get a connection.

However, when starting Boinc manager, the manager says it's connecting to the Boinc client. But that's all there is - it does this repeatedly, and goes into some kind of loop.

Any ideas?

Best regards,
Chocolcate eater




Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.