Martin wrote:

Corrupt user_info.sah? (If so, copy your backup, or just delete it and
relogin to the s@h servers.)

lock.sah file remains even when no s@h process? (If so delete it.)


If you wish to recover the WUs crunched with the corrupted user_info.sah
details, then use the following details:

(From a quick check on newsnet sci.astro.seti and alt.sci.seti)

 >>>>
I poked around on some archives. Here's what I found to clear up the
problem:

1. I deleted the file user_info.sah.

2. I ran seti@home and re-entered my e-mail address. This puts proper
data in the user_info.sah and then fails again with the "Unknown Fatal
Error: 100"

3. The result.sah file had bad values for "id" and "key". These are the
second and third fields in the result.sah. I got the proper values for
these from my user_info.sah and corrected the fields in the result.sah.

4. I then started up seti@home again. The result was returned correctly
and everything was happy.

Somehow, the user_info.sah gets corrupted and then it corrupts the
result.sah with the wrong id and key. You just need to fix those twho
things.

Hope they fix whatever is causing this.

--phil
 >>>>


and for SETIDriver users:
 >>>>
no, but I know how to fix it ;o)

first, copy the file "user_info.sah" from the SETIDriver root directory
into the directories with the "messed up" returns.
Then open the "user_info.sah" with wordpad and the "result.sah" in each
folder that has the "messed up" returns and replace the following info
result.sah                          user_info.sah
-----------                         -------------
user_id=0    with the number from   id=xxxxxxx
user_key=-1  with the number from   key=yyyyyyyy

and then just hit the [Transmit] button in SETIDriver

HTH

--
Robi
 >>>>


Good luck,
Martin

Thanx Martin but unfortunately this does not cover the problem, I have
completely installed 4 different new versions of seti, the 3.03 and 3.08
clients in new dirs and no matter how I start them or monitor them ( cli,
ksetiwatch or ksetispy with cache ) when the units finishes it will just not
send.

If I zip the dir and place on another machine on same network running
identical Suse 8.1 with ksetispy it sends the result, so by the process of
elimination it must be something on this machine, ksetispy does communiicate
with seti as it will refill the cache that the completed unit has left empty.

I have now copied the complete working dir of seti from the good machine over
to the bad one and completed a unit and it still will not send.

So it must be something external from the actual Seti dir as nothing was added
or changed from the good machine.

However if I move the cache dir over to good machine it transmits the unit so
there can be nothing wrong with the .sah files

I will take drastic action and restart the firewalll on the server to see if
that does anything but I cannot find anything in the logs.


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