Hello Robert!
Noticed an odd thing about -s with ARJ and ran a few tests to confirm this:
Example:
Archive contains a file dated 04/01/97.  Since it just arrived via ftp, the 
archive has the transfer date of 04/15/97.  I extract the file, make some 
changes and "a" it back into the archive.  Despite the -s in ARJ.CFG, the 
date of the archive will *not* change to reflect the date of the file just 
added. However, if I "a" the very same file a second time, the archive date 
will change to reflect the date of the file.  Why on the second try, but not 
on the first?
Details:
Using environment variable: C:\ZIP\ARJ\ARJ.CFG=-a -s -jm1 -js -jt1
                                                  -jyryv -wC:\Temp
Long filenames enabled
Updating archive  : gd.arj
Archive created: 1997-04-15 22:08:58, modified: 1997-04-15 22:09:24
Replacing gd.txt                       81.5%
Testing gd.txt                      Matched,     OK
Copying temp C:\Temp\ARJTEMP.$00 to archive gd.arj
Testing gd.arj  OK
    2 file(s)
E:\ > dir gd*.*
 Volume in drive E is OVERFLOW
 Volume Serial Number is 0EF3-0B6C
 Directory of E:\
GD       TXT            27  03-03-93  3:33a gd.txt
GD       ARJ           122  02-02-94  2:22a gd.arj
         2 file(s)            149 bytes
         0 dir(s)      27,459,584 bytes free
================== cut ===============
Note that the archive date has not changed to reflect the file date.  
Important to note that the file date is ***older*** than the archive date.  
Issuing the identical ARDJ a GD.ARJ GD.TXT command a second time will result 
in the archive showing the proper date (i.e. 03-03-93).
Cheers, Hans
... Black holes Suck.
--- GoldED/386 2.50+ / Squish / Maximus / Binkley / WINDOWS 95 / V34+
---------------