CPUUSAGE has stoppe...
 
Notifications
Clear all

We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.

Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.

CPUUSAGE has stopped working in other languages

14 Posts
2 Users
6 Reactions
133 Views
(@roadarsi)
Eminent Member Registered
Joined: 5 years ago
Posts: 18
Topic starter  

Hello, after four years I decided to update DesktopInfo from version 3.5.0 to version 3.22.0, but an old problem I had with version 3.3.0 has returned: the CPU usage is no longer displayed in my system’s language, Brazilian Portuguese.

At the time, you configured it to work regardless of the language, by cross-referencing the English name—which is always present—with the operating system’s current language.

Below are the relevant thread from that time:

https://www.glenn.delahoy.com/community/desktop-info/help-to-migrate-from-v2-3x-to-v3-3x/

and your solution:

There was another comment that mentioned that performance counters don't necessarily line up across installations. So the correct method to look up counter names is:

1. Look up the English version of the desired counter names in the 009 key (which is present in every Windows installation regardless of language).
2. Get the index numbers of the found English counters.
3. Look up those index numbers in the CurrentLanguage key.
4. Get the matching local language counter name strings.

I'll put up v3.3.1 shortly.

Perhaps a code regression at some point? I tested version 3.21.0 and it also fails to display CPUUSAGE in my language.

I use Windows 11 and have tested it on the 24H2 and 25H2 builds.

Thank you very much for your work; for now I’ll stick with version 3.5.0, but I’d really like to use the latest version, as I really like the individual CPU usage feature.


   
Glenn reacted
Quote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

There's been lots of changes since v3.5.  You should probably check the Release Notes at the end of the manual.  The following comes from the desktopinfo-advanced.ini file

CPUUSAGE=wide:1, font-face:Consolas, font-size:8, rich-text:1, align:c,\
  chart:bar max:100 border-color:%grey%  series1:%PercentProcessorTime% color1:c00000 threshold:80 width:230,\
  display:Core %1: \c%white%\%2[3.0f]% %chart%

This item requires the Processor performance counter. If this counter is not available, the item returns no results.

See the discussion on retrieving performance counters on page 43, CPUUSAGE on page 86.

 

 


   
ReplyQuote
(@roadarsi)
Eminent Member Registered
Joined: 5 years ago
Posts: 18
Topic starter  

Hello, I checked the counters and the changes, and ran a very simple test by adding cpuusage to the end of the automatically generated desktopinfo.ini file (I just changed the form color).

In the test, I set cpuusage to the format I want and also used your example from the desktopinfo-advanced.ini file.

As you can see in the attachment, when I change the operating system language to English, the CPU usage is displayed correctly; when I leave the operating system in Brazilian Portuguese, only “n/a” is displayed.

It seems there really was some regression at some point between version 3.5.0 (the one I’m currently using) and version 3.21.0 of the fix you made in version 3.3.1.  😥 


   
Glenn reacted
ReplyQuote
(@roadarsi)
Eminent Member Registered
Joined: 5 years ago
Posts: 18
Topic starter  

I was focused solely on CPU usage, but I just realized that other counters also suffer from this problem. In the same image I sent earlier, we can see that NETWORKPERF, when the operating system is in Portuguese, is not displayed correctly. Instead of showing the bytes sent, received, and connection speed (which are displayed correctly when the operating system is in English), it only displays R: %BytesReceivedPerSec%[3.1b]Bps\, S: %BytesSentPerSec%[3.1b]Bps\, B: %CurrentBandwidth%[1.0B]bps


   
Glenn reacted
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

I presume the performance counter fields are in Portuguese.  You can elect to use the names in the local language (Portuguese) or use the English versions.

To use the English versions, add the following option to CPUUSAGE:    "local:0"  and then reference all counter fields in English.

To use the Portuguese version, add the following option to CPUUSAGE:    "local:1"   and then reference all counter fields in Portuguese. 

The fields are returned in the local language by default.

The easiest way to see your system performance counters is with Windows perfmon.exe. When you add
counters you're presented with a list of objects, instances and counters. These are the counters that Desktop
Info retrieves via the PDH API. There's a little bit of massaging of the counter names to make them more
usable, in the same way that WMI does. For example,
"Bytes Received /sec" becomes "BytesReceivedPersec"
If I'm retro-fitting an existing item, it will continue to use the return values it always has.

