- Joined
- Feb 3, 2003
- Location
- New Zealand
This peice of software is pretty much exactly what i need.
As i have got enoguh parts to build a second computer bar one thing HDD. Even if i did have the HDD id only be using it to crunch SETI.
So i was wondering.
I use SETI Queue on my Main machine (see sig.) to keep a cache of WU's. While a was skimming over the Overclockix Description i remember seeing something about network drivers. Now if ive got it right that would mean that overclockix would be able to get its WU's via a modem/ethernet card.
If i give it all the right IP addys etc will i have anytrouble getting the SETI on Overclockix to talk to the SETI Queue on My Main machine?
Also i on Main SETI gets its work units via 127.0.01:5516 what IP would i give the SETI on Overclockix so that itl grab the WU's via the network rather than the internet? as before i used 127.0.0.1:5516 my own COmputer was D/Ling its WUs from itself via the net, this slowed things up a bit....
Hope that makes sense.
TIA
As i have got enoguh parts to build a second computer bar one thing HDD. Even if i did have the HDD id only be using it to crunch SETI.
So i was wondering.
I use SETI Queue on my Main machine (see sig.) to keep a cache of WU's. While a was skimming over the Overclockix Description i remember seeing something about network drivers. Now if ive got it right that would mean that overclockix would be able to get its WU's via a modem/ethernet card.
If i give it all the right IP addys etc will i have anytrouble getting the SETI on Overclockix to talk to the SETI Queue on My Main machine?
Also i on Main SETI gets its work units via 127.0.01:5516 what IP would i give the SETI on Overclockix so that itl grab the WU's via the network rather than the internet? as before i used 127.0.0.1:5516 my own COmputer was D/Ling its WUs from itself via the net, this slowed things up a bit....
Hope that makes sense.
TIA