![]() ![]() This suite does not use HWiNFO shared memory (docs here). I don't mean to toot my own horn, but have you tried the Gadgets? If it is too retro looking for your taste, then you can "modernize" it with this. Some have, so you'll need to search those out. Many authors with HWiNFO-driven skins have not retrofitted their skins to use the new interface that does not require shared memory. I'm new to rainmeter, so sorry if any annoyance was caused. It got me thinking that maybe the problem was that I am using Windows 11 and maybe the plugin was written for Windows 10? Any ideas? I followed instructions and tried to make them work to no avail. Comments report that they work just fine. Just about every other plugin does this and it is considered standard operating procedure to do this (As well as a. It also means that then the developer can install a skin with in the showcase how to use the plugin. I am not sure what Cacheman does internally, but for some of the more advanced things like managing cache it could be using a kernel driver as well (which could cause directly blue screens). They gave a solution, make an rmskin to install the plugin so it is correctly installed and there is no user interaction needed. I found a couple that show CPU and GPU temperatures they use Open Hardware Monitor and both use a plugin called "OpenHardwareMonitorPlugin.dll". The Open Hardware Monitor uses a kernel driver, so it could cause blue screens by itself in theory (but I don't have evidence of any case where it does). One of the first ones I tried was RainformerHWi, a brilliant skin, displays many monitors and panels, but it uses HWiNFO64 which requires a reactivation of memory share every 12 hours. I tried more than one skin that monitors temperatures, but each has it's own downside. I know that many have something similar working, but it's not working for me. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |