Yes, I put Seti Queue on a Win98 machine a while ago, maybe a year,
and it has been flawless. I believe that it would work the same on any
machine you put it on. I do suggest though that you use names for your
network instead of IP addresses. I have names like Seti 1, Seti 2,
etc. . In the "proxy host" box in Seti Driver I put Seti 2 and it
connects regardless of whatever the IP address is. It is easier since
I use DHCP for most of my IP addresses. I currently have Seti 1 thru
6, 3 named machines, ie "dads", and I named "server". They all connect
just fine to the Seti Queue. I set the queue to do its connects at
10PM  so it connects in the nightime. I have cable. I also set the
depth to 4 to 5 days. I am currently returning about 40 per day, I
have cpu's from 300mhz to 2200mhz. I also ran a FreeSCO LInux setup
for a few days and it connected to the Queue no problem. The Linux
runs off a floppy so no hard drive needed, just a mb, ram, power
supply and a floppy drive.
I setup in the bios to NOT stop on any errors and the machines run
with no video cards. Oh, it does need a network card but I found some
on www.pricewatch.com for $5.00 each with free shipping. I can Seti up
and running for less than $100.00 and using an AMD 1700+ or so.

 On Thu, 10 Jul 2003 16:31:25 +0100, John Clark
<fredclark@consltec.demon.co.uk> wrote:

In article <v7sqgvs6q3hogdofrlb16f3rmktdel0o33@4ax.com>, f/f george
<an16365785@nonanon.penet.de> writes

If you also get a copy of Seti Watch it will show you the actual
processing times on each work unit per processor. I am not sure about
HT but it does work on my dual 300 compaq server.
Just remember to set the cache level at twice whatever the individual
machine does at the moment for dual and above processors. That way it
can handle units being returned at the same time.
Like my dual does 2 at a time so my cache level is 4. I use Seti Queue
on a different machine so I only need the minimum on each machine.

I agree this is the best way for multi-proc systems and networks.
Caching with SETI Que, dishing out to SETI Driver (local small cache)
and SETI Spy/SETI Watch monitoring.

Like you, I have a small home network. This currently consists of the
dual proc Xeon, a dual proc P3 and single proc P3. All run under Win2K
pro, and are peer-to-peer networked.

I am still playing with the Xeon system. When this is complete I want to
set it up as a SETI Que proxy, for the different SETI Drivers to send
completed units to and collect new WUs.

Have you any advice for when I move to this position, please?

-- Have you checked your Smoke Detector...LATELY?