Jim,

When this happens the client is NOT talking to SetiGate but directly to the 
Seti@Home server.  It gets the new units also directly from Seti@Home. You must 
configure the client with the -proxy:<port> command line option.

Ron

Jim Stevenson <jim@abacad-design.com> wrote:

In article <3f56ed43$0$23133$e4fe514c@dreader8.news.xs4all.nl>, 
setigate@author.com says...

Hi all,

I have built a new SetiGate version (1.94). You can download it from my site 
http://home.wanadoo.nl/rongrooteman/seti/.

I have fixed a problem in the communication between the client and SetiGate. 
The client has trouble sometimes fetching a new unit from SetiGate. This 
problem occurred only under Windows XP so it seemed. Have fun and keep 
crunching.... :-)

Ron

Hi Ron,

I thought I would try out SETI Gate and have hit a problem. I went 
through the installation instructions, set up my account, set up my team 
details, set the cache, downloaded 30 WUs and started crunching.
The problem I have hit is the very first WU is 'stuck' at 99.180% 
completion with something like 2 minutes to go and it has been like that 
for 3 hours now!!
So what have I missed?
It is running on a P4 2.53Mhz, 512Mb RAM Laptop with Windows XP Home 
(SP1) which does not have a permanent internet connection.
I re-read the instructions an the only thing I could find that I hadn't 
done was to set Client Properties Command Line to -proxy localhost80 but 
nothing has changed. Any suggestions would be gratefully appreciated

Regards,

Jim
-- 
------------------------
Seti@home team - SetiUK
The Official UK Team 
------------------------