For more or less static stuff, related to the same class and that you'd use PowerShell for, you could also "pack" everything in a single query so that it lasts less to get the data:Even so, and even inside the PowerShell window, getting this data won't be instantaneous (not even if you only get the processor name!), but at least you'd get most of these just once, as already mentioned. To make this more user friendly, I use both the string (the output) and the number (the error code) value of the corresponding RunCommand measure to display the "phase" of data retrieval in my skins (the GPU data shown below, see how something is always displayed in the lower part of the GIF to tell the user what happens, even though it's just "Detecting bla bla bla...preparing." or even some "Please wait" message until the PowerShell data is actually retrieved):
Code:
Get-CimInstance -ClassName Win32_Processor | Select-Object -Property Name,LoadPercentage,CurrentClockSpeed,CurrentVoltage,NumberOfEnabledCore,NumberOfLogicalProcessors,L2CacheSize,L3CacheSize,VirtualizationFirmwareEnabled | Format-ListCode:
[MS_RunCommand_VideoInfo]Measure=PluginPlugin=RunCommandProgram=powershellParameter=-command ......RegExpSubstitute=1Substitute="^$":"≡ Detecting video controllers...RC[MS_RunCommand_VideoInfo:].","\.\.\.RC-1\.$":"...preparing.","\.\.\.RC0\.$":"...processing.","\.\.\.RC1\.$":"...none found.","\.\.\.RC\d{3}\.$":"...errors logged.",...Statistics: Posted by Yincognito — Today, 8:37 am