Gary Heston wrote:
[...]

held off for various reasons are forced to switch or shut down. Many people
have not converted because their systems have had problems with BOINC which
were not fixable or easily fixable at the time they tried to convert. I have

Please take a look at the latest versions. Its been debugged on many thousands of users and their systems now.

If you do have any issues, the Q&A forums are keenly manned to help the swap-over.

issues with connectivity at the moment that limit me to one system that can
connect; the rest of the farm has been supported via SETI Queue. There's no
equivalent for BOINC, so at best I'll go from 13 systems to one. (I've got
more, I shut down several others due to utility bills.)

For the machine running SetiQueue, that one just needs to be run with "Internet Connection Sharing" instead.

If you're concerned about security, then you can firewall it to only permit connections to the Berkeley servers and nowhere else. You could even set up a proxy on that machine for yet greater control.

Slightly more involved than using SetiQ as proxy, but no more so than in that you are making up a non-standard network for yourself already.

Gary
79,475 results returned
118,025 years CPU time

With your experience I'm surprised you've got problems with Boinc & Boinc-s@h...

Happy crunchin',
Martin



For install help and step-through see:
http://boinc-doc.net/boinc-wiki/index.php?title=Installing_the_BOINC_Client_Software_And_Participating_In_A_BOINC_Powered_Project
in case you have missed something...

For a huge amount of help and information:
>     See:
>     http://boinc-doc.net/boinc-wiki
>     for all you might want to know about Boinc and s@h and other Boinc
>     projects!

And then there are the Q&A forums manned by some very keen and helpful fellow Boinc volunteers:
http://setiathome.berkeley.edu/forum_help_desk.php