You can also see the performance object and counter names in your registry at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

The cpu performance counters used by CPUUSAGE are: \Processor(*)\% Processor Time

 

 


   
ReplyQuote
(@roadarsi)
Eminent Member Registered
Joined: 5 years ago
Posts: 18
Topic starter  

That worked for the network, but not for cpuusage 😥 😥


   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

@roadarsi Post the item you are trying to get working.


   
ReplyQuote
(@roadarsi)
Eminent Member Registered
Joined: 5 years ago
Posts: 18
Topic starter  

@glenn I'm trying to get your example to work:

CPUUSAGE=wide:1, font-face:Consolas, font-size:8, rich-text:1, align:c,\
  chart:bar max:100 border-color:%grey%  series1:%PercentProcessorTime% color1:c00000 threshold:80 width:230,\
  display:Core %1: \c%white%\%2[3.0f]% %chart%

That's how I want it to be :

CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,display:%2[2.0f]%,color:FFFFFF,display:%2[2.0f]% %chart%

Both modes work if my operating system is in English, but not in Portuguese, even if I set the parameter to local:0

 

 

For the network, I used WMI like this:

WMI=interval:1,color:00ffbb,text:Realtek Gaming,namespace:root\cimv2,query:Win32_PerfFormattedData_Tcpip_NetworkInterface where Name = "Realtek Gaming GbE Family Controller",display:Entrada: %BytesReceivedPersec%[6.2b]B  Saida: %BytesSentPersec%[6.2b]B   %CurrentBandwidth%[3.0B]bps

NETWORKPERF works this way even though my operating system is in Portuguese (thanks to your tip about the locale:0), so it’s already set up just the way I want it:

NETWORKPERF=local:0, filter:+Realtek Gaming GbE Family Controller,row-text:Realtek Gaming, color:00ffbb, \
  display:Entrada: %BytesReceivedPersec%[6.2b]B Saida: %BytesSentPersec%[6.2b]B %CurrentBandwidth%[3.0B]bps

 

All the other settings I was using still work properly.

 

Just for reference, these are my old settings (version 3.5.0); the only feature I use that I can't get to work is cpuusage

[items]


# page 1 - cpu
CPUTYPE=active:1,lid:cputype,color:0099EE
CORETEMP=active:1,interval:5,color:00dddd,threshold1:1 70,display:%1%2
DATETIME=interval:1,display:%12
CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,display:%2[2.0f]%,color:FFFFFF,display:%2[2.0f]% %chart%


COLOR=aaCCEE
# page 1 - top processes
TOPPROCESSCPU=active:1,interval:3,display:%1 (pid:%2) %3[3.2f]%
TOPPROCESSMEM=active:1,interval:5,display:%1 (pid:%2) %3[1.1b]B
PAGEFAULTS=interval:5,font-size:100%,threshold1:5 -80,display:Total: %1\, Hard: %2\, Hit: %5%


# page 1 - memory
PHYSICALRAM=active:1,interval:5,color:FFFFFF,threshold1:3 80 0000FF,display:%1[4.2b]B / %2[4.2b]B (%3% used)
PAGEFILE=active:1,interval:5,color:aaaaaa,threshold1:3 80 0000FF,tcolor:0000FF,display:%1[4.2b]B / %2[4.2b]B (%3% used)


color=77ee00
# page 1 - network
NETWORKINTERFACES=interval:30,operstatus:1,iftype:6 71,row-text:Interface ,display:%3|  %8 (%4)|  Gateway: %17
NETCONNECTIONS=interval:10
WMI=interval:30,threshold1:11 30,text:Network Latency, namespace:root\cimv2,query:Win32_PingStatus where address='one.one.one.one',display:%ResponseTime%ms (one.one.one.one)
WMI=interval:1,color:00ffbb,text:Realtek Gaming,namespace:root\cimv2,query:Win32_PerfFormattedData_Tcpip_NetworkInterface where Name = "Realtek Gaming GbE Family Controller",display:Entrada: %BytesReceivedPersec%[6.2b]B  Saida: %BytesSentPersec%[6.2b]B   %CurrentBandwidth%[3.0B]bps
#WMI=interval:1,color:00ffbb,text:Realtek Gaming,namespace:root\cimv2,query:Win32_PerfFormattedData_Tcpip_NetworkAdapter where Name = "Realtek Gaming GbE Family Controller",display:Entrada: %BytesReceivedPersec%[6.2b]B  Saida: %BytesSentPersec%[6.2b]B   %CurrentBandwidth%[3.0B]bps


