Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
updated scripts to v5
- Thread starter mc68k
- Start date
- Sort by reaction score
Thank you!
I'm half way through a p295 so I won't be able to update until late Wednesday or early Thursday. I'll post if I have any issues...
I'm half way through a p295 so I won't be able to update until late Wednesday or early Thursday. I'll post if I have any issues...
mc68k said:
No problem, we are realize that you have a life outside of MacRumors also. Thank you for your work to assist us all and that of medical research.
Just to be safe than sorry will this updated script work with a Power Mac Dual 450? Is the install intuitive?
yeah it's the same as before. just make sure u uninstall the old one first using the command 'rid'wdlove said:No problem, we are realize that you have a life outside of MacRumors also. Thank you for your work to assist us all and that of medical research.
Just to be safe than sorry will this updated script work with a Power Mac Dual 450? Is the install intuitive?
any non-completed WUs will be deleted
bousozoku said:If you're currently using his scripts, download the new one and read the readme file before doing anything else.
I'm not, but next version I wanted to see how it worked overall...kinda. I've gotten 10 hours of sleep out of the last 48, so bear with me as I make random posts.
Mechcozmo said:I'm not, but next version I wanted to see how it worked overall...kinda. I've gotten 10 hours of sleep out of the last 48, so bear with me as I make random posts.
At least, I can figure out what you're saying now.
I'm not sure how you're starting FAH4 but after downloading the new FAH5 executable, you'll place it in the directory where you now have FAH4. If it's a console version and you start the current one by typing ./FAH4, then you'll start it with ./FAH5 instead. If you use a GUI client, you can just download and start the new GUI client.By the way, thanks for joining the team. I saw it in your message but I didn't think to mention it.
bousozoku said:At least, I can figure out what you're saying now.
By the way, thanks for joining the team. I saw it in your message but I didn't think to mention it.
I'm gonna read your post in the morning. Too many words...
BTW, I have been folding for a little while now...#701 on the team!
My WU's seem to have fallen into a black hole since running the new script
mc68k
I ran your updated scripts on my dual 1.8 G5, and I'm pretty sure that I put in my name correctly, but for some reason, my production has fallen off. I'm runing 2 other computers, a G4 867 powerbook and a dell notebook from work, but my production has dropped to 1 WU a day over the last few days, which seems low. Is it possible to double check my info and/or reinput my name and team without running the scripts again?
mc68k
I ran your updated scripts on my dual 1.8 G5, and I'm pretty sure that I put in my name correctly, but for some reason, my production has fallen off. I'm runing 2 other computers, a G4 867 powerbook and a dell notebook from work, but my production has dropped to 1 WU a day over the last few days, which seems low. Is it possible to double check my info and/or reinput my name and team without running the scripts again?
to double check open terminal and typelssmit02 said:
Code:
egrep "(user|team)" ~/F\@H1/client.cfg ~/F\@H2/client.cfgto change team/username use
Code:
cd ~/F\@H1/; ./fah5 -configonly
cd ~/F\@H2/; ./fah5 -configonlymacrumors is team 3446
Thanks, I found the black hole!
mc68k,
Thanks for the help. It turns out that I had entered the info correctly, but the problem was an improper termination of the FAH client. (I should have checked this first, but the timing seemed to correlate exactly to the update. Sorry to have wasted your time.)
Just to let people know, when the client is terminated incorrectly, it automatically turns off altivec when it restarts. This causes the time it takes to work on a problem to increase dramatically! For example, I'm running two processes, F@H1 and F@H2. On F@H1 it was completing a step every 10 mins before it terminated, after, it was every 19 minutes. On F@H2, it was worse, it went from a step every 36 minutes, to 2 hours and 10 minutes! No wonder this machine stopped reporting work units.
Thanks again to mc68k for responding so quickly. I wish there were a way to know when the client terminates improperly. All you have to do to reset it, is to stop and restart it.
[edit:typo]
mc68k,
Thanks for the help. It turns out that I had entered the info correctly, but the problem was an improper termination of the FAH client. (I should have checked this first, but the timing seemed to correlate exactly to the update. Sorry to have wasted your time.)
Just to let people know, when the client is terminated incorrectly, it automatically turns off altivec when it restarts. This causes the time it takes to work on a problem to increase dramatically! For example, I'm running two processes, F@H1 and F@H2. On F@H1 it was completing a step every 10 mins before it terminated, after, it was every 19 minutes. On F@H2, it was worse, it went from a step every 36 minutes, to 2 hours and 10 minutes! No wonder this machine stopped reporting work units.
Thanks again to mc68k for responding so quickly. I wish there were a way to know when the client terminates improperly. All you have to do to reset it, is to stop and restart it.
[edit:typo]