• File tossing etc

    From Vincent Coen@2:250/1 to All on Fri Jul 14 13:09:21 2023
    Hello All!

    I have hatched the latest, for file area: PDNBASIC filename: QBSHELLG.ZIP with REPLACE set for QBSHELL*.ZIP.

    This is not working here, so please check your systems when processing today - well since 12:50 GMT+1 and advise if your system is also not doing so or you get any warning or error messages from the processing of the file and the .tic file etc.

    Thanks,

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Alan Ianson@1:153/757 to Vincent Coen on Fri Jul 14 06:50:00 2023
    I have hatched the latest, for file area: PDNBASIC filename: QBSHELLG.ZIP with REPLACE set for QBSHELL*.ZIP.

    The file arrived and was imported here fine. I had a look in the PDNBASIC directory and there are a lot of QBSHELL*.ZIP in there.

    I know that BBBS won't replace files with * in the filename, it'll only replace files by name.

    Is there an FTSC document that describes the replaces keyword? It might shed better light on what might be happening here.

    --- BBBS/Li6 v4.10 Toy-6
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Vincent Coen@2:250/1 to Alan Ianson on Fri Jul 14 21:50:03 2023
    Hello Alan!

    Friday July 14 2023 06:50, you wrote to me:

    I have hatched the latest, for file area: PDNBASIC filename:
    QBSHELLG.ZIP with REPLACE set for QBSHELL*.ZIP.

    The file arrived and was imported here fine. I had a look in the
    PDNBASIC directory and there are a lot of QBSHELL*.ZIP in there.

    I know that BBBS won't replace files with * in the filename, it'll
    only replace files by name.

    Is there an FTSC document that describes the replaces keyword? It
    might shed better light on what might be happening here.


    Yes, its FTS-5006.001 and it states :

    Replaces

    This specifies that the file replaces one or more files that
    were sent previously. It is up to the receiving system if it
    honours this keyword.
    The wildcard characters '?' and '*' may be used with the usual
    meaning as in MS-DOS.
    Some tic processors do not support wild cards and use of
    wild cards with this keyword may cause unexpected results.

    Clearly this last bit means that s/w should check that any first star is at least say the 5th char.

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)