DungKHoang Posted November 30, 2006 Report Share Posted November 30, 2006 Hi, I run this command and it crashes all the time: PS C:\> ps | out-gauge -value CPU -refresh 0:0:1 Here is the configuration: Windows XP SP2 PowerShell 1.0 RTM PowerGadgets Trial version Let me know if you need more information to debug the problem /Dung Test Min Max Properties.zip Quote Link to comment Share on other sites More sharing options...
TheGadgetGuy Posted November 30, 2006 Report Share Posted November 30, 2006 The problem is that get-process (ps) is returning CPU for ALL the processes in your machine, if you do out-chart instead of out-gauge you will see a chart showing CPU with many processes. The out-gauge cmdlet displays a single value in a radial, vertical, horizontal and digital panel gauge so you must first filter the variable you want to plot. If you type the following script: ps | select ProcessName,CPU | where {$_.ProcessName -eq "System"} | out-gauge -value CPU It will create and display the gauge. You just need to know which process you want to monitor and change the name in the where cmdlet. TheGadgetGuy_ Quote Link to comment Share on other sites More sharing options...
JuanC Posted December 1, 2006 Report Share Posted December 1, 2006 Have you tried with other Process properties (e.g. WorkingSet, HandleCount). CPU is kind of special, if you do ps | get-member you will notice that most properties's MemberType are "Property" but CPU, Company and others are "ScriptProperty". Script properties are injected by PowerShell and we have had issues before with those properties. I would also recommend installing our most recent build. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.