FahMon 2.3.3 Released

Associate
Joined
22 Feb 2007
Posts
278
Location
Oxfordshire
FahMon 2.3.3 Released

FahMon 2.3.3 is now available for download here: http://fahmon.net/download.html

What's new in this release:

* The client list view has been made much more configurable and additional columns can be added with a right click on the column title.
* You can now completely hide the WU Info panel on the right hand side of the main FahMon window.
* Clients can now be managed from the main menu instead of a right click menu in the clients list.
* Clients can now be manually disabled if you don't want FahMon to monitor them.
* Paused clients can now be detected and shouldn't register as *hung*.
* A number of debilitating bugs that affected GPU monitoring have been fixed.
* FahMon on Windows now follows MS guidelines for storage of settings. This means no more problems with UAC on Vista when downloading project updates.

Special thanks go to John Daiker for providing a number of patches to improve GPU2 support as well as fixing the "quick-refresh" crash bug.

As always if you find any bugs in FahMon please report them using trac

Complete changelog:
Code:
v2.3.3 (01/11/08)

    General

    * Added new cores support.
    * Made "Last 3 Frames" the default PPD/ETA calculation method.
    * Added multiple new data columns.
    * Made client management more intuitive by adding a "Clients" menu.
    * Made main window menus more intuitive.
    * Added ability to remove the "WU Info" panel from view.
    * Updated queue structure to qd FR 069
    * Add ability to select custom web output templates.
    * Altered About Dialog text.
    * Added custom variables to web output templates.
    * Fixed GPUv2 always reporting PPD as "inaccurate."
    * Updated folding support forum link in "Web" menu (thanks to Mark Gerber).
    * Fixed div by zero error that affected GPU2 clients (thanks to John
      Daiker).
    * Fixed quick refresh crash bug (thanks to John Daiker).
    * Fixed file manager bug with paths containing spaces (thanks to John
      Daiker).
    * Fixed team number and username refresh issue (thanks to John Daiker).
    * Changed client list style and removed "zebra" background colour scheme.
    * Issue time no longer used as download time.
    * Added ability to disable clients.
    * Improved sorting algorithm.
    * Added client pause detection.
    * Added support for truncating usernames in the web output.

    Windows

    * Fixed cosmetic issue with work/current.xyz using / instead of \.
    * Migrated configuration folder to %APPDATA% to improve behaviour in Vista.
    * Updated installer to add entry to add/remove programs.
    * Fixed some minor installer issues.
    * Now built against wxWidgets 2.8.9.

    Linux

    * Fixed an issue with latest GCC and inline functions (thanks to KB3LWJ).
    * Fixed compiler warnings about deprecated conversions (thanks to John
      Daiker).
    * Added configure test to check for ANSI wxWidgets and warn if found.
 
Works Great uncle_fungas !!

Vista / Windows Install Note: Speaking to uncle_fungas, they've changed where the config folder resides. It is now in \UserData\AppData\Romaing where before it was in the same folder as the installation.

It's sorted out the UAC problem with Vista when updating Projects, Gotta-Love-WinDoze !!!

I don't use the msi installer, I just unzip it, so if you do the same, in order to keep you Client List + Benchmark data, you have to copy them from your previois version.

I first ran the FahMon so it would create the folder in \UserData\AppData\Romaing then closed and copied the two files over.
.
 
You shouldn't need to, but it won't hurt. FahMon will automatically copy the files over automatically the first time you run it.

Does that apply if you dont run the installer, just run it after you unzip the download, cuz mine came up blank with Clients and Benchmarks until I copied them over.
.
 
Lots of good improvements but it's being reluctant to update a local WinSMP client, either automatically or with F5. Restart FahMon and it picks up the current details from the log file so it's pointing to the right place. The local GPU and remote diskless FAH clients update correctly. This is under XP64 BTW. Should I file a formal fault report?

<Later> Now it seems to be updating correctly. Most confusing.... I'll keep an eye on it.

<Even later> It's done it again: last update was 48% at 21:09 and the WU is now 51% at 22:04. The update of the local GPU client seems a bit intermittent too. I'll check if this is anything to do with shares vs local paths tomorrow.
 
Last edited:
Lots of good improvements but it's being reluctant to update a local WinSMP client, either automatically or with F5. Restart FahMon and it picks up the current details from the log file so it's pointing to the right place. The local GPU and remote diskless FAH clients update correctly. This is under XP64 BTW. Should I file a formal fault report?

<Later> Now it seems to be updating correctly. Most confusing.... I'll keep an eye on it.

<Even later> It's done it again: last update was 48% at 21:09 and the WU is now 51% at 22:04. The update of the local GPU client seems a bit intermittent too. I'll check if this is anything to do with shares vs local paths tomorrow.

Yes, unfortunately it seems the patch to fix the "quick refresh" bug is too aggressive and is stopping legitimate refresh requests. I've had reports on the official forum and over at OCAU that this is indeed a problem. I'm going to try and work out a fix either tonight or tomorrow evening.
 
Great news, love te program and the updates will be great, I'l install it tonight... I only wish the Folding clients got as much love, many EUE's and Unstable machine errors on the GPU client atm :rolleyes:
 
I'll agree with Snapshot, it doesn't refresh my Console Client at all well, starts out OK then refuses to update it even on refresh.

The SMP refreshes fine.

Not a problem though, I just restart Fahmon and all is OK.

Great piece of software though, couldn't do without it.:)
 
Yes, unfortunately it seems the patch to fix the "quick refresh" bug is too aggressive and is stopping legitimate refresh requests. I've had reports on the official forum and over at OCAU that this is indeed a problem. I'm going to try and work out a fix either tonight or tomorrow evening.
Thanks for the confirmation.
For another time, could you look at the ordering of the inactive clients? There's obviously some case-sensitivity in the client names and it makes things a bit inconsistent, especially when things move from one end of the list to the other.

fahmon233.jpg
 
Back
Top Bottom