[Previous] 

6003     Integer divide by 0
This error has occurred on "fast" machines with 200MHz MMX Intel processors, AMD and Cyrix processors, and/or 100Mbit network cards. Error 6001 may also occur. The error is due to timing loops running too quickly. 
Action: Get the patch at "The Oasis" (http://www.the-oasis.net/). The file you need is http://www.the-oasis.net/files/patch/r6003fix.zip 

8002     Indexing error
While indexing, ordcreate(0) internal error 8002 may appear. It seems to appear mostly with CA-Clipper 5.3 programs linked with ExoSpace and running under Windows 95, although it has also been reported under Windows 3.1, and with CA-Clipper 5.2e and 5.01, and linked with Blinker. Typically, the error occurs on "larger" files (e.g. >10MB or 80,000 records), although that is not always the case. 
It has been reported that the 8002 error occurs unders the German version of CA-Clipper 5.3a during a section of code that opens and closes many tables repeatedly. 
When the error occurs with a Blinker-linked program under Win95, the program terminates with an Windows exception error. With an ExoSpace-linked program the 8002 error appears. 
The ExoSpace link option "EXOSPACE PACKAGE NOVM" disables the VMM system so that when Clipper uses up all available physical memory it will cause either error 8002 or "Conventional memory exhausted". It is not recommended for normal applications, although it may be appropriate for installation programs. Blinker has a similar link option available. 
Internal error 8002 may also be caused by an error in custom C or ASM code which allocates memory and then does not release it properly. 
The Windows memory system may interfere with CA-Clipper's Virtual Memory Manager, causing the error. It is not known whether the problem is limited to the DBFNTX RDD, or occurs in other (all) RDDs. 
Action: Try one or more of the following: 
1) Try increasing the available Virtual Memory to the CA-Clipper programs. Include in the SET CLIPPER environment variable the option:
   //VMSIZE:16834
For example:
   set CLIPPER=//F:99 //VMSIZE:16834
Try using different (smaller) values for //VMSIZE. The //F:99 value is just an example - you may have something different. 
2) The program may need more stack space. You can adjust the amount of stack space with the following:
   In RTLINK: add /STACK:sizeBytes
   In BLINKER: add STACK sizeBytes
The default value of sizeBytes is around 5000. Try increasing it to 8192. 
3) Use the OPTEDIT program with the EXTRAMIN switch. The Option Editor, OPTEDIT.EXE, is a utility that allows you to change the behavior of your CA-Clipper applications which have been linked using ExoSpace.
EXTRAMIN values of 4096 and 8000 have been reported as successful. To reserve 4MB of memory:
  OPTEDIT appname -EXTRAMIN 4096
The OPTEDIT program can be found on The Oasis at: http://www.the-oasis.net/files/patch/ca_clipper_mirror/opt_53.zip 
4) An ExoSpace application can run out of virtual memory if Windows runs out of virtual memory. Try increasing the maximum size of the Windows swap file.
 

8009     Unknown error
This error has been reported in an application that uses the FiveWin library, while attempting to open a file. No other details are known at this time. 
Investigations are ongoing. 
See Also: Some of the techniques in solving Error 8002 may help. 

9001     Database RDD failed to load
The runtime system has failed to detect an RDD loaded in an application that requires one. 
Action: Refer to Actions and Notes under Error 999 and Error 1011. Check third party .LIBraries for compatibility and version. Check link script and order. Look for missing RDD .LIBrary or .OBJ files. The .EXE may be invalid. 
See Also: "Linking" and "Debugger" chapters of the Programming and Utilities Guide. 

9002     RDD invalid or not linked
The runtime system has failed to detect a matching RDD loaded for the database and indices used in the application. 
Action: Make sure the database header is correct. Recreate the indices. Refer to Actions and Notes under Error 999 and Error 1011. Check third party .LIBraries for compatibility and version. Check link script and order. Look for missing RDD .LIBrary or .OBJ files. The .EXE may be invalid. 
See Also: "Linking" and "Debugger" chapters of the Programming and Utilities Guide. 

9005     Unable to load database table
The runtime system has failed to load the database table for use with an RDD, or the RDD failed to load or is unavailable. 
Action: Use a utility to test the database header integrity. Refer to Actions and Notes under Error 999 and Error 1011. Check third party .LIBraries for compatibility and version. Check link script and order. Look for missing RDD .LIBrary or .OBJ files. The .EXE may be invalid. 
See Also: "Linking" and "Debugger" chapters of the Programming and Utilities Guide. 

9006     DBFNTX RDD index buffer access error
The runtime system has failed to detect an RDD loaded in an application that requires one. 
Action: Check third party .LIBraries for compatibility and version. Check link script and order. Look for missing RDD .LIBrary or .OBJ files. The .EXE may be invalid. 
See Also: Error 999, Error 1011, "Linking" and "Debugger" chapters of the Programming and Utilities Guide. 

9999     Invalid .EXE caused by RDD unavailable at startup
The runtime system has failed to detect an RDD loaded in an application that requires one. 
Action: Check third party .LIBraries for compatibility and version. Check link script and order. Look for missing RDD .LIBrary or .OBJ files. The .EXE may be invalid. 
See Also: Error 999, Error 1011, "Linking" and "Debugger" chapters of the Programming and Utilities Guide. 

----     VM Integrity failure
This error indicates a misuse of the VM System has occurred by either an internal or external (third-party) subsystem. 
Action: Test the following suggestions to help eliminate the problem: 
1) Check for memory conflicts that could result in virtual memory corruption. 
2) Check for incorrect data type passed to the IAMBS (VMM) or a GET instance variable. 
3) Check third party .LIBraries for compatibility and version. 
4) Test using a simple .LNK script to create the .EXE. 
5) Resolve 100% of all warnings and errors occurring at link time. Link with VERBOSE while redirecting to an error output file. 
6) Attempt to extract a test without using built-in, add-on, or third party .LIBrary functions, and see if the error still occurs. 
7) Create a protected mode version of the application linking with MAP S, N, A. Identify the runtime address reported by comparing it with the named module for the most closely matched address listed in the .MAP file. 
See Also: Error 999, Error 5302, "Linking" and "Debugger" chapters of the Programming and Utilities Guide, "VM API" in the Technical Reference Guide.


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 2000/02/01
All trademarks contained herein are the property of their respective owners