Version 3.52 has been released!
 
This version brings several important changes. Most importantly, it includes a FAH client updater, in order to simplify the process of updating to the new 6.34 SMP client. Note that this client will be REQUIRED for bigadv WUs on the new core A5, and the transition of bigadv from A3 -> A5 will be fairly soon.
 
In addition, this release also has several bugfixes, performance improvements, and an updated Games.txt list.

joeomerta

i noticed this doesn't give you an option of where to install to.  i'm running 2 ssd's in raid 0 for my primary drives with a 640gb hdd data drive.  i'm currently folding on the hdd.  if i switch to this, does this replace my existing clients, and how do i get it on my hdd to keep my ssd's safe?

 
It doesn't need to install, it just runs out of whatever folder you put it in. It also doesn't modify any files outside of it's own directory, so the existing clients won't be modified.
 
Just put the Tracker in a folder on your HDD and it will work.

Hi, first of all I want to say that this tracker is a great tool that will help alot of people. I use it for my GPU clinet and work flawlessly on that. But when I tried the SMP client (with all cores and bigadv) I was only getting around 8-9k PPD instead of 35-40kPPD with the orginal smp client. Tried to delate wu and start over but allways got the same low numbers.
So I just use the tracker now for GPU and the orginal SMP client for my CPU and get around 55-60ppd total.

snuddi

Hi, first of all I want to say that this tracker is a great tool that will help alot of people. I use it for my GPU clinet and work flawlessly on that. But when I tried the SMP client (with all cores and bigadv) I was only getting around 8-9k PPD instead of 35-40kPPD with the orginal smp client. Tried to delate wu and start over but allways got the same low numbers.
So I just use the tracker now for GPU and the orginal SMP client for my CPU and get around 55-60ppd total.

 
Do you remember what project it was? The thing with the bigadv's is it takes 2-3 days to complete so you will have to fold for a few hours before tracker will get an accurate reading. If you were unlucky enough to get a 2864, they are SUPER slow. My 980x @4.2 only gets 28,000PPD on that WU

joeomerta

i checked it.  i stopped the gpu0 and started it again, seems to have picked back up

The other thing it could be is if you have failed multiple WU's in a row it will pause your GPU. I will fail some projects cause my OC is too high. Example WU..6801...if I have my shadders over 1400 I will fail the WU. If Stanford keeps giving me that WU it will fail 10x in a row and pause my GPU for 4 hours. So keep an eye on you OC and the WU if it happens again.

The 2600k is a great CPU so im not sure why it would take so long. If you try another one, let it get to 4% then look at the TPF and project #. If it's still slow post it here so we can try to help. Good Luck

I'm updated & it will not let me check the  bigadv box or auto confeg my GPU's too so what's up with that!

OK this is what I get when I click auto detect:
 
 See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Management.ManagementException: Invalid query
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at FAH_GPU_Tracker_V2.GPUDetect.LoadGPUInfo()
   at FAH_GPU_Tracker_V2.frmConfig.cmdDetectGPUs_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FAH GPU Tracker V2
    Assembly Version: 3.5.2.0
    Win32 Version: 3.5.2.0
    CodeBase: file:///C:/Users/The%20Stroups/FAH%20GPU%20Tracker%20V2/FAH%20GPU%20Tracker%20V2.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
CUDA.NET
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.0.0
    CodeBase: file:///C:/Users/The%20Stroups/FAH%20GPU%20Tracker%20V2/CUDA.NET.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box. 
 
And what highlighted is what I'm talking about my os is win 7 64bit & cpu is i7-920 oc to 4-4.2!

The crash during GPU detection is a system-specific problem with WMI queries. This is also the reason CPU detection is failing and not allowing you to enable bigadv. For now, you can manually set up the GPU clients and use the -nocpudetect flag for the Tracker to allow enabling bigadv.
 
I fixed the unhandled exception when this occurs for GPU detection but there is nothing I can do about WMI queries failing. If you have UAC enabled you can try run as administrator but otherwise I don't really know what would cause this.

Turbo_T

