TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 be01a106   
   REPLY: 2:201/137 316589ae   
   TZUTC: -0400   
    BW> Since -- isn't it so that any output from these commands will be shown   
    BW> to the user (possibly confusing the user and garbling the "screen" with   
    BW> a lot of technical mumbo-jumbo)? So one wants to avoid any such output   
    BW> to the user?   
      
   In Windows it does not redirect the console through a telnet connection like   
   it does in Unix-based systems, so doing the NUL is just to stop error messages   
   from an archive leak through to the local screen when doing local mode logins   
   and when MUTIL is performing archive related functions.   
      
   In other words, if a bunch of archive error messages are leaking into the   
   display when MUTIL is doing its GUI updates, it would cause the status screen   
   to appear garbled.   
      
   ... A Mystic asking for a hot-dog: "Make me one with everything"   
      
   --- Mystic BBS v1.12 A47 2021/08/08 (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