All A3 cores will not be -bigadv enabled any more. All -bigadv will be A5 core and will not run unless the 6.30 client is upgraded to 6.34 or later version From here: http://foldingforum.org/viewtopic.php?f=55&t=17695 upcoming core changes (bigadv will switch from A3 to A5) Quote by kasson ยป Wed Feb 23, 2011 8:45 pm Just a heads-up: we are planning to migrate bigadv from running on Core A3 to running on Core A5 very shortly. Core A5 utilizes the same codebase as A3, but pegged to specific version snapshots. We have 64-bit Linux, Win32, and 64-bit OS/X versions of the core in testing; the initial release will likely be Win32 & Linux. The new core will require a client upgrade; A5 will require version 6.34 or later. The Linux and Win32 versions of the 6.34 client will be released to the public very shortly. If you are running bigadv work units, please upgrade your clients. That will ease the transition as we start turning Core A5 bigadv projects on and turning Core A3 bigadv projects off. ****added***** Visit the download page: http://folding.stanford.edu/English/DownloadWinOther to download the 6.34 clients Thanks and happy folding! kasson Pande Group Member Posts: 2114 Joined: Thu Nov 29, 2007 10:37 pm Quote We don't currently have 64-bit A3 Windows cores in release; 64-bit versions of windows run the 32-bit version. This may change in the future, but the initial release of A5 will use the same model. The bigadv changeover will be relatively rapid; we highly encourage donors who wish to run bigadv to upgrade their clients to 6.34 or later within the first few days of public release. We do not normally perform rapid switchovers for public-release clients, but bigadv is more of a "power user" configuration. After the switchover, pre-6.34 clients set to bigadv will roll over to normal A3 work units (and thus won't be spinning their wheels idly). We also have a number of non-bigadv A3 projects ready for public release that cannot go public until bigadv migrates for technical reasons.
well a question for all, what do you think i should do? i can no longer run smp11 on core A5 like i could on core A3 ( was this damaging the project even though it was running stable? panther??) im currently doing smp10 54k ppd (smp11 was 59-61k) but when on smp12 it at 71k ppd:bang: i dont want to move the 460 out of the box but there only netting me 23k total for both + the 54 smp10 = 77k ppd it not worth the wattage to run the 460s for only +6k ppd. so im thinking of moving the old 260 witch is still running in the second rig to the 970 rig (as gpu2 is coming to end soon) and putting the two 460s with the q9550 but gpu 3 will take more cpu cycles away from the cpu than gpu3 does i.e more loss ppd:bang: witch ever way im going to do it im losing ppd
I'm in the same boat as you Ian. I can't run smp12 because I've got 3 GTX 470's in my system that I can't put any where else. I would think that this is a step back for the folding project. It's going to slow down almost everyone running and SMP client. But I've got an additional problem, I'm currently processing a P6901 project and HFM is not showing any points or credits. Client type is "Unknown (6.34)" and core is "Unknown (2.27)".
mine took a little while to find the ppd but you could try going to tool-download project from stanford, in HFM and see what that does nice 970 you got there:thumbup: it a good chip when now that imrunning at 4.4Ghz smp10 i get the same ppd as when i was at 4Ghz smp11 all the effort for no extra points
Custom built. Swiftech Apogee XT for the CPU. Koolance VID-NX470 and MB-ASP6WR on the video cards and chipset. Cooled down with a Black Ice GT Stealth 360 and XSPC RX480 radiators. With the CPU folding I'm getting between 45c and 49c. I've got one core designated for processing WU on the video cards it's sitting at about 40c.
pretty cool loop, lots of temp head room there have you got any pic for us :nerd: http://forums.guru3d.com/showthread.php?t=324132 and hit over 3 million for a month congrats
AFAIK, those values that are "bad" i.e. will not fold WUs properly, will be automatically rounded down by the new FahCore_a5. This is done internally by PG so I am not sure of the procedure in determining what value is "bad" or "good" Sorry to hear about your loss of points
my main problem/question, was running bigadv on smp11 damaging the project even though it was returning the project/wu ok, not to bothered about the points as long as the work was still usable