distributed.net Pre-Release clients v2.8012.465 now available

Toggle sidebar Toggle sidebar
M

Moose

Member
Apr 8, 2000
180
0
0
The Following Clients have been placed/updated for pre-release:

  • Windows 95/98/NT/2000/Me [x86/Zipped] v2.8012.465 2001-01-01
  • Windows 95/98/NT/2000/Me [Alpha/Zipped] v2.8012.465 2001-01-01
  • Windows 3.x [x86] v2.8012.465 2001-01-01
  • PC-DOS, MS-DOS [x86] v2.8012.465 2001-01-01
  • FreeBSD [x86/ELF] v2.8012.465 2001-01-01
  • Linux [x86/ELF/all lib versions] v2.8012.465 2001-01-01
  • Linux [arm/ELF] v2.8012.465 2001-01-01
  • BSD/OS [2.x/3.x/4.x/x86/aout] v2.8012.465 2001-01-01
  • NetBSD [m68k] v2.8012.465 2001-01-01
  • OpenBSD [Sparc/aout] v2.8012.465 2001-01-01
  • OpenBSD [x86/aout] v2.8012.465 2001-01-01


The Pre-Release Page can be found at: http://www.distributed.net/download/prerelease.html

changes.txt file is included in the download. or at http://www.distributed.net/download/changes.txt

Please remember to report bugs at http://www.distributed.net/bugs/

moose
 
ViRGE

ViRGE

Elite Member, Moderator Emeritus
Oct 9, 1999
31,516
167
106
Dude, a GUI!:D Thank you so very very much Moose!:) Oh, and we'll be glad to help you tweak the GUI(including adding a TA logo to it;)).
 
T

TGEN

Junior Member
Jul 3, 2000
19
0
0
And look at that speed... a performance increase of 0,01 Mkeys/sec here!!! woohoo... in stead of 3,178 Ik got 3,189... in RC5

OGR sux :)
 
Fardringle

Fardringle

Diamond Member
Oct 23, 2000
9,200
765
126
I LIKE the instantaneous speed display in OGR! Very nice!!

