• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Seti Queue 3

Very nice! Now I don't have to use Trayer to get it off my TaskBar!! 🙂

Multiple users is also cool, and could be an answer to our proxy idea, since SetiGate seems to lack a few features like being able to accept results from WU's that weren't downloaded from that particular queue..
 
From what I can tell on the SETIQ page, the new version of SETIQ does not currently support connecting to proxy servers. While SETIQ could still be used as a team proxy, people running SETIQ couldn't connect to the proxy.

I already e-mailed Ken about this, so hopefully he'll reply.
 
So does that mean that I can't connect to the seti servers through my proxy or just can't get wu's from another proxy? 🙁
 
As of right now, I don't think you'll be able to have SETIQ go through a proxy server to get to the SETI servers.

But now that I think of it, you may be able to put a line in the HOSTS file to redirect the SETI server address to your proxy server, so SETIQ will then try to go through the proxy server. I'm not sure if it'll work.

But this problem may be changing soon...see my thread on SETIQ and proxy servers.
 
I had a little time to play with the new version yesterday before I had to leave for the airport. I stopped the current SetiQ and installed the new version into the same directory as the existing one. I started the program and it would no allow me to change any of the configuation setting, basically it acted as if it were hung. So, I went back to Ken's site and found a page that stated that you need to clean out your existing queue before installing (using?) the new program. Since I had 39 WUs in my Queue I was not able (willing) to get the new version running.

I have a cable modem at that location, so I setup the two PIII systems running cli 3.03 with SetiDriver, I loaded ALL of the WUs from SetiQueue and turned it off (deleted it). So, over the next two weeks that location will run without SetiQueue. I move two slower Celerons over to RC5.

Ater my flight I am back at the apartment. To prepare for the new version I have reduced the quantities in the SetiQ config files to: Min=0, Max=1 and turned off autoconnect. Over the next few days I will use up all of the queued WUs and flush the results. Thus, I am still using cli 3.0 on this setup. Once all of my queues are empty, then I will make the switch. So, more in a few days.

 
Back
Top