Hi G00r00,
I always have problems receiving and processing files with TIC and attachments (tossing) if the attachment or the TIC file has a space in
the name. This does not cause any problems for Windows users because
they can handle spaces, but it does for us Linux and Raspberry Pi users with a Linux.
I always have problems receiving and processing files with TIC and attachments (tossing) if the attachment or the TIC file has a space in the name. This does not cause any problems for Windows users because they can handle spaces, but it does for us Linux and Raspberry Pi users with a Linux.
for full compatibility, all files transferred with TICs should use the standard 8.3 naming convention... LFNs are not supported by the majority of TIC processors for numerous reasons...
Probably but why MysticBBS with Windows do not have trouble? Only the Linux Based MysticBBS run always in trouble with spaces in the
Filename.
I know it's retro but ther
shut be a solutin in the 21th century to support us *nix user as well.
Again, Windows and *nix are very different in how they use files. There
is no easy solution to that.
I always have problems receiving and processing files with TIC and attachments (tossing) if the attachment or the TIC file has a space in
I always have problems receiving and processing files with TIC and attachments (tossing) if the attachment or the TIC file has a space in
the name. This does not cause any problems for Windows users because
they can handle spaces, but it does for us Linux and Raspberry Pi users with a Linux.
+ Jan 09 09:25:37 File MyGUI v1.0.2.26.zip Area FSX_MUTL From 21:1/100
I always have problems receiving and processing files with TIC and attachments (tossing) if the attachment or the TIC file has a space i the name. This does not cause any problems for Windows users because they can handle spaces, but it does for us Linux and Raspberry Pi use with a Linux.
Another thing to consider here is that in Unix systems filenames are case sensitive. So for example:
+ Jan 09 09:25:37 File MyGUI v1.0.2.26.zip Area FSX_MUTL From 21:1/10
If your .TIC has "MyGUI v1.0.2" as the filename but the actual file is "mygui v1.0.2" in lower case, then those are not the same files in Unix. This could be a reason why it would work in Windows (which is not case sensitive) but not in Linux.
If we determine this is your issue, then maybe what I can do is add a new option that you can turn on to make that TIC filename check case insensitive in Unix.
I know I need to update to the A47 version, but I have too many things
on my plate at the moment, and I am also unable to work due to massive
Yes, I realise that the addon/option would have to harmonise the
filenames all to lower case and without spaces that are previously replaced by underscores "_" before sending these files via the FTN
mailer with a TIC file to it.
As far as I know, A47 users are also affected by the same problem, so it seems to me that this problem is not fixed yet. As I said, it would be
But to reiterate: Most likely the filename in the .TIC file does not
match the case of the actual file on disk. In Linux they must be exact matches. If your TIC says TEST.ZIP and you have test.zip on your disk,
it will not toss.
Using BinkD (running Linux) as the mailer.. I noticed some Mystic nodes polling in were having this issue:
v1.0.2.26.zip as MyGUI\x20v1.0.2.26.zip (1669424)
This seems to be related to a long standing issue with BinkD escaping filenames incorrectly. You'll have to get it fixed in BinkD.
This seems to be related to a long standing issue with BinkD escaping filenames incorrectly. You'll have to get it fixed in BinkD.
OK thanks for the info. I'll take this to BinkD dev.
| Sysop: | Xerxes |
|---|---|
| Location: | Azle, Texas |
| Users: | 118 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 155:54:47 |
| Calls: | 3,009 |
| Calls today: | 0 |
| Files: | 152 |
| U/L today: |
0 files (0K bytes) |
| D/L today: |
0 files (0K bytes) |
| Messages: | 290,535 |
| Posted today: | 0 |