home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR4
/
PMPSTAT.ZIP
/
PMPSTAT.DOC
< prev
next >
Wrap
Text File
|
1993-08-21
|
4KB
|
96 lines
Documentation (sort of) for PMPSTAT:
------------------------------------
But FIRST: Registration Info
-----------------
There IS none. Feel free to distribute and play around with PMPSTAT
as much as you like. PMPSTAT is "WeirdWare".
WHAT IS WEIRDWARE?
------------------
Well, basically the idea is: if you like PMPSTAT so much that you
feel you absolutely have to send me something, you're free to do
so. You won't get a "registered" version, though, because there
is no such thing.
PLEASE do not send money. I'd much rather you used your imagination
and sent me something "interesting". No bombs or human body parts
or offal, please. "Interesting" things may be postcards from odd
places, toys, aluminum foil sculptures, concert ticket stubs, even
a catalog of mail-order brides!
Use your imagination, I'm sure you can think of something that will
make me smile or scratch my head.
If you CAN'T think of anything nifty to send, you can send money, but
if you do so, please make it a small amount of unusual currency, for
example, assorted Tibetan change. Hint: I like going to Mexico...
ENOUGH! TELL US ABOUT PMPSTAT!
-------------------------------
Okay, okay, get out of my face already. PMPStat was written to allow
me to do several things I wanted to do when developing programs.
It allows you to check out system processes, threads, shared memory,
semaphores, and DLLs. It allows you to kill off system processes,
see who's using what DLLs, memory, semaphores, etc.
Play with it for a while and see if you can use it. Unless you're a
developer, you'll probably just use it to kill off hung processes.
The problem is: if your desktop is hung, you can't get at PMPSTAT
to do anything about it, anyway. So its use as a program killer is
limited; you'll still have to hit CTRL-ALT-DEL occasionally.
WHAT ABOUT BUGS?
----------------
PMPStat is not gospel. I have noticed some inconsistencies between
what PSTAT thinks is going on and what PMPSTAT thinks is going on.
Semaphores are especially confusing, and because DLLs can "import"
other DLLs (even themselves), the way I report on them is: if
the DLL imports a DLL I have already reported on, I do not list the
imported DLL again; if the DLL imports itself, I put an asterisk (*)
behind it. Maybe I'll figure out a better way of doing this some
day. By the way, IBM's DOSQPROC.INF is...er...not entirely accurate.
HOW DO WE INSTALL IT?
---------------------
Well, you'll want to expand the .LZH thing using LH2 with /a /e.
Just put the DLLPSTAT.DLL in your OS2/DLL or somewhere like that. Then
you can run PMPSTAT.EXE.
WHY DON'T THE HELP BUTTONS WORK?
--------------------------------
Ho Ho Ho. PMPStat was designed and written at my house while I was
employed at a company where I had a registered copy of GPF, the tool
I used to do all the screens and so forth.
I am still employed there for a day or two, so THIS iteration IS
LEGAL; doing the help would take a week or two of my spare time, by
which time I will be employed elsewhere and will not be able to use
GPF unless I buy myself a copy or my new employer buys me one.
Note to GPF: Gee, a free copy of GPF 2.1 would make me smile a LOT!
Note to Everyone Else: The above endorsement of GPF is sincere, it
IS a useful development tool. I like it.
In any case, I may just code the bit that GPF does in C++ one day,
and come out with a version that has help.
WHERE SHOULD GPF -- OOPS, *WE* SEND STUFF?
------------------------------------------
Oh sure, you expect me to give out my home address? Okay okay. You
can send stuff to:
Gerald Callow
c/o 633 Melrose Avenue West
Winnipeg, MB
R2C 1P6
CANADA
Note: The Logo and Name "DragonWare" is whimsical. I don't have a
company named that, and if someone else DOES, "Oops! Sorry!".