Windows Error Code 2 with NetDrive client

[raikonz]

When trying to compare drive(s) with drive mapped by NetDrive client
([http://www.netdrive.net/).](http://www.netdrive.net/.)) It causes quite a
number of "Windows Error Code 2" errors. However, comparison works perfectly
when using standard Windows mapping.

[Zenju]

The directories for which this happens are empty, right? With empty I mean
issuing a "dir" in the console not even brings up "." and ".." entries?

The problem is "FindFirstFileEx" returns with ERROR_FILE_NOT_FOUND in both
cases where a directory does not exist and when it didn't find a single child-
entry.

Former is an error, while latter is not, alas "FindFirstFileEx" doesn't bother
to make this fundamental distinction.
FFS let's this error propagate, since in general a directory always has "."
and ".." entries, so the error must mean that the directory is not existing.
Exceptions: Root directories and NetDrive.

[raikonz]

just double checked, no they are not empty but containing Asian characters.
This is not a analytical result because I have switched to another solution
and lazy to dig out what the problem is. Thanks for your respond!

[Zenju]

It seems to be a NetDrive bug. When trying to create a new file on an FTP
server via NetDrive using some non-ANSI characters Windows Explorer returns
"file not found" instead of "character not supported", "internal failure",
whatever it is it's certainly not "file not found". FFS probably hits the same
wall.

[hayenadeblue]

Hi Zenju,
You're very good in supporting the software. I'm using Netdrive to map my SFTP as a drive. I'm facing the same problem as raiko, but in my case whenever the source folder is empty, or containing only .java files.
I don't think this is bug from NetDrive because I can copy the folders/files using explorer.



I'm using FreeFileSync 5.10 and NetDrive 1.3.2.0

Thanks for the great software.

[Zenju]

FreeFileSync supports SFTP directly as of version 7.2.