Works
fine with both screen saver and cli versions on Win 2K Pro for
me.
-----Original Message-----Sorry guys but i don't have such problems with Seti and my 2000 server machine. I have not had any problems with it or the OS. I run the command line in the background all the time and it works great. Hope you get the problem worked out.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Scott Brandt
Sent: Monday, January 15, 2001 3:04 PM
To: [EMAIL PROTECTED]
Subject: Re: running SETI on Windows 2000 Server
Scott
My experience was that Windows 2000 Server DOES NOT LIKE SETI. It did some really funky things like reboot, freeze, the blue screen of death, and alot of other things. When I stopped running Seti the computer worked fine.
----- Original Message -----
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 15, 2001 10:47 AM
Subject: running SETI on Windows 2000 Server
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
