When upgrading HFM, please take the new Zip file and extract it to the same location as your current install and overwrite the older files.

The user settings are tied to the location of the HFM.exe file. So if you move or otherwise rename any directory in the path to the HFM.exe file, you will lose your custom settings. Please choose your install location wisely, I recommend a very generic folder name like "\Program Files\HFM". Settings will also not follow the application from machine to machine. It is possible to transfer them and I will post instructions on how to do so at a later time.

Primarily a bug fix/change release for a few issues that have been discovered by myself or brought to my attention over the last few weeks. Most notibly: 'AllFrame' and 'EffectiveRate' now persist from session to session. The Green Status Color has been changed to make it a ligher shade. Added another check on the EOC Stats refresh to help eliminate continuous refreshes when the stats do not change but have been updated (like what usually happens at 12 noon). Changed the Time based alternate column formatting to use a leading 0 (i.e. 00min 00sec) - this was requested, I think it's fine... but please let me know if you don't like it. I could add the non-leading 0 formatting back in and have another variation, and I might do this anyway but if you like the previous style telling me so will nudge me to add it back in sooner. Otherwise, quite a few changes 'under the hood' to prep for the future. I anticipate this being the last version under the v0.2 moniker. Version 0.3 should be next up baring anything major that crops up from this release. Here's a list of potential changes/enhancements to the next major milestone:

Okay, here's some feedback. Dropping "donate" buttons in the two posts which serve to introduce the project seems to me to be out of line. I'm sure you spent a lot of time developing this platform and wouldn't mind recoving some money for your effort, but how about restraining those impulses and keeping the solicitations for funds on your site?

This problem was caused by Windows, which was created by Microsoft Corporation.

Okay, here's some feedback. Dropping "donate" buttons in the two posts which serve to introduce the project seems to me to be out of line. I'm sure you spent a lot of time developing this platform and wouldn't mind recoving some money for your effort, but how about restraining those impulses and keeping the solicitations for funds on your site?

Dude... take it for what it is. I have threads about HFM.NET on 9 forums where Folding Teams reside. One formatted for vBulliten, one formatted for phpBB... it's just my standard post Top Post and standard Update Post when I release a new version. If you're reading the posts as "please give me money" then you're not reading the other 95% of the posts. May I reiterate... the software is FREE... GPL v2 code. Donation is a way for users to say "Thank You" if they wish. Geeze... again, take it for what it is... this project has been active for a three plus months now. I'm just posting about it over here for the first time as the other forums/teams have kept me quite busy.

I hate to get off on the wrong foot here with you guys... but I feel like you are the one who is out of line with your response.

harlam357 wrote:Dude... take it for what it is...I hate to get off on the wrong foot here with you guys... but I feel like you are the one who is out of line with your response.

I'm not even close to being any sort of spokesperson for the general population here, so I shouldn't worry too much yet about getting off on the wrong foot with everyone else.

My objections to your post were, I thought, fairly clear and to the point. But just from a practical point of view, wouldn't it make more sense to solicit for donations after people have tried, approved, and adopted your project as useful tool rather than going with "Hi, my name's harlam, here's my cool program and a donate button and a list of donors"? You tell me.

Oh, and "Dude"? Really?

This problem was caused by Windows, which was created by Microsoft Corporation.

Welcome to the TR forums and thank you for creating another FaH monitoring program. There has been an empty space since Larry "TheWeatherman" quit supporting Electron Microscope (I hope he is OK), although I've managed to get by with FahMon.

There has been moderator discussion related to your introductory post. And like sluggo, I feel the inclusion of a donate button in your first post is a bit spamish. just brew it!'s opinion is to let it stand, however the chief administrator said, "If it was a program that wasn't about folding, would it be considered spam? I'd tend to think yes..." While I feel that free to download software presented in the appropriate forum is not spam, the chief does have a point and is the chief.

The Electron Microscope download page had a donate button and I was happy to donate for a program I used on many folding systems. The point being that many people consider a donate button in the introductory post to be poor form. I hope you take this in the spirit of the constructive feedback you asked to receive.

Welcome to the TR forums and thank you for creating another FaH monitoring program. There has been an empty space since Larry "TheWeatherman" quit supporting Electron Microscope (I hope he is OK), although I've managed to get by with FahMon.

