SETI@home - 2004-06-25 05:42:17 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-25 05:42:26 - Scheduler RPC to
SETI@home - 2004-06-25 05:42:26 - No work from project
SETI@home - 2004-06-25 05:42:26 - Deferring communication with project for 4 minutes and 14 seconds

SETI@home - 2004-06-25 05:46:49 - Message from server: Not sending work - last RPC too recent: 263 sec

Why do I get the message "last RPC too recent" when the timing was set by the program. Also the "deferred communication" is anywhere from about 1 minute to 3+ hours. I'm on a dial-up, I probably won't be on-line three hours from then. Is it a safe bet that your new splitter will moot this set of problems?

(Using AMD XP2400, Win98se & v3.19 - if it matters)

S@H has a requirement of 10 minutes of timeout between communcations sessions. BOINC is multi project, so this is not enforced on the client. It is my belief that the project server should send a minimum timeout to the client, but this has not happened (yet?).