Hi Andrew,   
      
   Got another one for you.   
      
   I've noticed that I receive tic files from non MBSE BBS's (Mystic at the   
   moment), and those tic files have a name similar to the file they are   
   representing. EG: pinet.tic for pinet.250, fsxinfo.tic for fsxinfo.zip.   
      
   MBSE is not processing those tic files - however if I renamed the tic file to   
   have 8 numbers (with .tic) at the end, they were processed. EG: I renamed   
   pinet.tic to 00000000.tic and it was processed.   
      
   I had a quick look at FTSC specs (5006.001 and 1039.001), and it doesnt   
   mention anything about how a tic file should be named (character limit nor   
   only numerical/hex chars, etc).   
      
   I then had a quick look at the code mbfido/tic.c and it looks like it will   
   only process a tic file if it has a length of 12 chars (being 8 chars plus   
   ".tic"). Could this be changed? Or is it referenced somewhere else that tic   
   files should be 8 chars (suffixed with .tic) and other BBS software is not   
   following that standard?   
      
   ...deon   
      
   --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)   
    * Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)