There has been moderator discussion related to your introductory post. And like sluggo, I feel the inclusion of a donate button in your first post is a bit spamish. just brew it!'s opinion is to let it stand, however the chief administrator said, "If it was a program that wasn't about folding, would it be considered spam? I'd tend to think yes..." While I feel that free to download software presented in the appropriate forum is not spam, the chief does have a point and is the chief.

The Electron Microscope download page had a donate button and I was happy to donate for a program I used on many folding systems. The point being that many people consider a donate button in the introductory post to be poor form. I hope you take this in the spirit of the constructive feedback you asked to receive.

Thank you for the welcome!

Although the feedback I was looking for was regarding the application, not my post... I do appreciate your constructive tone regarding my post.

I'm not going to get into the whys of my post formatting... I think it's clear by now that this post format was already established and I am just trying to share my work. Some forums have rules against donation links or anything else that can be viewed as solicitation. I did read the Forum rules and guidelines and I found nothing that prohibits such on these forums. If I missed something that would have spoken to such, I apologize and please point me in the right direction so I can be informed. I do see the rule against spam, but I hardly think my posts qualify as spam. However, in cases such as this... it's a matter of opinion.

Please know that I'm trying to form good relations with you guys... so I hate that this has blown up as it has. Besides one other forum I received no such response to the donation links in my posts... and the forum that did have the problem had it explicitly stated in their rules, so it was my fault. I've made it a point since then to read other forums' rules before posting a new thread regarding HFM.NET.

The links are gone and I hope we can put this behind us... I'm sure you'll all soon see that my application and I are here for the betterment of the FAH Project and not my own wallet.

Fix: Issue with Save As... function not using the file name supplied by the user in the Save As... Dialog. Was using current config file name instead... which in the case of a new configuration would result in an unhandled exception - Thanks augie!!!

Change: Messages Window can now be closed using F7 key.

