In article <8Daxc.65897$OI5.12243@edtnps84>,
Seti Cruncher <SetiCruncher@"NOSPAM"WildMail.com> wrote:
  [ ... ]

I Understand your concerns Raj, and feel the same way.  However, given the
security issues Auto-updateing may cause, I would like to believe the SETI
designers would include an option that would allow the user to manually
disable the autoupdate if they choose.

Too bad there hasn't been any mention of that, but I know the developers
are _real_ busy. No doubt they'll address little things like that when
the science and basic functionality are working reliably.

Auto Update works well for Windows XP

Ha! Dreamer! 

                                     and in a certain sense the current
SETI@Home project kinda does the same when you allow it to auto send in
results and retrieve fresh WU's, but at least we have the option of
disabling these features and manually handling the process.

Send/receive of WU and results is in no way comparable to changing the
programs' code under remote control over something as unreliable as
the Internet. Anyone running S@h on non-dedicated systems is rightly
concerned about auto-update; nodes in dedicated farms are not as much
of a concern.

I hope the final BOINC build will allow for the same option, or SETI may
lose a number of its crunchers.

Yes. Those of us with farms fed via SETI Queue and similar setups may 
have problems, too, if a comparable queueing method isn't available.


Gary

-- 
Gary Heston  gheston@hiwaay.net 

Contrary to popular opinion, _not_ everyone loves Raymond.