zig wrote:

Bob wrote:

zig wrote:

SNIP

I installed SetiQueue last night.  I followed the directions, but nothing much has happened.  Completed a couple WU's, but SQ has not yet pulled down any WU's.  I'll give SQ a few hours and see if it grabs any.  If not, I'll reinstall SetiMonitor.

SNIP

Have you poointed your client at setiqueue?

if cli start with -proxy:127.0.0.1:5517
else there are some proxy settings in the menu somewhere

I do not understand.  I went over all the settings.  S@H is connecting and pulling down 1 WU at a time.  SetiQueue is doing nothing.  I know I'm missing something here.

It WOULD be nice if SetiQueue was written and installed in a language that was understandable by the non-geek-speaking public...I'm putting SetiMonitor back up.  That was 'simple'.

Thanks for your reply Bob.

zig

SETI Queue is written in ada, but whatever it was written in you probably wouln't understand it.

Most people have little or no trouble getting SETI Queue to run.

You say you have it running, but that your SETI client is still collecting a wu at a time.  The only reason that would be the case would be if you have not done the ONE piece of config required to get SQ to actually work.  The SETI client must be pointed at SETI Queue.  That is achieved by using it as a proxy server.

There are two types of client, a graphical client and a command line based client.

The graphical client is also known as a screensaver, and has several menu items, amongst which are proxy settings.  You want to configure the client to use proxy server 127.0.0.1 port 5517