Change: Now a single instance application (attempting to start HFM.exe again won't yield an exception, just a dialog telling you the app is already running).

Change: User specific UI settings like log file splitter location, column indexes, and column sort are now being saved at the time they are changed... not just on application shutdown.

When upgrading HFM, please take the new Zip file and extract it to the same location as your current install and overwrite the older files.

The user settings are tied to the location of the HFM.exe file. So if you move or otherwise rename any directory in the path to the HFM.exe file, you will lose your custom settings. Please choose your install location wisely, I recommend a very generic folder name like "\Program Files\HFM". Settings will also not follow the application from machine to machine. It is possible to transfer them and I will post instructions on how to do so at a later time.

A major fix for a nasty bug I created. If you're auto-loading a default config file, you probably didn't experience it. Couple other quick changes and enhancements based on user feedback. Please upgrade to avoid any problems saving your configuration files.

Just to let you know that I will be downloading it tonight and letting you know how get along with it. I'm sure it will work good. I like all the numbers on the grid, so I think it will rock me!

Hang tight and more is coming.

A fact is a simple statement that everyone believes. It is innocent, unless found guilty. A hypothesis is a novel suggestion that no one wants to believe. It is guilty, until found effective.Edward Teller

Yea, I like this one... I'll try it for a while... When I get the new node, many more will show. I have to find a way to show images, even flash...

A fact is a simple statement that everyone believes. It is innocent, unless found guilty. A hypothesis is a novel suggestion that no one wants to believe. It is guilty, until found effective.Edward Teller

Enhancement: Email Reporting - Configure a reporting Email Address and SMTP Server and option to report clients detected in a 24hr. EUE Pause state (not yet tested on live data).

Enhancement: Encrypt sensetive data before storing in XML. This includes Host Server Passwords (encrypted the next time the configuration file is saved) and the following preferences fields: Proxy Server Password, SMTP Server Password, & HTML Output Folder or FTP URL (these fields will be encrypted on the first run of HFM v0.3.0).

Enhancement: Update code to write Core Name and Core Version, Average Frame Time based on all frames, and upgrade support from previous file layout for CompletedUnits.csv.

Enhancement: Indentify a Core Shutdown Result of "INTERRUPTED" and add these to the failed WU count.

Fix: Altered code to use DateTimeStyle values specifically for Mono Framework. Mono does not appear to like the NoCurrentDateDefault style, which results in the DateTime.ParseExact method returning a DateTime equivalent to DateTime.MinValue. This yields a TimeOfDay equal to TimeSpan.Zero, which results in no frame durations being calculated. The bottom line... I BELIEVE THIS FIXES THE LOG PARSING ISSUES ON MONO!!!

Fix: Use local volatile list in Messages Form to hold current Debug messages in lieu of accessing the current message lines from the TextBox. This appears to have solved the problem with messages that go "missing" from the Messages Form (most evident when running under the Mono Framework).

Fix: Unhandled exception when double-clicking a client with the Ctrl key held down - Thanks ixor!

Fix: Progress Column sorting. The value 100% was not being sorted properly (sorting was based on text value, now based on float value) - Thanks ixor!

Fix: Benchmarks Form to use TableLayoutPanel. Now scales properly when using Large Fonts (120 DPI) - Thanks ixor!

Fix: Project ID has to be known before any work unit data is added to the benchmarks data. Any data added by previous versions with a Project ID of 0 will be deleted upon entering the Benchmarks Form.

Fix: Fixed a long standing bug that output an incorrect Expected Completion time on Instance web pages.

Fix: File name validation (as used by the Host Configuration Dialog). FAHlog.txt and unitinfo.txt file names could be entered with grossly unacceptable values.

Change: Remove requirement for unitinfo.txt file to be present for log parsing to run.

Change: Update Main Form and HTML Summary to draw "Unknown" when Download Time or Deadline is DateTime.MinValue.

Change: SysTray Icon ToolTip to read "x Working Clients" and "x Non-Working Clients" to use the same nomenclature as the HTML Output.

Change (for anyone building from source): ScriptedRelease config is the only config that runs Pre or Post Build events. It is to be used for CruiseControl.NET CI Server Builds. The standard Debug and Release configs are available to use without any third-party dependencies (MSBuild Community Tasks, NUnit, NCover, FxCop, etc). Set AssemblyVersion.cs Revision number to 0, only official releases should contain the Revision number. This file will be updated only with Major.Minor.Build from now on.

Upgrading HFM to the latest release

When upgrading HFM, please take the new Zip file and extract it to the same location as your current install and overwrite the older files.

The user settings are tied to the location of the HFM.exe file. So if you move or otherwise rename any directory in the path to the HFM.exe file, you will lose your custom settings. Please choose your install location wisely, I recommend a very generic folder name like "\Program Files\HFM".

I've been quite busy getting this ready the last month or so. The code has gone through so many changes that the notes above really just touch on the highlights. I really can't say much of anything else... long time coming.

Enhancement: HTML Output Instance Pages - include the FAHlog.txt section for the active work unit.

Enhancement: HTML Output Instance Pages - include a link to the full FAHlog.txt file. - Note: The option enable or disable the copy/upload of the FAHlog.txt files is available in the Preferences.

Enhancement: Benchmarks and Messages Forms now save their Size and Position from session to session.

Enhancement: Option to run the application minimized to the system tray.

Fix: Bug causing partial cpu client frames to be detected as a full frame.

Fix: HTML Output pages are now correctly marked as utf-8 and have their DOCTYPE set to HTML 4.01 TRANSITIONAL.

Fix: (Mostly) Compatibility issues with GUI layout under 120DPI fonts (Windows only). There are still some small alignment issues with the queue viewer show/hide functionality.

Fix: Grid Tooltip paints when entering a cell the first time, not continually. This fixes high cpu usage on Windows 7 (and probably Vista) due to continual redraw.

Change: Text benchmark output only shows production lines when the client is running the benchmark project.

Change: Reduced the number of simultaneous log retrieval threads from 64 to 20 (I believe I was starving the thread pool with too many threads).

Change: Effective Rate is no longer based on a sliding value (current Date and Time). It is now based on the last log retrieval time for each client, yielding a fixed value between data refresh cycles.

This will be the last version update post in this format. For the sake of simplicity and to make it easier on me to do version update posts on this forum and other forums, I have moved the content found in the Top Post of this thread into This Page in the HFM.NET Google Group. From now on these version update posts will simply be a post with the latest version number and links to the HFM.NET Google Code Homepage and HFM.NET Google Group.

Although I will continue to visit this thread periodically, the HFM.NET Google Group will now be the primary place to go for HFM.NET News, Discussion, and Support - enabling all users to converge in one central location. I encourage all HFM.NET users to join the Google Group. It's Free!

To easily keep up with the latest project news, subscribe to a HFM.NET News Feed!

Wow! Happy New Year Everyone! I'm pleased to announce that version 0.4.7 of HFM.NET was the most popular yet, with more than 500 individual downloads!!! Lots of good stuff planned for 2010. Start off by updating to v0.4.8. This is an incremental update with a few fixes - primarily a pretty big bug that surfaces when mangled SMP Client logs are encountered. Check the HFM Google Code page for downloads and details on the changes.

---

Need help with HFM? Have a Feature Request? Please Join the Discussions. Post in the HFM Google Group.

Wow Again!!! (see my last release post) It's been a few since I've made an HFM update but I think it is well worth the wait. With the advent of the SMP2 client and readily available Bonus/KFactor work, HFM v0.4.8 hit an all time high in downloads for single version. Clock him in at over 2600 downloads!!! ...and I was all giddy about the 500 that v0.4.7 reeled in.

Check the HFM Google Code page for downloads and details on the changes.

---

Need help with HFM? Have a Feature Request? Please Join the Discussions. Post in the HFM Google Group.

It has been brought to my attention that Stanford has rules against accessing their cgi-bin based pages and HFM violates those rules by accessing the Project Information pages in a scripted manner. Please note, HFM only attempts to access these pages when users enable the Web Generation option on the Preferences -> Scheduled Tasks Tab. Continued use of the Web Generation feature in ANY prior version of HFM MAY result in your IP being blacklisted by Stanford. Please update to avoid any undue action against your IP and undue load on Stanford's servers. I apologize to anyone who may have been blacklisted. I have asked the Pande Group if they would remove any user's IP from the blacklist if they come forth citing this issue with HFM. I assure you my intentions are for the betterment of the FAH community and in no way was I intentionally trying to violate the rules - I was simply ignorant of them.

What upsets me the most is that I am not the victim here, but rather my users are the victim. Again, I apologize if you were effected and I hope you will continue to use and support HFM.

Check the HFM Google Code page for downloads and details on the changes.

---

Need help with HFM? Have a Feature Request? Please Join the Discussions. Post in the HFM Google Group.

Whew! Been a couple of months since I last came around huh? I'm pleased to annouce the availability of HFM v0.5.0 - which includes the long awaited "auto-update" feature. Just a couple (five) words about this.

You have the option to turn on or off the check for updates on start-up. The ONLY time HFM will auto-check for updates is on start-up. However, there is also a manual check in the Help Menu that will provide you more verbose feedback than the auto-check will.

What does this mean? It means I'll be able to deliever updates and fixes more quickly and easily. It means I will be in a thread near you even less often than I already am now. I have about 9 threads where I maintain/update this same information when I release an update. It's time consuming and I can easily spend several hours getting all my threads updated. So, for smaller, less significant updates my plan is to forego the usual thread updates since running HFM can now tell you when an update is available. I'm going to look into scheduling update checks or another means of ongoing notification since, if you're like me, you don't shutdown HFM that often.

When receiving an update notification you can download either the MSI or Zip distribution. If you're on Windows and download the MSI it will install once you exit HFM. No change to the Zip distribution, you're on your own.

Check the HFM Google Code page for downloads and details on the changes. As always, if you need to find me quickly, see below. I usually answer pretty quickly.

---

Need help with HFM? Have a Feature Request? Please Join the Discussions. Post in the HFM Google Group.

I'm proud to bring you all two pretty big feature additions to this version of HFM. The first is the addition of the Work Unit History Viewer and Database. This database supersedes the CompletedUnits.csv file that has been written with information on completed work units prior to this version. Check the Tools menu.

You also have the option to Import your CompletedUnits.csv file so we don't leave all that good data you've been collecting with no where to go. There were some inconsistencies in the manner HFM wrote to the CompeltedUnits.csv file so I've done my best to write the Import to only process *Good* data that can be verified without a whole lot of fuss. The Import will weed out any duplicate entries in the file and also give you option to "fix-up" the entries in the file that were unable to be imported. Here are a couple likely scenarios:

- p6701/6702 have an issue with a comma in the work unit name. You can safely remove the ENTIRE work unit name from those entries. The import completely ignores the work unit name value. Once the bad entries file is clean-up up you can Import that file and only those entries by performing another Import on that file.

You can find the WU Database file in the HFM Data Files. See the Help menu. The file name is WuHistory.db3. If don't feel like you got everything Imported the way you want you can simply delete that file and try again.

- International users are likely out of luck using the CompletedUnits.csv Import unless you want to script or hand convert your CompletedUnits.csv file to be formatted in United States English format. The issues here include decimal numbers written with commas and date values not in en-US format. I apologize to any of you this will effect but this Import is a one off deal and I made the decision to keep it simple and not attempt to write a bunch of code to fix this one time deal. The software is Beta and issues like this are the reason I continue to label it as such.

The second big addition is the ability to Merge Client Data from other instances of HFM. For example, you have clients running at work and would like to monitor them in conjunction with your clients running at home. However, you do not have access to all the log files over HTTP or FTP. The solution, the HFM instance at work can act as a data collector using the Web Generation option 'Copy Client Data to Target' to place a ClientData.dat file in a location exposed by a HTTP or FTP server. Then on your home machine you can use the Clients -> Merge Client Data option to point HFM to that data file. Once retrieved the clients monitored by the remote instance of HFM will be visible in the local instance IN A READ-ONLY FASHION. You cannot edit or otherwise control the remote clients. It's simply a data merge.

What else? FahMon Import support has been removed from the main code base. It is now available as a Plugin. Download and read the readme.txt file for instructions on getting it installed. There are also new hotkey options (Alt+O) and (Alt+P) to cycle the Bonus and PPD Calculation options respectively.

Check the HFM Google Code page for downloads and details on the changes. As always, if you need to find me quickly, see below. I usually answer pretty quickly.

---

Need help with HFM? Have a Feature Request? Please Join the Discussions. Post in the HFM Google Group.

A little over a year in the making... I proud to annouce a major update to HFM.NET! The premier feature of this update is the addition of Folding@Home v7 Client support. This includes v7 support for HFM's Benchmarking, Work Unit History, and Web Generation features. You can't find similar features anywhere else with any other monitoring software, including FAHControl. In addition to v7 support, HFM still has all the same v6 support you've enjoyed over the last few years. It's the best of both worlds! Making this happen was quite an undertaking and required a partial rewrite of HFM. So while things look generally the same on the surface it's very much a new day for HFM.

Please note that your user preferences will be reset by this new version. This is a one time issue and your preferences will persist with future upgrades.

Check the HFM Google Code page for downloads and details on the changes.

---

Need help with HFM? Have a feature request? Please join the discussions. Post in the HFM Google Group.

HFM now requires the .NET Framework 4.0 Client Profile on Windows or Mono 2.8+ (2.10 recommended) on Linux. A 32-bit only package is now being offered. This build has "x86" in the file name. The only difference in this build vs. the existing distribution, now with "Any CPU" in the file name, is that the "x86" build will run as a 32-bit process on a 64-bit OS. The builds are mutually exclusive and cannot be installed side-by-side with windows installer. If you have a 32-bit OS then either the "Any CPU" or "x86" build will offer the same experience. There was a rather large, pun intended, memory issue with v0.9.0.548. This largely pertained to how I was handling the log file coming from the v7 client (growing pains with v7). I'm happy to report that the memory consumption is much, much improved in this version. I certainly hope this gets all you guys experienced any memory related issue back in action, especially those who contacted me and help me. The move to .NET 4.0 was largely prompted by this issue as that move in and of itself made a positive impact on the situation.

Otherwise... not a lot has changed. This is a well overdue bug fix release for v0.9.0. I hope to bring some goodies with the next release. Primarily an overhaul of the WU History Database. This should include some extra data added as well as much enhanced querying (wildcards, ANDs, ORs, etc).

Check the HFM Google Code page for downloads and further details on the changes.

---

Need help with HFM? Have a feature request? Please join the discussions. Post in the HFM Google Group.

Hello everyone... long time - I know. Life has taken a busy turn for me the last few years. The biggest change with this release is support for FAH v7.4.4. Please check the HFM Google Code project site for details on the changes. Note, the download location has changed to Google Drive.