Just for the information

Why I say there is not much reason in hiding computer, even for work one is that people cannot see a lot about them

Just OS, CPU and benchmarks really


i.e. This much
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=212252
and
https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=2322

That's pretty muich it.

Nothing to even remotely say where the computer is or anything.


You can see a lot more about your own computers, e.g. IP address, names of them etc but we cannot.

OK, I unhid my computers based o what you guys have provided for feedback. Hope this helps.

Well the Xeon seems to be returning and collection jobs fine and running happily.
-So either ignore the fact you cannot use BoincManager to monitor them if you really must use crunch3r's or 5.2.13 (you don't need BoincManager running for boinc to work)
-If you do need to monitor them use BOINCView in file read mode (though you cannot control it in that mode)
-Try monitoring it over a network, strangely seems to work on my client when they have this problem. (BoincView is easier for this, in RPC mode)
-Switch to Truxoft calibrating client (it should default to the other port, else specify it manual with the configuration files in truxoft)
-Switch to a newer Boinc 5.4.x version (and maybe try with Truxoft-cc if you must inflate benchmarks)

---

Team mauisun.org