HighMem

Program is distributed as ZIP package: download to temporary directory and unpack to destination folder, better if in PATH.

The various options are:

1. load code high
2. load data high
3. load both code & data high

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."