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

Troubleshooting


 We are confident that Rescue5 will accurately recover source
 code from the vast majority of CA- Clipper 5 applications.  It
 is however self evident that the number of possible
 combinations of source statements is so large as to be
 effectively infinite, and that there may be versions of linkers
 and/or CA-Clipper that we have not come across.

 Should Rescue5 fail to recover source code for any of the above
 reasons it is our policy that, provided you supply us with a
 copy of the file you are trying to recover the source from, we
 will recover the source code for you.

 Note that this service is conditional on the following:

    . The .EXE, .LIB or .OBJ file concerned has not been
      protected by some password, encryption or scrambling device

    . You have not failed to recover the source code through
      misuse of Rescue5

    . You can prove that own the rights to the source code you
      are trying to recover

 In addition to the above service we will release linker and
 CA-Clipper version upgrades to Rescue5 from time to time.

 Before you contact us, please check the following:

 If CA-Clipper reports errors compiling the recovered code

 1) Ensure (where possible) that the application is being
    re-compiled with the same version of the CA-Clipper compiler
    as it was originally built with.  Note that the library
    version reported in the .RMK file identifies the CLIPPER.LIB
    file it was linked with and not the compiler version.  We
    have encountered legal code that some versions of CA-Clipper
    5 fail to compile, reporting internal errors, but which
    other versions compile without fault.

 2) Check that you have enough free memory and disk space; it is
    possible to get an "out of string space" error with
    CA-Clipper if you do not have enough free memory.

 3) If CA-Clipper reports a macro error when there is no macro
    in sight, try compiling with a different version of the
    compiler (see 1 above).

 4) If you used /r0 to disable line splitting the recovered code
    may have lines that are too long for CA-Clipper to parse.
    Either split the lines manually or use a different /r
    setting.

 If all else fails see the Support section for details of how to
 contact us.

 If there are missing symbols when you try to link the
 application:

 1) Check the source code produced to see if any initialisation
    procedures exist for RDD's other that DBFNTX.  Link again
    with the appropriate RDD.

 2) You may not have the third party libraries necessary to
    re-link the application.  Identify the libraries you need
    and include them in the link script.