home *** CD-ROM | disk | FTP | other *** search
- IBM Internal Use Only
-
- NEWS file for PSPM package --- Seth Eilbott
- Software Development Tools
- Boca Raton, FL
- SETH at BCRVM1
-
- 02/24/94 -- Version 6.31:
- * Fixed a bug which caused PSPM to process a mouse button
- when it shouldn't (as discussed in the PSPM FORUM).
-
- 02/10/94 -- Version 6.3:
- * Added the following command-line options (minimum
- acceptable abbreviations are CAPTIALIZED):
-
- /NOConfirm -- to prevent PSPM from asking for
- confirmation when you ask to kill a
- process or process tree.
-
- /NOLogo -- to prevent PSPM from displaying its
- logo during startup.
-
- /MINimize -- to instruct PSPM to start minimized
-
- /MAXimize -- to instruct PSPM to start maximized
-
- * Changed my displayed address to reflect the fact that
- I am now on BCRVM1, and added my Internet address while
- I was in the neighborhood.
-
- 01/11/94 -- Version 6.2:
- * Display session names (in quotes) for 'processes'
- running in DOS and Win-OS/2 sessions. GOODBYE ZOMBIES]
- * Added support for the recognition of "system" processes
- (via the PSPM profile), and for the exclusion of system
- processes and their descendants from the display.
- * Reorganize the menu bar.
-
- 04/01/93 -- Version 6.11:
- * Handle OS/2 1.3's returning of undocumented priority
- values; display "Unknown" for the priority class if
- such a value is returned.
-
- 03/31/93 -- Version 6.10:
- * Fixed a bug in the profile support which caused PSPM to
- TRAP if a blank line was encountered.
- * Added class and level detail to the process priority
- displayed in the threads information dialog.
- * Added "*** IBM Internal Use Only ***" to the product
- information screen.
-
- 01/21/93 -- Version 6.00:
- * New support for "extended information" about processes:
- At startup, PSPM will now read a profile containing
- extended information about processes, one "line" per
- process. The format of the line is:
-
- procname description
-
- in which the first word (everything up to the first
- whitespace character) is the process name, and
- everything else is taken as the description.
-
- Since it might be desirable to have descriptions that
- are longer than the longest line your editor supports
- (EOS2 does not support lines > 255 characters, for
- example), lines can be continued, if desired. The
- continuation processing is very simple: If the last
- character on the line is a backslash (\), then the
- backslash is discarded, and the next line appended to
- the current. *No* spaces are discarded or added from
- one line to the next. PSPM supports (or, at least, is
- designed to support) lines of *any* length, so please
- feel free to try lines as long as you like.
-
- PSPM will also handle a few (C) escape sequences in the
- extended text. Specifically, PSPM will translate \n
- and \r to a newline (they are both treated the same),
- and will translate \\ to a single backslash; any other
- sequence will be left unchanged.
-
- Blank lines are ignored.
-
- The default name of the profile is "PSPM.PRO" (with no
- path, which means that PSPM will look for it in the
- current directory *only*; however, this profile name
- can be overriden with the new -p<name> command-line
- argument, in which <name> is the fully-qualified
- filespec of the profile. Do not put any spaces between
- the -p and the filespec; for example,
- "PSPM2 -pD:\util20\pspm.pro"
-
- While PSPM does not have an interface to add, delete,
- or change entries in the profile, it does let you tell
- it to reread the profile so that it picks up any
- changes that you may have made. Select the "Reread
- PSPM profile" item from PSPM's Option pull-down to
- refresh that information.
-
- I have supplied a sample profile with the package.
- This profile was built from the OS2FLIST PACKAGE on
- OS2CSD (this package contains a list of all files
- supplied with OS/2 2.0), and from a few (non-IUO)
- entries suggested by users.
-
- If you have any suggestions for profile entries, please
- feel free to submit them either to the PSPM FORUM on
- IBMPC, or to me directly. Remember to indicate which
- of these entries are for IUO programs, since PSPM will
- soon (hopefully) be release to customers via the OS2EWS
- program.
-
- Thanks to Al Connor for originally suggesting this
- idea]
-
- * PSPM should now look good on all displays, whether they
- are VGA, BGA (8514/A), or XGA. Please let me know if
- any dialog box is incorrect.
-
- * PSPM used to continue to refresh the process tree even
- though you had previously highlighted a process name by
- using the keyboard (arrow keys). PSPM now disables the
- automatic refresh until you manually de-select the
- process name, either by pressing mouse button one when
- pointing to an empty area, or by pressing the ESCape
- key.
-
- * You can now request that all active processes
- (processes that have one or more non-blocked and
- non-frozen threads) have their names displayed in
- UPPERCASE. Use the new "Highlight Active Processes"
- item in the Options pulldown, or the Ctrl-A
- accelerator, to toggle this highlighting.
-
- Thanks to Ron Schwabel for originally suggesting this
- idea]
-
- * Every PSPM dialog now has a title bar with "PSPM" in
- it. The presence of a title bar also makes the dialogs
- moveable.
-
- 10/01/92 -- Version 5.31:
- * Enabled the fully-qualified process name information
- when running on 1.3 (version 5.30 only displayed this
- information when running on 2.0).
- * Each executable now displays its name and version
- number.
-
- 09/30/92 -- Version 5.30:
- * Added the fully-qualified process name in the "Process
- Info" dialog of PSPM(2). The name will be truncated if
- it is longer than the allowed space in the dialog.
-
- ANALYZE(2) has a new parameter, FULL, which instructs
- ANALYZE to include this fully-qualified name.
-
- NOTE: The fully-qualified name is only available on
- OS/2 2.0.
-
- * The refresh interval entry field (in the "Refresh
- Parameters" dialog box of PSPM(2)) is now disabled if
- refresh is turned off.
-
- 06/16/92 -- Version 5.20:
- * Fixed a bug which caused a TRAP when a process with a
- long filename (such as LONGFILENAME.EXE) was processed.
- * Fixed a bug which caused the ENTER key to be ignored
- when running PSPM.EXE on OS/2 1.3.
-
- 06/03/92 -- Version 5.10:
- * KILLIT(2) now allows you to specify the process ID in
- hex, as well as decimal. Simply start the PID with
- "0x" and/or end the PID with "x" to indicate that the
- value is hex.
- * PSPM(2) now switches immediately to a selected process
- when the right mouse button is process over that
- process' name.
- * Fixed a bug in KILLIT(2) which prevented the KILLTREE
- processing from working correctly on OS/2 2.0.
-
- 05/20/92 -- Version 5.00:
- * Added PSPM2, ANALYZE2, and KILLIT2 to the package.
- These are 32-bit versions of PSPM, ANALYZE, and KILLIT,
- respectively, and run only under OS/2 2.0.
-
- The CHILD and SESSION parameters are now invalid for
- all executables, as the only supported method is DIRECT
- (For compatibility, "DIRECT" is allowed as a
- command-line parameter, even though it doesn't really
- have an effect). Because CHILD and SESSION are now
- invalid, PSPMR has been removed from the package.
-
- Note: PSPM and PSPM2 do *not* share the saved
- information (refresh, colors, fonts, centering,
- position/size), so you'll have to establish new
- information for PSPM2 (once).
-
- 04/24/92 -- Version 4.00:
- * DosQProcStatus is back]] Due to the OUTSTANDING efforts
- of Dave Glowny, all programs (PSPM, ANALYZE, and
- KILLIT) can now use the DosQProcStatus API on OS/2 2.0
- to get the process information directly, *without*
- requiring the use of PSPMR or PSTAT] Way to go, Dave]
-
- Note: The programs do not use the API by default, but
- still operate the same as version 3.20 (ANALYZE
- and KILLIT use CHILD, PSPM uses SESSION); to
- force any of the programs to use the API, specify
- a command-line parameter of DIRECT (for example,
- "PSPM DIRECT").
-
- 04/20/92 -- Version 3.20:
- * All programs (PSPM, ANALYZE, and KILLIT) now try to
- run PSPMR from the invoked directory (the one where
- the invoked program was found) first, and then try to
- run PSPMR from the PATH.
-
- 04/16/92 -- Version 3.10:
- * Fixed a bug in the analysis routine which prevented
- allocated memory from being freed.
-
- 04/07/92 -- Version 3.04:
- * Fixed a minor quirk in PSPM.EXE that caused two screen
- paints when the mouse button one was pressed over an
- open area.
-
- 04/02/92 -- Version 3.03:
- * Changed NEWPSPM.EXE to PSPM.EXE, NEWPSPMR.EXE to
- PSPMR.EXE, and sent this version to OS2TOOLS
- (replacing Doug Hill's last version there); kept
- Doug's version -- OS/2 1.x ONLY, DON'T RUN HIS
- VERSION ON OS/2 2.0]]]] -- in OLDPSPM ZIPBIN.
- * Added help to ANALYZE and KILLIT via '?' (ANALYZE ? or
- KILLIT ?)
- * Fixed a minor bug with redirected files.
-
- 03/30/92 -- Version 3.02:
- * Rebuilt all programs with different optimization, due
- to bugs in that optimization in MSC 6.0.
-
- 03/30/92 -- Version 3.01:
- * First attempt to fix problems that some people have
- with the programs on 2.0.
-
- 03/27/92 -- Version 3.00:
- * Added support for OS/2 2.0. The same executable still
- runs on 1.x. The "SESSION" command-line parameter
- forces NEWPSPM to use a secondary session on 1.x (so
- you can see how it will run on 2.0). The secondary
- session *requires* NEWPSPMR.EXE somewhere along the
- PATH.
- * Added the ANALYZE.EXE and KILLIT.EXE programs to the
- package.
- * Fixed a bug which caused refreshing to be disabled if a
- dialog box was brought up.
-
- 02/25/92 -- Version 2.00:
- * Added keyboard support
-
- 01/21/92 -- Version 1.00:
- * Original version (an attempt to mimic the behavior of
- Doug Hill's PSPM program on OS2TOOLS, plus add some
- bells and whistles).
-