After reading the latest issue of Voice News Letter, about virtual memory limitations and how to improve OS/2 operation under its restrictions, I decided to change my MEMMAN configuration on CONFIG.SYS to "NOSWAP,PROTECT" and it seems Sentinel Memory Watcher on eCenter/xCenter just cannot understand my memory usage anymore.
This machine has 2GB of RAM and, after tweak the CONFIG.SYS the usagem by Sentinel shows the following:
Free RAM: 383KB
Used RAM: 2.086.385 KB
Swapper size: 2.048 KB
But this is, of course, not true. Free RAM was about 400KB before I opened FireFox and now it is 383KB. Using SysInfo/2, I received the following:
RAM Used: 387.3 Mb
RAM Free: 1.6 Gb
SWAP Used: 0.0 Kb
SWAP Free: 0.0 Kb
Which makes much more sense. Anyone has ever had this kind of issue?
Is it possible that Sentinel is not capable of parsing out the numbers to that many digits, and is instead reporting the non-zero values to the maximum number of places it can? IE, KB instead of MB or GB.
Have you tried using the Free Physical Memory Monitor widget in eCenter, that always reports properly for me with 2gb of RAM.
djc:
The problem (I THINK) is related to having a swap file, and telling the OS not to use it. Some of the memory APIs do weird things.
The "solution" I have used is to figure out what the offset is (ie: let's assume that free RAM is off by 1GB, I modify the widget code to add 1GB to it).
The odd thing I have found is that changing swap size in such scenarios changes the offset in an unexpected way. Dunno if you can modify the Sentinel Code... but you could create your own widget that calls the REXX calls from something like RXU or so to write your own. RXU and the other packages that report back memory usage seem to vary in their implementation - which will probably (under your circumstances) require some "tweaking" with offsets so memory amounts are properly displayed.
The SWAPPATH statement, unfortunately, requires a minimum value of at least 512 for the first parameter...
-Rob