I tried to update my tracker to 2.2 but it freezes after displaying the trying to update tracker msg. It hangs there and on one occasion actually gave me a failed message. If I download and run the full install is that going to wipe out my log files and work folders for the wu I have underway? If so I presume it will not permanently impact my stats if I stop all wu at next completion and update the, overwriting all folder in the process. I don't want to loose my Smp status so I can continue folding big adv with the bonus pts. Please let me know which method is prefered since the updater isn't working for me. Thanks

 
Ok, either you have the version number wrong or are running a REALLY outdated version. Anything older than 3.08 is no longer supported by the update system. If you are really running 2.2 then I would recommend starting fresh.
 
Otherwise, just download the latest version of the Tracker manually and replace the exe in your existing folder. This won't affect WUs in progress or your stats.

Turbo_T

Yeah sorry, I fat fingered the 5.2. replying on my Droid.  I have just started folding so I am running the latest version before this release I just can't get the updater to finish the job.  it restarts the update process every time I restart the app.  It just seemingly doesn't find the file or can't finish the job.  So if I just copy the App exe that's all I need to get updated?  I'll give that a try tonight and hopefully it works.  The existing config info will remain or will I need to re-enter all that too?  I'll copy it down just in case.  Thanks,

 
The update process is pretty simple, it just downloads a .zip file with the new exe then runs Tracker Updater.exe which replaces the original with the new version. So manually replacing the exe will produce exactly the same result 99% of the time. The updater supports a few additional functions, but these are rarely needed.
 
I am not quite sure why the automatic update isn't working for you though.

rjbelans

jedi, bigadv is moving to A5 core today, just a heads up in case there's anything you need to do to Tracker.

 
This has already been dealt with in the form of a client updater (Setup -> Update FAH Clients) released last week with 3.52.
 
Checklist for core A5 support:
1. Works with 6.34 SMP client (yes, all versions since initial release)
2. Downloads 6.34 SMP client during initial setup (yes, since 3.00) (it's web based so I can update it anytime)
3. Supports bonus points calculation for non-A3 cores (yes, since 3.38) (now uses kfactor>0 to detect bonus)
4. Easy way to upgrade an existing install to 6.34 SMP client (yes, client updater added in 3.52)

Turbo_T

Ok I have 5.2 installed and working but I have one question.  My CPU is set for SMP and Add-advmethods, my GTX480 Hydro Copper GPU is running gpu3 with Add -advmethods, but the auto detect suggested gpu2 for my 260 216 superclocked gpu.  I had previously set it to GPU3 and had the Add -advmethods flag selected as well.  Is it ok to run it using the GPU3 option with the -advmethods flag set?  I though the 260 was on the list of compatible cards for GPU3.  I can't find the list now. Can I expect and increase in PPD with either setup?  Memory is the second thing to go isn't it.... I can't remember....what's the first....??? 

 
Running the GPU3 client on non-Fermi cards when you have Fermi cards in the same system causes problems if you get a Core 15 WU. This is because core 15 uses GPU0 when detecting the GPU specs regardless of which card it's set to run on. Since Fermi cards and non-Fermi cards have different capabilities this results in the core failing to start. Using the GPU2 client for non-Fermi cards in this case prevents the download of core 15 WUs.
 
PPD doesn't depend on the client in any way, so you shouldn't see much of a difference between GPU2 and GPU3. The reason I set the Tracker to use GPU2 on non-Fermi cards is to avoid the problem with core 15.

Running 2x 470's on GPU3 Client & 1 x 260 on GPU2 - works a treat

Don't know if it's been asked (20pgs :O ), but is there a way to limit the CPU usage; not the number of cores but the actual load? Noticed the client from Stanford's download page* only pegs my i7 at about 45-50% load across all cores. However, your tracker pegs them all at 100%, which kind of sucks because I have to stop it completely if I want to use the system.
 
Something like the CPU Usage Percent slider...even though it's at 100% and...doesn't seem to use more than 50% of the CPU; anywho, just a suggestion because I'd rather be putting the other 50% of my CPU Load to use....it's just sitting there...collecting Digital Dust ; something along the lines of say 60% usage. Leaving the remaining percentage for non-Folding activities.
 
 
 
*http://folding.stanford.edu/English/Download