This patch fixes a crash in AppUsage. It also adds support for out of sequence
events reported by the operating system's native event tracer, due to which
AppUsage logged wrong elapsed time for some processes.
Typically, this only happened for processes which were started multiple times 
in quick succession and stopped after a few seconds.

Will provide Windows client support for the new Process datatype, which
contains information about cpu usage, memory usage, I/O and process
elapsed time - for selected processes.

This patch requires Patch481 to be installed on the server.
You must specify which processes to account for, since this functionality
is rather costly in terms of system resources.
To specify processes, edit the appusage_process_rules_rel.conf file on
the server, which is then distributed to the clients.

Also, this patch introduces selective module logging. You need to install
patch #493 on the server, to enable this option.
To specify modules, edit the appusage_modpoller_rel.conf file on the
server, which is then distributed to the clients.

Windows Application Usage (AppUsage) would log a value of 1 in the 'count' measurement
field for each record, and multiple records could be logged for the same application
(if it ran for long enough). This could result in a 'count' of more than 1 when records
for the same application were added on the server. After this patch, subsequent redcords
will be logged with a 'count' of zero. This will make the sum total 1 on the server when
multiple records for a single application are added. (But a side effect is that some
records may show a 'count' of zero, when not added. Records with zero count must be
interpreted as 'count' = 1, but they started prior to the report period.

Windows Application Usage (AppUsage) would log a value of 1 in the 'count' measurement
field for each record, and multiple records could be logged for the same application
(if it ran for long enough). This could result in a 'count' of more than 1 when records
for the same application were added on the server. After this patch, subsequent redcords
will be logged with a 'count' of zero. This will make the sum total 1 on the server when
multiple records for a single application are added. (But a side effect is that some
records may show a 'count' of zero, when not added. Records with zero count must be
interpreted as 'count' = 1, but they started prior to the report period.

Upgrade to patch 1056, with corrected data type (Process accounting) details.

AppUsage has been partly rewritten to better conform to Microsoft standards
(which is important with respect to accuracy and for running on 64 bit).

Also, this patch introduces selective module logging. You need to install
patch #493 on the server, to enable this option.
To specify modules, edit the appusage_modpoller_rel.conf file on the
server, which is then distributed to the clients.

Will provide Windows client support for the new Process datatype, which
contains information about cpu usage, memory usage, I/O and process
elapsed time - for selected processes.

This patch requires Patch481 to be installed on the server.
You must specify which processes to account for, since this functionality
is rather costly in terms of system resources.
To specify processes, edit the appusage_process_rules_rel.conf file on
the server, which is then distributed to the clients.

Also, this patch introduces selective module logging. You need to install
patch #493 on the server, to enable this option.
To specify modules, edit the appusage_modpoller_rel.conf file on the
server, which is then distributed to the clients.

Because of an algorithmic error in AppUsage, some processes just starting
could be logged as just ended, if the process information could not be
accessed right away. This has now been fixed.

Because of an algorithmic error in AppUsage, some processes just starting
could be logged as just ended, if the process information could not be
accessed right away. This has now been fixed.