Cliff Beach wrote:

baskitcaise wrote:

baskitcaise wrote:

[SNIP]

There must be a global lock file or something that is stopping all
uploads
from any version of seti whether it is run by cli or ksetispy or
Ksetiwatch
no matter where they are situated and no matter what version.

The odd thing I can`t seem to figure out is that it is communicating
from the
machine as it connects and downloads new unit to fill the cache.

This has only started happening since the disk crash a few days ago at
Seti@home.

Anyone give me a clue?

I also have been having trouble returning "result.sah" using SETI@home
client Platform: i586-pc-beos Version: 3.08 and Version: 3.03,  my
problems sound just like yours.  Normally I use "setimgr" a unix type
Caching program to control uploads, downloads, and caching of extra
work_units, so I tried to manually sent the "result.sah with seti@home
client but failed with No errors when using the -verbose mode of client.

Since I wanted to return the finished "result.sah", I zipped up all the
folders that had not been returned and moved them to one of my Win XP
Pro machine using SetiDriver and returned the "result.sah" file without
any problems.  This has been going on for about 3 or 4 days.

Sorry, I can not help any further!

Cliff Beach

Boy am I glad that I am not the only one here.

Will see if I can delve even deeper

-- 
Mark
Twixt hill and high water.
N.Wales, UK.
Email is spam trap try baskitcaise at gmx dot co dot uk