Folding Forum

HFM doesn't need to access to the v7 FAHClient file, it connects to it through the API (on a local client : localhost:36330).

Are you adding the correct client (Client v7 vs Legacy v6) to HFM ?

You need to allow remote access in the config.xml files of the clients you want to monitor : 192.168.1.5 is the IP of the machine that will be monitoring the client ... it doesn't seem to matter a lot, since mine changed and remote connection is still possible (my monitoring machine is now 192.168.1.2) ...

@toTOW It looks to me as if you have set access for the whole range between the two addresses, so the change of monitoring address within that range will be irrelevant.
A smaller range to match your network (and the single loopback address 127.0.0.1) would be a little safer. Try "127.0.0.1 192.168.1.0/24"

Yes maybe ... but I won't touch it since it's working ... and I don't care about allowing everything, all the machines are on my LAN behind the router firewall

Aha. There is a hidden directory which belongs to each user on the system -- one which cannot be used if all users need to access it.

We don't recommend the "install for all users" option. It contains several poor assumptions and is often a challenge to get running correctly.

The environment variable %APPDATA% is set by Windows and is what applications are supposed to use. %APPDATA%\Fahclient is what FAH would use if you had installed "just for me"

Nevertheless, if you're using the up-to-date HFM, it will expect to find 127.0.0.1:36330 open to a telnet-like connection.

Thanks for all the comments and advice.

Out of curiosity, what are the "poor assumptions" of an "install for all users"? As far as it being a challenge installing it, it seems to go right in and work the first time, every time.

What I was looking for was a plug and play remote monitor. I guess this isn't it. My days of fooling with .xml are long ago and I have zero interest in getting back into it. I'll stick to the shoe leather method and check the machine every now and then. I know I can uninstall and then reinstall the FAH client for single user, but it just isn't worth the effort. KISS principle.

New Version: 0.9.5 - Revision 478 - Project Site - Download

Fix/Update: Use project summary JSON feed for project (work unit) information in lieu of parsing psummary.html.

---

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

http://groups.google.com/group/hfm-net

A new version of HFM is available, see this post from Harlam357 in the project Google Group : https://groups.google.com/forum/#!topic ... -PC84vRSrY

HFM.NET v0.9.6.501

Download Location on Google Drive: https://drive.google.com/open?id=0B8d5F ... zdsaEd5UXM

- Release Date: March 12, 2016

- Fix: Change the default Project Summary download URL for new installs to http://assign.stanford.edu/api/project/summary.

- Enhancement: Right-click context menu now includes commands to Fold, Pause, and Finish the FAH client slot.
- Enhancement: Work Unit History data can now be exported to csv through the File menu of the Work Unit History window.

- Change: Reworked HFM's FAH v7 client interface API.
- Change: Reworked FAH v7 client handling code. Testing has shown faster retrieval times of the log.txt file through the FAH v7 client API.

HFM.NET v095 is up to date. Do update not work in hfm.net?

The answer is in Harlam357's posts in the Google Group ... he didn't push this version to his auto-update mechanism yet ...

Okay.

I wish he would add a filter to "View Cached Log File" so I could see just one slot.

Has he fixed the double-click if the icon to default to "Restore"?

(I know, I should suggest these on the Google Group)

Today, after the restart of two computers I see a message for new update to HFM.NET. The new version: v. 0.9.6.501 (Release Date: June 19, 2016)

Fix: Change the default Project Summary download URL for new installs to http://assign.stanford.edu/api/project/summary.

Enhancement: Right-click context menu now includes commands to Fold, Pause, and Finish the FAH client slot.

Enhancement: Work Unit History data can now be exported to csv through the File menu of the Work Unit History window.

Change: Reworked HFM's FAH v7 client interface API.

Change: Reworked FAH v7 client handling code. Testing has shown faster retrieval times of the log.txt file through the FAH v7 client API.

Download from Google Drive - https://drive.google.com/open?id=0B8d5F ... authuser=0

Project Site: https://github.com/harlam357/hfm-net

Thank you harlam357

He finally pushed to automatic update system the version I announced on May 19th

I watched only the date June 19, 2016. For me it came as a new update, because update on May 19th I have missed.

I am running HFM.NET 0.9.6.501 on a Win10 machine. When doing the "Download Projects from Stanford" update, I have been getting:
"Unexpected character encountered while parsing value: <. Path '', line 0, position 0.".

I had to re-install the OS once to fix a problem, so it may be on my machine. But uninstalling/reinstalling HFM.NET does not fix it.
Any suggestions?