UFDFND.LIT FUNCTION: To compile a list of blocks on the disk that could possibly be or have been User File Directory (UFD) blocks. This list could be useful in rebuilding the directory(s) for an account where the file directory system for a device has been lost. HINTS/RESTRICTIONS: UFDFND may be run from any account on the system and will function on any device on the system. UFDFND does not require the bitmap or the file directory system to be intact, and is intended as an aid to rebuild the file directory system. Although not required, it is recommended that there be no other users on the system, or at least no access of the faulty device. UFDFND will read every block on the device, and is very time consuming in the form of disk reads. UFDFND may return blocks that were not directory blocks if the correct bit pattern happens to be in the correct location for a directory block. FORMAT: .UFDFND {device:}{/P} The device may be any device that is currently mounted on the system. The driver must be resident in system memory as part of the monitor. Multiple digit drive numbers are permitted. The /P switch will allow for the output of a file by the name device.UFD (ie. DSK0.UFD). This will allow for a printed copy to work from in the rebuilding of the directory(s). To prevent the possible destruction of valid data, it is recommended that the /P option not be used with the default device. The file is created in the account you are logged into when you run UFDFND. 1 DEFAULTS: If no device is specified, then UFDFND will default to the device you are currently logged into. The /P option is NOT defaulted and must be specified. OPERATION: 1. Type UFDFND followed by the device you wish to search for possible UFD blocks. Use the /P option if you expect a lengthy list. 2. UFDFND will return the block numbers that have any of the extensions listed below in the correct position and in RAD50 in the block for it to be a UFD block. There only has to be one match for the block to be displayed. 3. UFDFND will not locate the any MFD blocks. 4. The output file produced by the /P option is an ASCII file and the same format as the output to the screen. The file may be printed or VUEd. ERRORS: A. ^specification error: Your command line was of incorrect format. The ^ indicated the location that UFDFND did not understand. B. All other errors are from the AMOSL operating system. CHARACTERISTICS: You can use UFDFND to determine a list of possible directory blocks to be used in the rebuilding of UFD's. You will have to use DSKDDT or other block editor program to do the actual rebuilds. Consult the AMOSL System Commands Reference Manual for help. UFDFND will probably not be needed unless you lose the file directory system, then it will become a valuable tool to assist in saving lost data. The best safeguard is a current backup of the data. Do not depend on UFDFND to save all your data! 2 UFDFND is control C (^C) interruptable, if CTRLC is SET on the user's terminal. The output file will be properly closed if the program is ^C interrupted. EXAMPLES: .UFDFND UFD search commencing on DSK0 This device contains a total block count of: 29088 The following blocks appear to be User File Directories: 13 14 15 17 .......... .UFDFND DSK1:/P Print option has been initiated - output to DSK1.UFD UFD search commencing on DSK1 This device contains a total block count of: 29088 The following blocks appear to be User File Directories: 13 14 15 17 .......... EXTENSION LIST: .BAK .BAS .BV .CMD .CMN .CPY .DAT .DBD .DBK .DO .HLP .HLV .IDA .IDX .INI .LIT .LIB .LSP .LST .M68 .MNU .OBJ .OLD .QRY .R .REN .RPT .RUN .S .SAV .SBR .SEQ .SV .SYM .SYS .TXT .UNV .VUE UFDFND.LIT was written by: Quaker State Oil Refining Corp. Research Center Oil City, PA 16301 - March 1984 3 .