--- In [email protected], "entropyreduction" 
<alancampbelllists+ya...@...> wrote:
> 
> Cleaned up script, 
> see processRAMusageUsingCOM.powerpro
> in http://tech.groups.yahoo.com/group/power-pro/files/Scripts/
> 
> you need latest version of powerpro at
> http://powerpro.webeddie.com/download/powerpro.exe

Also latest beta of com plugin?

Hmmn. Something is a little funky with that for each.  The com.dll I am using 
is dated Apr 1, so maybe this has changed. With mine, the for-each needs to be 
skipped if colProcessMem.count is zero.

if (colProcessMem.count > 0) do
  local processinfo
  for each processinfo in colProcessMem
   win.debug("Name: " ++ processinfo.Name ++ "; ProcessId: " ++ 
processinfo.ProcessId ++ "; WorkingSetSize: " ++ (processinfo.WorkingSetSize / 
1024))
  endfor
else
  win.debug("No processes matched the WMI query executed.")
endif

Since we have useful error diagnostics in recent versions of the com plugin, 
probably should avoid using com.error_dialog_off() any more (except maybe in a 
script that does its own error handling and turns the error dialog back on 
afterwards).

Regards,
Sheri


Reply via email to