Setiq and S@H CLI ?'s please help

[Clinth]

I'm trying to set up the new setiQ,But the lack of documentions is a pain. How to I tell the S@H CLI version to go to a specific sever address instead of directly to Berkley? Also will setiQ keep track of WU not being routed through it? I've got on machine not tied in to the Network so It does its own thing. Also is there any way to make setiQ hide the CLI version?

Thanks,
Clinth

 

[Fardringle]

If you are only going to have one computer use the buffer program, I would recommend that you try SetiDriver rather than SetiQ, since it will completely control the client (including hiding it) and will also cache work units for you, as well as keeping a log of the work done. SetiQ is a great program (we're testing it now for use as a Team proxy) but is better suited to larger groups of clients...

 

[Fardringle]

SetiDriver would also work for your computer that is not connected to the network since you can have it store work for you and it can also store the results until you want to connect (or you can copy the results to a computer with an Internet connection for uploading...)

 

[Clinth]

I'm sorry I didn't clarify I currently have one machine out of 4 not on my LAN. I was using the old SetiQ but lost the program during a HD replacement. So I started using Setidriver(also switch from GUI to CLI) for all the machines(setidriver on each machine) I finally noticed that SetiQ web site was back up with a new version. So I thought I would start using it again for the machines on my LAN but I'm not sure how to set up the CLI to get the WU from SeitQ instead of connecting to the net and getting it straight from Berkley. See I would rather use on caching program for all the machines on the LAN instead of a caching program for each.

Clinth

 

[Orange Kid]

If you want you can point your clients torawd the Team proxy and let us do the caching for you
just set your proxy info to;
orangekid.teamanandtech.com:5001 or
24.25.104.20:5001

The new Seti Queue works the same as the old one basically just the default port has changed---it is now 5517.

 

[Sukhoi]

I think he's talking about the CLI switches.

Make a shortcut to the CLI (or SETILog if you use it) and add the

-proxy IPort

switch. I think that's the right syntax.

 

[Clinth]

Sukhoi-Yes the CLI switches are what i'm looking for where /how to I set it up to use a proxy server.

Thanks
Clinth

 

[Orange Kid]

it needs to be done using a short cut.
1.)make a short cut on your desk top using what ever program you use to start the seti client [it is best to make the short cut in the directory and then drag it to the deck top]
2.)right click the short cut and go to properties
3.)edit the target area to add [-proxy IP#: PORT] no brackets though


then put this short cut in your startup folder and the client should start when ever you start your comp.

hope this helps



edit---you'll need a third party add on like setihide or setidriver to hide the client though

 

[Clinth]

Thanks you ror the help i got the shourt cut working. Now what setting do I need to use in setiQ on the server?

thanks

 

[Sukhoi]

No, SETILog will hide the client (well, it works with 3.0 CLI, dunno about 3.03 CLI) if you put SETILog in the same folder as the CLI and make the shortcut go to SETILog. SETILog will then automatically start the CLI with whatever switches you put in the shortcut to SETILog.