672 - Problem renaming files on network drives
Posted: 08.10.2014, 13:12
FCXE 6.72, 64-bit, on Windows 7 SP1 64-bit.
Occasionally, when renaming files on a network drive (e.g. "\\somecomputer\folder\file"), I'll get an error saying that the file cannot be renamed because the file is open in a program. But the program that it says that the file is open in, is FreeCommander itself!
If I try again, I'll just get the same message. Even if I close FCXE and launch a new instance of it, then try again, I still get the error trying to rename that same file. The only way I can use FCXW to rename the file at this point is to shut down and restart Windows completely before making another attempt. So it appears there is a "lock" placed on the file that can only be cleared by restarting the computer.
What's interesting is that I can use Windows Explorer to rename the same file, even while FXCE is still running (and in spite of having already gotten the error in FCXE). So the "lock" is ONLY affecting FCXE.
This seems to happen when I am rapidly hopping between folders on the networked drive and renaming files one at a time. That is, I'll rename a file, switch to a different folder, rename another file, repeat a number of times. Also note, before I get the error message, FXCE's file-rename status window appears on-screen for several seconds, with the progress bar not moving (normally, renaming a single file is pretty much instant and the status window never even appears).
If it makes any difference, the networked computer on which the files are being renamed, is a Synology DiskStation NAS box, which runs some flavor of Linux.
Aimhere
Occasionally, when renaming files on a network drive (e.g. "\\somecomputer\folder\file"), I'll get an error saying that the file cannot be renamed because the file is open in a program. But the program that it says that the file is open in, is FreeCommander itself!
If I try again, I'll just get the same message. Even if I close FCXE and launch a new instance of it, then try again, I still get the error trying to rename that same file. The only way I can use FCXW to rename the file at this point is to shut down and restart Windows completely before making another attempt. So it appears there is a "lock" placed on the file that can only be cleared by restarting the computer.
What's interesting is that I can use Windows Explorer to rename the same file, even while FXCE is still running (and in spite of having already gotten the error in FCXE). So the "lock" is ONLY affecting FCXE.
This seems to happen when I am rapidly hopping between folders on the networked drive and renaming files one at a time. That is, I'll rename a file, switch to a different folder, rename another file, repeat a number of times. Also note, before I get the error message, FXCE's file-rename status window appears on-screen for several seconds, with the progress bar not moving (normally, renaming a single file is pretty much instant and the status window never even appears).
If it makes any difference, the networked computer on which the files are being renamed, is a Synology DiskStation NAS box, which runs some flavor of Linux.
Aimhere