More SETI problems....

[Stallion]

Here is the latest problem SETI is now giving me. I loaded it on my Parents PC (coppermine 600) and it usually spits out a unit in 6-7 hours no questions asked and yet as of friday it started to do a unit and when it was finished it wouldn't send in the unit, it would just go to idle. So I had to go to there house and manually start it back up and it would then send in the unit and the down load another. Then the same thing happened, it processed the unit then went to idle. I was back over there today to manually re-start it. But it looks like it has gone back to idle as the unit hasn't been sent in yet.

Has anyone else had this problem? I'm running the 3.0 text only.

 

[BadThad]

The obvious first, I assume they have an always on internet connection? Do you get the message "will retry in one hour?"

If not the above, I would try a new exe file...perhaps that one is corrupt?

 

[Stallion]

Yep, they have cable.. I has worked great for about 3 months now I don't have a clue. If I could just keep all these things running I could do close to 90 units a week, I got 85 last week. But alas, it's not meant to be.

 

[blade47]

One of my remote machines does that sometimes. I have no idea why. If it can't connect to the seti servers one day it may wait several days before it'll connect again. Luckily I run setiQ on it so it keeps crunching. The simpliest thing to try would be to do a fresh install of the client in an empty directory.

Are you running SetiDriver?

If it were me I'd do a fresh install of the client and SetiDriver on that machine and set SetiDriver to auto transmit. A caching program is always a good idea with all the server outages.

 

[Stallion]

Nope, no SETI driver but that might be a good idea if I want to stay in the hunt.