What makes you think that Seti is actually working on the old unit as
well as the new one?

On Wed, 3 Mar 2004 09:15:22 +0100, Visje <thewiz@zonnet.nl> wrote:

Hi everyone.

I've been processing WU's for about 3 years now, and finally I upgraded 
my compu to a real system. So my first thought was to start S@H with a 
cache of WU's. I already used SetiSpy, and I wanted to use SetiDriver 
for the caching.

Everything went well, untill I discovered the SetiSpy log told me I 
completed more WU's than Seti indicated. I then compared the WU's and it 
seems that I'm processing the same WU twice, so it's been send back 
twice aswell.

When I look at SetiSpy it switches between WU's. S@H is working on a new 
unit from the cache, but also a unit that had recently been completed.

I don't like the fact that I'm working on the same unit twice, let alone 
the fact that I'm bothering Seti with redundant data.

Can anyone tell me how to solve this problem?
I've tried the following:
* SetiSpy & SetiDriver in a folder.
* S@H in a subfolder
* All WU's in subfolders, like Setidriver does. (no wu's in de setispy 
or S@H folder)

Then the unit s@h is working on is copied to the SetiSpy folder and S@h 
starts working on it, but SetiDriver points to a subfolder, so S@H is 
working on that one aswell.

I use the latest versions of the three programs.

For now I have the cache set to 0 to complete everything and then I'm 
going back to just SetiSpy. :(