[Previous] 

612    EVAL() given something other than codeblock.
A data type other than a codeblock was supplied as the first argument to eval(). 
A common cause is linking in an old ERRORSYS.OBJ file from a Summer '87 application -- even if it was recompiled with 5.x. Check the source code for the correct calling conventions. 
In a custom ERRORSYS procedure, not setting ERRORBLOCK() or committing an error prior to setting ERRORBLOCK() will force this error. 

650    Out of stack space
This error is often the result of another error -- CA-Clipper encounters an error while it is trying to handle the first error. 
Action: Some suggestions to resolve the problem are: 
1) Use STACK or PROCEDURE DEPTH command to instruct the linker to increase the stack space at link time. 
2) Check for recursion. Some modifications to the CA-Clipper ERRORSYS.PRG may cause a recursive call, which will exhaust the call stack. 
3) Try using the default CA-Clipper ERRORSYS.PRG if the ERRORSYS.PRG was modified, in order to test for runaway recursion caused by an error occurring while attempting to handle an Error object. 
4) Check for UDFs/.PRGs that have the same name as an internal CA-Clipper function. 
5) Check for use of an incorrect or invalid version of the ERRORSYS.PRG. i.e., the Summer '87 CA-Clipper ERRORSYS.PRG does not use an Error object. 

666    C Function Attempt to Free Invalid Pointer
Indicates that a C function attempted to free an invalid pointer. 

667    Eval stack crashed
The evaluation stack (containing LOCAL variables, etc.) and/or MEMVAR table has grown too much and crashed into a locked VM segment in near memory. The system has run out of memory because the VM system only locks segments near the evaluation stack when the memory is very old. 
Action: Some suggestions to resolve this problem are: 
1) Decrease the STACK or PROCEDURE DEPTH setting for the linker. 
2) Decrease the number of LOCAL, STATIC or PRIVATE variables in use at one time. i.e., use arrays instead of individual variables. 
3) Decrease the number of ITEMS allocated if using ITEM.API of CA-Clipper. 
4. Free more conventional memory for use by the VM System. 
Note: There could also be an error in the runtime error handler. 
See Also: Error 650. 

668    Runtime error handler error (eval stack fault)
There could be an error in the runtime error handler. It is calling itself until the stack overflows. 
The evaluation stack expanded into a locked VMM segment. The CA-Clipper VM System will use the DGROUP Free Space when conventional DOS memory is very low. 
Action: Free up conventional DOS memory by reducing the application's load size and/or increasing free DOS memory as reported by DOS's MEM.EXE command. 
See Also: Error 650. 

669    Cannot expand MEMVAR table (eval stack fault)
The MEMVAR table expanded into a locked VM Segment. The CA-Clipper VM System will use the DGROUP free space when conventional DOS memory is low. 
Action: Free up conventional DOS memory by reducing the application's load size and/or increasing free DOS memory as reported by DOS's MEM.EXE command. 
Note: There could also be an error in the runtime error handler. 
See Also: Error 650. 

670    Memory initialization error
An error has occurred during the initialization or re-initialization of the memory system. This error usually indicates an extremely low memory condition at startup, or that an application that was RUN from within CA-Clipper allocated DOS memory without freeing it. 
Action: If the error occurred at startup, more conventional memory should be made available for the application. If it occurred immediately following the RUN command, the application that was run should be eliminated to see if this solves the problem. 
This problem may also occur with an improperly linked or corrupted application. 

701    Unable to locate keyboard driver upon startup.
Check to see if the latest PLL link script file was used to build the PLL, that the latest libraries are used, and no third-party libraries are linked. Determine that the .EXE is not corrupted. 

702    Keyboard driver I/O error upon startup
The keyboard detected was not compatible for I/O access. 
Action: Make sure the latest CA-Clipper libraries are used, and that no third-party libraries are linked. Determine that the .EXE is not corrupted. Determine if the keyboard may be accessed from the DOS prompt. 

703    Unable to locate display driver upon startup
Action: Make sure the latest CA-Clipper libraries are used, and that no third-party libraries are linked. Determine that the .EXE is not corrupted. 

704    Screen display driver I/O error upon startup
The CRT detected was not compatible for I/O access. 
Action: Make sure the latest CA-Clipper libraries are used, and that no third-party libraries are linked. Determine that the .EXE is not corrupted. Determine if the screen may be accessed from the DOS prompt. 

705    Unable to determine disk drivetype upon startup
Action: Make sure the latest CA-Clipper libraries are used, and that no third-party libraries are linked. Determine that the .EXE is not corrupted. 

706    Disk drivetype I/O error upon startup
The disk detected was not compatible for I/O access. 
Action: Make sure the latest libraries are used, and that no third-party libraries are linked. Determine that the .EXE is not corrupted. Determine if the disk may be accessed from the DOS prompt. 

715    Printer not ready.
Action: Make sure the latest libraries are used, and that no third-party libraries are linked. Determine that the link instructions are valid and the .EXE is not corrupted. Determine the printer may be accessed from the DOS prompt. 

773    Dynamic overlay system not linked in.
This may indicate an invalid link line or a corrupted executable file. Action: Make sure the latest libraries are used. Determine that the link instructions are valid and the .EXE is not corrupted. Confirm that the memory configuration did not affect linking. Perhaps a third-party library (maybe written in C) contains functions that conflict with the ones in the memory manager. 

998    Missing function
CA-Clipper has attempted to execute a function or UDF that is not recognized as valid CA-Clipper code. This error can occur if an attempt is made to execute code compiled with a new version of CA-Clipper under an older version, or because of a corrupted or invalid executable. 
Action: Make sure that all code is compiled under the same version of CA-Clipper, and is being linked with the correct version of the libraries. If a third-party linker is used, see if the error occurs when using the real mode linker for CA-Clipper. If a corrupted executable is suspected, recompile all .OBJ files and relink. Declare UDFs or built-in functions that are hidden from the compiler (in macro or INDEXing commands) with REQUEST if they are not called elsewhere in the code. Link in missing .OBJs. Make sure all linker warnings and errors are resolved. 

999    Attempt to execute invalid code
CA-Clipper has attempted to execute something that it doesn't recognize as valid CA-Clipper code. This error can occur if an attempt is made to execute code compiled with a new version of CA-Clipper under an older version, or because of a corrupted or invalid executable. 
Make sure that all code is compiled under the same version of CA-Clipper, and is being linked with the correct version of the libraries. If a third-party linker is used, see if the error occurs when using RTlink for CA-Clipper or CA-Clipper/Exospace or Blinker. 
If a corrupted executable is suspected, recompile all .OBJ files and relink.
[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