Kitutz / rainmeter

Automatically exported from code.google.com/p/rainmeter
0 stars 0 forks source link

Not reading multiple cores Vista x64 Ultimate #23

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hi,

I believe the Perfmon.dll is not reading my CPU%'s correctly.

What steps will reproduce the problem?
[MeasureCPU0]
Measure= Plugin
Plugin= Perfmon.dll
PerfMonObject="Processor"
PerfMonInstance=0
PerfMonCounter="% Processor Time"
PerfMonDifference=1
InvertMeasure=1

[MeasureCPU1]
Measure= Plugin
Plugin= Perfmon.dll
PerfMonObject="Processor"
PerfMonInstance=1
PerfMonCounter="% Processor Time"
PerfMonDifference=1
InvertMeasure=1

What is the expected output? What do you see instead?
Expected output on normal usage should be nowhere higher than 2%.  Instead,
numbers are showing as '-10000000'.  The output value does change (between
9000000 to 11000000).

What version of the product are you using? On what operating system?
Perfmon.dll is version 1.2
Rainmeter .14 for 64-bit
Vista x64 Ultimate SP1
Intel Core i7 920

I checked Perfmon.msc and that is showing the Data correctly.

In the attached screenshot - the above CPU is using the standard rainmeter
capture while the bottom one (CPU2) is trying to read one of the cores.

Original issue reported on code.google.com by nocod...@gmail.com on 30 Mar 2009 at 4:07

Attachments:

GoogleCodeExporter commented 8 years ago
Just tried this on my work PC which is Vista Business 32-bit SP1 and had the 
same 
problem.

It is running Intel Core 2 Duo CPU T7300.

Original comment by nocod...@gmail.com on 30 Mar 2009 at 2:49

GoogleCodeExporter commented 8 years ago
I just did a script which did the same thing on my Athlon X2 so I'm pretty sure 
it's
the same issue you guys are seeing. The solution was:

[CPU0%]
MeasureName=MeasureCPU0
Meter=STRING
Percentual=1

Voila! No more crazy numbers.

Original comment by kbuffing...@gmail.com on 2 Apr 2009 at 7:38

GoogleCodeExporter commented 8 years ago
Can you add this to a wiki page for others to see in the future?

Original comment by brian.to...@gmail.com on 16 Apr 2009 at 6:20

GoogleCodeExporter commented 8 years ago

Original comment by kbuffing...@gmail.com on 29 Apr 2009 at 5:10