SetiQ beta1h released - Update - Now Beta 2a is out! - Updated again!

[JWMiddleton]

Ken release a new beta version with the following fixes:

. Added time generated time to http page output

. Change the way compatible dc's where allocated to try to solve painting problem on win98se

. Ahh yes the big one... Found various program asserts due to the different ways different versions of like to dispatch messages when calling windows API. Changed the socket IO code to stop using windows messages.

. Added support for the previous seti server name (so those outdated clients will be recognized)

. Fixed assertion caused when seti reports an error when downloading a wu

. Added service control support.

. Modified subnet check to always allow 127.0.0.1 to succeed.

I sent him email today about a problem with "Assertion" and he let me know that the error was fixed in the latest release.

 

[Fardringle]

Time to download a new SetiQ...

 

[Fardringle]

Sweet! Just did some testing and the new version does in fact fix the problem version G had with crashing when a new client connects..

And, version G and newer will also allow use of a proxy address, meaning my work SetiQ is now pointing to my home SetiQ, which points to Orange Kid's SetiQ!! (Just doing some testing to determine the viability of a round-robin type proxy network for the Team, and it seems to be working very well!)

 

[JHutch]

The only thing it doesn't allow is setting a proxy to get through a firewall and then setting a server address to go to once you're through the firewall... For instance, if I put the firewall address inthe proxy line, it automatically connects to the SETI servers, NOT OrangeKid's proxy.

I sent him a feature request e-mail, but haven't heard anything back on it.

JHutch

 

[Assimilator1]

Jhutch

Yeah that would be useful for a remote client I have ,it sits behind a firewall & connects directly to the SETI server .I have no idea of its productivity & obviously if the SETI server goes down it goes idle too

BTW does anyone know if you can disable autoconnect & connect manually with the new SETIQ? & can it keep a result log file in a similar fashion to the old SETIQ?

I see on my 2nd in Comm SETIQ(GUI) that it has a result.log in the client directory ,but the format sucks (hard to read) & it has stopped recording(its possible he's disabled it! )

 

[Fardringle]

<<does anyone know if you can disable autoconnect &amp; connect manually with the new SETIQ?>>

Yep, under the Queue Server settings for the automatic connect times, there is an option to Disable Online Times which will prevent the Q from connecting until you manually tell it to...

 

[Assimilator1]

Doh! ,thanks

 

[Sukhoi]

I'm going to e-mail Ken again tomorrow about how the proxy support is going.

I would guess that Ken wouldn't have any way to support two layer proxies...wouldn't it be the job of the first proxy to route the data to the second proxy? I don't see how SETIQ could be involved in that.

 

[Fardringle]

Version 2 seems even more stable and there's a neat new function on the starmap! All pending WU's have markers that shows all info for the WU and what client has the WU, and there are also markers for all completed WU's. Cool!

Getting better with every revision!

If this continues, I may have to start a Ken Reneris Fan Club...


(Yes, that was over-dramatized, but this is a really cool and useful program and I am WAY too tired to be at work... )

 

[JWMiddleton]

Ken is a very talented and prolific young man!!

Beta2 is out and as Fardringle said it just keeps getting better!

Once you have installed a version of SetiQ you can simply download the .exe file and overwrite the previous version (this assumues a stop of the progam before hand.)

SetiSpy and SetiDriver also have new versions! These guys are keeping us busy!

 

[JHutch]

Sukhoi,

This is how I understand the proxy setting to work currently...

SETI Queue knows what the main SETI servers are called (shserver2.ssl.berkeley.edu). It is &quot;hardcoded&quot; to talk to that server.

When you specify a &quot;proxy&quot; server, it sends its request for the main SETI server to the proxy. Now, with a normal firewall proxy, it just forwards that request on to the real SETI server.

However, when you specify a SETIQ proxy as the proxy setting, it receives the request for the SETI servers, realizes that you REALLY mean to talk to it, and doesn't pass the request along.

What I need for my machines here at work, is for the SETI servers to NOT be hard-coded. If there was a setting to allow me to &quot;change&quot; the address of the SETI server (like SETI Gate does), then I could punch in OrangeKid's proxy address and talk to it, instead.

I hope that was understandable.

JHutch

 

[Sukhoi]

Ah, makes perfect sense.

 

[JWMiddleton]

Well, Ken's daily update is ready. He has released Beta2a. It now allows password protected web remote control.

 

[Assimilator1]

Cool

Sukhoi
Ah, makes perfect sense
I'm glad someone understood it!