Robi wrote:

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
(2.9#@ 2.75 yrs)

Robi,

What do you do if even after changing the keys it still won`t return them?
What happens if you install a new one that has the correct keys and still
won`t return?

I have been trying for the last 3 days to send units from this machine have
tried with ksetispy, ksetiwatch and from the commandline with the old
setiathome 3.03 I have been running for 5 years, with a newly installed 3.03
and with a new 3.08 ( d/loaded yesterday ) client all complete the units but
when returning they just sit there with NO error messages.

I do the initial reg and unit d/load with the cli so that I get the id strings
correct.

Have installed over the old ones, made new folders and tried from there but no
joy.

This morning I have started another new installation and am running it from
the cli to see if it will work without any intervention or monitoring tools
to see what happens now.

the machine next to this one on the same network has had no prblems
whatsoever.

If this unit does not go I will copy the full dir from the other machine to
this one and see what happens.

I will keep on trying if only to get past the 5 year mark next month.

If things get that bad I might boot into windows and install on there to see
if that has any affect :(


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