In  this  .ZIP file  you should find all  the files related to Perf_Meter  V2.3,
including three .COM files.

  MAKE_PERF_METER.com  will remake  the  .EXE  files from  the original  source.

  PFM$STARTUP.com  (after  you modify  it to reflect the location  of Perf_Meter
files on  your system)  should be  run at  system  startup, if you  want  anyone
to be able to run Perf_meter.

  PERF_METER.com  is a  template for  defining  logicals  and running Perf_meter
with  customized devices being  monitored.  Modify  this  to reflect your system
requirements, and make it  available as  a  default template  for local users to
customize.

NOTES:
=====

  In V2.3, you must  run PERF_METER with WORLD  priv, or install the image  with
WORLD priv. This  is needed  so that $GETJPI can  do it's thing.  If run without
this priv, the top process will usually be yourself.

  On  Alphas, CMKRNL privilege  is needed to get  the PERF_METER to run at  all,
and it  must  be  installed with CMKRNL  and WORLD  privileges if non-priv users
are to use it.

  The  CPU  percentages are  calculated the way monitor  calculates  them, which
means that on a 2 CPU SMP system, 100% really means 50%.

Changes made since V2.2:

 -Added back the UIL definitions for additional devices to be monitored.

 -Changed the  .UIL to use fixed  areas of  the  screen, even  when text
  exceeds  the available  space.  This fixes some display problems  with
  long device TITLEs or when the  TOP  CPU  user has an image file  name
  longer than the Perf_meter window.

 -Modified the C code  which gets CPU usage and state times, not to need
  CMKRNL on the VAX version (like  in  version 2.0) so  "ordinary" users
  can see  CPU  usage without  having  to install the .EXE  with  CMKRNL
  privs.  Without  WORLD priv  the user can still only see "his" MAX CPU
  user. On the Alpha, KERNEL mode  is needed  to get the CPU usage time.
  See the comments in the Perf_meter.C code for details.

 -Note that like in previous  versions  device logicals can  consist  of
  other logicals, and  can point to multiple devices. But only the first
  device will have  its  IO  monitored. I am working  on  a version that
  will  sum  over devices,  like  the VWS  (for those of you old enough)
  version supports. That may be available soon.

                                  RDS   24-MAY-1995
                                  PJO   12-JUN-1995
