Page 2 of 2

Re: v0.78 Bug: BAD Delete/Move Bug - May Corrupt file system

Posted: Thu Mar 10, 2016 12:45 am
by XnTriq
Thanks for your determination and persistence in hunting down this serious bug, Erixx haxx!

Re: v0.78 Bug: BAD Delete/Move Bug - May Corrupt file system

Posted: Sun Mar 27, 2016 11:14 pm
by CameronD
I have just come across this myself.
Apparently the Win-7 system library has a serious problem with trailing spaces in names and folders, and fails in
windows explorer, cmd.exe, powershell, bash running under msys - to name a few.

There is no filesystem corruption.

Solutions include:
  • rename or delete using something with a different i/o library (xnview (I did not think of this), 7-zip, bash under cygwin)
  • use the UNC local path syntax in cmd.exe: rmdir "\\?\C:\path\to\Copy of "

Re: v0.78 Bug: BAD Delete/Move Bug - May Corrupt file system

Posted: Mon Mar 28, 2016 12:17 am
by Mixer
CameronD wrote:Apparently the Win-7 system library has a serious problem with trailing spaces in names and folders, and fails in windows explorer, cmd.exe, powershell, bash running under msys - to name a few.
This is explicitly declared in
MSDN: Naming Files, Paths, and Namespaces, Naming Conventions wrote:Do not end a file or directory name with a space or a period. Although the underlying file system may support such names, the Windows shell and user interface does not. However, it is acceptable to specify a period as the first character of a name. For example, ".temp".

Re: v0.78 Bug: BAD Delete/Move Bug - May Corrupt file system

Posted: Wed Mar 30, 2016 2:31 pm
by Erixx haxx
It sounds more like a typo in the code to me, and only Win7 is passing it on.