color=ffccaa
# page 1 - disks
LOGICALDRIVES=interval:5,row-text:%1: (%2), display:%6[5.1b]B / %5[5.1b]B (%8[5.1b]B livres) (%7[1.1f]% used),threshold1:7 90 0000ff

   
Glenn reacted
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

We need to check if the performance counters are there.

1. Open perfmon, right click on the chart area and select "Add Counters"

2. Wait for a while until it populates the dialog with counters

3. Drop down the Processor item   (Processador ?)

4. You will see a number of counters including "% Processor Time" or possibly "% Tempo de Processador".

5. If you can't see this then the performance counter is missing on that machine.

6. If you do see this then make a note of exactly how it is spelt.

7. Adjust as follows:

I expect you will find something like "% Tempo de Processador"

a. Replace % with Percent

b. Remove spaces

You will end up with something like "PercentTempodeProcessador"

8. Put this in the DTI item.  (No Local option)

CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,\
  display:%PercentTempodeProcessador%[2.0f]%, color:FFFFFF, %chart%

 

Edit: Corrected the translated counter instance name.

This post was modified 2 weeks ago 3 times by Glenn

   
ReplyQuote
(@roadarsi)
Eminent Member Registered
Joined: 5 years ago
Posts: 18
Topic starter  

If I understood correctly, is that what you wanted?

In the image, you can see that on my system the name is "% tempo de processador".

After the adjustment, it looked like this:

CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,\
  display:%Percenttempodeprocessador%[2.0f]%, color:FFFFFF, %chart%

But that doesn't work either.

I tried the options below, but none of them work:

CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,\
  display:%PercentTempoDeProcessador%[2.0f]%, color:FFFFFF, %chart%

CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,\
  display:%2[2.0f]%, color:FFFFFF, %chart%

CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,\
  display:path:\Processador(*)\% tempo de processador[2.0f]%, color:FFFFFF, %chart%

CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,\
  display:\% tempo de processador[2.0f]%, color:FFFFFF, %chart%
But I finally managed to get it working using the PERF call:
PERF=interval:1,path:\Processador(*)\% tempo de processador, \
  row-text:Cpu %Instance%,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,display:%2[3.0f]%,color:FFFFFF,display:%2[3.0f]% %chart%
 
If possible, I would prefer to use the CPUUSAGE call.
 
Here's what my final configuration file looks like:
[items]


# page 1 - cpu
CPUTYPE=active:1,lid:cputype,color:0099EE, maxrows:1
CORETEMP=active:1,interval:5,color:00dddd,alarms:(%1 ge 70 2222e0),display:%1%2
DATETIME=interval:1,display:%12
PERF=interval:1,path:\Processador(*)\% tempo de processador, \
  row-text:Cpu %Instance%,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,display:%2[3.0f]%,color:FFFFFF,display:%2[3.0f]% %chart%


COLOR=aaCCEE
# page 1 - top processes
TOPPROCESSCPU=active:1,interval:3,display:%1 (pid:%2) %3[3.2f]%
TOPPROCESSMEM=active:1,interval:5,display:%1 (pid:%2) %3[1.1b]B
PAGEFAULTS=font-size:100%,alarms:(%5 le 80 2222e0),display:Total: %1[1.0f]\, Hard: %2[1.0f]\, Hit: %5[1.0f]%


# page 1 - memory
PHYSICALRAM=active:1,interval:5,color:FFFFFF,alarms:(%3 ge 80 2222e0),display:%1[4.2b]B / %2[4.2b]B (%3% used)
PAGEFILE=active:1,interval:5,color:aaaaaa,alarms:(%3 ge 80 2222e0),tcolor:0000FF,display:%1[4.2b]B / %2[4.2b]B (%3% used)


