ArcaOS 5.0 Russian
Russian ARCAOS exists and it's available since the middle of 2017. All versions are supported: 5.0, 5.0.1, 5.0.2.

eCo Software is able release OS/2 LIP packages for any other language (German, Dutch, Brazilian Portuguese, Spanish, Sweden, etc)

.... .. ...... ........ ................ . DOS - ......, . ...... .. ......... ...... ........ .. .... ..... ........ ...... ........., ....... .. ......... ......, ...... . ....... .. ......... ........ - ... ... ........ ..... ....... . .......... .... .. ......... ... ......., ........ .., ............ ............... ...... ... ................ . ............ ...... . ........... ....... (. . ....... ........... . OS/2) ... ... .......... .. ..... ...... .. ... ..., .... ....... ...... .. ............ . ....... ......... ............ ......... (... ....... ...... OS/2 - ..... 512 .........., . ....... ....... .............. ..........). ........ ... ......... ....., . ..... ..... .. ......... ... ....., ......, ..... ................... ..........:

int fd = open (filename,mode);
long size_of_file = filesize(fd);
char * input = malloc(size_of_file);
read(fd, input, (unsigned) size_of_file);

(.. ........, ... ... - 32-....... ..., . ........ sizeof ........ ......... ....... read ..... 4, ... . ........ long)

19 Maximum number of bytes of memory that can be allocated by all processes in the system 529948672

20 Maximum number of bytes of memory that this process can allocate in its private arena. 318111744

21 Maximum number of bytes of memory that a process can allocate in the shared arena. 193331200

19 Maximum number of bytes of memory that can be allocated by all processes in the system 2068279296

20 Maximum number of bytes of memory that this process can allocate in its private arena. 271450112

21 Maximum number of bytes of memory that a process can allocate in the shared arena. 231538688

A new config.sys parameter, VIRTUALADDRESSLIMIT, has been added to specify the highest virtual memory address that may be accessed. The default value for OS/2 Warp Server for SMP is 2 GB, which is specified in megabytes in the command argument:

VIRTUALADDRESSLIMIT=2048

The smallest value allowed is 512, which provides compatability with previous versions of OS/2 which only allowed access to 512 MB. The largest value supported is 3072 (3 GB). The VIRTUALADDRESSLIMIT parameter may be specified as part of selective install.

Values in excess of 512 will reduce the number of processes that can concurrently run on the system. When memory has been exhausted, OS/2 control program functions will fail with ERROR_NOT_ENOUGH_MEMORY and PM functions will fail with PMERR_INSUFFICIENT_MEMORY.

This information can be found in the SMP programming addendum, shipped as part of the Warp SMP toolkit (SMP.INF).

26 Number of processors in the machine 1

27 Maximum amount of free space in process's high private arena 2348810240

28 Maximum amount of free space in process's high shared arena 2348810240

29 Maximum number of concurrent processes supported 172

30 Size of the user's address space in megabytes 3072

VisualAge C++ now gives you the option of creating and using your own pools of memory, called heaps. You can use your own heaps in place of or in addition to the default VisualAge C++ runtime heap to improve the performance of your program. This section describes how to implement multiple user-created heaps using VisualAge C++.

Note: Many readers will not be interested in creating their own heaps. Using your own heaps is entirely optional, and your applications will work perfectly well using the default memory management provided (and used by) the VisualAge C++ runtime library. If you want to improve the performance and memory management of your program, multiple heaps can help you. Otherwise, you can ignore this section and any heap-specific library functions.

#include
Heap_t _ucreate(void *block, size_t initsz, int clean, int memtype,
void *(*getmore_fn)(Heap_t, size_t *, int *)
void (*release_fn)(Heap_t, void *, size_t);

Language Level: Extension

_ucreate creates your own memory heap that you can allocate and free memory from, just like the VisualAge C++ runtime heap.

Before you call _ucreate, you must first get the initial block of memory for the heap. You can get this block by calling an OS/2 API (such as DosAllocMem or or DosAllocSharedMem) or by statically allocating it. (See the CP Programming Guide and Reference for more information on the OS/2 APIs.)
Note: You must also return this initial block of memory to the system after you destroy the heap.

• block The pointer to the initial block you obtained.
• initsz The size of the initial block, which must be at least _HEAP_MIN_SIZE bytes (defined in). If you are creating a fixed-size heap, the size must be large enough to satisfy all memory requests your program will make of it.
• clean The macro _BLOCK_CLEAN, if the memory in the block has been initialized to 0, or !_BLOCK_CLEAN, if the memory has not been touched. This improves the efficiency of _ucalloc; if the memory is already initialized to 0, _ucalloc does not need to initialize it.
  • Note: DosAllocMem initializes memory to 0 for you. You can also use memset to initialize the memory; however, memset also commits all the memory at once, an action that could slow overall performance.
• memtype A macro indicating the type of memory in your heap: _HEAP_REGULAR (regular) or _HEAP_TILED (tiled). If you want the memory to be shared, specify _HEAP_SHARED as well (for example, _HEAP_REGULAR | _HEAP_SHARED). Tiled memory blocks will not cross 64K boundaries, so the data in them can be used in 16-bit programs. Shared memory can be shared between different processes. For more information on different types of memory, see the Programming Guide and the Control Program Guide and Reference.
  • Note: Make sure that when you get the initial block, you request the same type of memory that you specify for memtype.
• getmore_fn A function you provide to get more memory from the system (typically using OS/2 APIs or static allocation). To create a fixed-size heap, specify NULL for this parameter.
• release_fn A function you provide to return memory to the system (typically using DosFreeMem). To create a fixed-size heap, specify NULL for this parameter.

If you create a fixed-size heap, the initial block of memory must be large enough to satisfy all allocation requests made to it. Once the block is fully allocated, further allocation requests to the heap will fail. If you create an expandable heap, the getmore_fn and release_fn allow your heap to expand and shrink dynamically.

When you call _umalloc (or a similar function) for your heap, if not enough memory is available in the block, it calls the getmore_fn you provide. Your getmore_fn then gets more memory from the system and adds it to the heap, using any method you choose.

Your getmore_fn must have the following prototype:

void *(*getmore_fn)(Heap_t uh, size_t *size, int *clean);

where:

• uh Is the heap to get memory for.
• size Is the size of the allocation request passed by _umalloc. You probably want to return enough memory at a time to satisfy several allocations; otherwise, every subsequent allocation has to call getmore_fn. You should return multiples of 64K (the smallest size that DosAllocMem returns). Make sure you update the size parameter if you return more than the original request.
• clean Within getmore_fn, you must set this variable either to _BLOCK_CLEAN, to indicate that you initialized the memory to 0, or to !_BLOCK_CLEAN, to indicate that the memory is untouched.

Note: Make sure your getmore_fn allocates the right type of memory for the heap.

When you call _uheapmin to coalesce the heap or _udestroy to destroy it, these functions call the release_fn you provide to return the memory to the system. function.

Your release_fn must have the following prototype:

void (*release_fn)(Heap_t uh, void *block, size_t size);

The heap uh the block is from, the block to be returned, and its size are passed to release_fn by _uheapmin or _udestroy.

For more information about creating and using heaps, see the "Managing Memory" in the Programming Guide.

Return Value: If successful, _ucreate returns a pointer to the heap created. If errors occur, _ucreate returns NULL.