Some SETI Advice, Please!

[JimMc]

I'm going to move two W2K machines, a 1.3 Gig TBir and a 933 Celery over to SETI, my crack rack will continue to run RC5 for a while.

Here's my setup--cable connection to the Tbird, the TBird is now running the pproxy for the rack and the celery. The Tbord is using 192.168.0.1 for the LAN NIC.

I have installed SETIQ on the TBird and it seems to be running in the tray. Which SETI client should I use? I can't figure out how to get the SETI CLI to start up in the tray and see SETIQ, should I install SETI driver also to point it to SETIQ and will it run the client minimized at boot-up?

I'm using SETIQ 'cause I assume it's the equivalent of running a DNET proxy to track all the machines. And I assuming there is somewhere in SETIQ that I can point it to fetch/flush through the TA proxy?

Sorry for the stupid questions....

 

[JimMc]

I installed SETI Driver, fooled around with some settings, and it now appears to be crackin' away--I've finished 4.91% according to the progress bar in SETI Driver and I have a little purple shape spinning on the star map in SETIQ, which I suppose is what should be happening.

So if I put SETI Driver in my startup folder, everything will hopefully fire up automatically at boot....?

 

[ElFenix]

the other thing you might have done was use setispy to launch and control the client. it provides a bevy of statistics, including current WU figures, past result log, a star map, and current user stats. it can also start, hide, and point the client at a proxy. but it sounds like you've got it with setidriver.

 

[Baldy18]

SetiQ is the way to go if you want a proxy for several conputers on a LAN. Just do a thread search and you will find many threads that will help you in setting this up. One thing that is different between setiq and setidriver is that setiq doesn't control the client like setidriver does. Instead you will want to startup the client with setilog and I also you setiwatch for additional (and more accurate) monitoring. Make sure you check out those threads, you should be able to get all info you need from them. If you need anything else you can PM me. Hope this helps.

 

[Sukhoi]

Yeah, just use 192.168.0.1:5517 (default port) as the proxy server for all your clients.

Just put a shortcut to SETI Driver in the StartUp folder and go into the shortcut properties and have it start minimized. 🙂

 

[soni]

Remember you can install SetiQueue as a service in Win2K
That way you dont have to be logged in to have setiqeueue running

It's done by making a shortcut to the setiqueue.exe file
Edit the shortcut (right click - properties)
Add -i after the setiqueue.exe in the target textbox part.

Run the shortcut, then Setiqueue is installed as a service!
It is not runnning yet, so go to Services in control panel/NT4 or Administrative tools/2K
Select services scroll down to SetiQueue, choose start and remember to set it to automatic start!

If you reinstall SetiQueue (by running the shortcut again f.ex.) you have to do this again!

Then the queue is installed as a service and you can't see it in the tray!
If you want to administrer the queue, you can stop the service and run setiqueue.exe or set up setiqueue with a password and administrer it by webbrowser (this is the way to do it!)