mike luther

Is there a small OS/2 memory watcher utility that can display memory
parameters for OS/2 in a continuously running graphics or even just a
numeric PM display other than MEMWATCH or MEMSIZE for OS/2?

I want to be able to watch the play on system memory on a continuously
visible basis for troubleshooting. MEMSIZE has problems with MCP2 and
so on relative to system uptime rollover during SWAPPER.DAT expansion
episodes. That and related issues cause problems in other places.
MEMWATCH, at least in test here, produces many hard box locks at the
time of .INI file writes. I need a graphical screen change alert when
memory available takes any unexpected size jump issues for research
purposes. While THESEUS4 sure can display this, as far as my ability to
use it, the display doesn't have a viewable graph for instant alert when
things go awry.


Thank you.

--


--> Sleep well; OS2's still awake!

Mike Luther

ilya zakharevich

[A complimentary Cc of this posting was sent to
Mike Luther

I use DINFO. Small and stable. ;-)

Hope this helps,
Ilya

will honea

On Tue, 16 Dec 2003 19:17:00 UTC Mike Luther <mike.luther@ziplog.com>

Mike, have you looked at PMPATROL? I think that was the name but I
haven't used or even heard of the program in several years. ISTR it
had a graphic memory use display available and it always ran well for
me way back then. I'll see if I can find it in junk pile here if you
can't locate it - but that might take a lot longer <g>. --
Will Honea <whonea@codenet.net>

mike luther

Thank you very kindly for your suggestion Ilya ..

It's almost .. grin .. just what the Dr. ordered! Part of the IBM
Employee Written Software group it has this exactly bright nice print
sized report, which also has a timing selection. But .. groan .. the
one I have here doesn't report memory of that free memory, which is, in
theory, 'in use'. What I need to know is a running ticker of what is,
in theory, in use at any given time.


For other note, there is also another EWS contribution which might
work. It's what I have here as 20MEMU in the EWS collection. But the
date on it is sort of early. Earlier, as I think I reason, before FP10
was crafter for OS/2. My garbage scow memory recalls from the running
list of problems that surfaced between FP10 and FP14 up, there were
troubles in RIver City with memory utilities and clock watchers and so
on. Memory says that there were problems in which MEMSIZE, PMPATROL,
all these creatures, when loaded, maxed out the CPU indicator, even if
there may not have been any real CPU mashing activity.


At any rate I was fishing for something later when I downloaded MEMWATCH
to try in hopes to avoid that. But thank you for taking time to try to
help me.

--
--> Sleep well; OS2's still awake!

Mike Luther

mike luther

Ah yes, Will ...

Yes, but no. My Garbage Scow Personal Memory takes me back to an issue
with PMPATROL as IBM moved from FP10 upward. I kept pages and pages of
all the bugs found and reported fixed and so on. In the problems was an
issue where PMPATROL maxed out the CPU graph on the WPS shell, even if
it really didn't. Same thing actually happened, per my memory, for
MEMSIZE, which is one of the reasons it was reworked to the current
version 400 that's on Hobbs. I got rid of PMPATROL off the desktop
after I hit this with FP14 research.


But to tell you the truth, it may be that after all the kernel work that
has been done on OS/2 since then, it may just be that PMPATROL will
work. I happen to have a version 4.3 here which notes that's this
version was 'fixed' for FP10 issues. I'll unpack it and test it with
MCP2 and report back here. If it works now, that might help some other
poor lost puppy dog like Mikey..

--
--> Sleep well; OS2's still awake!

Mike Luther

ilya zakharevich

[A complimentary Cc of this posting was sent to
Mike Luther

But on virtual memory OS the notion of "free memory" does not make any
sense. All the info you get this way is going to be bogus anyway
(unless you do very heavy manual stats of used pages like Theseus
does). If you trust the bogus numbers obtained the "easy way", you
start to buy into snake oil like "allocmem.exe" etc.

Hope this helps,
Ilya

mike luther

Thanks Ilya for the suggestion.


I tried it as a part of the IBM Employee Written Software collection,
but it only displays the 'available' memory total and the swapper
memory. I couldn't see any way to make it report 'used' memory...
Also in the collection of EWS which I got en total off the IBM server
site before they scotched it, is 20MEMU as well. However it is awful
early in date and before FP10 if memory is correct. There were some
major CPU WPS interference problems with this sort of stuff back then if
my memory is correct. I kinda was thinking about something more like
MEMWATCH that had an offering date beyond FP10...
--
--> Sleep well; OS2's still awake!

Mike Luther

mike luther

Thanks Will..


You know I glossed over that in my feeble Garbage Scow Mind Will. I
knew about it, but digging back around FP10 time, it and MEMSIZE both
got into trouble with botching the CPU graph up on the WPS if memory is
right. They didn't actually bash the CPU, but there were problems. At
that time I wiped PMPATROL off the desktop because it didn't get solved
in the near-time frame of things. But looking back through all the BBS
stuff here, I discover, now that you have suggested this that there is a
version 43 that was later released I didn't realize was in there. In
theory, it says it 'fixed' the FP10 CPU bug.


OK .. it's back on the desktop now. I've discovered that in certain
setup modes it still does smash the WPS CPU monitor graph, but seems to
be able to be set so that it doesn't interfere with it now. Also seems
to run on MCP2 latest kernel as well. For the short term, it hasn't
smashed the system. More important it has exactly the staus bar display
and the Activity monitor I need to keep chasing this gravy ****ing
memory pig or multiple pigglets I'm honing in on.


Thanks for getting me to go back and investigate it. I'll have to
register it to get more than two hour at a time service, but that may be
a bargain considering the time saved doing re-work of the desktop to
detail the glitch in the graph that could catch my eye as I work and
yank on this pig's nose ring!


--
--> Sleep well; OS2's still awake!

Mike Luther

peter

What are the problems? I'm using MEMSIZE here (eCS 1.03) with
absolutely no problems. Perhaps that's because I've configured it
not to display the Date/Time and Elapsed Time.

The thing I like about Memsize is that, once you've selected
Table Format and dropped a small font on it, it takes up only a
narrow strip at the bottom of the screen, so it can be left running
all the time. (Oh, and I also make sure that I disable the
displays of anything that is not interesting to me.)

My screen has the xCenter at the top, the PC/2 task bar at the
bottom, Memsize just above that, and dink's "New Mail" to the right
of Memsize. Taken together, those four things take up such a small
part of the screen that I still have a good-sized desktop to work with.

--
Peter Moylan Peter.Moylan@newcastle.edu.au
http://eepjm.newcastle.edu.au (OS/2 and eCS information and software)

will honea

On Wed, 17 Dec 2003 01:52:21 UTC Mike Luther <mike.luther@ziplog.com>

And they say that the memory is the first thing to go! Now, what were
those other things??? --
Will Honea <whonea@codenet.net>