If geeks love it, we’re on it
You found the friendliest gaming & tech geeks around. Say hello!
Change Logs:FAHClient:v7.1.50:Don't return WU results if they are less than 512 bytes.v7.1.49:Improved Windows install error message.Fixed next-unit-percentage. #842Attempt to fix negative/wrong PPD numbers. #843Track project runtime estimates per slot. #828FAHControl:v7.1.50:Z in the Zulu time display was still partially cut off. #839v7.1.49:Z in the Zulu time display was partially cut off. #839Build Linux version on Debian testing for python 2.7 support. #763FAHViewer:No change.Additional Notes:I've tested installing FAHControl on Ubuntu 11.10 in a VM and it works for me. Here's a handy way to install on the command line:CODE: SELECT ALLsudo apt-get install gdebiwget --no-check-certificate https://fah-web.stanford.edu/file-releases/beta/release/fahcontrol/debian-testing-64bit/v7.1/fahcontrol_7.1.50-1_all.debsudo gdebi fahcontrol_7.1.50-1_all.debThe alternative to gdebi is to first run sudo dpkg -i fahcontrol_7.1.50-1_all.deb which will give you errors and then run sudo apt-get install -f.There are probably good ways to do this via the GUI too.Conclusion:If all goes well we will publish this release to the front page. If you think there are any compelling reasons not to do so please let us know but keep in mind that we are currently in a feature freeze
Install notes: I told the installer to keep the old config, installed right on top of the older client, it is running smooth. Installer ran an uninstall routine before updating, but kept WU in progress and resumed it from checkpoint. Only thing I do not like, is that it ran the FAHControl, and FAHControl ended up running in a window almost totally over the window that informed me the install was complete. The completion window was not quite covered, the top bar was visible, so I brought the installer window to front and closed the installer.
so maybe depending on what you have. The actual clients themselves have not been changed to my knowledge, so you wouldn't get any actual increase in PPD/results.
The RAM reported matters at lower levels, or if you want to limit the amount possibly exposed to F@H for other reasons. Right now, my "server" is folding a 6097 through FAH GPU tracker (so, 6.34 rather than v7 beta client but the GPU tracker is really just what FAHControl does in v7) and 9800GX2 is folding a pair of GPU2 WUs.The SMP core (what is actually doing the work) is only using ~178MB of RAM and the GPU2 cores are at 73MB each. The clients are at ~1MB each and the overall program (FAHControl, in your case, FAH GPU Tracker in mine) is at 29MB. Total memory hit: 356MB.
My main rig, which I run -adv and -big (which you should be for SMP) WUs is around the same total hit.As to why you got a points increase, who knows. Maybe it was getting sent to swap when you were doing other things and now it doesn't.
Icrontic — Home of the Big Beef Burrito since 8-8-2000, fool.
A Short-Media community © 2003–2013.
Powered with <3 from Vanilla & WordPress.