Just open the list and remove pandora.exe. I am sure it refers to the avatar game (though I could be wrong). 

just put my i7 930 together. ran your program to do smp and gpu with a gtx260 & gtx275. worked great then changed some stuff and wrecked it, could'nt get smp to work without making my machine shut off after 5 seconds of running smp. beat my head with it for awhile then just reinstalled windows 7, reloaded all programs and everything is great. all running ( 2 gpu's and smp) justwanted to say

thank you
I spent 2 months playing around,trying to get it to work. found your program and it only took minutes.

Sorry if this was already asked but is there anyway to monitor PPD for each client within this application? Or should we still use Fahmon etc.

Thanks!

jedi95

bg8780

Sorry if this was already asked but is there anyway to monitor PPD for each client within this application? Or should we still use Fahmon etc.

Thanks!

The current version of the Tracker does not calculate PPD. This is something I may add in the future though.

Thanks! Ill use Fahmon for now. I love this utility AWESOME job! Makes Multi-gpu very easy! Thanks again!

Possible Bug: When pressing "Start CPU" I was receiving a .NET error. Pressing "Continue" gave the impression that the client was started, however checking Task Manager confirmed that it was not. Pressing "Quit" closed FAH GPU Tracker V2. I determined that "FAH_SMP.exe" was missing in my "\FAH GPU Tracker V2\SMP" directory. Moving this file here (from another SMP folder) resolved the issue. Additionally, pressing "Stop CPU" gave a similar error message, potentially because the file did not exist, or more likely because the process did not exist.

FAH GPU Tracker V2 (v2.8 Beta as per the Readme)
Windows 7 Ultimate x64

I was unable to capture the exact error message (over wrote my clipboard -- d'oh!) and am currently Folding so I don't want to intentionally break anything :P



EDIT:


I literally just got the prompt to update to 2.93 and so I did. After it restarted I was prompted to update a second time. I did so and it seems to be OK. 

I took this time to re-create my issue. Rather than delete/rename the FAH_SMP.exe I simply renamed the directory to SMP2. After pressing "Start CPU" I receive this message:

"Error"
Unhandled exception has occured in your application. If you click Continue, the application will ignore the error and attempt to continue. If you click Quit, the application will close immediately. Could not find a part of the path 'S:\FAH GPU Tracker V2\SMP\starttime.txt'.

"Details"
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'S:\FAH GPU Tracker V2\SMP\starttime.txt'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at System.IO.StreamWriter.CreateFile(String path, Boolean append)
   at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
   at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding)
   at Microsoft.VisualBasic.FileIO.FileSystem.WriteAllText(String file, String text, Boolean append, Encoding encoding)
   at Microsoft.VisualBasic.MyServices.FileSystemProxy.WriteAllText(String file, String text, Boolean append)
   at FAH_GPU_Tracker_V2.frmMain.StartCPU()
   at FAH_GPU_Tracker_V2.frmMain.cmdStartCPU_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.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FAH GPU Tracker V2
    Assembly Version: 2.9.3.0
    Win32 Version: 2.9.3.0
    CodeBase: file:///S:/FAH%20GPU%20Tracker%20V2/FAH%20GPU%20Tracker%20V2.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
    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.4927 (NetFXspW7.050727-4900)
    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.4927 (NetFXspW7.050727-4900)
    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.4927 (NetFXspW7.050727-4900)
    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.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.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.

AH. This is great.

I hate forgetting to resume folding after a long gaming sesh.

Odd, I updated to 3.0 and now I can't start GPU WUs.  It says sigsend.dll is missing, but it's plainly there alongside the actual FAH Tracker executable.  Help?

Yeah, it's definitely present on my machine.   I reinstalled 3.0 last night and it worked, and now it seems to be giving me the sigsend issue again.  I'll PM you with my log.

Version 3.01 is out which should correct any sigsend.dll missing errors. Let me know if you still experience this issue with the new version. This version also adds a "Links" menu with common FAH links.

In addition, my mirror site is back up so it also has the latest version now.

tanner2

Again, your program was great for me. Would it be possible to do bigadv on this?

