UBBFriend: Email This Page to Someone!
Get 3DNow! Message Board
Team 3DNow! SETI
text-client bugs
profile | register | preferences | faq | search
|
UBBFriend: Email This Page to Someone!
|
Get 3DNow! Message Board Team 3DNow! SETI text-client bugs
|
| Author | Topic: text-client bugs |
| Cruncher Follower of Athlon |
 posted September 01, 2000 20:42  
I've got one that's cropped up lately. Win98 running on a ramdisk. Occasionally when the WU is finished and SETI client goes to the internet to return the results and get a new WU, I get a file called "wtemp.sah" and then the command client program shuts down. When I try to restart it, it starts, runs for about 15 seconds, then shuts down. SetiSpy is showing the WU is at 98%, but it doesn't go to the SETI site over the net to get the new WU and return the results. The only way I can get it to work normally after this is to kill the SETI data, the WU, user info, everything, then start over from scratch. Anyone got any ideas or info on what's causing this? How it can be fixed? Thanks IP: Logged |
| fredro Priest of Athlon |
posted September 02, 2000 04:24
i wont be of any help to you cruncher, but could you tell us what version that is? IP: Logged |
| Cruncher Follower of Athlon |
posted September 03, 2000 16:08
2.4 text-client full name of it is "setiathome-2.4.i386-winnt-cmdline.exe" IP: Logged |
| Cruncher Follower of Athlon |
posted September 03, 2000 16:27
More debugging info I restarted the text-client with backed up data and used the -verbose option. I did a screen snap of what the crash looks like and posted it on my briefcase on Yahoo. It's the file named "SETI_client_crash": IP: Logged |
| Cruncher Follower of Athlon |
posted September 03, 2000 16:30
This is the contents of the "wtemp.sah" file: type=result IP: Logged |
| Cruncher Follower of Athlon |
posted September 08, 2000 05:25
Hey I fingered out what it causing this! It's not a bug! It's just really cryptic programming! This is what the SETI client is supposed to do when you try to process a work unit that you've already processed before! It isn't programmed to give any error messages about "you need to get a new work unit, this one has already been done". It just writes the wtemp.sah file, then closes the program. I guess the guys who wrote the client figured at some point somebody would get around to emailing them about why this was happening, and they'd tell you the reason (but I guess they didn't plan on ultimately having millions of members worldwide either). I haven't seen a FAQ or Q&A forum on SETI anywhere that tells why this happens. I figured it out by accident by not backing up my data and trying to repost the packet results for a work unit I'd already done. I watched it do the wtemp.sah/close program routine and I realized then why it was happening. The fix was to kill the wtemp.sah and userinfo.sah files, then restart the client. It prompted me for my email address, relogged me back in and downloaded the file I screwed up on. Now it works fine again. Pass the word! Cruncher (I owe, I owe, off to work I go..) IP: Logged |
| All times are ET (US) | next newest topic | next oldest topic |
|
|
|
|
|
|
All submissions are copyrighted by their respective authors and are not for re-use in any form without their explicit written consent.
Powered by: Ultimate Bulletin Board, Version 5.37
© Madrona Park, Inc., 1998 - 1999.