Hello Andrew!   
      
   Friday September 21 2018 18:04, you wrote to me:   
      
      
    VC>> At the moment I am currently running this version and have for   
    VC>> some days with no adverse results but cannot say that the   
    VC>> conditions have arisen where this fix shows up but I do have at   
    VC>> least one downlink using Mystic (v1.12A39 binkp/1.0).   
      
    > You won't notice anything unless a Mystic node sends you .TIC files.   
    > Mystic by default names .TIC files with the same name as the archive   
    > they relate to.   
    > ie: the .TIC file for fsxinfo.zip would be fsxinfo.tic.   
      
    > This causes problems with MBSE versions before 1.0.7.9, because MBSE   
    > expects that all .TIC files will be named with 8 character filenames   
    > followed by .TIC. The example above is only 7 characters, so it   
    > wouldn't be processed automatically.  The same applies to long   
    > filenames (longer than 8 characters.)   
      
    > The changes in 1.0.7.9 will handle .TIC files with filenames of 1   
    > character up to the maximum the OS supports.   
      
   Thanks for that, in which case I will not notice it as my master uplinks do    
   not   
   use mystic - have no idea why not!!   
      
   Must have a look at what hatch does though as I do process some long file    
   names   
   :)   
      
   Mind you I am fairly sure it renames them to a 8.3 - in some case very oddly    
   :)   
      
      
   Vince   
      
   --- Mageia Linux v6 X64/Mbse v1.0.7.9/GoldED+/LNX 1.1.501-b20150715   
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)