3.03 CLI!!!!

[Rattledagger]

I've got some more times:
Low angle range: 66% longer
Normal angle range: 56% longer
High angle range: 71% longer

The actual hourly added time is the same for normal and high angle-range wu. The added time is on the other hand around 30% larger for low angle-range wu. So the slowest wu before gets even slower with the new 3.03-client.

Since most wu is in the normal angle-range, this is most important to the results. This leads to an 36% decrease in current production.

[Brian R.]

Well, I changed to the 3.03 CLI client on all my computers and my production has bit the big one. Oh well, I don't get paid for this anyway...

[DentyCracker]

until i'm forced i 2 shall use 3.00. Then I'll be sure the playing field is truly level. Yes I agree the science is more important edit **but** edit I want to hold off Royceybaby for as long as possible

[This message has been edited by DentyCracker (edited 19 December 2000).]

[klambert]

I don't think there is anything wrong with waiting to upgrade to version 3.03 until we are SURE that it is the "real" upgrade. Look at all those people that spent a lot of time & effort upgrading their machines to 3.0 only to find that they'll have to do it again!

Where I do have a problem, is where someone deliberately chooses to use an old beta version (did I hear 2.70?) to pump their stats until it is banned.

[Rattledagger]

Well, since NT-cmd-3.00 for most non-Xeon-users was faster than 1.x- and 2.x-clients, most users upgraded to this client. I don't think any murc-user has so many computers running seti@home that it was any problem time&effort-wise to upgrade.

[Brian R.]

"Look at all those people that spent a lot of time & effort upgrading their machines to 3.0 only to find that they'll have to do it again!"

LOL - Yeah, that was a bitch all right

[agallag]

Well, I'm in this for the science more than anything, so all my 22 machines (give or take) are upgraded already. It's killing my output, but so be it.

------------------
Andrew
Carpe Cerevisi

[Jorden]

3.03 is mandatory

I can no longer upload my WU's thru 1.06, 2.4 or 3.0

That's a bitch, as now I lose at least 5 WU's... Why doesn't 3.03 want to take my old WU's? Either I'm upgrading... or I might quit again

Jord.

[Liquid Snake]

Jorden,

Are you sure? I just sent five units.

[Rattledagger]

Jorden, seti@home hasn't set a cut-off date for the old clients, so they are still accepting results from old clients. You are probably getting a connection-problem.
From here, I'm getting "unexpected end of data from server", and this is with 3.03

Currently I will guess many users is filling their caches before X-mas, so you should try again in a couple of days.

[DentyCracker]

I upgraded all my machines to 3.0 not too long after it came out. I'll probably update to 3.03 before the cutoff date as well. When all is said and done i'd love the playing field to be truly level but we know that won't be until we are forced to use the same client.

/me wonders how much longer he can hold off RoyceyBaby

[Assimilator1]

Still no problems here with CLi v3.0 .I even managed to send off results with the last GUI v2.04 client I have.
I will be changing that to CLi v3.0 tonight

------------------
I guess I won't recruit for my team here Team Anandtech

[Jorden]

Not when Seti itself keeps telling me that my Seti's are out of date and I must upgrade to a newer version, as soon as I try to upload the results

All 5 PC's running Seti were giving me that message, so all 5 are currently running 3.03 ... very slow I might add

[Sisyfos]

For what it's worth, this is posted on the S@H front page.

"OBSOLETE VERSION" BUG: Some windows users are downloading version 3.03 and getting messages saying this version is obsolete. If you do, please exit the client, delete the file: C:\Program Files\SETI@home\version.sah and restart the client. Sorry about the confusion.

Kim

[Jorden]

Thanks Kim

But I'll let the 5 Pcs run 3.03 for now. At least it gives me some time to test and tweak that version