Folding@Home...beta 4.. [Archive] - SpeedGuide.net Broadband Community

View Full Version : Folding@Home...beta 4..


downhill
06-10-02, 11:43 AM
is out. Trying it now, as I type. :)

emobley3
06-10-02, 03:02 PM
Hey downhill, does beta4 have the capability to choose which client to run? Just curious. Thanks

Ron

downhill
06-10-02, 05:15 PM
To tell you the truth, I don't know for sure. I didn't check out any options...A bad experience with beta 3. :D

It downloaded a protien A right off the bat. :D

I'm burning this one up on an average of around 7 minutes and 45 seconds a frame. With folding 2, it was over 8 minutes. But with it calling home all the time, I don't think that I'm actually gaining anything. Strange though, I talked to ryo today. He explains that with beta 3, you don't see it call home but it still does. (I'm talking about uploading before you finish a protien). This version must be doing the same thing.

ryo1
06-10-02, 05:34 PM
Emobley,
According to Stanfords site, they don't intend to incorporate g@h until a later date. They say they want to get f@h working correctly before they try to merge the two together.
I haven't seen a time line mentioned anywhere yet, but with all of the people asking about it it's probably not too far off.
I understand that the new beta4 times out on the 24th. So unless they jump ahead and decide to try to merge them early, I doubt we'll see it before then.

ryo

LT-73
06-10-02, 06:41 PM
I'm running the beta4 now also, i had the beta3 running but it must have timed out :( . Lucky i still had the 2.19 saved so i jumped back to it :D . I hope i did'nt lose any time. I had the beta3 running smooth then poof. Evry once in a while a take a peek to see the progress and i noticed it had just stopped. I tried to re-load it but it would'nt go thru so i started the 2.19 back up.
So far i see the beta4 take about 3 min. to complete a frame.

It's fast on the startup but lets see what it does in the long stretch.

I'll let you guyz know ;)

emobley3
06-10-02, 08:22 PM
Thanks for the info. I hope they do allow G@H to be integrated into the new folding client.

LT-73
06-11-02, 04:54 PM
I dunno what the heck is wrong with betas and my system. 1st i get the beta3 runnin fine then it goes out. I get the beta4 runnin ok last nite and this morning its dead too. WTF ?? Do i have to keep jumping back to the 2.0 all the time? This is really depressing. I'm jumping back and fourth like a dang kangaroo. Anybody get this same problems as i do or am i the only one?
Sheeeeeeeeesh ! :mad:

btracy
06-11-02, 06:30 PM
I have not used it yet on any of my systems but I did notice that there was a beta 5 released today that fixes a fairly serious bug that some people were experiencing. Basically if they closed the client having done 94/100 steps when they started it back up it would think that there was not a currently active WU and re-download a new one.

I know this has nothing to do with your problem but I figured you might want to know. :)

BTW what does your fahlog.txt file say when your folding stops working?

LT-73
06-11-02, 06:35 PM
Ask before connecting: No
- User name: LT-73 (Team 15)
- User ID = 4EACC3441C2F4F4D
- Machine ID #1

Benchmarking ...
Loaded queue successfully.
+ Attempting to get work packet
- Connecting to assignment server
- Could not send request to AS #2
- Successful: assigned to (0.0.0.0).
+ News From Folding@Home: Welcome to 2.0
- Connecting to server (0.0.0.0) on port 80
- Error: Getwork #1 failed, and no other work to do. Waiting before retry

Folding@Home Client Shutdown.

This is where it stopped. This morning when i checked it was just at the same spot. No progress so i shut i down and started back up with the old client 2.0 and that's what i'm running now.

** I d/led the beta5 and its runnin ok so far, lets see if i get any problems with this one. If i do then i'll just flush all the betas and stick to the old client. I'm not gonna keep busting my head over it .I know they're only betas but why does it keep just shutting down after only a few hours?**

btracy
06-11-02, 09:43 PM
Well assuming you did not manually change the log file for posting your problem lies here:

Connecting to server (0.0.0.0) on port 80

and

Successful: assigned to (0.0.0.0).

It looks like it lost it's ability to find the servers and plugged in an ip address of 0.0.0.0. There were some posts about the system running for a while and then the assignment servers would somehow not pass work to another server but it looks like this is another problem entirely. Anyway I could be wrong as to the cause but you should have IP address there.

LT-73
06-11-02, 10:00 PM
But that's the thing, i didnt change anything. All i do is d/l it to a folder , open the folder, i see a red spocket, double click on it and let it do it's thing. After it it installs, it automatically starts to hook up to the server, asks the questions of user name blah blah blah, then thats it, its starts runnin normal. I just don't get it at all. Well like i said b4, i'm runnin the beta5, so far so good. If at anypoint it stops and i can't get it to run then i'll just delete all the betas i have and just stick to the original client. If that fails too then i'll just throw in the towel and wipe my hands of it.I'm not gonna lose any sleep over it. I'm not gonna keep rackin my brain and try to figure out why it quits after a few hours.

Sorry to vent but this is how i feel about it.

downhill
06-12-02, 12:14 AM
I wonder why it's trying to connect you on port 80? I was under the impressing they were going to start using 8080?

btracy
06-12-02, 12:36 AM
Show you what I know. :)
I thought they were going to start using 80 to finally resolve most of their firewall issues. :confused:

downhill
06-12-02, 01:22 AM
Originally posted by btracy
Show you what I know. :)
I thought they were going to start using 80 to finally resolve most of their firewall issues. :confused:

Now you got me confused! lol

I just looked up my own config...for me it's 8080 but you could very well be right for server port numbers.

btracy
06-12-02, 02:31 AM
Bah I am probably wrong.

I just remember a snippit of reading about them including the ability to use port 80 to resolve firewall issues. It might not have ever made it in. :)

LT-73
06-12-02, 02:59 AM
Hey , aint this a kick in da head, i'm hook to port 80.
what the heck is goin on ? not 8080 but just plain 80.
And just like i said b4, dang beta5 shut down, i bounced back to beta4. I'm getting dizzy bouncing back and fourth here.

Chris
06-12-02, 07:22 AM
Originally posted by LT-73
Hey , aint this a kick in da head, i'm hook to port 80.
what the heck is goin on ? not 8080 but just plain 80.
And just like i said b4, dang beta5 shut down, i bounced back to beta4. I'm getting dizzy bouncing back and fourth here.

Beta's are fun aint they!!!!

LOL

LT-73
06-12-02, 11:26 AM
:rotfl: :rotfl: