"Nick M V Salmon" <spam@dump> wrote in message
news:407aa532$0$17516$cc9e4d1f@news.dial.pipex.com...

"Cambridge Computer Recycling" <sales@cambridge-computer-recycling.co.uk>
wrote

"Seti Cruncher" <SetiCruncher@"NOSPAM"WildMail.com> wrote
.......I cannot find how to set my Seti client to connect to
localhost port 5001

Start the CLI client with the switch -proxy localhost:5001 - ie. If you

use

an icon in Start / Programs / Startup or off the desktop to start

SETI@home

then rightclick the icon, select properties and add;

-proxy localhost:5001

to the end of the 'target' line.

Ciao...

[UK]_Nick...
-- 
Nick M V Salmon  Master Mariner  MN(Retd.)
Email: My four initials at dsl dot pipex dot com
http://www.nmvs.dsl.pipex.com/index.htm

It turns out that the problem was putting the Seti client in the Setigate
directory.  Once I put it in a seperate directory on its own, Setigate was
happy.  Lesson learned.