05-02-2006 08:41 AM
05-02-2006 08:58 AM - edited 05-02-2006 08:58 AM
Message Edited by smercurio_fc on 05-02-2006 08:58 AM
05-03-2006 03:39 AM
05-02-2007 08:36 AM
05-02-2007 09:10 AM
07-29-2011 01:36 PM - edited 07-29-2011 01:42 PM
Cool! Anyone know the name of counter for memory usage? How did you get the input reference to DISystemMonitor?
Yes I did go to MSDN, and after swimming in the links for awhile, I found some code for listing the counters... but wow, surely the typical name for a memory counter hasn't changed?
Thanks.
07-29-2011 03:01 PM - edited 07-29-2011 03:01 PM
The input is the ActiveX container on the front panel. Attached is the actual VI (LV 8.2). I know it works in XP, but it doesn't work in Windows 7. At least Windows 7 64-bit. Not sure about Windows 7 32-bit.
The syntax for the pathname is \\Computer\PerfObject(ParentInstance/ObjectInstance#InstanceIndex)\Counter. In my example "PerfObject" is "Process(*)" to show all processes, and "Counter" is the name of the counter, which is "% Processor Time". You can get the various performance objects from this page: http://technet.microsoft.com/en-us/library/cc783073%28WS.10%29.aspx. Once you select one of the performance objects you want then the right-hand pane will list the available counter names. As you'll note for the Memory object, there's lots of memory counters.
08-01-2011 11:05 AM - edited 08-01-2011 11:10 AM
Thanks!!! This was interesting. After trying various counters from Memory, TCP, Process, System, and Server, I couldn't find any which correlated with the "not enough memory" error associated with my TCP/IP connection. Any ideas? Do you think this is my Windows Message loop filling up?
08-01-2011 12:06 PM
That's a different question, and we should stick to the separate thread you created for this.