penfold2007

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About penfold2007

  • Rank
    Newbie
  1. Aah, now I see (FYI for anyone else trying this, there is an extra space needed after the first AnchorPoint). It seems a shame that the syntax for different gadget types does not appear to be entirely consistent though - have you any tips for quickly converting to other types?
  2. Sorry - they are only exposed in Vista/Longhorn. Just pick any others to be honest, so I can just see the principle. Available MBytes as the main series, although I may present this as line graphs or something. Inner gauges will be fine for now.
  3. To start with, having the following objects from the Win32_PerfRawData_PerfOS_Memory class on a single display would be really useful: AvailableMBytes ModifiedPageListBytes StandbyCacheCoreBytes StandbyCacheNormalPriorityBytes I realise this is probably real easy but I don't see it in the docs. (If it is in the documentation, point it out and I will stumble away with my head down in shame!) Thanks.
  4. Hi, that's half-correct. I am after the current value of the process working set size. However, Windows also offers the ability to set min/max limits on working sets, using the SetProcessWorkingSetSize (2000 and XP) or SetProcessWorkingSetSizeEx (only available in Server 2003 and Vista) APIs. This actively affects how the memory manager behaves when paging processes in/out of physical memory. For example, if you use the Ex version of the API to implement a max limit of 10MB on a process, an instance of that process attempting to use a working set of 15MB would result in the least-recently-used 5MB being written to pagefile. (the non-Ex API behaves slightly differently, although is essentially the same thing) I would like the smaller indicators to return the values of these limits. If it's too much hassle to get into the API calls, then tips for how to incorporate multiple perfmon counters into a single gadget via powershell would be just as welcome. Thanks for your help.
  5. @Marco Shaw, According to the File-Save As dialog box, MS Visio supports the SVG file format. I don't have access to Illustrator, anyone know if it should work with Visio? Regards, Dan.
  6. Hi there, Powergadgets appears to be very cool! I'm still evaluating it just now, and am trying to add multiple values to a gauge. I would like to monitor working set size and min/max working set limits. Ideally this would have the working set size as a vertical gauge, and the limits as little pointers on the gauge. I can get the working set size using: Get-wmiobject -class "Win32_PerfRawData_PerfProc_Process" | where {$_.Name -eq "_Total"} | out-gauge -value WorkingSet -floating -refresh 0:0:1 However, I am not a coder, so am unsure how to use the SetProcessWorkingSetSizeEx API to return the min/max limits in a powershell script, or how to incorporate this into the same gadget. Any help would be appreciated. Thanks, Dan.