I look for a way to communicate with Rainmeter Open Hardware Monitor.
OHM is a software I especially apreciated and Rainmeter . the concern is that it is difficult to retrieve information for OHM to inject them into Rainmeter . there is indeed a plugin which was released in 2011, but it is not very stable and uses WMI , which is quite slow and consumes a lot of resources.
I saw that one could query the OHM questioning the DLL ( OpenHardwareMonitorLib.dll ) that accompanies it as in the following example:
compiled in VS, it outputs an .exe which shows 3 first fans speed at each launch. it only needs OpenHardwareMonitorLib.dll to work, no need to OpenHardwareMonitor.exe running.
time to try to adapt it on Rainmeter plugin SDK ! because I'm more than a novice, see you in a month !
thanks man i am glad that you are doing this cuz i dont have any success at least i exepted more and many things are still not working... so when you could help me there it would be very appreciated
You need to copy the OHM Libary next to the rainmeter.exe and run rainmeter as admin
Measures:
gpuload, gputemp, cpuload, cputemp
Let me know if you need other hardware properties from OHM.
Edit (October 30, 2021):
The google drive link is expired and I'm receiving access requests. I won't reupload the files, because I agree with Brian that it is in fact the wrong approach.
A better solution would be to get the sensor values from WMI classes by using Get-WmiObject.
An example can be found here.
Edit (November 10, 2021):
I released a new version of the plugin on https://github.com/abichinger/Rainmeter-HardwareMonitor
The Plugin reads the data of OpenHardwareMonitor through WMI. Instructions on how to use it can be found on Github.
Last edited by Andi_2112 on November 10th, 2021, 2:23 pm, edited 4 times in total.
~Faradey~ wrote:Could you give an example of how to use it, i'd like to test it but simply having a .dll is not enough. What syntax it has and ect.
Thanks
Andi_2112 wrote:You need to copy the OHM Libary next to the rainmeter.exe and run rainmeter as admin
This is really unfortunate and something I would NOT recommend to anyone for several reasons. We would really like to discourage people from manually having to install plugins (or in this case, 3rd party .dll's). Several years ago, there was a lot of malware aimed at getting people to run some sort of skin installation program that was just really malware.
To combat this, we want all users to install skins and plugins through a .rmskin package. This way we can put the correct files in the correct place without the bad guys trying to hi-jack our product.
Installing a 3rd party .dll to the Program Files Rainmeter folder, then requesting admin status for Rainmeter.exe can be dangerous IF there is malware. (Not saying there is).
-Brian
PS - I am not suggesting this plugin is malware, I am just suggesting this method of delivery is suspect and highly NOT recommended.
I concur with Brian, and in addition I'm not sure I like the entire concept of using a "bridge" .dll to have Rainmeter reach through and access another program's .dll files.
Brian wrote:Installing a 3rd party .dll to the Program Files Rainmeter folder, then requesting admin status for Rainmeter.exe can be dangerous IF there is malware. (Not saying there is).
It's now on Github (here) so you can compile it yourself if you don't trust me.
Andi_2112 wrote:It's now on Github (here) so you can compile it yourself if you don't trust me.
Thanks for this information, however, this is still the wrong approach. The problem is NOT your plugin, it is requiring people to manually move (or copy) a .dll file and place it in the Rainmeter folder in order for your plugin to work. We really prefer people to install plugins through a .rmskin package and that cannot and will not ever support placing .dll files in the Rainmeter folder directly. Not to mention requiring Rainmeter to be ran as an admin (not that there is anything wrong with this, just an extra step that most users don't know how to do).
I applaud the effort, and I am glad there is someone tackling this plugin - however, this approach is a round-about way of using the OHM library and is not recommended. Plugins should be able to get the information on their own (without manually moving files around), or query other programs for information.