Hi Vadim!

[..]
 VB> Next my program stops with a system error "there are not
enough memory". 
 VB> 1) How can I know if my program has got a virtual, not a physical memory? 
You'll never know. This is exactly the advantage of a virtual memory system.

 VB> 2) Why xalloc exception do not thow to me? 
With the standard setup for the memory manager, OS/2 will NEVER give you a
ERROR_NOT_ENOUGH_MEMORY for a DosAllocMem request. It grows the swapfile
and if it reaches it's maximum size, HARDERR will offer you a dialog to
terminate your application. Unless you set MEMMAN=NOSWAP (anything but
recommended for the normal user :) you won't be able to catch the Borland
Runtime Exception as the runtime itself won't get ERROR_NOT_ENOUGH_MEMORY.

The "there are not enough memory" message you got indicates that
the system ran out of page table entries. For Intel boxes you have 8192
page table entries (GDT) of which already about 4000 are occupied when OS/2
is booted (depending on other applications running). So if Borland's
Runtime Heap Manager doesn't properly keep track of it's objects, it
trashes the system page table.

     __
     |_)
cu/2 |atrick
[Team  OS/2]

--- FleetStreet 1.18+