Subj : mbse v..4 and hatch and To : Andrew Leary From : Vincent Coen Date : Sun Jul 16 2023 10:55 pm Hello Andrew! Saturday July 15 2023 23:54, you wrote to me: > Hello Vincent! > Friday July 14 2023 21:46, Vincent Coen wrote to Sean Dennis: >>> I don't think you can use a wildcard. I believe it has to be an >>> actual filename. I am no expert on this but many years ago I >>> talked to the Allfix developer about this. VC>> Found the TIC spec in doc FTS-5006.001 which states : VC>> Replaces VC>> This specifies that the file replaces one or more files that VC>> were sent previously. It is up to the receiving system if it VC>> honours this keyword. VC>> The wildcard characters '?' and '*' may be used with the VC>> usual VC>> meaning as in MS-DOS. VC>> Some tic processors do not support wild cards and use of VC>> wild cards with this keyword may cause unexpected results. VC>> With the proviso of unexpected results which I assume means that VC>> if you use *.* it will scrap the lot so any s/w must check that VC>> such a first '*' is not less than the 5 chars etc. VC>> So the question is what does mbse do and more importantly in what VC>> program ? > MBSE does NOT support wildcards in the .TIC Replaces directive. The > processing of the Replaces directive is done in addbbs.c which handles > adding the file to the BBS file database. That's a shame but I will have to live with it. The trouble is I get new additions to one area i.e., PDNBASIC as a file without any TIC details including description so I have to do a unzip -z filename.ZIP just to get the one liner to use when running hatch - that then gets the full description via file_id.diz but if I just use a one word detail, that get passed on to all downlinks instead. I have now asked him to specify the previous fn. Can I assume that if I specify old fn to REPLACE it is NOT case sensitive ? He does NOT run a BBS. 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) .