[Previous]

5003     Bad block index
This error has occurred in a CA-Clipper 5.3b application which was compiled with Exospace. Random crashes occur under Dos 6.22 on machines with 8MB of RAM and HIGHMEM.SYS loaded. 
This error might be due to corruption of the VM (Virtual Memory) system by bad memory chips or conflicting software drivers. The error message could be interpreted as "the table (index) that manages blocks of virtual memory has gone bad". 
Investigations are ongoing. 
Action: Try using:
   SET CLIPPER=//BADCACHE


5211     SWAPFILE creation error
The virtual memory (VM) subsystem is unable to create a swap file on disk. 
See Also: Error 5311, "The Runtime Environment" chapter of the Programming and Utilities Guide.


5302     Conventional memory exhausted
This is an "out of memory" message that indicates that the CA-Clipper application no longer has sufficient conventional memory (below 640K) available to continue. 
Specifically, this error occurs when the virtual memory system attempts and fails to bring a VM segment into conventional memory that had been swapped out to disk or expanded memory. 
Action: Make more conventional memory available to the VM system. This can be done in several ways: 
1) Increase the amount of conventional memory available before running the application -- remove TSRs, make use of 386 memory manager, etc. 
2) Use a third-party linker that can dynamically overlay C and assembly-language code. C and ASM are not automatically overlaid by RTlink and therefore sit in conventional memory throughout the execution of the application. 
3) Ensure that any C or ASM code in use is making use of the virtual memory system if it is doing dynamic memory allocation. Any memory allocated using the Fixed Memory Allocator functions _xalloc() and _xgrab() reduces the amount of conventional memory available if it is not immediately freed. 
See Also: "VM API" chapter of the Technical Reference Guide.


5304     Conventional Memory Exhausted
This is an "out of memory" message that indicates that the CA-Clipper application no longer has sufficient conventional memory available to continue. 
Specifically, this error occurs when a function attempts to allocate conventional memory and fails. This error can be received as a result of the failure of _xgrab() in Extend System functions. 
Action: See action for 5302.


5305     VM Swap Space Exhausted
There is insufficient room in the VM swap area in real memory to load virtualized data. This only occurs in the undocumented internal function _vmTwo(). The CA-Clipper runtime issues calls to the _vmTwo() function when it must obtain two de-referenced virtual memory handles concurrently. Typically, _vmTwo() is useful for string operations such as copy or comparison. 
See Also: Error 5302, "VM API" chapter of the Technical Reference Guide.


5306     Conventional Memory Exhausted
This is an "out of memory" message that indicates that the CA-Clipper application no longer has sufficient conventional memory available to continue. 
Specifically, this error occurs when the virtual memory system attempts and fails to bring a VM segment into conventional memory that has been swapped out to disk or expanded memory. 
Action: See action for 5302.


5311     VMM Unable to Create Swap File
The virtual memory (VM) subsystem is unable to create a swap file on disk. This occurs for several reasons, including: 
1) The target disk is full; 
2) The target directory is full; 
3) Insufficient file handles are available; 
4) An invalid path is specified in the SWAPPATH parameter of the CLIPPER environment variable, or on the command line used to start the application; or 
5) The user has insufficient rights on a network drive to create the file. Without a SWAPPATH variable, the current directory will be used. This may be a network directory if the application is started from a network. 
See Also: "The Runtime Environment" chapter of the Programming and Utilities Guide.


5312     VM Swap File Overallocated
This is an "out of memory" message that indicates that the CA-Clipper application no longer has sufficient virtual memory available to continue. 
Specifically, this error occurs when the virtual memory system needs to swap a virtual memory segment out of conventional memory, and it has used all expanded memory and disk space that has been made available to it. 
Action: Make more virtual memory available to the application. This can be done by making more expanded memory available by increasing the E setting of the CLIPPER environment variable, or by making more disk space available by increasing the SWAPK setting of the CLIPPER environment variable. 
This problem can also be resolved by reducing the size and/or number of strings and arrays that are active at any one time. Probably, the most common cause of this error is the declaration of extremely large arrays (e.g., local aArray[4096][4096]). Note that every array element requires memory to store (even if its value is NIL) and that the number of array elements in an array is determined by multiplying the number of elements in every dimension and adding the sum of all dimensions except for the last. For example, a 4096 by 4096 array has (4096x4096)+4096 or 16,781,312 elements. 
Because every array element in CA-Clipper requires 14 bytes, this amounts to 16,781,312x14, or 234,938,368 bytes -- well in excess of the theoretical capacity of the virtual memory system. 
Note: There is no benefit gained by reusing arrays. CA-Clipper is much more efficient when strings and arrays are thrown away and rebuilt often rather than kept around unnecessarily for long durations.


5313     VMM Write Error on Swap File
Write errors typically occur for one of the following reasons: 
1) Disk full; 
2) Bad sector encountered; or 
3) The swap file was deleted by another process within a multitasking environment on a workstation in which the SHARE utility has not been loaded. 
See Also: Error 5311, "The Runtime Environment" chapter of the Programming and Utilities Guide.


5320     VMM IAMBS Manager Error
IAMBS manager is unable to provide more memory, or it encountered an error. Usually associated with indexing or sorting problems. 
Possibly the VMM has tried to map an EMS page when no EMS is available or the EMS manager has returned an error code. 
The documentation for the SIx Driver RDD states that an internal error 5320 will be generated by CA-Clipper when you set the Mach SIx temporary file path to invalid drive or directory. This might apply to other RDDs as well. 
Action: Make more conventional memory available to the VM system and test with a clean environment after a cold boot. 
See Also: Error 5302, "The Runtime Environment" chapter of the Programming and Utilities Guide.


5321    VMM system unable to free EMS page
An error occurred during deallocating EMS page frames. 
Action: Some suggestions to resolve the problem are: 
1) Use the SET CLIPPER=//BADCACHE and/or unload TSRs and device drivers from the upper memory area. 
2) Try a clean boot with a basic CONFIG.SYS and AUTOEXEC.BAT. To find the conflict, add TSRs/device drivers back in until the problem recurs. 
See Also: Error 5302, "The Runtime Environment" chapter of the Programming and Utilities Guide.


5333     Misuse of VM System
This error occurs when there is a misuse of the virtual memory system by either an internal or external (third-party) subsystem. 
The following suggestions may eliminate the problem: 
1) Check to see if the user is assigning an incorrect data type to a IAMBS or GET instance variable. This is a known cause for this error. 
2) If the user is using any third-party libraries, see if the error still occurs without the library. 
3) If the user is using a third-party linker, see if the problem occurs with .RTlink.

[Next]

Home Web Design Programming Fairlight CMI Soap Box Downloads Links Biography About... Site Map

Site Map Send comments about this site to Greg at gregh@ghservices.com
All pages copyright © 1996-1999 GH Services™   Created 1997/09/28   Last updated 1999/09/30
All trademarks contained herein are the property of their respective owners