Error messages


 Rescue5 errors take the form:

    Error: <number> <message> [<information>]

 Errors are displayed on the screen and written into the ERROR
 file (if possible).

 If you encounter an error, please take the recommended action.

 Command line errors

 Invalid switch

   You specified a command line switch Rescue5 does not
   recognise.

 Multiple filename ignored

   You specified more than one .EXE file on the command line.
   Only the first filename is used.

 Invalid directory specified

   The directory specified by /o was not valid.

   Ensure the directory exists then run Rescue5 again.


 <.EXE name>.GRP errors

 Invalid function name

   A symbol name was specified in the <.EXE name>.GRP file
   and/or <.EXE name>.VAR file that does not exist, or requires
   a static function qualifier (i.e. fname(123)).

   Check the grouping and variable files, correct the problem
   then run Rescue5 again.  If all else fails, run Rescue5 with
   the /1 switch to force it to recreate the <.EXE name>.GRP and
   <.EXE name>.VAR files.

 Duplicate groups

   The same group has been defined more than once.

   Remove one of the groups, redistributing its contents if
   necessary, then run Rescue5 again.  If all else fails, run
   Rescue5 with the /1 switch to force it to recreate the <.EXE
   name>.GRP and <.EXE name>.VAR files.

 Attempt to group static frames together

   A group has been defined with more than one static frame
   (i.e. [6] [8]).

   Split the static frames across groups, one to each group,
   then run Rescue5 again.  If all else fails, run Rescue5 with
   the /1 switch to force it to recreate the <.EXE name>.GRP and
   <.EXE name>.VAR files.



 <.EXE name>.VAR errors

 Unknown identifier in variable file

   '(LOCAL)', '(BLOCK)' or '[]' was expected.  Something else
   was supplied.

   Check the variable file, correct the problem then run Rescue5
   again.  If all else fails, run Rescue5 with the /1 switch to
   force it to recreate the <.EXE name>.GRP and <.EXE name>.VAR
   files.

 Invalid function name

   A symbol name was specified in the <.EXE name>.GRP file
   and/or <.EXE name>.VAR file that does not exist, or requires
   a static function qualifier (i.e. fname(123)).

   Check the grouping and variable files, correct the problem
   then run Rescue5 again.  If all else fails, run Rescue5 with
   the /1 switch to force it to recreate the <.EXE name>.GRP and
   <.EXE name>.VAR files.



 VARIABLE.UDT and user defined type file errors

 GenericBaseNames already declared

   More than one GenericBaseNames section has been defined in
   the same user defined type file (multiple GenericBaseNames
   sections are allowed, but each must be in a different file).

   Merge the sections into a single section or split the
   sections into files, one to a file, and @ include them.

 Usertype file not found

   The file specified with the @ command cannot be found.

   Check that the file exists in the path specified, or use the
   /i switch to tell Rescue5 where it is.

 No generic types have been defined

   The GenericBaseNames: section is missing.

   There must be at least one GenericBaseNames:  section in one
   of the user defined type files.

 Type not defined in GenericBaseNames

   Rescue5 encountered a variable base name in the
   FunctionBaseNames: section that uses a type prefix not
   defined in the GenericBaseNames:  section.

   Add a variable base name with the correct type to the
   GenericBaseNames: section.

 Unknown header in user defined type file

   Rescue5 encountered an identifier other than
   GenericBaseNames: or FunctionBaseNames:.

   Remove or correct the spelling of the identifier concerned.



 .EXE file errors

 Protected .EXE <.EXE name>

   The .EXE has been protected against decompilation.

   If you can prove that you have the right to recover the code
   from the .EXE in question, contact us.  We may be able to
   recover the code for you.

 Unrecognised .EXE format <.EXE name>

   Rescue5 does not recognise this .EXE format because of one or
   more of the following:

    . It was linked with a linker or linker version currently not
      supported by Rescue5.
    . It has been encrypted.
    . It is corrupt.
    . It is not a Clipper 5.x .EXE file.

   Check the above.  If you are sure that Rescue5 should be able
   to recover the code from this .EXE file, report this error
   and supply us with a copy of the .EXE file.

 Unrecognised Blinker .EXE format <.EXE name>

   The .EXE is in Blinker format but was linked with a version
   of Blinker currently not supported by Rescue5 (or possibly a
   Blinker-like linker we have not come across).

   Please report this error and supply us with a copy of the
   .EXE file.

 Unrecognised RTlink .EXE format <.EXE name>

   The .EXE is in RTlink format but was linked with a version of
   RTlink currently not supported by Rescue5 (or possibly an
   RTlink-like linker we have not come across).

   Please report this error and supply us with a copy of the
   .EXE file.


 Memory errors

 Not enough free memory

   You have less than 500Kb of conventional memory free.

   Free some more conventional memory and try again.

 Not enough memory for VM (Try freeing n bytes)

   Rescue5 just needs a little bit more conventional memory...

   Free some more conventional memory and try again.

 Unable to allocated Fixed Memory

   Conventional memory is either exhausted or has become too
   fragmented for Rescue5 to continue.

   Change your memory setup and run Rescue5 again.  If the error
   persists, please report it.

 Unable to allocate Virtual Memory

   Virtual memory is either exhausted or has become corrupt.

   Change your memory setup and run Rescue5 again.  If the error
   persists, please report it.

 Disk errors

 Can't open file
 Can't create file
 Insufficient disk space available

   Rescue5 has been unable to perform a file operation.

   Check your MS-DOS environment (disk space, write protection
   etc).

 Illegal stack reference

   Memory has become corrupted.

   Change your memory setup and run Rescue5 again.  If the error
   persists, please report it.


 Decompilation errors

 Code generation error

   One of Rescue5's internal parsing rules has been violated.

   This could be caused by a failed link producing a corrupt or
   incomplete .EXE file.  Please report this error and supply us
   with the .EXE file.

 Static frame or ID mismatch

   Rescue5 has encountered a static function that has been
   called but does not exist in the .EXE file.

   This could be caused by a failed link producing a corrupt or
   incomplete .EXE file.  Please report this error and supply us
   with the .EXE file.