capital/lowercase letters in directory-/filenames and network-drive with TL-WR710

[MarkF]

Hi,
I wanted to use FreeFileSync for temporarily backups (simply adding all new and changed files) onto an USB-stick wich is plugged into the TL-WR710 (router), which I am using as WLAN-access-point (connected to LAN to improve the WLAN). The PCs are running with Win 7 and Win 10.
Here the problem occured that the SMB-implementation in the TL-WR710 seems to be buggy - the majority of directory-/filenames are generated in lowercase-letters only; only in a few directory-/filenames capital letters are possible (in the PCs the lowercase and capital letters are used/mixed, of course). For example: "RA" is generated as "ra", "TIMESTAX" is generated as "timestax". But "4GB-Patch" is generated original als "4GB-Patch" while "4GB-Pa" ist generated als "4gb-pa". There are no rules in this bug I could realize.
The problem is that FreeFileSync is capital-/lowercase-letter-sensitive: It does not realizes "ra" as "RA" oder "timestax" as "TIMESTAX". Of course keeping the original letters is o.k. in principle, although in Windows it doesnt matter.
Is there any way to force the software ignoring the difference between capital and lowercase letters in the directory- and filenames, just the behaviour that Win has?
I know that a real NAS would be better, but I do not need a real NAS, I just want to use the existing hardware for this purpose, to generate also temporarily backups in a drive which is separated from the PC.

[Zenju]

Is there any way to force the software ignoring the difference between capital and lowercase letters in the directory- and filenames, just the behaviour that Win has?

FreeFileSync is already ignoring case during folder matching (on all three Windows, Linux, macOS), unless you're using an old version of FFS.

[MarkF]

Thanks for your answer.
I am testing Version 11.3 (32Bit) 02.11.2020.
It´s strange:
As mentioned the target-drive is an USB-stick plugged into a TL-WR710N-device (configured as Access-Point) which is accessible as network-drive (Z:). For example the original directory "RA":
As mentioned the "RA"-directory (as target in FFS also "RA") was generated on the USB-stick as "ra" in the first backup-sequence and while further backups FFS does not realize this "ra" as "RA". My idea was that FFS is case-sensitive.
As test-workaround I have changed the target-directory in FFS to "ra". After deleting "ra" on the USB-stick and again initial backup (for "original" generating "ra" on the USB-stick) the further backups are working - FFS realizes the "ra"-directory on the USB-stick.
Now, after reading your answer, I have re-changed the target-directory in FFS to "RA" and testet with compare (on the USB-stick the directory is still "ra"). But now FFS does not realize the "ra"-directory on the USB-stick as "RA". Though case-sensitive?
But when you say the FFS is case-insensitiv there must be another reason. So I have done the same test with a backup to an USB-stick which is directly connected to the PC. At first I have done a new initial backup (with "ra" as target in FFS) and did a compare with "RA" as target in FFS. And in a second test I have copied the "ra"-directory from the network-USB-drive to the direct-plugged-USB-stick. In both tests FFS realizes the "ra"-directory on the USB-stick as "RA".
O.k., the SMB-implementation in the TL-WR710 may be buggy, so that uppercase-letters are a problem. But because FFS is case-insensitive: Why does this not work with the USB-stick plugged into the TL-WR710 with lower-case-letters?

[Plerry]

Your post is not fully clear in if
1) "RA" or "ra" is part of your left-right base folder pair definition, or
2) "RA" or "ra" is a (sub)folder located inside your left and right base folder location.

I believe what Zenju describes applies to case 2)

I am not sure if it makes a difference for case 1).
But, if it is case 1), try drag/drop the TL-WR710 base location into the left or right base location field, instead of typing it.

[Zenju]

A few screenshots and error messages would help to understand what you're doing.

[xCSxXenon]

Check if their is an update to your router's firmware too. They may have made a change to make capitalization more consistent