REPLY: 1:18/200@fidonet 621edd20   
   MSGID: 2:250/1@fidonet 621fa802   
   CHRS: UTF-8 2   
   TZUTC: 0000   
   TID: MBSE-FIDO 1.0.8 (Linux-x86_64)   
   Hello Sean!   
      
   Tuesday March 01 2022 21:57, you wrote to me:   
      
    > Hello Vincent,   
      
    > 27 Feb 22 15:23, you wrote to me:   
      
    VC>> OK, I will send you copies of the MOD-UPD files for each so look   
    VC>> in your inbox after Monday.   
      
    > I received the GOLDED file but not the WIN95 file.   
      
    > Also, to change the mod on an echo...send a .ECO listing the new mod   
    > as COMOD1 and then send in a .EC1 with the co-mod as mod and the old   
    > mod as COMOD1?   
      
   My trick and the one I recommend is to send in two submissions with a 1 and 2    
   at   
   the end of the file name, i.e., GOLDED1.ECO, GOLDED2.ECO and if needed   
   GOLED3.ECO   
      
   They get processed in file name order.   
      
   So 1st one, adds COMOD1 as you, 2nd one, changes MOD to you and you might get   
   away with also deleting COMOD1 but if needed use 3rd to do that and on any of   
   them doing a password change if you feel the need. Just remember to use the    
   new   
   one there after.   
      
   Each submission will be processed in turn and reported upon.   
      
   Once the coding changes finish for the elist program you will also be able to   
   submit (like the .RUL file) a DES file which has the echo description in it    
   (and   
   only that as plain text, exactly the same as the .RUL file but that the   
   description file MUST be name in the form :   
      
   AAA.BBB.CCCCCCC.DES   
      
   Where AAA = Group name i.e., FIDO   
   Where BBB = EchoTag name i.e., GOLDED   
   and ".DES" is fixed to specify the file type for processing.   
      
      
   This change will allow for a serious reduction in the elist record size from   
   2,816 bytes down to 1024 as the descriptions will be stored as a file with a   
   directory etc, therefore saving a lot of space when the backbone areas get    
   added   
   to the file base as they do not contain descriptions unless sysops add them by   
   submitting a .DES file for any they feel happy knowing them.   
      
   I have not yet decided on if the backbone content will be added to the    
   ELIST.RPT   
   file but so far leaning that way at least quarterly in place of the Rules   
   listings - may just try it and see what it looks like and how useful they will   
   be to every one.  To me the most useful file is ELIST.NA but there again what    
   do   
   I know :)   
      
   Vincent   
      
   --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707   
    * Origin: The Elist Maintainer (2:250/1)   
   SEEN-BY: 1/123 15/0 18/200 25/0 21 90/1 92/1 103/705 105/81 106/201   
   SEEN-BY: 120/340 123/131 129/305 330 331 153/7715 218/700 221/1 6   
   SEEN-BY: 226/30 227/114 229/110 206 317 400 424 426 428 664 700 240/1120   
   SEEN-BY: 240/5832 250/0 1 3 4 5 6 7 8 10 11 21 263/0 266/512 275/1000   
   SEEN-BY: 280/464 282/1038 292/854 301/1 113 317/3 320/219 322/757   
   SEEN-BY: 335/364 342/200 396/45 460/58 633/280 640/1321 712/848 3634/12   
   SEEN-BY: 5058/104   
   PATH: 250/1 301/1 229/426