Question regarding SetiQ and state.sah file?? One SETI computer DOWN!!

[JustStarting]

One of my machines froze up today- probably about the time it was transmitting by coincidence. When I restarted it went to transmit and asked me to enter existing account (2) and email. The dos screen just sits there now and won't do anything. SetiWatch says the computer can't find the state.sah file. I imagine this is because it deleted the temporary files when transmittting my info. Could I copy state.sah from my other computer to get it going?? I also have SetiQ installed on my other computer with the problem one as a client. It says there is a passthrough queued, but not doing anything. It won't transmit to Berkely due to obvious problems there. Basically- how do I get this computer crunching again.

 

[Poof]

If the directory where SETI is running still has a user_info.sah file (or you have one on another machine somewhere), then make sure that is in the SETI directory on the machine that is stuck, delete all the other files in there except for the SETI executable, and try again. As long as you have a user_info.sah in the directory, you won't need to login to SETI. The state.sah won't make any difference - I think in this case, the result may have uploaded and then something got interrupted on your machine, and some of the temp files (including state.sah) never got deleted.

[EDIT: If you don't have a user_info.sah, you might be able to create one from the info that Setiqueue has - I think file "user_info.txt" can be copied over and renamed to "user_info.sah".]

 

[JustStarting]

The WU did not complete loading. There was no state.sah file (couple others missing also- user_info etc..). I had a cache of 10 WU's that I downloaded from SetiDriver and "hid" them in my documents. I deleted the existing #1 folder and placed a saved WU in the Seti folder and renamed it #1. All is fine except I'll have to finish that WU before my computer shows back up on SetiQ.

 

[Poof]

Okay - good luck with that then... 🙂