Randall Schulz wrote:
[...]

1) The SETI@home client tends to "stall" occasionally--maybe once each
day--and must be manually stopped and restarted to get it going again.

Never suffered that, on either Windows or Linux machines.

2) The extrapolation of the remaining time is non-linear, indicating that
progress near the beginning and end of the work unit proceed much faster

[...]

Yes, this is well known and can be calibrated out in such as SetiSpy for monitoring s@h classic.

Has anybody else noticed these phenomema? Does anyone know why they
happen? In the case of (1), is there a way to prevent this problem?

Machine or CPU overheating? Overclocked? Choked with dust? PSU on its way out?? Other bad hardware or a bad 'interaction' with whatever Windoze virus scanner??


Good luck,
Martin