I have been running the 3.0.i386-winnt command line version of SETI on a
Windows 2000 Server machine for about a month.  The machine was mysteriously
rebooting occasionally, and in comparing the event log to the SETI log I
discovered that each reboot was just after a SETI unit was sent in and a new
one downloaded.  Once I stopped running SETI on the machine, there were no
more reboots.  Does anybody have experience with running SETI on a 2000
Server machine, and if so have you experienced this problem and/or know what
might cause?

Rocky

Reply via email to