color=77ee00
# page 1 - network
NETWORKINTERFACES=interval:30,operstatus:1,iftype:6 71,row-text:Interface ,display:%3|  %8 (%4)|  Gateway: %17
NETCONNECTIONS=interval:10
WMI=interval:30,alarms:(%11 ge 30 2222e0),text:Network Latency, namespace:root\cimv2,query:Win32_PingStatus where address='one.one.one.one',display:%ResponseTime%ms (one.one.one.one)
NETWORKPERF=local:0, filter:+Realtek Gaming GbE Family Controller,row-text:Realtek Gaming, color:00ffbb, \
  display:Entrada: %BytesReceivedPersec%[6.2b]B Saida: %BytesSentPersec%[6.2b]B %CurrentBandwidth%[3.0B]bps


color=ffccaa
# page 1 - disks
LOGICALDRIVES=interval:5,row-text:%1: (%2), display:%6[5.1b]B / %5[5.1b]B (%8[5.1b]B livres) (%7[1.1f]% used),alarms:(%7 ge 90 2222e0)

Just a note: in version 3.5.0, I use a 1-second interval for the DATETIME field and get updates every second; in version 3.22.0, even though it’s set to 1, the date and time are updated only every 2 seconds (if I set a longer interval, such as 5 seconds, it updates every 5 seconds, but the 1-second interval always takes 2 seconds)


   
Glenn reacted
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

Good, you got it working with PERF.  Curious why CPUUSAGE doesn't work. I'll have to look into it.

Posted by: @roadarsi

Just a note: in version 3.5.0, I use a 1-second interval for the DATETIME field and get updates every second; in version 3.22.0, even though it’s set to 1, the date and time are updated only every 2 seconds (if I set a longer interval, such as 5 seconds, it updates every 5 seconds, but the 1-second interval always takes 2 seconds)

It's basically a function of how much work it has to do each time around. It will most likely take more than a second to run through the whole ini file once, particularly when there are long running items such WMI queries.  You can experiment by putting some items like WMI in a thread so that they return immediately. 

This post was modified 2 weeks ago by Glenn

   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

Can you try the following please.

1. enable desktop info debug by adding the "debug" option to the log-level in the [options] section of the ini.

2. run desktop info and navigate to wherever the CPUUSAGE item is and wait for it to populate or not.

3. quit desktop info (cos it runs really slowly in debug)

4. open the log file in notepad and search for "[TPdhReader.Start]" and look for the Processador entry

this will tell us the performance counters it is reading.


   
ReplyQuote
(@roadarsi)
Eminent Member Registered
Joined: 5 years ago
Posts: 18
Topic starter  

@glenn 

Here with CPUUSAGE using the English default

CPUUSAGE=wide:1, font-face:Consolas, font-size:8, rich-text:1, align:c,\
  chart:bar max:100 border-color:%grey%  series1:%PercentProcessorTime% color1:c00000 threshold:80 width:230,\
  display:Core %1: \c%white%\%2[3.0f]% %chart%
 
26/05/2026 23:51:31:903 COLLECTOR     [TCollector.SyncDoEvaluate] uid:cpuusage - ProcLastUpdate=0
26/05/2026 23:51:31:903 DEBUG         [DoProc]
26/05/2026 23:51:31:903 DEBUG         [PdhReader.GetCoreUsage]
26/05/2026 23:51:31:903 DEBUG         [TPdhReader.Create] \Processor(*)\% Processor Time
26/05/2026 23:51:31:904 DEBUG         [TPdhReader.ConvertObjectNameToLocalLanguage] \Processor(*)\% Processor Time
26/05/2026 23:51:31:904 DEBUG         [TPdhReader.Start] \\PC-NAME-EDITED\Processador(*)\% Processor Time
26/05/2026 23:51:31:904 DEBUG         [TPdhReader.Start] PdhExpandWildCardPath(1) Failed: (0xC0000BB9) \\PC-NAME-EDITED\Processador(*)\% Processor Time
26/05/2026 23:51:31:904 DEBUG         [TPdhReader.GetCurrentValues] \\PC-NAME-EDITED\Processador(*)\% Processor Time
26/05/2026 23:51:31:904 DEBUG         [TPdhReader.ConvertToRawData] \\PC-NAME-EDITED\Processador(*)\% Processor Time
26/05/2026 23:51:31:905 TIMING        [cpuusage] time: 0ms
26/05/2026 23:51:31:905 DEBUG         [ProcessData] cpuusage
26/05/2026 23:51:31:905 DEBUG         [SetUserVariables]
26/05/2026 23:51:31:905 DEBUG         [SetAlarms2] cpuusage 0
 
 
Here with CPUUSAGE trying in Portuguese
CPUUSAGE=interval:1,row-text:Cpu %1,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,\
  display:%Percenttempodeprocessador%[2.0f]%, color:FFFFFF, %chart%
 
