• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Changing settings/moving work?

marty9876

[H]ard|DCer of the Month - February 2006
Joined
Jun 11, 2003
Messages
4,906
Hoping you guys can help me make the most of what I have going. Only using the win command line folder.

Can you move work in progress from one boxen to another? I know you need to install the folding program uniquely but I was hoping you could move the "work" folder.

Can you change the settings on a boxen running the command line program? I.E. turn large blocks on/off, change the interval for saved work?

Thanks,
Marty

ps any idea what happened here?

[22:24:07] Completed 1980000 out of 2000000 steps (99)
[22:39:55] Writing local files
[22:39:55] Completed 2000000 out of 2000000 steps (100)
[22:39:55] Writing final coordinates.
[22:39:56] Past main M.D. loop
[22:40:56]
[22:40:56] Finished Work Unit:
[22:40:56] - Reading up to 2160600 from "work/wudata_01.arc": Read 2160600
[22:40:56] - Reading up to 30172 from "work/wudata_01.xtc": Read 30172
[22:40:56] goefile size: 0
[22:40:56] logfile size: 255006
[22:40:56] Leaving Run
[22:40:58] - Writing 2610318 bytes of core data to disk...
[22:40:58] ... Done.
[22:40:58] No C.P. to delete.
[22:40:58] - Shutting down core
[22:40:58]
[22:40:58] Folding@home Core Shutdown: FILE_IO_ERROR
[22:41:01] CoreStatus = 75 (117)
[22:41:01] Error opening or reading from a file.
[22:41:01] Deleting current work unit & continuing...
[22:41:05] - Preparing to get new work unit...
[22:41:05] + Attempting to get work packet
[22:41:05] - Connecting to assignment server
[22:41:06] - Successful: assigned to (171.65.103.152).
[22:41:06] + News From Folding@Home: Welcome to Folding@Home
[22:41:06] Loaded queue successfully.
[22:41:21] + Closed connections
[22:41:26]
[22:41:26] + Processing work unit
[22:41:26] Core required: FahCore_78.exe
[22:41:26] Core found.
[22:41:26] Working on Unit 02 [December 30 22:41:26]
[22:41:26] + Working ...
[22:41:26]
[22:41:26] *------------------------------*
[22:41:26] Folding@Home Gromacs Core
[22:41:26] Version 1.70 (October 24, 2004)
 
Actually, if you move the whole folder to a new computer, you should be fine.
 
If you want to change the settings of the console version then just start it from a short cut with the "-config" switch added.
Then just change the settings as needed as you run down the list.
When you finish it will continue where it left off but just with the new settings.

As for moveing work.
Stanford records which protien it sends to which box.
So just moveing the work unit may mean you don't get credited with the points.
So you need to move the config data with the work unit.
The best way to move work around is to first run useing the "-local" switch which means that the FAH.exe reads the config data from the local directory not the register.
Then move the whole FAH folder not just the work unit.

You may also want run Regedit and then change the key "HKEY_LOCAL_MACHINE -> Software -> Pandegroup -> Folding@Home -> UserID" so it matches the one from which you moved the work from.
But unless you rerun the "-config" switch you dont normaly need to go that far.

As for the error its either a bad work unit or you may have bad memory/ unstable overclock etc.
Check your box for stability.
Check Stanford's forums for signs of a bad work unit.

Luck......... :D
u=Tigerbiten.gif
 
Thanks.

I ran -config on a box (already had a core going), it made the changes and started a new core. Not exactly what I had planned, note to self: stop core first.

So to move form one box to another with core running, 1. stop core 2. launch console with -local switch 3. stop core that it just started (continuing the previous core), 4. move the whole mess to a new box.

As for the error, I've been having trouble with this boxen. No OC on the box, stupid ram does not run to even it's own specs. If I manaully loosen the timings (as loose as the MB will go sadly...) it seems to settle down.

Marty
 
Back
Top