![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
Hi!
I'm new to this Newsgroup, but I have a very interesting problem. On my machine (Win2k SP4) the combination of seti command line client 3.08, seti driver and seti spy ran without any problem for about 100 WU's. So did the same combination of two other Win2k SP3 machines, but i didn't run these client very often. Then, one day about one week ago, when i started the seti spy, the client crashed. i tried any combination of restarting. deleting the *.sah files, reinstalling seti driver and seti spy, running the client barely without one of the helper applications. it crashed again and again. sometimes it happened, that the client finished a WU. but in most cases, it crashed. then i checked on on of the other machines: the same story. i left the problem as is, and when i reinstalled my machine (now with WinXP), i tried to run seti. it finished one WU and the story goes on..... Can anybody imagine what happened and how i can fix it!?!? greetings |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
How smart are SETI@homers? | Andrew Nowicki | Policy | 212 | June 3rd 04 01:02 AM |
SETI Driver 1.6.4.2 | Michael D. Ober | SETI | 0 | December 13th 03 03:44 PM |
G5 optimized Seti Client | Aske Andersen | SETI | 0 | December 4th 03 08:42 AM |
3.08 cmdline client won't connect | Jim Wilson | SETI | 8 | September 2nd 03 06:45 PM |
seti server Errors - Linux 3.03/8 Client | James de Lurker | SETI | 1 | July 10th 03 07:26 PM |