A call to arms!

[High_Jumbllama]

I decided to wait until the Genome client is more developed if I'm to put it on machines other than my own.

Woohoo now looking at under 16 hours per unit. Those tweaks helped out a lot.

[Pace]

Let's celebrate.

____________
<a href="http://www.distributedatmurc.co.uk">Dist@Murc</a>

[Guru]

I wonderd were you would move the site! When will you move the files?

[Zyn]

hey guru, you think we could have our own private murc seti wu download center? so that we dont have to keep waitng for berkeleys down tiwe.

iv lost half if not more of my wus due to berkeleys cruddy servers.

[Zyn]

guru?

[Guru]

All my ip's are static! So I don't think it's possible for me! Have you checkt out tlc as I told you? http://www.teamlambchop.com/queue.htm

Public SetiQueue Servers

Many of you know that Berkeley has been under some horrible bandwidth problems. This has affected the S@H project big time since the contact with their data servers
create a major bandwidth drain. The University has decided to make traffic to the S@H data servers low bandwidth and it has caused major problems in sending results and receiving work units. This bandwidth cap for the project is only for certain hours and contact with the data servers is best done in the early hours to the Berkeley campus (local time that is). For more information on their bandwidth problems see this link.

Some members of TLC and others have set up some public SetiQueue servers to help ease the connections to the S@H servers. Here are a list of the currently available servers (more will be added if they come available):

http://jdaw.cjb.net:5517/

http://jdaw.cjb.net:443/

http://kulish.com:5517/

http://gms8994.dyndns.org:5517/

http://www.dbestern.com:5517/

http://goobland.dyndns.org:5517/

http://setiq.new-swankton.net:5517

http://www.irishguys.org:5517

You do not need to have SetiQueue installed to access these servers, all you need to do is to point your SETI program to point to the public servers. For those of you who do not have SetiQueue installed and want to (for yourself or as a public Queue) you can download a copy here from the SetiQueue homepage. If there are any questions about the public Queues please check out this forum thread...any other questions about setting up SetiQueue or other Queue programs can be asked on the forum also.

[Zyn]

sorry guru, your going to have ho dumb down the instructions for me because i cant seem to get it to work with or without setiqueue. I must be retarded or something. I type in the server into setiqueue, sometimes i get responses back, sometimes i dont, whatever i do, i still cant download work units.

Frustrated, Zyn

[Guru]

You should realy ask rat. about that (he knows how setiQ works) or do a search in tlc's forum! I think that you need to edit the host.sam file get it to work without setiQ the same trick as many people used when we were forced to upgrade to v. 3.03! I myself have switched most of my comps to genome becouse the problems over at berkley but I will be back crunching seti when their problems are solved!

[Rattledagger]

You don't need to edit any hosts -file.

In my examples I'm using http://jdaw.cjb.net:5517/ I don't know how this queue is, but the comments is the same for all queues.

If you're trying to connect directly to an external setiqueue, use
seti.exe -proxy jdaw.cjb.net:5517

If you're running setiqueue yourself, edit Settings to:
Proxy server to http://jdaw.cjb.net or jdaw.cjb.net
port to 5517
Connection Type to WinINetProxy or WinSockProxy

After registering a new client on a queue, it can go some hours before you have anything to download in your queue, since SetiQueue must also get the wu from someplace.


To register a new client on a queue, the easiest is to return a result, and wait for the proxy getting wu from Berkeley. You can also send a message to the operator requesting him to fill the queue with wu.

A more dangerous method is to request a wu from a queue, without returning a result first. If you're terminating without downloading a wu this will most often happen:
Either the queue downloads some wu, or the operator fills the queue manually (and doesn't make permanent client...)-
On next re-start of SetiQueue, the wu is deleted since the client/queue is obsolete since no upload/download.

The last method is to get an operator to manually setup a queue for you...