I've hatched out MyGUI137.zip to FSX_MUTL file area today.
I've hatched out MyGUI137.zip to FSX_MUTL file area today.
What, exactly, is this file supposed to be used for? I'm assuming that you're sharing AgencyBBS GUI with us, but I feel like that's wrong...
This replaces the MyGUI v1.0.2.26.zip file that was sent out a few weeks ago. This file (you may recall) caused a few hassles with some
mailers getting stuck because the file name had a space in it.
If anybody wants to test it, I'll happily put a "spacy" name in my outbound for you and we can see if you get it...
22 Jan 22 10:12, you wrote to Avon:
If anybody wants to test it, I'll happily put a "spacy" name in my outbound for you and we can see if you get it...
I've reviewed the MBSE code and it should be good, but it can't hurt to test it...
I did in the TIC sent with MyGUI137.zip use the REPLACE verb and
included the old filename of MyGUI v1.0.2.26.zip to be swapped out with the new 137 version.
I've reviewed the MBSE code and it should be good, but it can't
hurt to test it...
Done, I just dropped a file to you:
+ 22 Jan 16:16:40 [1354505] outgoing session with
phoenix.bnbbbs.net:24554 [2601:193:c400:7786:f1d0:1:320:219] - 22 Jan 16:16:41 [1354505] NDL IBN,IFC,ITN:60177,XX,CM - 22 Jan 16:16:41
[1354505] TIME Sat, 22 Jan 2022 00:16:40 -0500 - 22 Jan 16:16:41
[1354505] VER mbcico/1.0.8/GNU/Linux-x86_64 binkp/1.1 - 22 Jan
16:16:41 [1354505] PHN phoenix.bnbbbs.net - 22 Jan 16:16:41 [1354505]
OPM Home of MBSE BBS for Linux/*BSD + 22 Jan 16:16:41 [1354505] addr: 21:4/105@fsxnet + 22 Jan 16:16:41 [1354505] sending /fido/mailer/box/21.4.105.0.h/My filename with spaces.txt as My\x20filename\x20with\x20spaces.txt (46) - 22 Jan 16:16:41 [1354505]
OPT EXTCMD GZ BZ2 PLZ CRC + 22 Jan 16:16:41 [1354505] Remote supports EXTCMD mode + 22 Jan 16:16:41 [1354505] Remote supports GZ mode + 22
Jan 16:16:41 [1354505] Remote supports BZ2 mode - 22 Jan 16:16:41 [1354505] TRF 0 0 + 22 Jan 16:16:41 [1354505] Remote has 0b of mail
and 0b of files for us + 22 Jan 16:16:42 [1354505] sent: /fido/mailer/box/21.4.105.0.h/My filename with spaces.txt (46, 46.00
CPS, 21:4/105@fsxnet) + 22 Jan 16:16:43 [1354505] done (to 21:4/105@fsxnet, OK, S/R: 1/0 (46/0 bytes))
Not sure if this is something that would need g00r00's attention
(filename space handling mutil FileToss)?
It appears that FTS-5006.001 (http://ftsc.org/docs/fts-5006.001) states:
So it might be that HTick needs to be told to output Lfile keywords,
too, if possible. Can you spot any options for that?
Lfile
The name of the file in long file format.
Note that few file processors will recognise this Keyword.
Your milage may vary when attempting to distribute files
with long file names.
Example: Lfile Longfilename.extension
This is an optional keyword.
So it might be that HTick needs to be told to output Lfile keywords, too, if possible. Can you spot any options for that?
The TIC file contained this (no Lfile keyword):
File MyGUI137.zip
Replaces MyGUI v1.0.2.26.zip
Still, it might be an idea to check with g00r00 if mutil FileToss has support for Lfile in TICs?
On Sat Jan 22 02:45:00 2022, Al wrote to Zip <=-
MBSE always excepts files with the file keyword and when it sends files to linked nodes it sends them with the file keyword in UPPER CASE. It also includes the lfile keyword as the file was recieved (MyGUI137.zip) but I don't know of any other software that recognizes it.
I don't think htick knows about the lfile keyword. My BBBS doesn't know about it either.
MBSE always excepts files with the file keyword and when it sends files
to linked nodes it sends them with the file keyword in UPPER CASE. It
also includes the lfile keyword as the file was recieved (MyGUI137.zip) but I don't know of any other software that recognizes it.
I suppose it's not really an issue, I just prefer file names that don't SHOUT at me.. :)
I'm going to write to the BBBS author and ask if he'll consider adding support for the lfile keyword. I don't like my chances but I suppose
it's woth a try.
Postie will use the "Lfile" or "Fullname" fields if they exist, if not it fall back to "File"
It will only hatch files with 8.3 filenames, mostly because I am lazy to work out a decent Long filename -> 8.3 conversion, and I didn't want any more command switches than it already has.
If some tic file came through with a non 8.3 filename in the "File" field then postie should still accept it - though I'm not sure what would happen
if it tried to forward files to downlinks with a long filename in the "File" field.
I'm actually suprised BBBS doesn't have it, I would have thought it was common given long filenames have been around for a very long time.
MBSE always excepts files with the file keyword and when it sends files
to linked nodes it sends them with the file keyword in UPPER CASE. It
also includes the lfile keyword as the file was recieved (MyGUI137.zip)
but I don't know of any other software that recognizes it.
Sounds like it has a good strategy for the downlinks!
Yes, although they thid [look like that] in the past. :-D
Sounds like it has a good strategy for the downlinks!
It's a bad strategy. Some nodes will have lower or mixed case filenames and once they pass through a BBBS they will be all upper case unless that BBS can use the lfile keyword.
On my A48 version (not the very very latest, I think), it barfed on the space in the REPLACE:
- 2022-01-21 21:18:13 Replace "MyGUI"
+ 2022-01-21 21:18:13 Added to "FSX_MUTL: Mystic BBS Utils, Mods,
Lfile
The name of the file in long file format.
So it might be that HTick needs to be told to output Lfile keywords,
too, if possible. Can you spot any options for that?
The TIC file contained this (no Lfile keyword):
File MyGUI137.zip
Replaces MyGUI v1.0.2.26.zip
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.
No mention of short or long filenames there, it appears...
I'll try to check with g00r00 how this is handled.
Postie will use the "Lfile" or "Fullname" fields if they exist, if not
it falls back to "File"
It will only hatch files with 8.3 filenames, mostly because I am lazy to work out a decent Long filename -> 8.3 conversion, and I didn't want any more command switches than it already has.
I've hatched out MyGUI137.zip to FSX_MUTL file area today.[...]
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 512 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 155:18:33 |
| Calls: | 8,281 |
| Calls today: | 1 |
| Files: | 15,511 |
| D/L today: |
2 files (29K bytes) |
| Messages: | 926,752 |