Remember, it's not just the clients that is obsolete, the results is also obsolete. There is no point using some cache-software or other to upload results, since they aren't counted.
It's the same if you use a newer version of seti@home or a cache-program as SetiQueue. You will get this error-message:
"WARNING: discarding result because it is from an obsolete version of SETI@HOME"
I've just tested both methods, and no result is counted. You can't use the old version to upload, since it's a different server-name. To edit the hosts-file isn't useful either, old clients will just print an error-message then you tries to connect.
Old versions of SetiQueue on the other hand works great if you're using only 3.03-clients.
On win2k to use old version of SetiQueue, edit \winnt\system32\drivers\etc\hosts
and add this line:
128.32.18.166 shserver.ssl.berkeley.edu
It's the same if you use a newer version of seti@home or a cache-program as SetiQueue. You will get this error-message:
"WARNING: discarding result because it is from an obsolete version of SETI@HOME"
I've just tested both methods, and no result is counted. You can't use the old version to upload, since it's a different server-name. To edit the hosts-file isn't useful either, old clients will just print an error-message then you tries to connect.
Old versions of SetiQueue on the other hand works great if you're using only 3.03-clients.
On win2k to use old version of SetiQueue, edit \winnt\system32\drivers\etc\hosts
and add this line:
128.32.18.166 shserver.ssl.berkeley.edu
Comment