However, if the client (Windows9x x86 client) is started using a shortcut which automatically minimizes the client, the program cannot be restored to the screen no matter what I try. It just sits in a 'button' on the Taskbar which will either let me Maximize the client (which I don't want to do since it looks funny full screen :)) or Close it, which I also don't want to do...

Starting the client normally, and then manually minimizing it allows it to be restored normally...


Also, Fetching and Flushing DO work for me in OGR, although I haven't tried it in RC5 yet.
 
Fardringle

Fardringle

Diamond Member
Oct 23, 2000
9,200
765
126
Thanks wildhagen! I looked at that page, but in my sleep-deprived delirium :confused: I must have missed the reference to that bug when I looked through the list.. :eek:
 
BGod

BGod

Golden Member
Oct 9, 1999
1,375
39
91
I found a work around for not maximizing correctly.

If you double click the icon in the system try, or right click it and use Restore all that happens is it shows up on the Task Bar. Right click the Task Bar entry for it and click on Move. Use the arrow keys just a little bit, then move the mouse up and left and you should see the client window appear from somewhere off the screen.

Once you've done this, the Minimize and Restore features function correctly. :D
 
ViRGE

ViRGE

Elite Member, Moderator Emeritus
Oct 9, 1999
31,516
167
106
Humm, it looks like the "minimized" bug is fixed in the beta build I'm using.:) Hopefully, Dnet will make it pre-release soon.

PS It looks like the Athlon/Tbird core is a tad faster now too in 465 :D
 
I

ikke

Junior Member
Sep 12, 2000
21
0
0
Watch out with flushing. Some of the communications has been changed. If your behinde a HTTP proxy with port 80 open, the client wil try to flush to port 80 on the perproxy. The old client always tried to flush to port 2064 if you don't specify it. Now it could be automaticly port 80. Not all perproxy's have port 80 open to fetch/flush.

Narzy: maybe this is your problem also.
 
Fardringle

Fardringle

Diamond Member
Oct 23, 2000
9,200
765
126
I do like the new config and display options, but I don't know if I'll be using the beta for much longer as my OGR rates on this computer (K6-3+ 600) have dropped from ~3.8 Mnodes/sec to ~3.2 Mnodes/sec. :(

Anybody else seeing slowdowns, improved speed, no change, etc.?
 
D

dkappos

Senior member
Oct 11, 1999
502
0
0
My Logfile Visualizer cannot open the log files that are created by the new version :(. Anybody else has the same problem? Polo's log cleaner has no problem with these log files (I do only RC5).
 
K

Kilowatt

Golden Member
Oct 9, 1999
1,272
0
0
Dnet should spend the time it takes to invent new buggy clients, and grab their plunger to unstop their plugged up proxies.

Fix the damn problems you have now, before starting new ones and compiling the problem(s) more.

I tested one of their Linux pre-release clients last month, and took a hit when I had to redo my networking on that box.
They have the resources to test they're own new stuff.

>> The above is just my voiced opinion <<

What is this fascinations with untested betas anyway.
 
M

Moose

Member
Apr 8, 2000
180
0
0
This is a simple statement. In no way do I mean disrespect to anyone.

If you do not wish to test clients then by all means don't. We provide these clients in Pre-Release for testing for bugs that users run into that we do not. Never have we told you that you must use this client or test the client for us.

We have asked that if you have the resources and the time and you feel like helping us out by testing for things in your environment then by all means we thank you for helping us out. If you think that in any way using new clients is going to disrupt your perfect setup with optimal rate output, then by all means do not try the clients. Right on the Pre-release page it says



<< These clients should not be used for widespread distribution. >>



and



<< Please remember these clients are not officially released yet and can be removed at any time. >>



These clients are not untested. If you would like I will stop posting to this forum when we have clients that others have shown an interest in checking out before they are mass released.

As far as resources for testing and proxies backed up. Those are 2 different things. Neither has to do with the other. The proxy network is built to allow for redundancy. Say the master goes down for changes or updates, or the masters connection to the net goes down the keyservers buffer the returned blocks. Those blocks will make it back to the master and into stats.

As far as the lost blocks in the last month and the lost logs you saw posted in .plans. We have the logs but need to feed the logs into the master. With the master having connectivity problems we have chosen to hold off on doing this. It just takes time.

Thanks
moose
 
K

Kilowatt

Golden Member
Oct 9, 1999
1,272
0
0
I don't want to get in an argument with you Moose, or anyone one else.
(There are enough of my own Team mates that love to jump on me for speaking my mind in my posts)

If your betas are tested before pre-release status, then you should know about them messing up network settings and speed increase/decrease and the like.
Are they compiled on a standalone machine? And run on it for awhile crunching randoms?
Don't you have a network there, and see they mess with your perfectly good network settings?
 
M

Moose

Member
Apr 8, 2000
180
0
0
What network problems are you refering to? We had a change in proxy/firewall support. (Basicly fixing what didn't work properly before. I see no Bugzilla report on linux networking problems with the client.

What exactly is the problem?

moose
 
J

JHutch

Golden Member
Oct 11, 1999
1,040
0
0
Kilowatt, I hate to sound authoritarian, but ... BACK OFF!

Moose is just being nice to our team by posting these announcements. He very nicely asked (a LONG time ago) if it was okay and we responded with a resounding yes. And I don't know how much large scale troubleshooting you've been involved with, but there is NO WAY they will catch all the bugs before release if they don't do a large scale beta test. The client is stronger because people test these clients before they hit general release, finding gotchas (like the Linux network bug) that escaped the testing the programmers run. After all, I've seen plenty of cases where a bug never pops up on one machine but wrecks havoc on another...

Please, Moose, keep posting these announcements. I think (hope) that some of Kilowatt's words are borne out of frustration with the lost WUs (which, though temporary, seem to be a LONG temporary).

JHutch
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom