• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

what is up with this!??

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

trulyred

Member
Joined
Oct 8, 2001
Location
ah, maple falls , wa.
I have been folding quitely for some time now when i noticed my [email protected] program is not communicating properly . I keep getting a closed connections on the bottom left .I did upgrade to the 2.19 but it still does the same thing.......any clues on a fix??tr
 
I'm sorry if I didn't explain better.I use a dial up modem.In the past [email protected] would just bring up the dial up prompt when it was ready to access the internet . it would then go thru a series of send and recieves ,update the count , and all this info would be on the bottom left of the [email protected] window.Usually when it said "working " I knew it had finished it's uploading and down loading and Ican go on and do whatever.......

now what it does is goes thru all the send and recieve commands and ends up with a "closed connections". This happens alot now just this morning i was able to get thru an am now working on abeta 17-42. I check my pc daily even so that i can keep on top of the situation and send those proteins in on time.

by the way I dont know how to post a screen shot,for that matter I don't even know how to get a screen shot!!never paid attention i guess.........tr:p
 
The way I capture a screen shot is to hit the print screen button, which takes a shot of everything on your monitor screen and then paste it into some program like lview pro and crop the part that I want to post out of the screen shot. I then save it as a jpg file and then you can attach it to your message post here in the forums. I think the max size that the forums will let you attach is 600 pixels wide. Hope this helps you out.

EDIT: trulyred, you better shorten up your sig to 10 lines or the sig nazi's will kill your sig and post a naughty little message saying that you need to read the signature rules.
 
They chopped mine up while I was at work; put that stupid little message in instead. Basically, they are doing it on a point system, with 10 points being the max allowed. Small type is .75 points per line, normal type is 1 point per line and large type is 1.5 points per line. Blank lines also count as points. All you need to do is cut down on your blank lines in your sig and you shoud be fine.
 
It was probably trying to connect to server 115 which was having some problems the last couple of days. Look in your fahlog.txt And cut and paste or post a screenshot of the part that is about connecting and sending or recieving. That should help us narrow it down. If it turns out to be a modem specific thing then I can not really help because I do not have a modem. good luck and fold on!!!!!
 
I hope this works



# Windows Graphical Edition ###################################################
###############################################################################

[email protected] Client Version 2.19

http://foldingathome.stanford.edu
email:[email protected]

###############################################################################
###############################################################################
Benchmarking ...
- Ask before connecting: No
- ID = 6DBFA6CD41147A57

Loaded queue successfully.
Initialization complete

+ Attempting to send results
- Connecting to server (171.64.122.113)
+ Results successfully sent
+ Starting local stats count at 1

+ Attempting to send results
- Connecting to server (171.64.122.113)
+ Results successfully sent
+ Number of Units Completed: 2
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.111).
+ News From [email protected]: Welcome to 2.0
+ Closed connections

+ Processing work unit
Core required: Core_65.exe (found)

[March 15 14:49:12] Working on Unit 03
+ Working ...
[14:49:13] [email protected] Client Core Version 2.41 (Jan 22, 2002)
[14:49:13]
[14:49:13] Proj: work/wudata_03
[14:49:13] nsteps: 500000 dt: 2.000000 dt_dump: 100.000000 temperature: 288.000000
[14:49:13] xyzfile:
[14:49:13] " 225 ABeta17-42
[14:49:13] 1 N 16.220744 -12.959064 26.623102 20 2 ..."
[14:49:13] keyfile:
[14:49:13] "#verbose
[14:49:13] NOVERSION
[14:49:13] ARCHIVE
[14:49:13]
[14:49:13] #cutoff 16.0
[14:49:13] #taper 12.0
[14:49:13]
[14:49:13] printout ..."
[14:49:13]
[14:49:13] - Couldn't get size info for dyn file: work/wudata_03.dyn
[14:49:13] Starting from initial work packet
[14:49:13]
[14:49:13] Protein: ABeta17-42
[14:49:13] - Frames Completed: 0, Remaining: 100
[14:49:13] - Dynamic steps required: 500000
[14:49:13]
[14:49:13] Writing local files:
[14:49:13]
[14:49:13] parameters work/wudata_03.prm
[14:49:13] - Writing "work/wudata_03.key": (overwrite)successful.
[14:49:13] - Writing "work/wudata_03.xyz": (overwrite)successful.
[14:49:13] - Writing "work/wudata_03.prm": (overwrite)successful.
[14:49:14] - Writing "work/wudata_03.key": (append)successful.
[14:49:14]
[14:49:14] PROJECT="work/wudata_03", NSTEPS=500000, DT=2.0000, DTDUMP=10.000000, TEMP=288.00
[14:49:14] TINKER: Software Tools for Molecular Design
[14:49:14] Version 3.8 October 2000
[14:49:14] Copyright (c) Jay William Ponder 1990-2000
[14:49:14] portions Copyright (c) Michael Shirts 2001
[14:49:14] portions Copyright (c) Vijay S Pande 2001
[[17:55:48] TINKER is Exiting following Normal Termination
[17:55:48]
[17:55:48] Finished Work Unit:
[17:55:48] ARC file integrity verified
[17:55:48] logfile size: 5887
[17:55:48] Leaving Run
[17:55:48] - Writing 156955 bytes of core data to disk.
[17:55:48] end (WriteWorkResults)
[17:55:48] - Shutting down core
[17:55:48]
[17:55:48] [email protected] Core Shutdown: FINISHED_UNIT
CoreStatus = 64 (100)
Sending work to server

+ Attempting to send results
- Connecting to server (171.64.122.111)
+ Results successfully sent
+ Number of Units Completed: 3
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #1 failed, and no other work to do. Waiting before retry
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #2 failed, and no other work to do. Waiting before retry
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #3 failed, and no other work to do. Waiting before retry
Opening C:\PROGRA~1\INTERN~1\iexplore.exe http://www.stanford.edu/group/pandegroup/Cosm/phase2.html http://www.stanford.edu/group/pandegroup/Cosm/phase2.html
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #4 failed, and no other work to do. Waiting before retry
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #5 failed, and no other work to do. Waiting before retry
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #6 failed, and no other work to do. Waiting before retry
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #7 failed, and no other work to do. Waiting before retry
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
- Error: Getwork #8 failed, and no other work to do. Waiting before retry
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.113).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #9 failed, and no other work to do. Waiting before retry
+ Attempting to get work packet
- Connecting to assignment server
- Successful: assigned to (171.64.122.111).
+ News From [email protected]: Welcome to 2.0
+ Closed connections
- Error: Getwork #10 failed, and no other work to do. Waiting before retry
 
It seams like it might be a modem Issue. first thing to try is to shut down the folding client, then get online, While you are already online start the folding client. This might help. Also I would go into the folding directory and delete core65. It will automatically download a new core. I do this whenever there is a problem and it solves it most of the time. Good luck and let me know if it works or doesn't. Fold on!!!!
 
Well I did what you said to do and it worked. I 'm not sure why it's messing up now when there was a time when it never messed up. Also howcome when i up graded to 2.19 I lost the wu count that I had? I know it still has the count at the home page, but why loose the count on my pc? :p tr
 
Back