Recent content by jsmorley

You don't ever actually write to HKEY_CURRENT_USER, that doesn't really physically exist. that is just a "view" into the correct HKEY_USERS hive under the current account ID. I think of it like a "symlink" in the folder world... So If I'm following this correctly, it seems like this user is...

https://www.lifewire.com/hkey-current-user-2625901

By "consumer", I assume you mean the "Sensors" functionality? So what I'm hearing is that when the "sensors" are accessed by a non-admin account, the data is able to be written to HKEY_USERS, but then that is not transferred to the HKEY_CURRENT_USER hive? That semes very strange to me.

I guess in theory which "hive" to write to could be a setting in HWiNFO... HKCU is the most sensible to me, and would be what I would prefer. I really wonder if this is a problem that can only be properly solved by having the user ensure that HWiNFO itself is started with admin privileges...

I'm fine with that, but is there a possibility of this causing excessive "thrashing" of the registry when the values are written? I just select ALL the sensor values to be output, even though I only use a few of them. I do this so I can create new skins without having to worry about messing up...

The majority of users, who have accounts that can elevate programs to admin access on their PC's with UAC won't see any benefit from this. In addition, there will have to be a search and replace done on every skin, and there are no doubt tons, that have been changed or written to use...

I actually have some heartburn with this change. While having the error codes available when you are debugging a skin is a good thing, in practice not being able to turn this off when you are done with the skin causes some real cosmetic ugliness, and some errors in the log that shouldn't be...

That sounds fine. I just didn't want a log message once a second... ;-)

I think this is a wonderful idea. I would ask one thing if it is possible. Can we have an option in the plugin measure, something like: SuppressLogErrors=0/1 (default 0) That way if you have a skin that for instance is monitoring another PC on the local area network, you can watch...

I posted a link in my post on our forums to this: http://www.ghacks.net/2015/07/15/hwinfo32-and-hwinfo64-5-0-ship-with-remote-sensor-monitoring/ It was a reasonably good description / images of setting it up.

Well, that worked fine. Thanks Martin. I'm not sure why "Enumerate" won't work, and still doesn't, but hard coding the desired IP address in there and hitting "Connect" worked just fine. I wonder if on a network with DHCP providing IP addresses, it might be possible in the future to use the...

Nick,  I'd like at some point to better document the "remote" capabilities of the plugin, but I'm having some trouble getting it to work for me. What I have is another computer, which is hard-wired to the router. I have installed the latest beta of HWiNFO on it and have it running. I have...

Nick, HWiNFO is by far the best sensor monitoring tool available, certainly the best and most robust one that is supported via plugin by Rainmeter. I only regret we can't easily get it into our release "build", so it doesn't require any extra steps to be available to our users. Having said...

Nick, Thanks so much. I will edit / create some posts on our forums to point folks to the new plugin, and will update some .rmskins there to use it.  When we release Rainmeter 3.3 (Likely this Sunday if we don't hit any issues) I will be sure the release notes on our site prominently...

Outstanding...