| Subject: Re: SetiGate Won't work |
| From: "william dryden" <willdryden@ev1.net> |
| Date: 23/02/2005, 16:38 |
I did make a few asumptions, didn't I? (Te He He)
"Dave Trapnell" <dtresearch@earthlink.net> wrote in message
news:ru0p111qlofhhepf3rl8cj56opkmthi8q6@4ax.com...
Per below, it would appear that you have not actually
downloaded any workunits into Setigate. You must do this
first, before you try to load one into Seti from Setigate.
To do this, under "edit user" in SetiGate you must put the
email address that Seti uses to access Berkeley. Set the
Max Cache size to something reasonable like 3 or 5 until you
have it working. You can increase it later. Under
"File-Options" the "Seti Host" should be
"shserver2.ssl.berkeley.edu" (without quotes). The "Seti
Http Host" should be "setiathome.ssl.berkeley.edu" (without
quotes). "Seti Port" should be 80, "Seti http Port" should
be 80. "Local Port" should be 5001. You may want to set "Max
WU conn" to 1 or 2 if you are using dialup.
You then go to "Connect-Get Workunits" (after connecting to
the Internet). You should see workunits downloading from
Berkeley, except that I have not been able to get any for 12
hours because they seen to be having a problem at the
moment). When this happens, you will get a box that says
"Receive Workunit Error", "No workunit received". After you
have some workunits, you can try to transfer a workunit to
Seti from SetiGate and receive a completed workunit into
SetiGate from Seti.
To do this, it may be easier, for starting, if you have Seti
NOT set to "connect automatically" so you can control the
process. After you have managed to get some workunits into
Setigate, and Seti has finished it's current workunit, you
then go to "File-connect now" in Seti. In an instant, Seti
will transfer the completed workunit to Setigate and acquire
an unprocessed workunit from SetiGate.
You should then see, in Setigate, one "Done", one
"Processing", and one or more Cached. You may then, in
Setigate, go to "Connect - Send Results", and your completed
workunit should be sent to Berkeley. You can change Seti to
"connect automatically", increase the cache size, in
SetiGate, and use "Send-Receive" after you have it working.
"william dryden" <willdryden@ev1.net> wrote:
The one time you got a WU it did not get the WU
>from SetiGate. It downloaded it from Berkeley and SetiGate imported