This behavior might not be considered a bug but should be changed imho: When renaming a file in TC 7.03/Win XP on NTFS to a file name which contains an illegal char (eg "/") the error message is "Error cannot write ... Please remove the write protection!".
This message is misleading and directs the user to the wrong cause. Instead, it should show the correct warning/error similar to how Windows Explorer does and/or just filter the illegal chars.
TC misleading error message
Moderators: Hacker, petermad, Stefan2, white
Slash "/" isn't an illegal char, it is treated just like a "\" backslash.
If you rename "bla.txt" to "blubb/blob.txt" TC will try to move to directory "blubb" and then rename the file to "blob.txt". If "blubb" doesn't exist, you get an error message that it cannot write to "blubb".
So, if at all, the "bug" is that TC doesn't create directories when renaming but as ghisler will implement this in TC 7.5 for the MRT, it might work in normal panels as well then...
What char is illegal or legal depends on the file system TC writes to. Until now TC doesn't check that.
Icfu
If you rename "bla.txt" to "blubb/blob.txt" TC will try to move to directory "blubb" and then rename the file to "blob.txt". If "blubb" doesn't exist, you get an error message that it cannot write to "blubb".
So, if at all, the "bug" is that TC doesn't create directories when renaming but as ghisler will implement this in TC 7.5 for the MRT, it might work in normal panels as well then...
What char is illegal or legal depends on the file system TC writes to. Until now TC doesn't check that.
Icfu
This account is for sale
Hello, icfu.
OK, fine. This explains why "/" will not be considered an illegal character. Nonetheless the error message complaining about write protection does not really make sense.
Moreover, the same error message will be displayed if you use other illegal characters like e.g. the pipe sign "|".
Karl
I had suspected that this might be the answer when reading this thread: Renaming multiple files with cm_RenameOnly and ‘/’. (Searched the forum for "Error cannot write remove write protection")Slash "/" isn't an illegal char, it is treated just like a "\" backslash.
OK, fine. This explains why "/" will not be considered an illegal character. Nonetheless the error message complaining about write protection does not really make sense.
Moreover, the same error message will be displayed if you use other illegal characters like e.g. the pipe sign "|".
Karl
That's true, for the English version, I hadn't checked that one. The German translation doesn't say "Please remove the write protection!" but "Remove the potentially existing write protection!" which is be a clear signal that TC just doesn't know why the file cannot be written and offers write protection as a possible cause.Nonetheless the error message complaining about write protection does not really make sense.
Like I said above, TC doesn't check the underlying file system, it just sends the desired filename to the OS and then interprets the return code. The pipe isn't generally illegal in file names, I just renamed a file successfully to bla|blobb.txt on totalcmd.net FTP, so obviously it doesn't run on FAT or NTFS.Moreover, the same error message will be displayed if you use other illegal characters like e.g. the pipe sign "|".
Icfu
This account is for sale