On 09/12/18, Andrew Leary said the following...   
    AL> FTS-5006.001 specifies a filename in DOS 8.3 format.  Thus, it could be    
    AL> interpreted that .TIC files with shorter or longer names are   
    AL> non-compliant.   
      
   It could? I went to wikipedia to see what it has on 8.3 and it says this:   
      
   "8.3 filenames are limited to at most eight characters (after any directory   
   specifier), followed optionally by a filename extension consisting of a   
   period . and at most three further characters."   
      
   The key words there are "at most" - which would imply they can be shorter?   
      
   Is there somewhere else that mentions that they should be 8 chars.    
      
   Perhaps MBSE could use the incoming tic name transiently, and actually   
   discard the pre .tic component and save it as $(mbseq).tic when it has been   
   finally received? Then it wont matter how other systems present a tic file,   
   and it could avoid a clash (not sure if this part is ever an issue...)?   
      
   Just ideas...   
      
   ...deon   
      
   --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)   
    * Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)