Assuming that the Windows SMP client supports -bigadv, there is no reason it shouldn't work. I plan to add an option to enable -bigadv to the next version of the Tracker.

If you don't want to wait and you have experience editing client.cfg,  you can simply add -bigadv in the extra_params= section.

My gpus would finish one unit adn never start another one up with v2. I haven't tried v3 yet though.

jpeg387

Hi Jedi,

Found a few more things I wanted to give you a heads up on:

1. When updating to 3.0.1 it performs the update twice for some reason. I'm not certain if this is intentional, or if is performing a two-step upgrade, but each notification states it is upgrading to 3.0.1. This happened to me on two different PCs (both on Windows 7 64-bit). After the second run the update was successful and application ran normally.
2. When running with the "Disable hiding clients" OFF (meaning clients are hidden) it appears that any related prompts are hidden. Specifically, Windows Firewall was prompting to add the FAH Core executable to the white list, however I could not see the prompt to give it the OK. After enabling the option (meaning clients were visible) I saw the Windows Firewall prompt and was able to resolve the issue. This occurred on one of my Win7 64-bit boxes. 
3. If a handled application error occurs, for example if the application is run without Admin rights and fails to update, the error can message scroll out of the box and is not fully visible or readable. I had to open the actual log file to see the entire error message and resolve the problem. It seems that having the text wrap or allowing the window size to be increased may resolve this.
4. Love the ability to save FAHlogs and the tool in general -- keep up the great work! <3

1. Some updates have to be done before another update can be. The 3.00 update includes a file that allows the Tracker to extract zip archives. If i set 3.01 to download that file using the current system, users of 3.00 who already have the file will end up re-downloading it. As a result, I simply have the Tracker update to 3.00 then to 3.01. I am planning to redo the update system at some point. This change would allow direct updates to the latest version in 99% of cases.

2. That's odd, I would figure that Windows prompts would always appear regardless of running the client hidden. I don't use Windows Firewall so I didn't ever notice this problem.

3. Could you post LOG.txt from when this occured? The log function is supposed to auto-scroll to the bottom entry when called. Or do you mean that there were so many log entries at once that you couldn't scroll up far enough to see them all?

jpeg387

Re-reading the error and on second thought, I believe I found that the process hadn't stopped so I manually killed it, but I also re-launched as Administrator. Regardless, the cause shouldn't impact how it appeared in the log so this may is a moot point :) I'm not sure if running "Download FAH Clients" does currently kill all running FAH processes, but it may be something to look at.

That option should prompt you to stop any running clients before downloading them again. If it didn't stop the clients then there is something else going on.

jpeg387

Another issue that is on-going after upgrading from 2.x to 3.01 is that my SMP and GPU0 clients both seem to be stuck in "oneunit" mode, even though I have removed the flag in the configuration and restarted the clients (and FAH GPU Tracker). Please note that this is on a separate machine from the other reporter issue.


I've re-applied the configuration again this morning so we'll see if it helps. 

All the clients run by the Tracker should always have the -oneunit flag given. This is separate from the OneUnit option in the config. The Tracker will restart the FAH clients when they complete a WU unless OneUnit mode is enabled in the config. If the Tracker is failing to restart the clients after completing a WU then that is a different problem.

I'm getting some of the "hung WU" behavior myself on Vista x64.  My Win7 x64 machine seems OK.

My WUs will get to 100% and fahlog shows that the WU is complete/uploaded, but the tracker doesn't start the next WU.  Stopping the GPUs manually inside the tracker gives me "Error stopping GPUx safely, code=5".

I haven't yet checked if the process is perhaps still running somehow, but I'll do that the next time this happens.

Is there anything else I can do to help figure out what's going on with my machine?  This seems to happen every 10-12 WUs since I added a second GPU to the machine (I'm also folding on the CPU with smp 6 now as well). 

Thanks for any assistance!  I suppose if the FAH processes themselves are still running long after hitting 100% this would indicate the problem is not the tracker, right?

Hi folks!

Today I checked to see if there was a new version of FAH GPU Tracker, when I tried to upgrade to 3.0.8 I got the error below.

Any ideas?

Fold on!

IC