- Joined
- Sep 22, 2004
Yep... you change the directory you're client is Folding in it must also be changed in HFM as well.
The UnitInfoCache.dat file is read on startup and written on shutdown. It allows HFM to "remember" where it left off last time. This allows the user to shutdown HFM and have it pick back up where it left off in terms of updating benchmarks and writing units to the WU History Database.
Here's a scenario for a single client...
WU #1 - shutdown HFM (it remembers the current progress of this WU)
WU #2 - folded while HFM was not running
WU #3 - folded while HFM was not running
WU #4 - startup HFM - if #1 WU can be found in the logs HFM will finish parsing the performance data for this WU, update benchmarks, and write to the WU History Database. Now HFM knows where it left off, so naturally anything between WU #1 and WU #4 (now the current WU) will also be parsed and benchmarks/database are updated.
More to ChasR's statement... this UnitInfoCache.dat holds no log file data. If you're seeing a log file in the log viewer then it was just parsed, so there is still a log file available where the client path is pointing. Otherwise, if no logs can be obtained from the path to the client, then the client will be marked Offline and not Stopped.
The Messages (F7) window will tell you what's going on. To see what is reported when a path/logs cannot be accessed. Add a dummy client and point it to a dummy path or a path with no FAH log data. In either case the client will be marked Offline.
Sorry... I'm a bit under the weather, I hope that all made sense.
The UnitInfoCache.dat file is read on startup and written on shutdown. It allows HFM to "remember" where it left off last time. This allows the user to shutdown HFM and have it pick back up where it left off in terms of updating benchmarks and writing units to the WU History Database.
Here's a scenario for a single client...
WU #1 - shutdown HFM (it remembers the current progress of this WU)
WU #2 - folded while HFM was not running
WU #3 - folded while HFM was not running
WU #4 - startup HFM - if #1 WU can be found in the logs HFM will finish parsing the performance data for this WU, update benchmarks, and write to the WU History Database. Now HFM knows where it left off, so naturally anything between WU #1 and WU #4 (now the current WU) will also be parsed and benchmarks/database are updated.
More to ChasR's statement... this UnitInfoCache.dat holds no log file data. If you're seeing a log file in the log viewer then it was just parsed, so there is still a log file available where the client path is pointing. Otherwise, if no logs can be obtained from the path to the client, then the client will be marked Offline and not Stopped.
The Messages (F7) window will tell you what's going on. To see what is reported when a path/logs cannot be accessed. Add a dummy client and point it to a dummy path or a path with no FAH log data. In either case the client will be marked Offline.
Sorry... I'm a bit under the weather, I hope that all made sense.