26/05/202623:58:34:197 COLLECTOR     [TCollector.SyncDoEvaluate] uid:cpuusage - ProcLastUpdate=0
26/05/202623:58:34:197DEBUG         [DoProc]
26/05/202623:58:34:197DEBUG         [PdhReader.GetCoreUsage]
26/05/202623:58:34:197DEBUG         [TPdhReader.Create] \Processor(*)\% Processor Time
26/05/202623:58:34:198DEBUG         [TPdhReader.ConvertObjectNameToLocalLanguage] \Processor(*)\% Processor Time
26/05/202623:58:34:198DEBUG         [TPdhReader.Start] \\PC-NAME-EDITED\Processador(*)\% Processor Time
26/05/202623:58:34:198DEBUG         [TPdhReader.Start] PdhExpandWildCardPath(1) Failed: (0xC0000BB9) \\PC-NAME-EDITED\Processador(*)\% Processor Time
26/05/202623:58:34:198DEBUG         [TPdhReader.GetCurrentValues] \\PC-NAME-EDITED\Processador(*)\% Processor Time
26/05/202623:58:34:198DEBUG         [TPdhReader.ConvertToRawData] \\PC-NAME-EDITED\Processador(*)\% Processor Time
26/05/202623:58:34:199 TIMING        [cpuusage] time: 0ms
26/05/202623:58:34:199DEBUG         [ProcessData] cpuusage
26/05/202623:58:34:199DEBUG         [SetUserVariables]
26/05/202623:58:34:199DEBUG         [SetAlarms2] cpuusage 0
 
 
Here, using PERF in Portuguese
PERF=interval:1,path:\Processador(*)\% tempo de processador, \
  row-text:Cpu %Instance%,chart:bar scale:linear max:100 series1:2 threshold:70 color1:007700 color2:0077ff color3:0000ff,display:%2[3.0f]%,color:FFFFFF,display:%2[3.0f]% %chart%
 
