TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 564000ea   
   REPLY: 2:201/137 610f81cf   
   TZUTC: -0400   
    BW> Upon strace inspection, it appears that Mystic is looking for   
    BW> file_id.diz but not FILE_ID.DIZ when importing (e.g. when choosing   
    BW> (E)dit --> (I)mport DIZ from a file listing). Perhaps it should check   
    BW> for both?   
      
   Thats not quite how it works.  It does not look for FILE_ID.DIZ - what it does   
   changes based on the file and whether or not Mystic can internally handle the   
   archive format (ie ZIP, LZH/LHA, RAR).   
      
   It opens the file and does an archive listing to find the .diz or .ans file   
   and then attempts to extract the file name that it finds.   
      
   If it cannot find a file by internally looking at its archive data then   
   Mystic will try to extract "file_id.*" and then search for an .ans file and   
   finally a .diz file.  None of it is upper case.   
      
   This allows it to handle all types of file variations in case sensitive   
   systems such as "file_id.diz, FILE_ID.DIZ, File_ID.Diz and so on.   
      
   ... Youth is glorious, but it isn't a career   
      
   --- Mystic BBS v1.12 A47 2021/07/31 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 457 616 123/10 131 124/5016   
   SEEN-BY: 129/215 305 154/10 30 40 50 700 203/0 220/80 90 221/0 6 226/18   
   SEEN-BY: 226/30 227/114 201 702 229/101 310 424 426 428 452 550 700   
   SEEN-BY: 229/981 1016 1017 240/1120 5411 5824 5832 5853 6309 249/206   
   SEEN-BY: 249/307 317 400 280/464 5003 282/1038 292/854 8125 301/1   
   SEEN-BY: 317/3 320/219 322/757 342/200 396/45 633/280 770/1 2452/250   
   SEEN-BY: 2454/119 3634/12   
   PATH: 129/215 154/10 280/464 240/5832 229/426