Message boards :
Number crunching :
Communicating with BOIINC client. Please wait ... (I am STILL waiting ...)
Message board moderation
Author | Message |
---|---|
Jim Wright Send message Joined: 3 Sep 99 Posts: 36 Credit: 54,761,763 RAC: 17 |
It all started a several of weeks ago when BOINC persistently failed to communicate with the Seti systems. Something about an http error. I was running the then new BOINC_7.0.64_windows_x86_64. So I switched back to a prior version (BOINC_7.0.28_windows_x86_64) and the problem went away. OR did it? BOINC seemed to be O.K. and work flowed through both Seti and Milky-way. Since things settled down for a while, I left it alone and then got the bright idea to try 64 again. O.K. for a while, then the same failures reappeared for Seti. Milky-way continued merrily on. Switch back to 28, try 64 a few days later, back to 28, then 64 again. Now everything fails with the "Communicating with BOINC client. Please wait ..." message and nothing is happening. I last uninstalled BOINC, went into the registry and removed anything BOINC, rebooted, reinstalled 64, failure, reinstalled 28, failure (a couple of times). I cannot get BOINC to function at all. There was also a complaint about the app_info.xml file not able to process Astropulse. The system is AMD Phenom II X6 1055T, 8GB RAM, 64-bit OS, Windows 7 Ultimate with Service Pack 1 and all current updates. The GPU is NVIDIA GeForce GTX 465. TThrottle is installed and active to limit system heat. There is a long list of other programs installed and I use the system heavily. HELP!!! Thanks, Jim Wright |
Jim Wright Send message Joined: 3 Sep 99 Posts: 36 Credit: 54,761,763 RAC: 17 |
P.S. three other machines of different vintages are running fine. JCW |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.