Decompiling CA-Clipper 5 .EXE .OBJ & .LIB files


 Rescue5 will run faster if you have 1Mb or more of expanded or
 extended memory available and are running disk caching
 software.

  1) Ensure the file called RESCUE.EXE is in your DOS PATH and
     that VARIABLE.UDT is in the same directory as RESCUE.EXE.

  2) To decompile a .EXE file, type:

          rescue <EXE>[.EXE] [/o<out path>] [switches]

     Where:

        <EXE>[.EXE]     Name of the .EXE file to decompile
        [/o<out path>]  Directory in which to write files
        [switches]      Output control switches

     If paths are omitted Rescue5 uses the current directory.

  3) Optionally run Rescue5 a second time with the same command
     line to change the generated local and static variable
     names (which are removed by CA-Clipper during compilation),
     and/or the way code is grouped into source files.

     Rescue5 will recover local and static names from code
     compiled with the CA-Clipper /b switch and always recovers
     private, public and auto (undeclared memvar) variable
     names.

 To decompile .OBJ and .LIB files you must first link them into
 a .EXE file (to decompile all the object modules in a .LIB file
 link the .LIB file as if it were a .OBJ file, including the
 .LIB extension), then follow steps 2 and 3 (above).

 Rescue5 does not require a fully linked file and you can safely
 ignore any linker reported duplicate or missing symbols.