It may be possible to use SETIQ after the server IP change

[Sukhoi]

I found this info in some other posts, but I figured I'd make a thead so it was more noticeable.

Check out these 2 threads at Ars Technica:

Thread 1

Thread 2

So I guess with some tweaking it is possible to use SETIQ with the new server (whenever it's actually required).

 

[Orange Kid]

thanks for the link
now to do some hacking

 

[blade47]

My only concern is some people might try to just set setiQ to the new server address and continue to use v3.0.:frown:

 

[JHutch]

I think a lot of people ARE going to do that until they are forced (kicking and screaming in some cases) into using 3.03. Remember, some people are stats freaks and could care less about "more science."

JHutch

 

[Robor]

JHutch: That's where the people running SETI need to force the issue. I'm still using the old clients but it's more because I've got 35 to change over and I will have to do this on a weekend.

Rob

 

[Sukhoi]

Hmm, I hadn't thought of that JHutch. Good point

 

[Assimilator1]

I will change clients when they say it is no longer valid to run v3.0.

Any dates to that yet?

 

[Ben98SentraSE]

Isn't 3.03 just the GUI version? There is only still a 3.0 CLI correct? So those of us doing CLI don't have to worry about this issue, correct? Or did I miss the introduction of a 3.03 CLI?

 

[Fardringle]

There is a 3.03 CLI version now as well. You can get it here.

 

[Assimilator1]

Hmm ,whilst SETI say you should get v3.03 they haven't said that it is blocked yet or that you must get v3.03.
From SETI front page

SERVER STATUS: Due to reaching our current maximum bandwidth allowed by the University, many connections to the server are being dropped. Please upgrade to version 3.03 if you haven't done so already, which will help reduce the load.

From SETI text only download page

Client Version Transition

As you may have noticed, the expected transition of the v3.0 clients did not take place on schedule. With the release of the v3.03 client which will be a mandatory upgrade for all users, the v3.0 transition was postponed. At the time of this note (2000-12-18) the moment of transition for v3.03 has not yet been set. In the meantime, if you see a version 3.03 client for your platform, you should be upgrading. To verify your client version:

Looks like we can wait until the transition date ,BTW their servers are likely to get bogged down at that point so it would be a good idea to download the v3.03 client now ready for the date.