Peter, that is a good idea, user skipcube used sysinternals to trace what was happening in the
github reported issue. After that you can inspect the source code which modifies and copies the directories&filenames. But I expect no easy solution.
That issue 26 was closed by kovidgoyal without solving it. Reading that thread, it seems there is something mysterious going on in the way calibre (or the python IO libraries) work with the remote NTFS/SMB filesystem. I googled a bit and this issue does not seem that simple to solve - probably that is why kovidgoyal closed it. He is working on a totally new multi-user version anyway, I suspect this will use a true transactions based database model for all operations (SQL?, maybe client/server?).
Even Microsoft
has problems with their own transactions based NTFS file operations. They recommend not to use their API but use SQL filestreams instead... go figure..
I cloned the source code to see what I can track down. When I have time.. But I think kovidgoyal will come up with a multiuser version before I can find a cure for this issue
