HFM.NET v0.9.7.564
255 views
Skip to first unread message
harlam357
Sep 5, 2016, 9:50:21 PM9/5/16
to hfm-net
Second 0.9.7 build. If you used the Windows Installer to install the first 0.9.7 build you must uninstall it first. This build is a minor tweak to fix a logging issue with the preferences/configuration upgrade logging.
I'm releasing this latest build here before pushing it to the auto-update mechanism. Please test.
HFM.NET v0.9.7.564
Download Location on Google Drive: https://drive.google.com/open?id=0B8d5F59S5sCiS1RISzdsaEd5UXM
- Change: Reworked HFM's FAH Log File Parsing API. Changes targeted to make v7 log files a first class citizen in lieu of of being a derivation of v6 logs.
As a result HFM as a client application does much less repeated parsing and scanning of the log data which results in less memory usage and faster client data processing.
I'm also curious to see how well GPU work unit failures are now captured from v7 clients. I don't have any modern GPUs so this is obviously difficult for me to test.
- Change/Fix: Replaced the preferences/configuration storage mechanism (user.config) which has been a source of random problems since HFM's inception.
Existing preferences will migrate to the new (home rolled) storage mechanism. The new preferences can be found in the HFM data files folder (config.xml).
- Fix: Crash reported by john on the hfm-net Google Group. He discovered a race condition between HFM attempting to write to the cached log.txt file while the web
generation also attempts to upload (read) the same log.txt file via FTP, and vice-versa. HFM will attempt either operation multiple times before timing out and
also fail graciously in lieu of tearing the process down. Neither I/O operation is critical to the long term health of the process.
I'm releasing this latest build here before pushing it to the auto-update mechanism. Please test.
HFM.NET v0.9.7.564
Download Location on Google Drive: https://drive.google.com/open?id=0B8d5F59S5sCiS1RISzdsaEd5UXM
- Change: Reworked HFM's FAH Log File Parsing API. Changes targeted to make v7 log files a first class citizen in lieu of of being a derivation of v6 logs.
As a result HFM as a client application does much less repeated parsing and scanning of the log data which results in less memory usage and faster client data processing.
I'm also curious to see how well GPU work unit failures are now captured from v7 clients. I don't have any modern GPUs so this is obviously difficult for me to test.
- Change/Fix: Replaced the preferences/configuration storage mechanism (user.config) which has been a source of random problems since HFM's inception.
Existing preferences will migrate to the new (home rolled) storage mechanism. The new preferences can be found in the HFM data files folder (config.xml).
- Fix: Crash reported by john on the hfm-net Google Group. He discovered a race condition between HFM attempting to write to the cached log.txt file while the web
generation also attempts to upload (read) the same log.txt file via FTP, and vice-versa. HFM will attempt either operation multiple times before timing out and
also fail graciously in lieu of tearing the process down. Neither I/O operation is critical to the long term health of the process.
toTOW
Sep 30, 2016, 3:48:16 PM9/30/16
to hfm-net
I'm testing it ;)
harlam357
Sep 30, 2016, 4:05:07 PM9/30/16
to hfm...@googlegroups.com
Awesome! Let me know how it goes. If you're into it, give it a try in Linux on Mono. Should run fine.
--
--
You received this message because you are subscribed to the Google Groups "hfm-net" group.
To unsubscribe from this group, send email to hfm-net+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hfm-net?hl=en
---
You received this message because you are subscribed to the Google Groups "hfm-net" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hfm-net+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
toTOW
Sep 30, 2016, 4:29:04 PM9/30/16
to hfm-net
I updated two machines from 0.9.6.501 on similar installs (HFM installed in D:\HFM on Windows 10, slot configuration saved to D:\HFM\toTOW.hfmx) using the MSI installer.
One updated fine and I recovered the settings (in preferences), but the other one lost all the data ... luckily, I copied the config.xml file from the working one, and it worked again.
One updated fine and I recovered the settings (in preferences), but the other one lost all the data ... luckily, I copied the config.xml file from the working one, and it worked again.
harlam357
Sep 30, 2016, 4:39:11 PM9/30/16
to hfm...@googlegroups.com
Send me the HFM.log file from the installation that failed to upgrade please.
On Sep 30, 2016 3:29 PM, "toTOW" <tot...@gmail.com> wrote:
toTOW
Nov 13, 2016, 5:54:11 PM11/13/16
to hfm-net
Where is it ? (I don't know if it'll still be there after so much time)
Le vendredi 30 septembre 2016 22:39:11 UTC+2, harlam357 a écrit :
Send me the HFM.log file from the installation that failed to upgrade please.
On Sep 30, 2016 3:29 PM, "toTOW" <tot...@gmail.com> wrote:
I updated two machines from 0.9.6.501 on similar installs (HFM installed in D:\HFM on Windows 10, slot configuration saved to D:\HFM\toTOW.hfmx) using the MSI installer.--
One updated fine and I recovered the settings (in preferences), but the other one lost all the data ... luckily, I copied the config.xml file from the working one, and it worked again.
Le vendredi 30 septembre 2016 22:05:07 UTC+2, harlam357 a écrit :Awesome! Let me know how it goes. If you're into it, give it a try in Linux on Mono. Should run fine.
--
You received this message because you are subscribed to the Google Groups "hfm-net" group.
To unsubscribe from this group, send email to hfm-net+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hfm-net?hl=en
---
You received this message because you are subscribed to the Google Groups "hfm-net" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hfm-net+u...@googlegroups.com.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages