Not getting HWinfo apps work work

dalewj

Member
Trying to update my rainmeter with the newer software (Mine was 3 years old).  I can get everything to run but the CPU/GPU data.    attached is the HWinfo screen shot of my CPU

Here is what my HWiNFO.inc look like while testing the 64/tools skin. 

Code:
[Variables]

; CPU 0
HWiNFO-CPU0-SensorId=0xf0000300
HWiNFO-CPU0-SensorInstance=0x0
HWiNFO-CPU0-Usage=0x7000009
HWiNFO-CPU0-Core0Clock=0x6000000
HWiNFO-CPU0-Core1Clock=0x6000001
HWiNFO-CPU0-Core2Clock=0x6000002
HWiNFO-CPU0-Core3Clock=0x6000003

; CPU 0 DTS
HWiNFO-CPU0-DTS-SensorId=0xF0000400
HWiNFO-CPU0-DTS-SensorInstance=0x0
HWiNFO-CPU0-DTS-CoreMax=0x1000000

; Motherboard
HWiNFO-MOBO-SensorId=0xf0008721
HWiNFO-MOBO-SensorInstance=0x0
HWiNFO-MOBO-CPU-Fan=0x3000000
HWiNFO-MOBO-CPU-VCore=0x3000001

; GPU 0
HWiNFO-GPU0-SensorId=0xe0001800
HWiNFO-GPU0-SensorInstance=0x0
HWiNFO-GPU0-Usage=0x7000000
HWiNFO-GPU0-Temp=0x1000000
HWiNFO-GPU0-Fan=0x3000000
HWiNFO-GPU0-CoreClock=0x6000000
HWiNFO-GPU0-Voltage=0x2000000

I noticed that my entry ID numbers are larger then any demo I have ever seen.  My numbers show as 0x7000009  when the demo shows 0xfe.  wondering if that has anything to do with it.

thanks!
 

Attachments

  • Screenshot 2015-05-05 10.32.53.png
    Screenshot 2015-05-05 10.32.53.png
    33 KB · Views: 8
well in testing im using Version 2 of the HWiNFO as it created a directory of HWiNFO_2.0.0 . I am trying to use also dashboard 1.8 skin and he just mentions the change in the newer versions of HWinfo so I expect it works. But I would truly expect to get the HWinfo skin to work before I could get anything else to work.
 
Hi.  I have 4.62-2500 and Rainmeter 3.2.1 r2386, both 64 bit, and this plugin is working fine.

Can you close Rainmeter, leave HWiNFO running with sensor active, and then open Rainmeter.  Please right click the Rainmeter system tray icon and select About.  Are there any errors logged for HWiNFO?  And on the plugins tab, the HWiNFO.dll lists version 2.0.0.0?
 
stangowner said:
Hi.  I have 4.62-2500 and Rainmeter 3.2.1 r2386, both 64 bit, and this plugin is working fine.

Can you close Rainmeter, leave HWiNFO running with sensor active, and then open Rainmeter.  Please right click the Rainmeter system tray icon and select About.  Are there any errors logged for HWiNFO?  And on the plugins tab, the HWiNFO.dll lists version 2.0.0.0?

hmmmmm   strange it cant find HWiNFO.dll  see screen shots.   and stranger  it still shows version 1.1 in plugins?
 

Attachments

  • Screenshot 2015-05-05 13.10.37.png
    Screenshot 2015-05-05 13.10.37.png
    90.2 KB · Views: 4
  • Screenshot 2015-05-05 13.11.40.png
    Screenshot 2015-05-05 13.11.40.png
    44.1 KB · Views: 2
  • Screenshot 2015-05-05 13.13.43.png
    Screenshot 2015-05-05 13.13.43.png
    53.2 KB · Views: 2
Is your Rainmeter properly installed? It should pickup that extension automatically.
 
I just upgraded to 3.3 yesterday and this is the only thing I cant get working. I could fully uninstall and try over. there was no rmskin to run so I simply unzipped the zip file in rainmeter and closed and opened it to use it. with the files I have im gonna do the same thing if I uninstall/reinstall.
 
ok figured it out. IF you install manually you must

1 - copy HWiNFO.dll to C:\Program Files\Rainmeter\Plugins
2 - copy @Resources folder from \Documents\Rainmeter\Skins\HWiNFO_2.0.0\Skins\HWiNFO to \Documents\Rainmeter\Skins\HWiNFO_2.0.0
3 - then turn it off and back on and bamn it worked.

Something for you to note for others who have this problem.
 
Glad you got it going.

I assume there is a config issue with your web browser then.  The file is a .rmskin, not .zip.  So you should just be able to open it and the install should happen without needing to do anything else.

Thanks for mentioning the work-around in case others have the same issue.

BTW - that plugin folder is for Rainmeter provided .dll files.  Installing it the normal way puts it in "C:\Users\<username>\AppData\Roaming\Rainmeter\Plugins" which does not require admin rights.  Regardless, Rainmeter looks in both places for the .dll to load, so either one works.  Just keep this in mind in case you ever update......it won't overwrite the one you put under program files by yourself.
 
Back
Top