Please downgrade your d.net clients to v2.8010 or before

Moose

Member
Apr 8, 2000
180
0
0
We had to back rev the latest set of clients. V2.8012.466 contains a bug
that will produce bad results. Please downgrade to clients in the v2.8010.*
family. All v2.8012 clients have been removed from the download page
(http://www.distributed.net/download/clients.html) At this time we are
not rejecting results from v2.8012, but in the near future we will be.

Stats credit will continue to be given up until the time we start
rejecting v2.8012 work.

We will pre-release fixed clients ASAP, but once again for the time being
please downgrade to v2.8010 or before.

Sorry for any inconvenience this has caused.

Paul
 

Ken g6

Programming Moderator, Elite Member
Moderator
Dec 11, 1999
16,632
4,561
75
:frown:

For those of us who go by the second number, that's back to 463b from 466. Or for those who hadn't noticed any numbers, that's back to the old-style CLI-GUI from the newer graph-GUI.

What were the bad results? RC5 or OGR? Something you can fix in the master database, I hope?

Say, I just noticed I was running 465, not 466. Did it give the same bad results?
 

GSmith

Member
Jan 6, 2000
86
0
0
What about 8011 (464) on the Macs? I've got that running on a pair of G4s at work, and since they're at remote locations, this may be a problem to change right away.
 

Moose

Member
Apr 8, 2000
180
0
0
We can mark results for v2.8012 as bad in the master bitmaps and resend the work. This means work needs to be rerun, but we can isolate the damage. Stats will not be taken away for work you did with v2.8012 clients. However in the near future credit will not be given to you for work done with v2.8012 clients.

paul
 

Viztech

Platinum Member
Oct 9, 1999
2,807
0
0
Moose-

Uhhhh, how about the 8011-464g client? That's the one with the improved OGR performance with the P2/Celerons.

/me has many machines doing OGR with that one....

Signed
Anxious

aka viz
 

Moose

Member
Apr 8, 2000
180
0
0
464 are all pre-release clients and have other problems. please downgrade to v2.8010.
 

Russ

Lifer
Oct 9, 1999
21,093
3
0
Good thing I'm so anti-software upgrade. Nothing here later then 10.

NOTE to members of TA Cube. If you used our install disks, you're fine.

Russ, NCNE
 

mcmail

Junior Member
Feb 25, 2001
1
0
0
Please sort out yout "http" link for the 463b old client!!! it is pointing to the 466 version!

the ftp link is ok though

 

Eug

Lifer
Mar 11, 2000
24,048
1,679
126
OK,will do. Dasm, got a bunch on 464 - luckily you've given us a little switchover time. Sniff, 464 is so fast! :(

Cheers,

Eug
 

Moose

Member
Apr 8, 2000
180
0
0
mcmail

check your web proxy. http and ftp file are exactly the same file. web proxies tend not to give you the right file depending on their expire times. your service provider may be providing this service with out you knowing it.

paul
 

Poof

Diamond Member
Jul 27, 2000
4,305
0
0
Anyone know what version KLinux is running? It was only the couple of Linux clients that I recently downloaded that were 8012s (my other Linux boxen and NetBSD box have 8010s)...
 

AppleTalking

Golden Member
Dec 15, 2000
1,316
0
0
Poof, a look a Kilowatt's page shows that it's running 2.8010.463. Looks like we dodged a bullet there! :) Now I just have to downgrade my 8 Duron 800s :frown:. Should've set up my dnetc directory as a network share . . .

Nick Klingaman
appletalking@home.com
 

Poof

Diamond Member
Jul 27, 2000
4,305
0
0
Cool! Thanks AppleTalking... :)

I was gonna try to get a celly up and running hopefully tomorrow using it, so I'll just make up my floppy then and not worry about it! :D
 

Wolfie

Platinum Member
Oct 9, 1999
2,894
2
76
Wonderfull, I wonder how long they will let the 8012's fly. I know it's going to be HARD to track all those 8012's down and to see what ppl are using.
hrmmmmmm
Another little setback for the team.................

Moose
I know it's hard to let a client out and not know about a bug. But isn't there a way to test this before letting it out to us? So we don't lose blocks? I mean, I know we have a bunch around that are using 8012. But it's going to take some time downloading a new client and getting the client on ALL the machines. I am slightly disapointed that this didn't arise before letting the client out the public...... IMHO.......

Wolfie
 

Viztech

Platinum Member
Oct 9, 1999
2,807
0
0
Hmmmmm, and I thought that this was related to this log file excerpt found in this thread about the huge OGR output by the Feds this last week.



<< Just take a look at this section of the above log, especially the stub size:
2001-02-20 11:41:03,212.123.181.54,ta-cannibalcows@ragingbull.com,25/8-15-13-1-3-7,1080863913749519360,1,1,8010
2001-02-20 11:41:03,212.123.181.54,ta-cannibalcows@ragingbull.com,25/8-15-12-18-4-7,1152921505062373632,1,1,8010
2001-02-20 11:41:03,212.123.181.54,ta-cannibalcows@ragingbull.com,25/8-15-13-6-12-4,2522015793981362176,1,1,8010
2001-02-20 11:41:03,212.123.181.54,ta-cannibalcows@ragingbull.com,25/8-15-13-6-12-2,2233785417051583744,1,1,8010
2001-02-20 11:41:03,212.123.181.54,ta-cannibalcows@ragingbull.com,25/8-15-13-6-11-16,2089670230268462592,1,1,8010
2001-02-20 11:41:03,212.123.181.54,ta-cannibalcows@ragingbull.com,25/8-15-13-6-11-14,2161727824054665984,1,1,8010

Somehow the stub size has grown, compared to what is normal.
>>


Well, I guessed wrong. The abnormal results came from a 8010 client!

Any idea about that, Moose?

viz

BTW, 18 of my 20 affected machines are downgraded.