little bug in MR Tool when renaming network files.

[fredscal]

I am encountering a systematic bug in a very particular context...

The bug:

The MR Tool pops up a Warning box "The files in bold could not be renamed", showing all of them in bold, always, while in fact they are renamed successfully. (The only reason why it really bothers me is because, since TC believes no files were renamed, i can't press F5 in MR Tool)

The context:

On network files on a USB drive attached to my network/gateaway drive, which has a Linux-based firmware. (it doesn't bug with files on the network drive itself, but it does with files on the secondary USB drive attached to it, and accessed, obviously, through it via the network)


I would suppose this bug were related to my network hardware and/or Windows 2000, although I wonder: why does it only happen within to Multi-Rename Tool, and not when renaming single or multiple files in TC's main window?


Details:
The network storage/gateway device: Freecom FSG-3 (the product's name has changed but it appears to be basically the same except now it has wi-fi), firmware version 3.1.29 (= Linux version 2.4.27-uc1 (root@lindev) (gcc version 3.3.2) #1612 Fr Jun 9 13:10:52 CEST 2006)
The concerned HD: seagate barracuda 7200 10 98J148-305, firmware 3.AAE
The USB enclosure: LC Power EH-35BSII (S-ATA II HDD)
The OS: up-to-date Windows 2000, 5.00.2195, SP4
I'm using cables, no Wi-Fi (my version of FSG-3 doesn't have it anyway)
My Network drives are mapped, but accessing them through their full network address doesn't change anything to the problem.

[fredscal]

UPDATE:

The bug seems to have corrected itself after updating my FSG-3's Firmware to version 4.2.7 (Linux version 2.6.18 (root@theszlinux64) (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #161 Tue Jul 17 12:37:52 UTC 2007)

I'll still leave this thread posted because it doesn't explain why there was a difference of behaviour between the MR-Rool and classic F6-renaming... But as for my little me, the situation is solved

[Hacker]

It might be useful if you posted the filenames and the MRT settings.

Roman

[StatusQuo]

I can confirm that this happens while renaming files on a Samba file server.
This happens to me from time to time when renaming large file lists, but unfortunately I could not reproduce it so far.
What I remember from those cases:

The file names were nothing special,
special characters and even spaces are avoided wherever possible,
uppercase characters are autoconverted to lowercase by the server.

Trying to rename only the problematic files a second time with the same settings works without a problem.

Maybe it's a timing/cache problem?

[fredscal]

As a matter of fact, my FSG-3 does too have a peculiar uppercase/lowercase behaviour:

It doen't convert names to lowercase or uppercase automatically, like StatusQuo's server, but it prevents, in any case, renaming a file to the same name with uppercase characters changed t lowercaser or vice-versa (it just won't register the change). Maybe there's something in common here or not, i don't know...

As for a file list... It does it on every file, always... (see my post above)

Note: in my system's details, i forgot to mention, I'm using TC 7.02a