Mark Taylor <mtaylorx@xlrim.com> wrote in message news:<Xns94C372C96532Amtaylorxxlrimcom@66.170.196.249>...

Bill <bill@c.a> wrote in news:gKydnSBbOaoEXe_dRVn-uA@golden.net:

f/f george wrote:

Right now I'm trying Setiwatch, and it's pretty good except for one
minor problem. Under the User tab, the "units per day" is always 0.88
and doesn't increment even though my P4 crunches about 7 work units a
day.

I have it set up on my server, a 300mhz dual cpu machine, I KNOW IT'S
SLOW! About 19hrs per unit!
It shows the total number of units completed as well as the total
number per day completed by all the machines on my account.

I only have SAH running on this one computer.

I noticed today the total number of completed work units is low as it
doesn't match the user_info file in my main seti folder. And it still
does not update the units per day beyond 0.88 - it's always that same
number, which is odd.

However, I think I figured out why.

Setiwatch is only reading the information from the Setilog.csv file and
the currently processing cache folder (which always has an older
user_info file). I noticed that if I uncheck the option for SetiSpy in
Seti Driver, then delete the SAH files, everything still works the same.

Oh well...

I had this problem and what I did was blank (delete) the entry in the
number of work units per day. Exit watch and restarted it. Number of
work units per day updated correctly afterwards.