A small utility that allows you to mark libraries so that they are loaded in "high memory".
A note about the future of ecsoft2.org
ecsoft2.org runs on software (Drupal 7 and PHP 7.4) that reached its end of life years ago and no longer receives security updates. Keeping the site online safely is getting harder.
Giving it a future means migrating it to a current platform — and that is only worth doing if people still use it and want to help keep it alive.
If you care about ecsoft2.org, as a user, a contributor, or someone willing to lend a hand, please ggamba
tiscali [dot] it (get in touch) by January 31, 2027.
If no one comes forward by then, the site will be turned into a read-only archive, so that its content stays available.
This program is installable using the rpm package manager. See below for the install string. Required prerequisites are automatically processed by the package manager and, if needed, downloaded and installed.
yum install highmem
yum install highmem-debuginfo
Program is distributed as ZIP package: download to temporary directory and unpack to destination folder, better if in PATH.
The various options are:
According to Lars (http://www.os2world.com/forum/index.php?topic=1466.msg14540#msg14540 ):
"Loading code high should almost always be ok. That's because loading code high is mostly transparent to applications: it's the kernel's job to map high addresses to the physical memory where the code resides. Unless some code tries to map a linear code address (aka: a function pointer) to a segmented code address, see below but that does not happen very often.
For loading data high this is much more critical: of course, the same applies as for code but remember "thunking"? A lot of APIs make the silent assumption that a linear data address can be easily mapped to a segmented address and vice versa by a simple well known "thunking" algorithm. However that algorithm only works for "low memory". And OS/2 has enough 16-bit code in its bowels that can only access data via a segmented data address. If you have a big application like Firefox you never know if there is some low level OS component that makes that simple assumption, thunks a data address and subsequently gets it wrong if "high memory" data addresses are used."

This work is licensed under a Creative Commons Attribution 4.0 International License.
Add new comment