27/05/2026 00:02:51:365 COLLECTOR     [TCollector.SyncDoEvaluate] uid:perf - ProcLastUpdate=0
27/05/2026 00:02:51:365 DEBUG         [DoProc]
27/05/2026 00:02:51:365 DEBUG         [PdhReader.GetCustomPerf]
27/05/2026 00:02:51:365 DEBUG         [TPdhReader.Create] \Processador(*)\% tempo de processador
27/05/2026 00:02:51:365 DEBUG         [TPdhReader.ConvertObjectNameToLocalLanguage] \Processador(*)\% tempo de processador
27/05/2026 00:02:51:365 DEBUG         [TPdhReader.Start] \\PC-NAME-EDITED\Processador(*)\% tempo de processador
27/05/2026 00:02:51:366 DEBUG         [TPdhReader.Start] PdhExpandWildCardPath(1) Success: 930
27/05/2026 00:02:51:366 DEBUG         [TPdhReader.Start] PdhExpandWildCardPath(2) Success: 930
27/05/2026 00:02:51:366 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(0)\% tempo de processador
27/05/2026 00:02:51:366 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(1)\% tempo de processador
27/05/2026 00:02:51:366 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(2)\% tempo de processador
27/05/2026 00:02:51:367 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(3)\% tempo de processador
27/05/2026 00:02:51:367 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(4)\% tempo de processador
27/05/2026 00:02:51:367 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(5)\% tempo de processador
27/05/2026 00:02:51:367 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(6)\% tempo de processador
27/05/2026 00:02:51:367 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(7)\% tempo de processador
27/05/2026 00:02:51:367 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(8)\% tempo de processador
27/05/2026 00:02:51:368 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(9)\% tempo de processador
27/05/2026 00:02:51:368 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(10)\% tempo de processador
27/05/2026 00:02:51:368 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(11)\% tempo de processador
27/05/2026 00:02:51:368 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(12)\% tempo de processador
27/05/2026 00:02:51:368 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(13)\% tempo de processador
27/05/2026 00:02:51:368 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(14)\% tempo de processador
27/05/2026 00:02:51:369 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(15)\% tempo de processador
27/05/2026 00:02:51:369 DEBUG         [TPdhReader.ConvertLocalCounterToEnglish] \\PC-NAME-EDITED\Processador(_Total)\% tempo de processador
27/05/2026 00:02:51:369 DEBUG         [TPdhReader.Start] PdhOpenQuery: Success
27/05/2026 00:02:51:369 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(0)\% tempo de processador
27/05/2026 00:02:51:369 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(1)\% tempo de processador
27/05/2026 00:02:51:369 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(2)\% tempo de processador
27/05/2026 00:02:51:370 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(3)\% tempo de processador
27/05/2026 00:02:51:370 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(4)\% tempo de processador
27/05/2026 00:02:51:370 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(5)\% tempo de processador
27/05/2026 00:02:51:370 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(6)\% tempo de processador
27/05/2026 00:02:51:370 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(7)\% tempo de processador
27/05/2026 00:02:51:370 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(8)\% tempo de processador
27/05/2026 00:02:51:370 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(9)\% tempo de processador
27/05/2026 00:02:51:371 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(10)\% tempo de processador
27/05/2026 00:02:51:371 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(11)\% tempo de processador
27/05/2026 00:02:51:371 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(12)\% tempo de processador
27/05/2026 00:02:51:371 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(13)\% tempo de processador
27/05/2026 00:02:51:371 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(14)\% tempo de processador
27/05/2026 00:02:51:371 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(15)\% tempo de processador
27/05/2026 00:02:51:372 DEBUG         [TPdhReader.Start] Add Counter Succeeded: \\PC-NAME-EDITED\Processador(_Total)\% tempo de processador
27/05/2026 00:02:51:372 DEBUG         [TPdhReader.Start]
27/05/2026 00:02:51:372 DEBUG         [TPdhReader.GetCurrentValues] \\PC-NAME-EDITED\Processador(*)\% tempo de processador
27/05/2026 00:02:51:372 DEBUG         [TPdhReader.ConvertToRawData] \\PC-NAME-EDITED\Processador(*)\% tempo de processador
27/05/2026 00:02:51:372 TIMING        [perf] time: 16ms
27/05/2026 00:02:51:373 DEBUG         [ProcessData] perf
27/05/2026 00:02:51:373 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:373 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:373 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:373 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:373 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:374 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:374 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:374 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:374 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:374 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:374 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:375 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:375 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:375 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:375 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:375 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:375 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:376 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:376 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:376 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:376 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:376 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:376 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:377 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:377 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:377 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:377 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:377 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:377 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:378 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:378 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:378 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:378 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:378 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:378 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:379 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:379 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:379 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:379 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:379 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:379 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:380 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:380 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:380 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:380 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:380 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:380 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:381 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:381 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:381 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:381 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:381 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:381 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:382 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:382 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:382 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:382 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:382 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:382 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:383 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:383 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:383 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:383 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:383 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:383 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:384 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:384 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:384 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:384 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:384 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:384 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:385 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:385 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:385 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:385 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:385 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:385 DATA          [ProcessData] perf <null>% %chart%
27/05/2026 00:02:51:386 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:386 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:386 DEBUG         [AddDisplayLines]
27/05/2026 00:02:51:386 DEBUG         [SetUserVariables] <null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%|<null>% %chart%
27/05/2026 00:02:51:386 DEBUG         [SetAlarms2] perf 0
 

   
Glenn reacted
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

@roadarsi awesome, thanks for that.

That tells me the CPUUSAGE is failing to convert my english language counter names to the local language. Now I get to figure out why...


   
ReplyQuote
Glenn's Page