Click above to get retro games delivered to your door ever month!

/ou                     Place overlay pool in upper memory block (UMB).
---------------------------------------------------------------------------------

 Description:

 This option places the overlay pool in an Upper Memory Block, using
 the specified overlay pool size (/op).  If there is not enough room or
 UMBs are not supported on the machine running the overlaid program,
 conventional memory will be used.  All UMB memory allocated for use
 by /ou is automatically freed at program termination.

 If you have specified an overlay pool size with a minus '-' sign to leave
 a specified amount of memory free, the /ou option operates a bit
 differently since it is not allocating conventional memory.  In these
 cases, the WarpLink overlay manager will allocate three times the largest
 overlay size for the overlay pool in upper memory.

 The /ou option has lower priority than the /ox option if both are
 specified and enough free EMS is available to use the EMS page frame
 for the overlay pool.  If you specify both the /ox and /ou option, upper
 memory blocks will only be used for the overlay pool if the /ox EMS
 test fails.  You may wish to specify both options if your program will be
 operating on a mix of machines that may have either EMS or UMB
 memory.  Whichever type of memory is available will be used for the
 overlay pool, with EMS tried first.

 Technical Notes:

 MS-DOS 5.0 and above uses a different UMB allocation scheme than the
 XMS UMB-allocation standard when you use the command DOS=UMB
 in your CONFIG.SYS file.  The WarpLink overlay manager will attempt
 to detect this and allocate UMB's for the overlay pool using the alternate
 MS-DOS scheme.  If you experience problems using UMB's with MS-
 DOS 5.0 or above, try removing the DOS=UMB command in your
 CONFIG.SYS file.

 Free UMB space is not always noncontiguous.  For example, your
 computer may have 100K of free UMB space, but it may be split up into
 two 50K blocks.  If the overlay pool requires more than 50K in this
 situation, UMB's cannot be used and the overlay manager will place the
 overlay pool in conventional memory.

 Clipper 5 User Note:

 If you use the /ou option, the Clipper 5 debugger CLD.EXE will not function
 with your program.  Use WarpMod to turn the option on and off quickly, if
 necessary.