![]() HWInfo64 would then also start displaying a lot of new sensors on my NCT6687D which were garbled/incorrect (have readings of 0).Īlso to address PP2012/resudroid: I have noticed that you seem to be a bit pushy in terms of communication with developers of both FanControl and HWI. When HWInfo64 was started after FanControl, it would cause issues with FanControl's ability to, well, control fans. ![]() When I had the issue, yes, the start order of FanControl and HWInfo64 did matter in my case. So from my perspective the issue is not clear-cut. The problem PP2012 describes is something that I was able to observe on my system as well (but was fixed for me by updating both HWInfo64 and FanControl, or by magic I don't understand). I have observed LHM clashing with other hardware monitoring tools in the past intermittently, but I never observed HWInfo clashing with others. To clarify: I'm not affiliated with FanControl but am following the issue thread on github. First of all: Thanks Martin for responding and even showing interest in this issue at all, because it is quite obscure and only shows up for a small portion of users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |