Internal Error # 8002
 ExoSpace: Couldn't allocate VMM
──────────────────────────────────────────────────────────────────────────────────

 Internal error 8002 means the Clipper program couldn't allocate virtual
 memory it needed.  Currently ExoSpace defaults to an 8 MB virtual size
 which means it can allocate up to 8 MB of virtual memory.  It defaults to
 8 MB.  You can increase the virtual memory size to 16 MB by specifying
 "//VMSIZE:16000" in the Clipper environment variable.  The user can burn
 in this setting with the "EXOSPACE EXECUTABLE CLIPPER" command.

 Internal error 8002 can happen under Windows when it runs out of swap
 space. The Windows Control Panel controls the Windows swap file. ExoSpace
 asks Windows for virtual memory starting with 2 MB at startup and
 additional memory as it needs it.  The total amount of virtual memory is
 equal to the amount of free memory plus the maximum size of the swap file
 as set in the Control Panel. Thus an ExoSpace application can run out of
 virtual memory if Windows runs out of virtual memory.  To fix the problem,
 simply increase the maximum size of the swap file.

 Internal error 8002 can be caused when "EXOSPACE PACKAGE NOVM" is
 specified. This option is not recommended because it disables the VMM
 system and means that when Clipper uses up all available physical memory
 it will cause either error 8002 or the "Conventional memory exhausted"
 error.

 Internal error 8002 can also mean there is a bug in some C/ASM code which
 is allocating memory, but never releasing it when it is done with it.

 Regarding the 8002 error, try setting VMSIZE higher.

 (Jon Cole [ObjecTech] 73320,732)