setln2 has the following features:

Sets .LONGNAME EA on all files, which currently doesn't have one.
   This makes it easier to recover files with correct filename.

Sets a Jrescuer EA which holds the full path to the file.
   This makes it easier to recover a file to its former location.

Tries to unlock locked files, to be able to set EAs (requires unlock.exe)

Can optionally start a thread for each disk drive, to set EAs on all
   JFS volumes as fast as possible. Very usefull at startup/shutdown
   time.

Doesn't touch any files inside \lost+found
   Files in lost+found are put there by chkdsk, and we do not want
   to owerwrite any previus EA data we have written.

Setln2 times the operation, and outputs the total time used.

Setln2 measures the amount of space on the drive, and reports the
   difference after the operation. Measurement is only accurate of
   volumens, where there are no other files/programs in use.

Setln2 can be started with these options:
   setln2 <drive:|all> [delete][force][debug]

drive:  The driveletter for the volume to set EAs on, ex C:

all:	Will find all your JFS volumes, and set EAs on all of these.
        It will even start a separate thread for each harddisk, to get
        the job done as quick as possible.

delete: Deletes all .Longname and Jrescuer EAs, that have been set
        earlier witn this app.

force:  Forces rewrite of the Jrescuer EA. This needs to be done, if
        files have been moved to other positions - to get the stored
        path correct.

debug:  Outputs a lot of msgs to the screen. Totally useless.

Setln2.cmd have been tested even on bootable JFS volumes, and haven't
caused any problems.

   Happy computing....

allan@warpspeed.dyndns.dk
 