-
Notifications
You must be signed in to change notification settings - Fork 32
HWiNFO not working #63
Comments
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->Hi -=cOdEcSpIrIt=-, thanks for the help! I’m almost certain that I’m using the right Sensor ID and Sensor Instance, I’ve checked multiple times. I’ve attached a screenshot. Thank you for the assistance! -Ben From: -=cOdEcSpIrIt=-Sent: Tuesday, March 16, 2021 10:02 PMTo: marcopixel/SysDashCc: imbenjones; AuthorSubject: Re: [marcopixel/SysDash] HWiNFO not working (#63) Hi, friendly passerby volunteer -=cOdEcSpIrIt=- here!Have you made sure that you've pasted the correct sensor ID? Have you remembered to press enter after pasting. Because the text box don't apply unless you do that.Sensor ID and Sensor instance are supposed to be copied from the Sensor Details section of HWiNFO.Something like this. (I'm using an AMD Ryzen CPU)Extra tip: If you're using a Ryzen CPU, use CPU Enhanced - CPU (Tdie) because Tctl is for AMD's reference to throttle their CPU sooner by offsetting from the actual die temperature (why? to save your cpu from dying too soon, duh XD).Also, HWiNFO recently rolled out a new update that they have set a 12hr limit to Shared Memory Support for free users. Past 12hrs of activity, you'll have to go back to HWiNFO's settings to turn it back on, and that'll last for only 12hr, rinse repeat.—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
Virus-free. www.avast.com
|
If you don't want to go that route, here's the (slightly more) manual way: The following zip contains the new .ini files. Simply replace the ones you have currently in your Skins folder ( |
In the same boat as well. Tried every solution to no avail from tinkering with the .ini variables to trying different versions. Is it a binaries issue? |
@BoscoDomingo Im not very familiar with github, how can i try out your fork which might fix the issue with temperature readouts? |
I'm sorry, I deleted my fork just yesterday as I no longer use it and wanted to clear up my repos a bit!! |
I have found a fork of open hardware monitor that supposedly also has shared memory supported. sadly i havent figured out how to get it to communicate with this rainmeter skin as im not familiar with it. Would you be able to perhaps assist? |
@BoscoDomingo would you be able to take a look at it please? maybe this could fix the issue but im not sure since i personally dont know how it works |
I'm sorry I haven't used this in ages, and I don't really have the time right now for it. It's not my project, I simply contributed once and haven't followed it ever since. Best of luck with it though!! |
@SakurajimaMai-1202 You have to install HWiNFO yourself. |
The info from HWiNFO isn't showing up on the skins! In Settings on Status: it says "HWinFO is running," and the shared memory viewer is working. I followed the instructions on HWiNFO configuration guide, using the correct values for my CPU and GPU. CPU and GPU temp along with GPU usage are reading as 0. I'm using Rainmeter 4.4.0.3433 beta and Windows 10 64 bit, and am relatively amateur so could easily be missing something obvious. Thank you!
The text was updated successfully, but these errors were encountered: