Search results

Ah I see. It's a little awkward to interpret the dwSignature field as two types, but I can do it.

Agreed regarding potential breakage if anyone's only checking the incorrect value, rather than looking for both the known incorrect and documented values. An alternative could be to update the doc with the actual value. Your call! EDIT: I imagine most people will just check for the presence of...

The documented field values for dwSignature are "HWiS" or "DEAD", but the actual field value when dead is "DAED". This is on v7.12-4580

I guess if you have enough context about the program ;) a. At launch, "sensors only" and "report only" are unchecked. It's natural to assume both are running in this case. E.g. I didn't assume that the sensors aren't being monitored just because the window isn't displayed. b. The shared memory...

I did not - after launching it from the menu, the shared memory interface is indeed available. So I guess this isn't a bug as such. However it wasn't obvious to me that the sensors window in particular needs to be open. You could chalk it down to me not knowing all the parts of HWiNFO :rolleyes...

Thanks for the tip re: system tray icon settings. I had been looking in the "sensors settings" page. However, the original bug remains - even with the shared memory option checked, shared memory file is unavailable in the "full" UI. Only in the sensors-only UI is the shared memory feature...

Ha, I just found out a consistent repro: If you start up the application with both boxes unchecked (not sensors only mode, and not report only mode), the shared memory interface isn't being activated. If you start with sensors only mode (what I was using all day yesterday), the shared memory...

I've been developing a Python app to read the shared memory interface. I used it for a long time yesterday, was successfully able to read it from my code repeatedly. Since then, 12 hours have lapsed, and when I try to run my script again, it cannot find the shared memory file. Things that...