1	1847
2	System
3	The System performance object consists of counters that apply to more than one instance of a component processors on the computer. 
4	Memory
5	The Memory performance object  consists of counters that describe the behavior of physical and virtual memory on the computer.  Physical memory is the amount of random access memory on the computer.  Virtual memory consists of the space in physical memory and on disk.  Many of the memory counters monitor paging, which is the movement of pages of code and data between disk and physical memory.  Excessive paging, a symptom of a memory shortage, can cause delays which interfere with all system processes.
6	% Processor Time
7	% Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the duration of the idle thread is active in the sample interval, and subtracting that time from interval duration.  (Each processor has an idle thread that consumes cycles when no other threads are ready to run). This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time that the service is inactive, and subtracting that value from 100%.
9	% Total DPC Time is the average percentage of time that all processors spend receiving and servicing deferred procedure calls (DPCs).  (DPCs are interrupts that run at a lower priority than the standard interrupts). It is the sum of Processor: % DPC Time for all processors on the computer, divided by the number of processors.  System: % Total DPC Time is a component of System: % Total Privileged Time because DPCs are executed in privileged mode.  DPCs are counted separately and are not a component of the interrupt count.  This counter displays the average busy time as a percentage of the sample time.
10	File Read Operations/sec
11	File Read Operations/sec is the combined rate of file system read requests to all devices on the computer, including requests to read from the file system cache.  It is measured in numbers of reads.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.  
12	File Write Operations/sec
13	File Write Operations/sec is the combined rate of the file system write requests to all devices on the computer, including requests to write to data in the file system cache.  It is measured in numbers of writes. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
14	File Control Operations/sec
15	File Control Operations/sec is the combined rate of file system operations that are neither reads nor writes, such as file system control requests and requests for information about device characteristics or status.  This is the inverse of System: File Data Operations/sec and is measured in number of operations perf second.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval. 
16	File Read Bytes/sec
17	File Read Bytes/sec is the overall rate at which bytes are read to satisfy  file system read requests to all devices on the computer, including reads from the file system cache.  It is measured in number of bytes per second.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.  
18	File Write Bytes/sec
19	File Write Bytes/sec is the overall rate at which bytes are written to satisfy file system write requests to all devices on the computer, including writes to the file system cache.  It is measured in number of bytes per second.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.  
20	File Control Bytes/sec
21	File Control Bytes/sec is the overall rate at which bytes are transferred for all file system operations that are neither reads nor writes, including file system control requests and requests for information about device characteristics or status.  It is measured in numbers of bytes.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval. 
23	% Total Interrupt Time is the average percentage of time that all processors spend receiving and servicing hardware interrupts during sample intervals, where the value is an indirect indicator of the activity of devices that generate interrupts. It is the sum of Processor: % Interrupt Time for of all processors on the computer, divided by the number of processors.  DPCs are counted separately and are not a component of the interrupt count.  This value is an indirect indicator of the activity of devices that generate interrupts, such as the system timer, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. 
24	Available Bytes
25	Available Bytes is the amount of physical memory, in bytes, available to processes running on the computer.  It is calculated by adding the amount of space on the Zeroed, Free, and Standby memory lists. Free memory is ready for use; Zeroed memory consists of pages of memory filled with zeros to prevent subsequent processes from seeing data used by a previous process; Standby memory is memory that has been removed from a process' working set (its physical memory) on route to disk, but is still available to be recalled.  This counter displays the last observed value only; it is not an average. 
26	Committed Bytes
27	Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the physical memory which has space reserved on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average.
28	Page Faults/sec
29	Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages faulted per second because only one page is faulted in each fault operation, hence this is also equal to the number of page fault operations. This counter includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most processors can handle large numbers of soft faults without significant consequence. However, hard faults, which require disk access, can cause significant delays.
30	Commit Limit
31	Commit Limit is the amount of virtual memory that can be committed without having to extend the paging file(s).  It is measured in bytes. Committed memory is the physical memory which has space reserved on the disk paging files. There can be one paging file on each logical drive). If the paging file(s) are be expanded, this limit increases accordingly.  This counter displays the last observed value only; it is not an average.
32	Write Copies/sec
33	Write Copies/sec is the rate at which page faults are caused by attempts to write that have been satisfied by coping of the page from elsewhere in physical memory. This is an economical way of sharing data since pages are only copied when they are written to; otherwise, the page is shared. This counter shows the number of copies, without regard for the number of pages copied in each operation.
34	Transition Faults/sec
35	Transition Faults/sec is the rate at which page faults are resolved by recovering pages that were being used by another process sharing the page, or were on the modified page list or the standby list, or were being written to disk at the time of the page fault. The pages were recovered without additional disk activity. Transition faults are counted in numbers of faults; because only one page is faulted in each operation, it is also equal to the number of pages faulted.
36	Cache Faults/sec
37	Cache Faults/sec is the rate at which faults occur when a page sought in the file system cache is not found and must be retrieved from elsewhere in memory (a soft fault) or from disk (a hard fault). The file system cache is an area of physical memory that stores recently used pages of data for applications. Cache activity is a reliable indicator of most application I/O operations. This counter shows the number of faults, without regard for the number of pages faulted in each operation.
38	Demand Zero Faults/sec
39	Demand Zero Faults/sec is the rate at which a zeroed page is required to satisfy the fault.  Zeroed pages, pages emptied of previously stored data and filled with zeros, are a security feature of Windows that prevent processes from seeing data stored by earlier processes that used the memory space. Windows maintains a list of zeroed pages to accelerate this process. This counter shows the number of faults, without regard to the number of pages retrieved to satisfy the fault. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
40	Pages/sec
41	Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays.  It is the sum of Memory\\Pages Input/sec and Memory\\Pages Output/sec.  It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.
42	Page Reads/sec
43	Page Reads/sec is the rate at which the disk was read to resolve hard page faults. It shows the number of reads operations, without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in working set or elsewhere in physical memory, and must be retrieved from disk. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files. Compare the value of Memory\\Pages Reads/sec to the value of Memory\\Pages Input/sec to determine the average number of pages read during each operation.
44	Processor Queue Length
45	Processor Queue Length is the number of threads in the processor queue.  Unlike the disk counters, this counter counters, this counter shows ready threads only, not threads that are running.  There is a single queue for processor time even on computers with multiple processors. Therefore, if a computer has multiple processors, you need to divide this value by the number of processors servicing the workload. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent of the workload.
46	Thread State
47	Thread State is the current state of the thread.  It is 0 for Initialized, 1 for Ready, 2 for Running, 3 for Standby, 4 for Terminated, 5 for Wait, 6 for Transition, 7 for Unknown.  A Running thread is using a processor; a Standby thread is about to use one.  A Ready thread wants to use a processor, but is waiting for a processor because none are free.  A thread in Transition is waiting for a resource in order to execute, such as waiting for its execution stack to be paged in from disk.  A Waiting thread has no use for the processor because it is waiting for a peripheral operation to complete or a resource to become free.
48	Pages Output/sec
49	Pages Output/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written back to disk only if they are changed in physical memory, so they are likely to hold data, not code. A high rate of pages output might indicate a memory shortage. Windows writes more pages back to disk to free up space when physical memory is in short supply.  This counter shows the number of pages, and can be compared to other counts of pages, without conversion.
50	Page Writes/sec
51	Page Writes/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written to disk only if they are changed while in physical memory, so they are likely to hold data, not code.  This counter shows write operations, without regard to the number of pages written in each operation.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
52	Browser
53	The Browser performance object consists of counters that measure the rates of announcements, enumerations, and other Browser transmissions.
54	Announcements Server/sec
55	Announcements Server/sec is the rate at which the servers in this domain have announced themselves to this server.
56	Pool Paged Bytes
57	Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used.  Memory\\Pool Paged Bytes is calculated differently than Process\\Pool Paged Bytes, so it might not equal Process\\Pool Paged Bytes\\_Total. This counter displays the last observed value only; it is not an average.
58	Pool Nonpaged Bytes
59	Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated.  Memory\\Pool Nonpaged Bytes is calculated differently than Process\\Pool Nonpaged Bytes, so it might not equal Process\\Pool Nonpaged Bytes\\_Total.  This counter displays the last observed value only; it is not an average.
60	Pool Paged Allocs
61	Pool Paged Allocs is the number of calls to allocate space in the paged pool. The paged pool is an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used. It is measured in numbers of calls to allocate space, regardless of the amount of space allocated in each call.  This counter displays the last observed value only; it is not an average.
63	Pool Paged Resident Bytes is the current size, in bytes, of the paged pool. The paged pool is an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used. Space used by the paged and nonpaged pools are taken from physical memory, so a pool that is too large denies memory space to processes. This counter displays the last observed value only; it is not an average.
64	Pool Nonpaged Allocs
65	Pool Nonpaged Allocs is the number of calls to allocate space in the nonpaged pool. The nonpaged pool is an area of system memory area for objects that cannot be written to disk, and must remain in physical memory as long as they are allocated.  It is measured in numbers of calls to allocate space, regardless of the amount of space allocated in each call.  This counter displays the last observed value only; it is not an average.
66	Pool Paged Resident Bytes
67	Bytes Total/sec is the total rate of bytes sent to or received from the network by the protocol, but only for the frames (packets) which carry data. This is the sum of Frame Bytes/sec and Datagram Bytes/sec.
68	System Code Total Bytes
69	System Code Total Bytes is the size, in bytes, of the pageable operating system code currently in virtual memory. It is a measure of the amount of physical memory being used by the operating system that can be written to disk when not in use. This value is calculated by summing the bytes in Ntoskrnl.exe, Hal.dll, the boot drivers, and file systems loaded by Ntldr/osloader.  This counter does not include code that must remain in physical memory and cannot be written to disk. This counter displays the last observed value only; it is not an average.
70	System Code Resident Bytes
71	System Code Resident Bytes is the size, in bytes of the operating system code currently in physical memory that can be written to disk when not in use. This value is a component of Memory\\System Code Total Bytes, which also includes operating system code on disk. Memory\\System Code Resident Bytes (and Memory\\System Code Total Bytes) does not include code that must remain in physical memory and cannot be written to disk. This counter displays the last observed value only; it is not an average.
72	System Driver Total Bytes
73	System Driver Total Bytes is the size, in bytes, of the pageable virtual memory currently being used by device drivers. Pageable memory can be written to disk when it is not being used. It includes physical memory (Memory\\System Driver Resident Bytes) and code and data paged to disk. It is a component of Memory\\System Code Total Bytes. This counter displays the last observed value only; it is not an average.  
74	System Driver Resident Bytes
75	System Driver Resident Bytes is the size, in bytes, of the pageable physical memory being used by device drivers. It is the working set (physical memory area) of the drivers. This value is a component of Memory\\System Driver Total Bytes, which also includes driver memory that has been written to disk. Neither Memory\\System Driver Resident Bytes nor Memory\\System Driver Total Bytes includes memory that cannot be written to disk.
76	System Cache Resident Bytes
77	System Cache Resident Bytes is the size, in bytes, of the pageable operating system code in the file system cache. This value includes only current physical pages and does not include any virtual memory pages not currently resident. It does equal the System Cache value shown in Task Manager. As a result, this value may be smaller than the actual amount of virtual memory in use by the file system cache. This value is a component of Memory\\System Code Resident Bytes which represents all pageable operating system code that is currently in physical memory. This counter displays the last observed value only; it is not an average. 
78	Announcements Domain/sec
79	Announcements Domain/sec is the rate at which a domain has announced itself to the network.
80	Election Packets/sec
81	Election Packets/sec is the rate at which browser election packets have been received by this workstation.
82	Mailslot Writes/sec
83	Mailslot Writes/sec is the rate at which mailslot messages have been successfully received.
84	Server List Requests/sec
85	Server List Requests/sec is the rate at which requests to retrieve a list of browser servers have been processed by this workstation.
86	Cache
87	The Cache performance object  consists of counters that monitor the file system cache, an area of physical memory that stores recently used data as long as possible to permit access to the data without having to read from the disk.  Because applications typically use the cache, the cache is monitored as an indicator of application I/O operations.  When memory is plentiful, the cache can grow, but when memory is scarce, the cache can become too small to be effective.
88	Data Maps/sec
89	Data Maps/sec is the frequency that a file system such as NTFS, maps a page of a file into the file system cache to read the page.
90	Sync Data Maps/sec
91	Sync Data Maps/sec counts the frequency that a file system, such as NTFS, maps a page of a file into the file system cache to read the page, and wishes to wait for the page to be retrieved if it is not in main memory.
92	Async Data Maps/sec
93	Async Data Maps/sec is the frequency that an application using a file system, such as NTFS, to map a page of a file into the file system cache to read the page, and does not wait for the page to be retrieved if it is not in main memory.
94	Data Map Hits %
95	Data Map Hits is the percentage of data maps in the file system cache that could be resolved without having to retrieve a page from the disk, because the page was already in physical memory.
96	Data Map Pins/sec
97	Data Map Pins/sec is the frequency of data maps in the file system cache that resulted in pinning a page in main memory, an action usually preparatory to writing to the file on disk.   While pinned, a page's physical address in main memory and virtual address in the file system cache will not be altered.
98	Pin Reads/sec
99	Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk.  Pages read in this fashion are pinned in memory at the completion of the read.  While pinned, a page's physical address in the file system cache will not be altered.
100	Sync Pin Reads/sec
101	Sync Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk.  Pages read in this fashion are pinned in memory at the completion of the read.  The file system will not regain control until the page is pinned in the file system cache, in particular if the disk must be accessed to retrieve the page.  While pinned, a page's physical address in the file system cache will not be altered.
102	Async Pin Reads/sec
103	Async Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk.  Pages read in this fashion are pinned in memory at the completion of the read.  The file system will regain control immediately even if the disk must be accessed to retrieve the page.  While pinned, a page's physical address will not be altered.
104	Pin Read Hits %
105	Pin Read Hits is the percentage of pin read requests that hit the file system cache, i.e., did not require a disk read in order to provide access to the page in the file system cache.  While pinned, a page's physical address in the file system cache will not be altered.  The LAN Redirector uses this method for retrieving data from the cache, as does the LAN Server for small transfers.  This is usually the method used by the disk file systems as well.
106	Copy Reads/sec
107	Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer.  The LAN Redirector uses this method for retrieving information from the file system cache, as does the LAN Server for small transfers.  This is a method used by the disk file systems as well.
108	Sync Copy Reads/sec
109	Sync Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer.  The file system will not regain control until the copy operation is complete, even if the disk must be accessed to retrieve the page.
110	Async Copy Reads/sec
111	Async Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer.  The application will regain control immediately even if the disk must be accessed to retrieve the page.
112	Copy Read Hits %
113	Copy Read Hits is the percentage of cache copy read requests that hit the cache, that is, they did not require a disk read in order to provide access to the page in the cache.  A copy read is a file read operation that is satisfied by a memory copy from a page in the cache to the application's buffer.  The LAN Redirector uses this method for retrieving information from the cache, as does the LAN Server for small transfers.  This is a method used by the disk file systems as well.
114	MDL Reads/sec
115	MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the data.  The MDL contains the physical address of each page involved in the transfer, and thus can employ a hardware Direct Memory Access (DMA) device to effect the copy.  The LAN Server uses this method for large transfers out of the server.
116	Sync MDL Reads/sec
117	Sync MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages.  The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages.  If the accessed page(s) are not in main memory, the caller will wait for the pages to fault in from the disk.
118	Async MDL Reads/sec
119	Async MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages.  The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages.  If the accessed page(s) are not in main memory, the calling application program will not wait for the pages to fault in from disk.
120	MDL Read Hits %
121	MDL Read Hits is the percentage of Memory Descriptor List (MDL) Read requests to the file system cache that hit the cache, i.e., did not require disk accesses in order to provide memory access to the page(s) in the cache.
122	Read Aheads/sec
123	Read Aheads/sec is the frequency of reads from the file system cache in which the Cache detects sequential access to a file.  The read aheads permit the data to be transferred in larger blocks than those being requested by the application, reducing the overhead per access.
124	Fast Reads/sec
125	Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache.  Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache.  Even if the data is not in the cache, one invocation of the file system is avoided.
126	Sync Fast Reads/sec
127	Sync Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache.  Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache.  Even if the data is not in the cache, one invocation of the file system is avoided.  If the data is not in the cache, the request (application program call) will wait until the data has been retrieved from disk.
128	Async Fast Reads/sec
129	Async Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache.  Normally, file I/O requests will invoke the appropriate file system to retrieve data from a file, but this path permits data to be retrieved from the cache directly (without file system involvement) if the data is in the cache.  Even if the data is not in the cache, one invocation of the file system is avoided.  If the data is not in the cache, the request (application program call) will not wait until the data has been retrieved from disk, but will get control immediately.
130	Fast Read Resource Misses/sec
131	Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request.
132	Fast Read Not Possibles/sec
133	Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass the file system to get to data in the file system cache that could not be honored without invoking the file system.
134	Lazy Write Flushes/sec
135	Lazy Write Flushes/sec is the rate at which the Lazy Writer thread has written to disk.  Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding.  More than one page can be transferred by each write operation.
136	Lazy Write Pages/sec
137	Lazy Write Pages/sec is the rate at which the Lazy Writer thread has written to disk.  Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding.  More than one page can be transferred on a single disk write operation.
138	Data Flushes/sec
139	Data Flushes/sec is the rate at which the file system cache has flushed its contents to disk as the result of a request to flush or to satisfy a write-through file write request.  More than one page can be transferred on each flush operation.
140	Data Flush Pages/sec
141	Data Flush Pages/sec is the number of pages the file system cache has flushed to disk as a result of a request to flush or to satisfy a write-through file write request.  More than one page can be transferred on each flush operation.
142	% User Time
143	% User Time is the percentage of elapsed time the processor spends in the user mode. User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems.  The alternative, privileged mode, is designed for operating system components and allows direct access to hardware and all memory.  The operating system switches application threads to privileged mode to access operating system services. This counter displays the average busy time as a percentage of the sample time.
144	% Privileged Time
145	% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode.  When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process. 
146	Context Switches/sec
147	Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another.  Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service.  It is the sum of Thread\\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches.  There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval. 
148	Interrupts/sec
149	Interrupts/sec is the average rate, in incidents per second, at which the processor received and serviced hardware interrupts. It does not include deferred procedure calls (DPCs), which are counted separately. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards, and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended. The system clock typically interrupts the processor every 10 milliseconds, creating a background of interrupt activity. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
150	System Calls/sec
151	System Calls/sec is the combined rate of calls to operating system service routines by all processes running on the computer. These routines perform all of the basic scheduling and synchronization of activities on the computer, and provide access to non-graphic devices, memory management, and name space management. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval. 
152	Level 1 TLB Fills/sec
153	Level 1 TLB Fills/sec is the frequency of faults that occur when reference is made to memory whose Page Table Entry (PTE) is not in the Translation Lookaside Buffer (TLB).  On some computers this fault is handled by software loading the PTE into the TLB, and this counter is incremented.
154	Level 2 TLB Fills/sec
155	Level 2 TLB Fills/sec is the frequency of faults that occur when reference is made to memory whose Page Table Entry (PTE) is not in the Translation Lookaside Buffer (TLB), nor is the page containing the PTE.  On some computers this fault is handled by software loading the PTE into the TLB, and this counter is incremented.
156	Enumerations Server/sec
157	% User Time is the percentage of elapsed time that the process threads spent executing code in user mode. Applications, environment subsystems, and integral subsystems execute in user mode. Code executing in user mode cannot damage the integrity of the Windows executive, kernel, and device drivers. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.
158	Enumerations Domain/sec
159	% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service is called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.
160	Enumerations Other/sec
161	Enumerations Server/sec is the rate at which server browse requests have been processed by this workstation.
162	Missed Server Announcements
163	Enumerations Domain/sec is the rate at which domain browse requests have been processed by this workstation.
164	Missed Mailslot Datagrams
165	Enumerations Other/sec is the rate at which browse requests processed by this workstation are not domain or server browse requests.
166	Missed Server List Requests
167	Missed Server Announcements is the number of server announcements that have been missed due to configuration or allocation limits.
168	Server Announce Allocations Failed/sec
169	Missed Mailslot Datagrams is the number of Mailslot Datagrams that have been discarded due to configuration or allocation limits.
170	Mailslot Allocations Failed
171	Missed Server List Requests is the number of requests to retrieve a list of browser servers that were received by this workstation, but could not be processed.
172	Virtual Bytes Peak
173	Virtual Bytes Peak is the maximum size, in bytes, of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. However, virtual space is finite, and the process might limit its ability to load libraries.
174	Virtual Bytes
175	Virtual Bytes is the current size, in bytes, of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and the process can limit its ability to load libraries.
177	Page Faults/sec is the rate at which page faults by the threads executing in this process are occurring.  A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This may not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.
178	Working Set Peak
179	Working Set Peak is the maximum size, in bytes, of the Working Set of this process at any point in time. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before they leave main memory.
180	Working Set
181	Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use.  When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory.
182	Page File Bytes Peak
183	Page File Bytes Peak is the maximum number of bytes this process has used in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files.  Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory.
184	Page File Bytes
185	Page File Bytes is the current number of bytes that this process has used in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory.
186	Private Bytes
187	Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes.
188	Announcements Total/sec
189	% Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
190	Enumerations Total/sec
191	% Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
193	% User Time is the percentage of elapsed time that this thread has spent executing code in user mode.  Applications, environment subsystems, and integral subsystems execute in user mode.  Code executing in user mode cannot damage the integrity of the Windows NT Executive, Kernel, and device drivers.  Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes.  These subsystem processes provide additional protection.  Therefore, some work done by Windows NT on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.
195	% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode.  When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.
197	Context Switches/sec is the rate of switches from one thread to another.  Thread switches can occur either inside of a single process or across processes.  A thread switch can be caused either by one thread asking another for information, or by a thread being preempted by another, higher priority thread becoming ready to run.  Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes.  These subsystem processes provide additional protection.  Therefore, some work done by Windows NT on behalf of an application  appear in other subsystem processes in addition to the privileged time in the application.  Switching to the subsystem process causes one Context Switch in the application thread.  Switching back causes another Context Switch in the subsystem thread.
198	Current Disk Queue Length
199	Current Disk Queue Length is the number of requests outstanding on the disk at the time the performance data is collected. It also includes requests in service at the time of the collection. This is a instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have multiple requests that are active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks. For good performance, this difference should average less than two.
200	% Disk Time
201	% Disk Time is the percentage of elapsed time that the selected disk drive was busy servicing read or write requests.
202	% Disk Read Time
203	% Disk Read Time is the percentage of elapsed time that the selected disk drive was busy servicing read requests.
204	% Disk Write Time
205	% Disk Write Time is the percentage of elapsed time that the selected disk drive was busy servicing write requests.
206	Avg. Disk sec/Transfer
207	Avg. Disk sec/Transfer is the time, in seconds, of the average disk transfer.
208	Avg. Disk sec/Read
209	Avg. Disk sec/Read is the average time, in seconds, of a read of data from the disk.
210	Avg. Disk sec/Write
211	Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk.
212	Disk Transfers/sec
213	Disk Transfers/sec is the rate of read and write operations on the disk.
214	Disk Reads/sec
215	Disk Reads/sec is the rate of read operations on the disk.
216	Disk Writes/sec
217	Disk Writes/sec is the rate of write operations on the disk.
218	Disk Bytes/sec
219	Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations.
220	Disk Read Bytes/sec
221	Disk Read Bytes/sec is the rate at which bytes are transferred from the disk during read operations.
222	Disk Write Bytes/sec
223	Disk Write Bytes/sec is rate at which bytes are transferred to the disk during write operations.
224	Avg. Disk Bytes/Transfer
225	Avg. Disk Bytes/Transfer is the average number of bytes transferred to or from the disk during write or read operations.
226	Avg. Disk Bytes/Read
227	Avg. Disk Bytes/Read is the average number of bytes transferred from the disk during read operations.
228	Avg. Disk Bytes/Write
229	Avg. Disk Bytes/Write is the average number of bytes transferred to the disk during write operations.
230	Process
231	The Process performance object consists of counters that monitor running application program and system processes.  All the threads in a process share the same address space and have access to the same data.
232	Thread
233	The Thread performance object consists of counters that measure aspects of thread behavior.  A thread is the basic object that executes instructions on a processor.  All running processes have at least one thread.
234	PhysicalDisk
235	The Physical Disk performance object consists of counters that monitor hard or fixed disk drive on a computer.  Disks are used to store file, program, and paging data and are read to retrieve these items, and written to record changes to them.  The values of physical disk counters are sums of the values of the logical disks (or partitions) into which they are divided.
236	LogicalDisk
237	The Logical Disk performance object consists of counters that monitor logical partitions of a hard or fixed disk drives.  Performance Monitor identifies logical disks by their a drive letter, such as C.
238	Processor
239	The Processor performance object consists of counters that measure aspects of processor activity The processor is the part of the computer that performs arithmetic and logical computations, initiates operations on peripherals, and runs the threads of processes.  A computer can have multiple processors.  The processor object represents each processor as an instance of the object.
240	% Total Processor Time
241	% Total Processor Time is the average percentage of time that all processors on the computer are executing non-idle threads.   This counter was designed as the primary indicator of processor activity on multiprocessor computers.  It is equal to the sum of Process: % Processor Time for all processors, divided by the number of processors.  It is calculated by summing the time that all processors spend executing the thread of the Idle process in each sample interval, subtracting that value from 100%, and dividing the difference by the number of processors on the computer.  (Each processor has an Idle thread which consumes cycles when no other threads are ready to run). For example, on a multiprocessor computer, a value of 50% means that all processors are busy for half of the sample interval, or that half of the processors are busy for all of the sample interval.  This counter displays the average percentage of busy time observed during the sample interval.  It is calculated by monitoring the time the service was inactive, and then subtracting that value from 100%. 
242	% Total User Time
243	% Total User Time is the average percentage of non-idle time all processors spend in user mode.  It is the sum of Processor: % User Time for all processors on the computer, divided by the number of processors.  System: % Total User Time and System: % Total Privileged Time sum to % Total Processor Time, but not always to 100%.  (User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems.  The alternative, privileged mode, is designed for operating system components and allows direct access to hardware and all memory.  The operating system switches application threads to privileged mode to access operating system services). This counter displays the average busy time as a percentage of the sample time. 
244	% Total Privileged Time
245	% Total Privileged Time is the average percentage of non-idle time all processors spend in privileged (kernel) mode.  It is the sum of Processor: % Privileged Time for all processors on the computer, divided by the number of processors.  System: % Total User Time and System: % Total Privileged Time sum to % Total Processor Time, but not always to 100%.  (Privileged mode is an processing mode designed for operating system components which allows direct access to hardware and all memory.  The operating system switches application threads to privileged mode to access operating system services.  The alternative, user mode, is a restricted processing mode designed for applications and environment subsystems). This counter displays the average busy time as a percentage of the sample time. 
246	Total Interrupts/sec
247	Total Interrupts/sec is the combined rate of hardware interrupts received and serviced by all processors on the computer It is the sum of Processor: Interrupts/sec for all processors, and divided by the number of processors, and is measured in numbers of interrupts.  It does not include DPCs, which are counted separately.  This value is an indirect indicator of the activity of devices that generate interrupts, such as the system timer, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices.  These devices normally interrupt the processor when they have completed a task or require attention.  Normal thread execution is suspended during interrupts.  Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval. 
248	Processes
249	Processes is the number of processes in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  Each process represents the running of a program.
250	Threads
251	Threads is the number of threads in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  A thread is the basic executable entity that can execute instructions in a processor.
252	Events
253	Events is the number of events in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  An event is used when two or more threads try to synchronize execution.
254	Semaphores
255	Semaphores is the number of semaphores in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  Threads use semaphores to obtain exclusive access to data structures that they share with other threads.
256	Mutexes
257	Mutexes counts the number of mutexes in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  Mutexes are used by threads to assure only one thread is executing a particular section of code.
258	Sections
259	Sections is the number of sections in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  A section is a portion of virtual memory created by a process for storing data. A process can share sections with other processes.
260	Objects
261	The Object performance object consists of counters that monitor  logical objects in the system, such as processes, threads, mutexes, and semaphores.  This information can be used to detect the unnecessary consumption of computer resources.  Each object requires memory to store basic information about the object.
262	Redirector
263	The Redirector performance object consists of counter that monitor network connections originating at the local computer.
264	Bytes Received/sec
265	Bytes Received/sec is the rate of bytes coming in to the Redirector from the network.  It includes all application data as well as network protocol information (such as packet headers).
266	Packets Received/sec
267	Packets Received/sec is the rate at which the Redirector is receiving packets (also called SMBs or Server Message Blocks).  Network transmissions are divided into packets.  The average number of bytes received in a packet can be obtained by dividing Bytes Received/sec by this counter.  Some packets received might not contain incoming data (for example an acknowledgment to a write made by the Redirector would count as an incoming packet).
268	Read Bytes Paging/sec
269	Read Bytes Paging/sec is the rate at which the Redirector is attempting to read bytes in response to page faults.  Page faults are caused by loading of modules (such as programs and libraries), by a miss in the Cache (see Read Bytes Cache/sec), or by files directly mapped into the address space of applications (a high-performance feature of Windows NT).
270	Read Bytes Non-Paging/sec
271	Read Bytes Non-Paging/sec are those bytes read by the Redirector in response to normal file requests by an application when they are redirected to come from another computer.  In addition to file requests, this counter includes other methods of reading across the network such as Named Pipes and Transactions.  This counter does not count network protocol information, just application data.
272	Read Bytes Cache/sec
273	Read Bytes Cache/sec is the rate at which applications are accessing the file system cache by using the Redirector.  Some of these data requests are satisfied by retrieving the data from the cache.  Requests that miss the Cache cause a page fault (see Read Bytes Paging/sec).
274	Read Bytes Network/sec
275	Read Bytes Network/sec is the rate at which applications are reading data across the network. This occurs when data sought in the file system cache is not found there and must be retrieved from the network.  Dividing this value by Bytes Received/sec indicates the proportion of application data traveling across the network. (see Bytes Received/sec).
276	Bytes Transmitted/sec
277	Bytes Transmitted/sec is the rate at which bytes are leaving the Redirector to the network.  It includes all application data as well as network protocol information (such as packet headers and the like).
278	Packets Transmitted/sec
279	Packets Transmitted/sec is the rate at which the Redirector is sending packets (also called SMBs or Server Message Blocks).  Network transmissions are divided into packets.  The average number of bytes transmitted in a packet can be obtained by dividing Bytes Transmitted/sec by this counter.
280	Write Bytes Paging/sec
281	Write Bytes Paging/sec is the rate at which the Redirector is attempting to write bytes changed in the pages being used by applications.  The program data changed by modules (such as programs and libraries) that were loaded over the network are 'paged out' when no longer needed.  Other output pages come from the file system cache (see Write Bytes Cache/sec).
282	Write Bytes Non-Paging/sec
283	Write Bytes Non-Paging/sec is the rate at which bytes are written by the Redirector in response to normal file outputs by an application when they are redirected to another computer.  In addition to file requests, this count includes other methods of writing across the network, such as Named Pipes and Transactions.  This counter does not count network protocol information, just application data.
284	Write Bytes Cache/sec
285	Write Bytes Cache/sec is the rate at which applications on your computer are writing to the file system cache by using the Redirector.  The data might not leave your computer immediately; it can be retained in the cache for further modification before being written to the network.  This saves network traffic.  Each write of a byte into the cache is counted here.
286	Write Bytes Network/sec
287	Write Bytes Network/sec is the rate at which applications are writing data across the network. This occurs when the file system cache is bypassed, such as for Named Pipes or Transactions, or when the cache writes the bytes to disk to make room for other data.  Dividing this counter by Bytes Transmitted/sec will indicate the proportion of application data being to the network (see Transmitted Bytes/sec).
288	Read Operations/sec
289	File Read Operations/sec is the rate at which applications are asking the Redirector for data. Each call to a file system or similar Application Program Interface (API) call counts as one operation.
290	Read Operations Random/sec
291	Read Operations Random/sec counts the rate at which, on a file-by-file basis, reads are made that are not sequential.  If a read is made using a particular file handle, and then is followed by another read that is not immediately the contiguous next byte, this counter is incremented by one.
292	Read Packets/sec
293	Read Packets/sec is the rate at which read packets are being placed on the network.  Each time a single packet is sent with a request to read data remotely, this counter is incremented by one.
294	Reads Large/sec
295	Reads Large/sec is the rate at which reads over 2 times the server's negotiated buffer size are made by applications.  Too many of these could place a strain on server resources.  This counter is incremented once for each read. It does not count packets.
296	Read Packets Small/sec
297	Read Packets Small/sec is the rate at which reads less than one-fourth of the server's negotiated buffer size are made by applications.  Too many of these could indicate a waste of buffers on the server.  This counter is incremented once for each read. It does not count packets.
298	Write Operations/sec
299	File Write Operations/sec is the rate at which applications are sending data to the Redirector. Each call to a file system or similar Application Program Interface (API) call counts as one operation.
300	Write Operations Random/sec
301	Write Operations Random/sec is the rate at which, on a file-by-file basis, writes are made that are not sequential.  If a write is made using a particular file handle, and then is followed by another write that is not immediately the next contiguous byte, this counter is incremented by one.
302	Write Packets/sec
303	Write Packets/sec is the rate at which writes are being sent to the network.  Each time a single packet is sent with a request to write remote data, this counter is incremented by one.
304	Writes Large/sec
305	Writes Large/sec is the rate at which writes are made by applications that are over 2 times the server's negotiated buffer size.  Too many of these could place a strain on server resources.  This counter is incremented once for each write: it counts writes, not packets.
306	Write Packets Small/sec
307	Write Packets Small/sec is the rate at which writes are made by applications that are less than one-fourth of the server's negotiated buffer size.  Too many of these could indicate a waste of buffers on the server.  This counter is incremented once for each write: it counts writes, not packets.
308	Reads Denied/sec
309	Reads Denied/sec is the rate at which the server is unable to accommodate requests for Raw Reads.  When a read is much larger than the server's negotiated buffer size, the Redirector requests a Raw Read which, if granted, would permit the transfer of the data without lots of protocol overhead on each packet.  To accomplish this the server must lock out other requests, so the request is denied if the server is really busy.
310	Writes Denied/sec
311	Writes Denied/sec is the rate at which the server is unable to accommodate requests for Raw Writes.  When a write is much larger than the server's negotiated buffer size, the Redirector requests a Raw Write which, if granted, would permit the transfer of the data without lots of protocol overhead on each packet.  To accomplish this the server must lock out other requests, so the request is denied if the server is really busy.
312	Network Errors/sec
313	Network Errors/sec is the rate at which serious unexpected errors are occurring. Such errors generally indicate that the Redirector and one or more Servers are having serious communication difficulties. For example an SMB (Server Manager Block) protocol error is a Network Error. An entry is written to the System Event Log and provide details.
314	Server Sessions
315	Server Sessions counts the total number of security objects the Redirector has managed.  For example, a logon to a server followed by a network access to the same server will establish one connection, but two sessions.
316	Server Reconnects
317	Server Reconnects counts the number of times your Redirector has had to reconnect to a server in order to complete a new active request.  You can be disconnected by the Server if you remain inactive for too long.  Locally even if all your remote files are closed, the Redirector will keep your connections intact for (nominally) ten minutes.  Such inactive connections are called Dormant Connections.  Reconnecting is expensive in time.
318	Connects Core
319	Connects Core counts the number of connections you have to servers running the original MS-Net SMB protocol, including MS-Net itself and Xenix and VAX's.
320	Connects Lan Manager 2.0
321	Connects LAN Manager 2.0 counts connections to LAN Manager 2.0 servers, including LMX servers.
322	Connects Lan Manager 2.1
323	Connects LAN Manager 2.1 counts connections to LAN Manager 2.1 servers, including LMX servers.
324	Connects Windows NT
325	Connects Windows NT counts the connections to Windows 2000 or earlier computers.
326	Server Disconnects
327	Server Disconnects counts the number of times a Server has disconnected your Redirector.  See also Server Reconnects.
328	Server Sessions Hung
329	Server Sessions Hung counts the number of active sessions that are timed out and unable to proceed due to a lack of response from the remote server.
330	Server
331	The Server performance object consists of counters that measure communication between the  local computer and the network.
333	The number of bytes the server has received from the network.  Indicates how busy the server is.
335	The number of bytes the server has sent on the network.  Indicates how busy the server is.
336	Thread Wait Reason
337	Thread Wait Reason is only applicable when the thread is in the Wait state (see Thread State).  It is 0 or 7 when the thread is waiting for the Executive, 1 or 8 for a Free Page, 2 or 9 for a Page In, 3 or 10 for a Pool Allocation, 4 or 11 for an Execution Delay, 5 or 12 for a Suspended condition, 6 or 13 for a User Request, 14 for an Event Pair High, 15 for an Event Pair Low, 16 for an LPC Receive, 17 for an LPC Reply, 18 for Virtual Memory, 19 for a Page Out; 20 and higher are not assigned at the time of this writing.  Event Pairs are used to communicate with protected subsystems (see Context Switches).
339	% DPC Time is the percentage of time that the processor spent receiving and servicing deferred procedure calls (DPCs) during the sample interval. DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a component of % Privileged Time because DPCs are executed in privileged mode. They are counted separately and are not a component of the interrupt counters. This counter displays the average busy time as a percentage of the sample time. 
340	Sessions Timed Out
341	The number of sessions that have been closed due to their idle time exceeding the AutoDisconnect parameter for the server.  Shows whether the AutoDisconnect setting is helping to conserve resources.
342	Sessions Errored Out
343	The number of sessions that have been closed due to unexpected error conditions or sessions that have reached the autodisconnect timeout and have been disconnected normally.
344	Sessions Logged Off
345	The number of sessions that have terminated normally.  Useful in interpreting the Sessions Times Out and Sessions Errored Out statistics--allows percentage calculations.
346	Sessions Forced Off
347	The number of sessions that have been forced to logoff.  Can indicate how many sessions were forced to logoff due to logon time constraints.
348	Errors Logon
349	The number of failed logon attempts to the server.  Can indicate whether password guessing programs are being used to crack the security on the server.
350	Errors Access Permissions
351	The number of times opens on behalf of clients have failed with STATUS_ACCESS_DENIED.  Can indicate whether somebody is randomly attempting to access files in hopes of getting at something that was not properly protected.
352	Errors Granted Access
353	The number of times accesses to files opened successfully were denied.  Can indicate attempts to access files without proper access authorization.
354	Errors System
355	The number of times an internal Server Error was detected.  Unexpected errors usually indicate a problem with the Server.
356	Blocking Requests Rejected
357	The number of times the server has rejected blocking SMBs due to insufficient count of free work items.  Indicates whether the MaxWorkItem or MinFreeWorkItems server parameters might need to be adjusted.
358	Work Item Shortages
359	The number of times STATUS_DATA_NOT_ACCEPTED was returned at receive indication time.  This occurs when no work item is available or can be allocated to service the incoming request.  Indicates whether the InitWorkItems or MaxWorkItems parameters might need to be adjusted.
360	Files Opened Total
361	The number of successful open attempts performed by the server of behalf of clients.  Useful in determining the amount of file I/O, determining overhead for path-based operations, and for determining the effectiveness of open locks.
362	Files Open
363	The number of files currently opened in the server.  Indicates current server activity.
365	The number of sessions currently active in the server.  Indicates current server activity.
366	File Directory Searches
367	The number of searches for files currently active in the server.  Indicates current server activity.
369	The number of bytes of non-pageable computer memory the server is using.  This value is useful for determining the values of the MaxNonpagedMemoryUsage value entry in the Windows NT Registry.
370	Pool Nonpaged Failures
371	The number of times allocations from nonpaged pool have failed.  Indicates that the computer's physical memory is too small.
372	Pool Nonpaged Peak
373	The maximum number of bytes of nonpaged pool the server has had in use at any one point.  Indicates how much physical memory the computer should have.
375	The number of bytes of pageable computer memory the server is currently using.  Can help in determining good values for the MaxPagedMemoryUsage parameter.
376	Pool Paged Failures
377	The number of times allocations from paged pool have failed.  Indicates that the computer's physical memory or paging file are too small.
378	Pool Paged Peak
379	The maximum number of bytes of paged pool the server has had allocated.  Indicates the proper sizes of the Page File(s) and physical memory.
381	Server Announce Allocations Failed/sec is the rate at which server (or domain) announcements have failed due to lack of memory.
383	Mailslot Allocations Failed is the number of times the datagram receiver has failed to allocate a buffer to hold a user mailslot write.
385	Mailslot Receives Failed indicates the number of mailslot messages that could not be received due to transport failures.
387	Mailslot Writes Failed is the total number of mailslot messages that have been successfully received, but that could not be written to the mailslot.
388	Bytes Total/sec
389	Bytes Total/sec is the rate the Redirector is processing data bytes.  This includes all application and file data in addition to protocol information such as packet headers.
391	File Data Operations/sec is the rate at which the Redirector is processing data operations. One operation should include many bytes, since each operation has overhead. The efficiency of this path can be determined by dividing the Bytes/sec by this counter to obtain the average number of bytes transferred per operation.
392	Current Commands
393	Current Commands counts the number of requests to the Redirector that are currently queued for service.  If this number is much larger than the number of network adapter cards installed in the computer, then the network(s) and/or the server(s) being accessed are seriously bottlenecked.
395	The number of bytes the server has sent to and received from the network.  This value provides an overall indication of how busy the server is.
397	% Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. suspends normal thread execution during interrupts. This counter displays the average busy time as a percentage of the sample time.
398	NWLink NetBIOS
399	The NWLink NetBIOS performance object consists of counters that monitor IPX transport rates and connections. 
400	Packets/sec
401	Packets/sec is the rate the Redirector is processing data packets.  One packet includes (hopefully) many bytes.  We say hopefully here because each packet has protocol overhead.  You can determine the efficiency of this path by dividing the Bytes/sec by this counter to determine the average number of bytes transferred/packet.  You can also divide this counter by Operations/sec to determine the average number of packets per operation, another measure of efficiency.
404	Context Blocks Queued/sec
405	Context Blocks Queued per second is the rate at which work context blocks had to be placed on the server's FSP queue to await server action.
406	File Data Operations/sec
407	File Data Operations/ sec is the combined rate of read and write operations on all logical disks on the computer.  This is the inverse of System: File Control Operations/sec.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval. 
408	% Free Space
409	% Free Space is the percentage of total usable space on the selected logical disk drive that was free.
410	Free Megabytes
411	Free Megabytes displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.
412	Connections Open
413	Connections Open is the number of connections currently open for this protocol.  This counter shows the current count only and does not accumulate over time.
414	Connections No Retries
415	Connections No Retries is the total count of connections that were successfully made on the first try.  This number is an accumulator and shows a running total.
416	Connections With Retries
417	Connections With Retries is the total count of connections that were made after retrying the attempt.  A retry occurs when the first connection attempt failed.  This number is an accumulator and shows a running total.
418	Disconnects Local
419	Disconnects Local is the number of session disconnections that were initiated by the local computer.  This number is an accumulator and shows a running total.
420	Disconnects Remote
421	Disconnects Remote is the number of session disconnections that were initiated by the remote computer.  This number is an accumulator and shows a running total.
422	Failures Link
423	Failures Link is the number of connections that were dropped due to a link failure.  This number is an accumulator and shows a running total.
424	Failures Adapter
425	Failures Adapter is the number of connections that were dropped due to an adapter failure.  This number is an accumulator and shows a running total.
426	Connection Session Timeouts
427	Connection Session Timeouts is the number of connections that were dropped due to a session timeout.  This number is an accumulator and shows a running total.
428	Connections Canceled
429	Connections Canceled is the number of connections that were canceled.  This number is an accumulator and shows a running total.
430	Failures Resource Remote
431	Failures Resource Remote is the number of connections that failed because of resource problems or shortages on the remote computer.  This number is an accumulator and shows a running total.
432	Failures Resource Local
433	Failures Resource Local is the number of connections that failed because of resource problems or shortages on the local computer.  This number is an accumulator and shows a running total.
434	Failures Not Found
435	Failures Not Found is the number of connection attempts that failed because the remote computer could not be found.  This number is an accumulator and shows a running total.
436	Failures No Listen
437	Failures No Listen is the number of connections that were rejected because the remote computer was not listening for connection requests.
438	Datagrams/sec
439	Datagrams/sec is the rate at which datagrams are processed by the computer.  This counter displays the sum of datagrams sent and datagrams received.  A datagram is a connectionless packet whose delivery to a remote is not guaranteed.
440	Datagram Bytes/sec
441	Datagram Bytes/sec is the rate at which datagram bytes are processed by the computer.  This counter is the sum of datagram bytes that are sent as well as received.  A datagram is a connectionless packet whose delivery to a remote is not guaranteed.
442	Datagrams Sent/sec
443	Datagrams Sent/sec is the rate at which datagrams are sent from the computer.  A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.
444	Datagram Bytes Sent/sec
445	Datagram Bytes Sent/sec is the rate at which datagram bytes are sent from the computer.  A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.
446	Datagrams Received/sec
447	Datagrams Received/sec is the rate at which datagrams are received by the computer.  A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.
448	Datagram Bytes Received/sec
449	Datagram Bytes Received/sec is the rate at which datagram bytes are received by the computer.  A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.
451	Packets/sec is the rate at which packets are processed by the computer.  This count is the sum of Packets Sent and Packets Received per second.  This counter includes all packets processed: control as well as data packets.
452	Packets Sent/sec
453	Packets Sent/sec is the rate at which packets are sent by the computer.  This counter counts all packets sent by the computer, i.e. control as well as data packets.
455	Packets Received/sec is the rate at which packets are received by the computer.  This counter counts all packets processed: control as well as data packets.
456	Frames/sec
457	Frames/sec is the rate at which data frames (or packets) are processed by the computer.  This counter is the sum of data frames sent and data frames received.  This counter only counts those frames (packets) that carry data.
458	Frame Bytes/sec
459	Frame Bytes/sec is the rate at which data bytes are processed by the computer.  This counter is the sum of data frame bytes sent and received.  This counter only counts the byte in frames (packets) that carry data.
460	Frames Sent/sec
461	Frames Sent/sec is the rate at which data frames are sent by the computer.  This counter only counts the frames (packets) that carry data.
462	Frame Bytes Sent/sec
463	Frame Bytes Sent/sec is the rate at which data bytes are sent by the computer.  This counter only counts the bytes in frames (packets) that carry data.
464	Frames Received/sec
465	Frames Received/sec is the rate at which data frames are received by the computer.  This counter only counts the frames (packets) that carry data.
466	Frame Bytes Received/sec
467	Frame Bytes Received/sec is the rate at which data bytes are received by the computer.  This counter only counts the frames (packets) that carry data.
468	Frames Re-Sent/sec
469	Frames Re-Sent/sec is the rate at which data frames (packets) are re-sent by the computer.  This counter only counts the frames or packets that carry data.
470	Frame Bytes Re-Sent/sec
471	Frame Bytes Re-Sent/sec is the rate at which data bytes are re-sent by the computer.  This counter only counts the bytes in frames that carry data.
472	Frames Rejected/sec
473	Frames Rejected/sec is the rate at which data frames are rejected.  This counter only counts the frames (packets) that carry data.
474	Frame Bytes Rejected/sec
475	Frame Bytes Rejected/sec is the rate at which data bytes are rejected.  This counter only counts the bytes in data frames (packets) that carry data.
476	Expirations Response
477	Expirations Response is the count of T1 timer expirations.
478	Expirations Ack
479	Expirations Ack is the count of T2 timer expirations.
480	Window Send Maximum 
481	Window Send Maximum is the maximum number of bytes of data that will be sent before waiting for an acknowledgment from the remote computer.
482	Window Send Average
483	Window Send Average is the running average number of data bytes that were sent before waiting for an acknowledgment from the remote computer.
484	Piggyback Ack Queued/sec
485	Piggyback Ack Queued/sec is the rate at which piggybacked acknowledgments are queued. Piggyback acknowledgments are acknowledgments to received packets that are to be included in the next outgoing packet to the remote computer.
486	Piggyback Ack Timeouts
487	Piggyback Ack Timeouts is the number of times that a piggyback acknowledgment could not be sent because there was no outgoing packet to the remote on which to piggyback.  A piggyback ack is an acknowledgment to a received packet that is sent along in an outgoing data packet to the remote computer.  If no outgoing packet is sent within the timeout period, then an ack packet is sent and this counter is incremented.
488	NWLink IPX
489	The NWLink IPX performance object consists of counters that measure datagram transmission to and from computers using the IPX protocol.
490	NWLink SPX
491	The NWLink SPX performance object consist of counters that measure data transmission and session connections for computers using the SPX protocol.
492	NetBEUI
493	The NetBEUI performance object consists of counters that measure data transmission for network activity which conforms to the NetBIOS End User Interface standard.
494	NetBEUI Resource
495	The NetBEUI Resource performance object consists of counters that track the use of buffers by the NetBEUI protocol.
496	Used Maximum
497	Used Maximum is the maximum number of NetBEUI resources (buffers) in use at any point in time.  This value is useful in sizing the maximum resources provided.  The number in parentheses following the resource name is used to identify the resource in Event Log messages.
498	Used Average
499	Used Average is the current number of resources (buffers) in use at this time.  The number in parentheses following the resource name is used to identify the resource in Event Log messages.
500	Times Exhausted
501	Times Exhausted is the number of times all the resources (buffers) were in use.  The number in parentheses following the resource name is used to identify the resource in Event Log messages.
502	NBT Connection
503	The NBT Connection performance object consists of counters that measure the rates at which bytes are sent and received over the NBT connection between the local computer and a remote computer.  The connection is identified by the name of the remote computer.
505	Bytes Received/sec is the rate at which bytes are received by the local computer over an NBT connection to some remote computer.  All the bytes received by the local computer over the particular NBT connection are counted.
506	Bytes Sent/sec
507	Bytes Sent/sec is the rate at which bytes are sent by the local computer over an NBT connection to some remote computer.  All the bytes sent by the local computer over the particular NBT connection are counted.
508	Total Bytes/sec
509	Bytes Total/sec is the rate at which bytes are sent or received by the local computer over an NBT connection to some remote computer.  All the bytes sent or received by the local computer over the particular NBT connection are counted.
510	Network Interface
511	The Network Interface performance object consists of counters that measure the rates at which bytes and packets are sent and received over a TCP/IP network connection.  It includes counters that monitor connection errors.
512	Bytes/sec
513	Bytes Total/sec is the rate at which bytes are sent and received over each network adapter, including framing characters. Network Interface\\Bytes Received/sec is a sum of Network Interface\\Bytes Received/sec and Network Interface\\Bytes Sent/sec.
515	Packets/sec is the rate at which packets are sent and received on the network interface.
517	Packets Received/sec is the rate at which packets are received on the network interface.
519	Packets Sent/sec is the rate at which packets are sent on the network interface.
520	Current Bandwidth
521	Current Bandwidth is an estimate of the current bandwidth of the network interface in bits per second (BPS).  For interfaces that do not vary in bandwidth or for those where no accurate estimation can be made, this value is the nominal bandwidth.
523	Bytes Received/sec is the rate at which bytes are received over each network adapter, including framing characters. Network Interface\\Bytes Received/sec is a subset of Network Interface\\Bytes Total/sec.
524	Packets Received Unicast/sec
525	Packets Received Unicast/sec is the rate at which (subnet) unicast packets are delivered to a higher-layer protocol.
526	Packets Received Non-Unicast/sec
527	Packets Received Non-Unicast/sec is the rate at which non-unicast (subnet broadcast or subnet multicast) packets are delivered to a higher-layer protocol.
528	Packets Received Discarded
529	Packets Received Discarded is the number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their delivery to a higher-layer protocol.  One possible reason for discarding packets could be to free up buffer space.
530	Packets Received Errors
531	Packets Received Errors is the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
532	Packets Received Unknown
533	Packets Received Unknown is the number of packets received through the interface that were discarded because of an unknown or unsupported protocol.
535	Bytes Sent/sec is the rate at which bytes are sent over each each network adapter, including framing characters. Network Interface\\Bytes Sent/sec is a subset of Network Interface\\Bytes Total/sec.
536	Packets Sent Unicast/sec
537	Packets Sent Unicast/sec is the rate at which packets are requested to be transmitted to subnet-unicast addresses by higher-level protocols.  The rate includes the packets that were discarded or not sent.
538	Packets Sent Non-Unicast/sec
539	Packets Sent Non-Unicast/sec is the rate at which packets are requested to be transmitted to non-unicast (subnet broadcast or subnet multicast) addresses by higher-level protocols.  The rate includes the packets that were discarded or not sent.
540	Packets Outbound Discarded
541	Packets Outbound Discarded is the number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent transmission. One possible reason for discarding packets could be to free up buffer space.
542	Packets Outbound Errors
543	Packets Outbound Errors is the number of outbound packets that could not be transmitted because of errors.
544	Output Queue Length
545	Output Queue Length is the length of the output packet queue (in packets). If this is longer than two, there are delays and the bottleneck should be found and eliminated, if possible. Since the requests are queued by the Network Driver Interface Specification (NDIS) in this implementation, this will always be 0.
546	IP
547	The IP performance object consists of counters that measure the rates at which IP datagrams are sent and received by using IP protocols.  It also includes counters that monitor IP protocol errors.
549	Datagrams/sec is the rate, in incidents per second, at which IP datagrams were received from or sent to the interfaces, including those in error. Forwarded datagrams are not included in this rate.
551	Datagrams Received/sec is the rate, in incidents per second, at which IP datagrams are received from the interfaces, including those in error. Datagrams Received/sec is a subset of Datagrams/sec.
552	Datagrams Received Header Errors
553	Datagrams Received Header Errors is the number of input datagrams that were discarded due to errors in the IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
554	Datagrams Received Address Errors
555	Datagrams Received Address Errors is the number of input datagrams that were discarded because the IP address in their IP header destination field was not valid for the computer. This count includes invalid addresses (for example, 0.0.  0.0) and addresses of unsupported Classes (for example, Class E). For entities that are not IP gateways and do not forward datagrams, this counter includes datagrams that were discarded because the destination address was not a local address.
556	Datagrams Forwarded/sec
557	Datagrams Forwarded/sec is the rate, in incidents per second, at which attemps were made to find routes to forward input datagrams their final destination, because the local server was not the final IP destination. In servers that do not act as IP Gateways, this rate includes only packets that were source-routed via this entity, where the source-route option processing was successful.
558	Datagrams Received Unknown Protocol
559	Datagrams Received Unknown Protocol is the number of locally-addressed datagrams that were successfully received but were discarded because of an unknown or unsupported protocol.
560	Datagrams Received Discarded
561	Datagrams Received Discarded is the number of input IP datagrams that were discarded even though problems prevented their continued processing (for example, lack of buffer space). This counter does not include any datagrams discarded while awaiting re-assembly.
562	Datagrams Received Delivered/sec
563	Datagrams Received Delivered/sec is the rate, in incidents per second, at which input datagrams were successfully delivered to IP user-protocols, including Internet Control Message Protocol (ICMP).
565	Datagrams Sent/sec is the rate, in incidents per second, at which IP datagrams were supplied for transmission by local IP user-protocols (including ICMP). This counter does not include any datagrams counted in Datagrams Forwarded/sec. Datagrams Sent/sec is a subset of Datagrams/sec.
566	Datagrams Outbound Discarded
567	Datagrams Outbound Discarded is the number of output IP datagrams that were discarded even though no problems were encountered to prevent their transmission to their destination (for example, lack of buffer space). This counter includes datagrams counted in Datagrams Forwarded/sec that meet this criterion.
568	Datagrams Outbound No Route
569	Datagrams Outbound No Route is the number of IP datagrams that were discarded because no route could be found to transmit them to their destination.  This counter includes any packets counted in Datagrams Forwarded/sec that meet this `no route' criterion.
570	Fragments Received/sec
571	Fragments Received/sec is the rate, in incidents per second, at which IP fragments that need to be reassembled at this entity are received.
572	Fragments Re-assembled/sec
573	Fragments Re-assembled/sec is the rate, in incidents per second, at which IP fragments were successfully reassembled.
574	Fragment Re-assembly Failures
575	Fragment Re-assembly Failures is the number of failures detected by the IP reassembly algorithm, such as time outs, errors, etc.  This is not necessarily a count of discarded IP fragments since some algorithms (notably RFC 815) lose track of the number of fragments by combining them as they are received.
576	Fragmented Datagrams/sec
577	Fragmented Datagrams/sec is the rate, in incidents per second, at which datagrams are successfully fragmented.
578	Fragmentation Failures
579	Fragmentation Failures is the number of IP datagrams that were discarded because they needed to be fragmented at but could not be (for example, because the `Don't Fragment' flag was set).
580	Fragments Created/sec
581	Fragments Created/sec is the rate, in incidents per second, at which IP datagram fragments were generated as a result of fragmentation.
582	ICMP
583	The ICMP performance object consists of counters that measure the rates at which messages are sent and received by using ICMP protocols.  It also includes counters that monitor ICMP protocol errors.
584	Messages/sec
585	Messages/sec is the total rate, in incidents per second, at which ICMP messages were sent and received by the entity. The rate includes messages received or sent in error.
586	Messages Received/sec
587	Messages Received/sec is the rate, in incidents per second at which ICMP messages were received. The rate includes messages received in error.
588	Messages Received Errors
589	Messages Received Errors is the number of ICMP messages that the entity received but had errors, such as bad ICMP checksums, bad length, etc.
590	Received Dest. Unreachable
591	Received Destination Unreachable is the number of ICMP Destination Unreachable messages received.
592	Received Time Exceeded
593	Received Time Exceeded is the number of ICMP Time Exceeded messages received.
594	Received Parameter Problem
595	Received Parameter Problem is the number of ICMP Parameter Problem messages received.
596	Received Source Quench
597	Received Source Quench is the number of ICMP Source Quench messages received.
598	Received Redirect/sec
599	Received Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were received.
600	Received Echo/sec
601	Received Echo/sec is the rate, in incidents per second, at which ICMP Echo messages were received.
602	Received Echo Reply/sec
603	Received Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were received.
604	Received Timestamp/sec
605	Received Timestamp/sec is the rate, in incidents per second at which ICMP Timestamp Request messages were received.
606	Received Timestamp Reply/sec
607	Received Timestamp Reply/sec is the rate of ICMP Timestamp Reply messages received.
608	Received Address Mask
609	Received Address Mask is the number of ICMP Address Mask Request messages received.
610	Received Address Mask Reply
611	Received Address Mask Reply is the number of ICMP Address Mask Reply messages received.
612	Messages Sent/sec
613	Messages Sent/sec is the rate, in incidents per second, at which the server attempted to send. The rate includes those messages sent in error.
614	Messages Outbound Errors
615	Messages Outbound Errors is the number of ICMP messages that were not send due to problems within ICMP, such as lack of buffers.  This value does not include errors discovered outside the ICMP layer, such as those recording the failure of IP to route the resultant datagram.  In some implementations, none of the error types are included in the value of this counter.
616	Sent Destination Unreachable
617	Sent Destination Unreachable is the number of ICMP Destination Unreachable messages sent.
618	Sent Time Exceeded
619	Sent Time Exceeded is the number of ICMP Time Exceeded messages sent.
620	Sent Parameter Problem
621	Sent Parameter Problem is the number of ICMP Parameter Problem messages sent.
622	Sent Source Quench
623	Sent Source Quench is the number of ICMP Source Quench messages sent.
624	Sent Redirect/sec
625	Sent Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were sent.
626	Sent Echo/sec
627	Sent Echo/sec is the rate of ICMP Echo messages sent.
628	Sent Echo Reply/sec
629	Sent Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were sent.
630	Sent Timestamp/sec
631	Sent Timestamp/sec is the rate, in incidents per second, at which ICMP Timestamp Request messages were sent.
632	Sent Timestamp Reply/sec
633	Sent Timestamp Reply/sec is the rate, in incidents per second,  at which ICMP Timestamp Reply messages were sent.
634	Sent Address Mask
635	Sent Address Mask is the number of ICMP Address Mask Request messages sent.
636	Sent Address Mask Reply
637	Sent Address Mask Reply is the number of ICMP Address Mask Reply messages sent.
638	TCP
639	The TCP performance object consists of counters that measure the rates at which TCP Segments are sent and received by using the TCP protocol.  It includes counters that monitor the number of TCP connections in each TCP connection state.
640	Segments/sec
641	Segments/sec is the rate at which TCP segments are sent or received using the TCP protocol.
642	Connections Established
643	Connections Established is the number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
644	Connections Active
645	Connections Active is the number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
646	Connections Passive
647	Connections Passive is the number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
648	Connection Failures
649	Connection Failures is the number of times TCP connections have made a direct transition to the CLOSED state from the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
650	Connections Reset
651	Connections Reset is the number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
652	Segments Received/sec
653	Segments Received/sec is the rate at which segments are received, including those received in error.  This count includes segments received on currently established connections.
654	Segments Sent/sec
655	Segments Sent/sec is the rate at which segments are sent, including those on current connections, but excluding those containing only retransmitted bytes.
656	Segments Retransmitted/sec
657	Segments Retransmitted/sec is the rate at which segments are retransmitted, that is, segments transmitted containing one or more previously transmitted bytes.
658	UDP
659	The UDP performance object consists of counters that measure the rates at which UDP datagrams are sent and received by using the UDP protocol.  It includes counters that monitor UDP protocol errors.
660	% Total DPC Time
661	Datagrams/sec is the rate at which UDP datagrams are sent or received by the entity.
662	% Total Interrupt Time
663	Datagrams Received/sec is the rate at which UDP datagrams are delivered to UDP users.
664	Datagrams No Port/sec
665	Datagrams No Port/sec is the rate of received UDP datagrams for which there was no application at the destination port.
666	Datagrams Received Errors
667	Datagrams Received Errors is the number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
669	Datagrams Sent/sec is the rate at which UDP datagrams are sent from the entity.
670	Disk Storage Unit
671	Disk Storage device statistics from the foreign computer
672	Allocation Failures
673	The number of allocation failures reported by the disk storage device
674	System Up Time
675	System Up Time is the elapsed time (in seconds) that the computer has been running since it was last started.  This counter displays the difference between the start time and the current time. 
676	System Handle Count
677	The current number of system handles in use.
678	Free System Page Table Entries
679	Free System Page Table Entries is the number of page table entries not currently in used by the system.  This counter displays the last observed value only; it is not an average. 
680	Thread Count
681	The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.
682	Priority Base
683	The current base priority of this process. Threads within a process can raise and lower their own base priority relative to the process' base priority.
684	Elapsed Time
685	The total elapsed time, in seconds, that this process has been running.
686	Alignment Fixups/sec
687	Alignment Fixups/sec is the rate, in incidents per seconds, at alignment faults were fixed by the system.
688	Exception Dispatches/sec
689	Exception Dispatches/sec is the rate, in incidents per second, at which exceptions were dispatched by the system.
690	Floating Emulations/sec
691	Floating Emulations/sec is the rate of floating emulations performed by the system.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
692	Logon/sec
693	Logon/sec is the rate of all server logons.
694	Priority Current
695	The current dynamic priority of this thread.  The system can raise the thread's dynamic priority above the base priority if the thread is handling user input, or lower it towards the base priority if the thread becomes compute bound.
696	% DPC Time
697	The current base priority of this thread.  The system can raise the thread's dynamic priority above the base priority if the thread is handling user input, or lower it towards the base priority if the thread becomes compute bound.
698	% Interrupt Time
699	The total elapsed time (in seconds) this thread has been running.
700	Paging File
701	The Paging File performance object consists of counters that monitor the paging file(s) on the computer.  The paging file is a reserved space on disk that backs up committed physical memory on the computer.
702	% Usage
703	The amount of the Page File instance in use in percent.  See also Process\\Page File Bytes.
704	% Usage Peak
705	The peak usage of the Page File instance in percent.  See also Process\\Page File Bytes Peak.
706	Start Address
707	Starting virtual address for this thread.
708	User PC
709	Current User Program Counter for this thread.
710	Mapped Space No Access
711	Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
712	Mapped Space Read Only
713	Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.
714	Mapped Space Read/Write
715	Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Read/Write protection allows a process to read, modify and write to these pages.
716	Mapped Space Write Copy
717	Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have write access to this shared memory, a copy of that memory is made.
718	Mapped Space Executable
719	Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.
720	Mapped Space Exec Read Only
721	Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Execute/Read Only memory is memory that can be executed as well as read.
722	Mapped Space Exec Read/Write
723	Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Execute/Read/Write memory is memory that can be executed by programs as well as read and modified.
724	Mapped Space Exec Write Copy
725	Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.
726	Reserved Space No Access
727	Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
728	Reserved Space Read Only
729	Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.
730	Reserved Space Read/Write
731	Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Read/Write protection allows a process to read, modify and write to these pages.
732	Reserved Space Write Copy
733	Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made.
734	Reserved Space Executable
735	Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.
736	Reserved Space Exec Read Only
737	Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Execute/Read Only memory is memory that can be executed as well as read.
738	Reserved Space Exec Read/Write
739	Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Execute/Read/Write memory is memory that can be executed by programs as well as read and modified.
740	Image
741	The Image performance object consists of counters that monitor the virtual address usage of images executed by processes on the computer.
742	Reserved Space Exec Write Copy
743	Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.
744	Unassigned Space No Access
745	Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
746	Unassigned Space Read Only
747	Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.
748	Unassigned Space Read/Write
749	Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Read/Write protection allows a process to read, modify and write to these pages.
750	Unassigned Space Write Copy
751	Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.
752	Unassigned Space Executable
753	Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.
754	Unassigned Space Exec Read Only
755	Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Execute/Read Only memory is memory that can be executed as well as read.
756	Unassigned Space Exec Read/Write
757	Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Execute/Read/Write memory is memory that can be executed by programs as well as read and written.
758	Unassigned Space Exec Write Copy
759	Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.
760	Image Space No Access
761	Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
762	Image Space Read Only
763	Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.
764	Image Space Read/Write
765	Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Read/Write protection allows a process to read, modify and write to these pages.
766	Image Space Write Copy
767	Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.
768	Image Space Executable
769	Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.
770	Image Space Exec Read Only
771	Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Execute/Read-Only memory is memory that can be executed as well as read.
772	Image Space Exec Read/Write
773	Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Execute/Read/Write memory is memory that can be executed by programs as well as read and written and modified.
774	Image Space Exec Write Copy
775	Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.
776	Bytes Image Reserved
777	Bytes Image Reserved is the sum of all virtual memory reserved by images within this process.
778	Bytes Image Free
779	Bytes Image Free is the amount of virtual address space that is not in use or reserved by images within this process.
780	Bytes Reserved
781	Bytes Reserved is the total amount of virtual memory reserved for future use by this process.
782	Bytes Free
783	Bytes Free is the total unused virtual address space of this process.
784	ID Process
785	ID Process is the unique identifier of this process. ID Process numbers are reused, so they only identify a process for the lifetime of that process.
786	Process Address Space
787	The Process Address Space performance object consists of counters that monitor memory allocation and use  for a selected process.
788	No Access
789	Image Space is the virtual address space in use by the selected image with this protection.  No Access protection prevents a process from writing or reading these pages and will generate an access violation if either is attempted.
790	Read Only
791	Image Space is the virtual address space in use by the selected image with this protection.  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.
792	Read/Write
793	Image Space is the virtual address space in use by the selected image with this protection.  Read/Write protection allows a process to read, modify and write to these pages.
794	Write Copy
795	Image Space is the virtual address space in use by the selected image with this protection.  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.
796	Executable
797	Image Space is the virtual address space in use by the selected image with this protection.  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.
798	Exec Read Only
799	Image Space is the virtual address space in use by the selected image with this protection.  Execute/Read Only memory is memory that can be executed as well as read.
800	Exec Read/Write
801	Image Space is the virtual address space in use by the selected image with this protection.  Execute/Read/Write memory is memory that can be executed by programs as well as read and written.
802	Exec Write Copy
803	Image Space is the virtual address space in use by the selected image with this protection.  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.
804	ID Thread
805	ID Thread is the unique identifier of this thread.  ID Thread numbers are reused, so they only identify a thread for the lifetime of that thread.
806	Mailslot Receives Failed
807	Mailslot Opens Failed/sec indicates the rate at which mailslot messages to be delivered to mailslots that are not present are received by this workstation.
808	Mailslot Writes Failed
809	Duplicate Master Announcements indicates the number of times that the master browser has detected another master browser on the same domain.
810	Mailslot Opens Failed/sec
811	Illegal Datagrams/sec is the rate at which incorrectly formatted datagrams have been received by the workstation.
812	Duplicate Master Announcements
813	Announcements Total/sec is the sum of Announcements Server/sec and Announcements Domain/sec.
814	Illegal Datagrams/sec
815	Enumerations Total/sec is the rate at which browse requests have been processed by this workstation.  This is the sum of Enumerations Server/sec, Enumerations Domain/sec, and Enumerations Other/sec.
816	Thread Details
817	The Thread Details performance object  consists of counters that measure aspects of thread behavior that are difficult or time-consuming or collect.  These counters are distinguished from those in the Thread object by their high overhead.
818	Cache Bytes
819	Cache Bytes is the sum of the Memory\\System Cache Resident Bytes, Memory\\System Driver Resident Bytes, Memory\\System Code Resident Bytes, and Memory\\Pool Paged Resident Bytes counters.  This counter displays the last observed value only; it is not an average. 
820	Cache Bytes Peak
821	Cache Bytes Peak is the maximum number of bytes used by the file system cache since the system was last restarted. This might be larger than the current size of the cache. This counter displays the last observed value only; it is not an average. 
822	Pages Input/sec
823	Pages Input/sec is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation. Compare the value of Memory\\Pages Input/sec to the value of  Memory\\Page Reads/sec to determine the average number of pages read into memory during each read operation.
870	RAS Port
871	The RAS performance object consists of counters that monitor individual Remote Access Service ports of the RAS device on the computer.
872	Bytes Transmitted
873	The number of bytes transmitted total for this connection.
874	Bytes Received
875	The number of bytes received total for this connection.
876	Frames Transmitted
877	The number of data frames transmitted total for this connection.
878	Frames Received.
879	The number of data frames received total for this connection.
880	Percent Compression Out
881	The compression ratio for bytes being transmitted.
882	Percent Compression In
883	The compression ratio for bytes being received.
884	CRC Errors
885	The total number of CRC Errors for this connection.  CRC Errors occur when the frame received contains erroneous data.
886	Timeout Errors
887	The total number of Timeout Errors for this connection.  Timeout Errors occur when an expected is not received in time.
888	Serial Overrun Errors
889	The total number of Serial Overrun Errors for this connection.  Serial Overrun Errors occur when the hardware cannot handle the rate at which data is received.
890	Alignment Errors
891	The total number of Alignment Errors for this connection.  Alignment Errors occur when a byte received is different from the byte expected.
892	Buffer Overrun Errors
893	The total number of Buffer Overrun Errors for this connection.  Buffer Overrun Errors when the software cannot handle the rate at which data is received.
894	Total Errors
895	The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.
896	Bytes Transmitted/Sec
897	The number of bytes transmitted per second.
898	Bytes Received/Sec
899	The number of bytes received per second.
900	Frames Transmitted/Sec
901	The number of frames transmitted per second.
902	Frames Received/Sec
903	The number of frames received per second.
904	Total Errors/Sec
905	The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.
906	RAS Total
907	The RAS performance object consists of counters that combine values for all ports of the Remote Access service (RAS) device on the computer.
908	Total Connections
909	The total number of Remote Access connections.
920	WINS Server
921	The WINS Server performance object consists of counters that monitor communications using the WINS Server service.
922	Unique Registrations/sec
923	Unique Registrations/sec is the rate at which unique registration are received by the WINS server.
924	Group Registrations/sec
925	Group Registrations/sec is the rate at which group registration are received by the WINS server.
926	Total Number of Registrations/sec
927	Total Number of Registrations/sec is the sum of the Unique and Group registrations per sec.  This is the total rate at which registration are received by the WINS server.
928	Unique Renewals/sec
929	Unique Renewals/sec is the rate at which unique renewals are received by the WINS server.
930	Group Renewals/sec
931	Group Renewals/sec is the rate at which group renewals are received by the WINS server.
932	Total Number of Renewals/sec
933	Total Number of Renewals/sec is the sum of the Unique and Group renewals per sec.  This is the total rate at which renewals are received by the WINS server.
934	Releases/sec
935	Total Number of Releases/sec is the rate at which releases are received by the WINS server.
936	Queries/sec
937	Total Number of Queries/sec is the rate at which queries are received by the WINS server.
938	Unique Conflicts/sec
939	Unique Conflicts/sec is the rate at which unique registrations/renewals received by the WINS server resulted in conflicts with records in the database.
940	Group Conflicts/sec
941	Group Conflicts/sec is the rate at which group registration received by the WINS server resulted in conflicts with records in the database.
942	Total Number of Conflicts/sec
943	Total Number of Conflicts/sec is the sum of the Unique and Group conflicts per sec.  This is the total rate at which conflicts were seen by the WINS server.
944	Successful Releases/sec
945	Total Number of Successful Releases/sec
946	Failed Releases/sec
947	Total Number of Failed Releases/sec
948	Successful Queries/sec
949	Total Number of Successful Queries/sec
950	Failed Queries/sec
951	Total Number of Failed Queries/sec
952	Handle Count
953	The total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in this process.
1000	MacFile Server
1001	Services for Macintosh AFP File Server.
1002	Max Paged Memory
1003	The maximum amount of paged memory resources used by the MacFile Server.
1004	Current Paged Memory
1005	The current amount of paged memory resources used by the MacFile Server.
1006	Max NonPaged Memory
1007	The maximum amount of nonpaged memory resources use by the MacFile Server.
1008	Current NonPaged memory
1009	The current amount of nonpaged memory resources used by the MacFile Server.
1010	Current Sessions
1011	The number of sessions currently connected to the MacFile server.  Indicates current server activity.
1012	Maximum Sessions
1013	The maximum number of sessions connected at one time to the MacFile server.  Indicates usage level of server.
1014	Current Files Open
1015	The number of internal files currently open in the MacFile server.  This count does not include files opened on behalf of Macintosh clients.
1016	Maximum Files Open
1017	The maximum number of internal files open at one time in the MacFile server.  This count does not include files opened on behalf of Macintosh clients.
1018	Failed Logons
1019	The number of failed logon attempts to the MacFile server.  Can indicate whether password guessing programs are being used to crack the security on the server.
1020	Data Read/sec
1021	The number of bytes read from disk per second.
1022	Data Written/sec
1023	The number of bytes written to disk per second.
1024	Data Received/sec
1025	The number of bytes received from the network per second.  Indicates how busy the server is.
1026	Data Transmitted/sec
1027	The number of bytes sent on the network per second.  Indicates how busy the server is.
1028	Current Queue Length
1029	The number of outstanding work items waiting to be processed.
1030	Maximum Queue Length
1031	The maximum number of outstanding work items waiting at one time.
1032	Current Threads
1033	The current number of threads used by MacFile server.  Indicates how busy the server is.
1034	Maximum Threads
1035	The maximum number of threads used by MacFile server.  Indicates peak usage level of server.
1050	AppleTalk
1051	AppleTalk Protocol
1052	Packets In/sec
1053	Number of packets received per second by Appletalk on this port.
1054	Packets Out/sec
1055	Number of packets sent per second by Appletalk on this port.
1056	Bytes In/sec
1057	Number of bytes received per second by Appletalk on this port.
1058	Bytes Out/sec
1059	Number of bytes sent per second by Appletalk on this port.
1060	Average Time/DDP Packet
1061	Average time in milliseconds to process a DDP packet on this port.
1062	DDP Packets/sec
1063	Number of DDP packets per second received by Appletalk on this port.
1064	Average Time/AARP Packet
1065	Average time in milliseconds to process an AARP packet on this port.
1066	AARP Packets/sec
1067	Number of AARP packets per second received by Appletalk on this port.
1068	Average Time/ATP Packet
1069	Average time in milliseconds to process an ATP packet on this port.
1070	ATP Packets/sec
1071	Number of ATP packets per second received by Appletalk on this port.
1072	Average Time/NBP Packet
1073	Average time in milliseconds to process an NBP packet on this port.
1074	NBP Packets/sec
1075	Number of NBP packets per second received by Appletalk on this port.
1076	Average Time/ZIP Packet
1077	Average time in milliseconds to process a ZIP packet on this port.
1078	ZIP Packets/sec
1079	Number of ZIP packets per second received by Appletalk on this port.
1080	Average Time/RTMP Packet
1081	Average time in milliseconds to process an RTMP packet on this port.
1082	RTMP Packets/sec
1083	Number of RTMP packets per second received by Appletalk on this port.
1084	ATP Retries Local
1085	Number of ATP requests retransmitted on this port.
1086	ATP Response Timouts
1087	Number of ATP release timers that have expired on this port.
1088	ATP XO Response/Sec
1089	Number of ATP Exactly-once transaction responses per second on this port.
1090	ATP ALO Response/Sec
1091	Number of ATP At-least-once transaction responses per second on this port.
1092	ATP Recvd Release/Sec
1093	Number of ATP transaction release packets per second received on this port.
1094	Current NonPaged Pool
1095	The current amount of nonpaged memory resources used by AppleTalk.
1096	Packets Routed In/Sec
1097	Number of packets routed in on this port.
1098	Packets dropped
1099	Number of packets dropped due to resource limitations on this port.
1100	ATP Retries Remote
1101	Number of ATP requests retransmitted to this port.
1102	Packets Routed Out/Sec
1103	Number of packets routed out on this port.
1110	Network Segment
1111	Provides Network Statistics for the local network segment via the Network Monitor Service.
1112	Total frames received/second
1113	The total number of frames received per second on this network segment.
1114	Total bytes received/second
1115	The number of bytes received per second on this network segment.
1116	Broadcast frames received/second
1117	The number of Broadcast frames received per second on this network segment.
1118	Multicast frames received/second
1119	The number of Multicast frames received per second on this network segment.
1120	% Network utilization
1121	Percentage of network bandwidth in use on this network segment.
1124	% Broadcast Frames
1125	Percentage of network bandwidth which is made up of broadcast traffic on this network segment.
1126	% Multicast Frames
1127	Percentage of network bandwidth which is made up of multicast traffic on this network segment.
1150	Telephony
1151	The Telephony System
1152	Lines
1153	The number of telephone lines serviced by this computer.
1154	Telephone Devices
1155	The number of telephone devices serviced by this computer.
1156	Active Lines
1157	The number of telephone lines serviced by this computer that are currently active.
1158	Active Telephones
1159	The number of telephone devices that are currently being monitored.
1160	Outgoing Calls/sec
1161	The rate of outgoing calls made by this computer.
1162	Incoming Calls/sec
1163	The rate of incoming calls answered by this computer.
1164	Client Apps
1165	The number of applications that are currently using telephony services.
1166	Current Outgoing Calls
1167	Current outgoing calls being serviced by this computer.
1168	Current Incoming Calls
1169	Current incoming calls being serviced by this computer.
1228	Gateway Service For NetWare
1229	The Gateway Service For NetWare performance object consists of counters that measure the Gateway Server service.
1230	Client Service For NetWare
1231	The Client Service For NetWare object consists of counters that measure packet transmission rates, logons, and connections.
1232	Packet Burst Read NCP Count/sec
1233	Packet Burst Read NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Read.  Packet Burst is a windowing protocol that improves performance.
1234	Packet Burst Read Timeouts/sec
1235	Packet Burst Read Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Read Request because the NetWare server took too long to respond.
1236	Packet Burst Write NCP Count/sec
1237	Packet Burst Write NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Write.  Packet Burst is a windowing protocol that improves performance.
1238	Packet Burst Write Timeouts/sec
1239	Packet Burst Write Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Write Request because the NetWare server took too long to respond.
1240	Packet Burst IO/sec
1241	Packet Burst IO/sec is the sum of Packet Burst Read NCPs/sec and Packet Burst Write NCPs/sec.
1242	Connect NetWare 2.x
1243	Connect NetWare 2.x counts connections to NetWare 2.x servers.
1244	Connect NetWare 3.x
1245	Connect NetWare 3.x counts connections to NetWare 3.x servers.
1246	Connect NetWare 4.x
1247	Connect NetWare 4.x counts connections to NetWare 4.x servers.
1260	Logon Total
1261	Logon Total includes all interactive logons, network logons, service logons, successful logon, and failed logons since the machine is last rebooted.
1300	Server Work Queues
1301	The Server Work Queues performance object consists of counters that monitor the length of the queues and objects in the queues.
1302	Queue Length
1303	Queue Length is the current length of the server work queue for this CPU.  A sustained queue length greater than four might indicate processor congestion.  This is an instantaneous count, not an average over time.
1304	Active Threads
1305	Active Threads is the number of threads currently working on a request from the server client for this CPU.  The system keeps this number as low as possible to minimize unnecessary context switching.  This is an instantaneous count for the CPU, not an average over time.
1306	Available Threads
1307	Available Threads is the number of server threads on this CPU not currently working on requests from a client.  The server dynamically adjusts the number of threads to maximize server performance.
1308	Available Work Items
1309	Every request from a client is represented in the server as a 'work item,' and the server maintains a pool of available work items per CPU to speed processing.  This is the instantaneous number of available work items for this CPU.  A sustained near-zero value indicates the need to increase the MinFreeWorkItems registry value for the Server service.  This value will always be 0 in the Blocking Queue instance.
1310	Borrowed Work Items
1311	Every request from a client is represented in the server as a 'work item,' and the server maintains a pool of available work items per CPU to speed processing.  When a CPU runs out of work items, it borrows a free work item from