1 REI
                   REI - File Reincarnation Utility 
 
 REI can recover deleted files as well as files from a disk with a corrupted
 index file. The disk can be mounted or dis-mounted. The program allows you to
 specify a UIC and filespec on the command line, including wildcards. It can
 recover deleted or undeleted files. It prompts you for every file and asks
 you where you want to put the recovered one. A separate disk for the
 recovered file, is recommended. 
       
 Usage:  >REI 
         REI>filespec 
       
 REI will ignore parity and bad block errors on the input file. It will print
 out a warning message to warn you that the output file may have some bad data
 in it. 

 For additional help, type AID REI XXXXXX  where XXXXXX is

 INPUT  - Input filespec interpretation   OUTPUT  - Output filespecs & messages
 ERRORS - Error messages                  EXAMPLE - Output example
 
2 INPUT

 REI input:
 
 The input filespec must at least be a device specification. If this is the
 case then every file on the disk (including INDEXF.SYS, 000000.DIR, etc.)
 will match. This is therefore equivalent to ddn:[*,*]*.*;*. If a UIC is
 specified, then only files whose OWNING UIC match will be selected. Note that
 this may not necessarily be the same as the directory that contained the
 file. The file may have been renamed to that directory or copied to that
 directory while under a different UIC. The UIC specification may contain wild
 cards. If no file name is given, the default is ddn:[uic]*.*;*. If a file
 name is specified, it may have wild cards. If no extension is given, it
 defaults to "*". Also if no version number is specified, it defaults to "*". 
 
2 OUTPUT

 REI output:

 When a file that matches the input filespec is found, REI will print a line
 containing the file name, type, version number, file ID, number of blocks
 used and allocated to the file, creation date and time, owning UIC and the
 logical block number of the file header. It will then print:
       
 Enter option or ? > 
       
 At this point, CTRL-Z will exit the program, carriage return will cause REI
 to skip the file just found and search for the next file that matches. A ?
 will display a list of the options. If a filespec is entered, the file just
 found will be copied to the new filespec. 
 
2 EXAMPLE

 REI example: 
       
     >REI 
     REI>VD:[176,107]REI.*;1 
     REI.COR;1 (243,23) 5./5. 11-FEB-83 09:51:06 [176,107] <0,24243> 
     Enter option or ? > 
     REI.VGN;1 (625,3) 44./44. 10-FEB-83 16:25:52 [176,107] <0,24625> 
     Enter option or ? >VD4:REI.SAV 
     Enter option or ? > 
     REI.TSK;1 (652,5) 98./97. 11-FEB-83 10:16:40 [176,107] <0,24652> 
     Enter option or ? > 
     REI.TSK;1 (0,11) 104./103. 10-FEB-83 20:38:43 [176,107] <0,24731> 
     Enter option or ? > 
     REI - Specified input filename not found. 
     REI>^Z 
       
In this example, the first file matched was REI.COR;1. This was not the file
we were interested in so carriage return was entered. The second file was
REI.VGN. We did want to copy this file so a file specification was entered
and the file was copied to VD4:[176,107] with a new name of REI.SAV. Then
return was entered to look for the next matching file. Note that there are
two REI.TSK;1's but the second one has a file number of 0 in its file ID.
This indicates that it is a deleted file. When REI has searched the entire
disk and finds no more files that match, it will print the last message in
the example and prompt for another input line. 
2 ERRors 
     1.  Syntax error. 
         The command line contained more than one  filespec,  an  equal 
         sign or the output filespec was syntactically incorrect. 
 
     2.  Syntax error in input file spec. 
         The input filespec did not contain a device  specification  or 
         was not syntactically correct. 
 
     3.  Input device not assignable. 
         The ALUN$ (assign lun) failed for the input device  specified. 
         It was probably an invalid device. 
 
     4.  Syntax error in output file spec. 
         The output filespec was not syntactically correct. 
 
     5.  Error reading input device:  FCS (-nn). 
         A read error occurred when reading the file to  be  recovered. 
         (-nn) is the FCS error code. 
 
     6.  Specified input filename not found. 
         The input device  either  did  not  contain  any  files  which 
         matched  the input filespec or contains no more after the last 
         one found. 
 
     7.  File has extension file header:  truncated. 
         REI will not handle multi-header files, it will only copy  the 
         portion of the file mapped by the first header. 
 
     8.  File has unsupported retrieval pointer type. 
         REI will only handle the usual ODS-1 retrieval pointer format, 
         1 byte for block count and 3 bytes for block number. 
 
     9.  Bad block in file. 
         REI encountered a read error on the input  file.   This  is  a 
         warning  to indicate that the output file may have bad data in 
         it. 
 
     10. Error opening output file:  errtyp (-nn). 
         REI encountered an error when it  tried  to  open  the  output 
         file.   "errtyp"  will  be FCS or DIR depending on the type of 
         error and (-nn) will be the error code. 
 
     11. Error writing output file:  %I (-nn) :  aborted. 
         REI encountered  an  error  while  writing  the  output  file. 
         "errtyp" will be FCS or DIR depending on the type of error and 
         (-nn) will be the error code. 
