Issue in copying large file to network drive

[whytea]

Totalcmd: 8.0, 64-bit
Windows: 7 Pro
Network connection: VPN

Sequence of events:
1) Copied a file of 130+MB to a network drive
2) Put into background
3) After 2-3 minutes, I decided to stop the file copy
4) Couldn't pause or quit, had to shutdown Totalcmd (took long time)

To my surprise, the file was actually created on the destination with the right size but wrong file date. Obviously it wasn't a complete file (I checked it by RDP to the remote machine).

This is no doubt a bug somewhere in 8.0 and probably the older version too. But wasn't there a discussion in the past about using a separate thread in file copying and other time consuming tasks?

/WT

[karlchen]

Hello, Whytea.

What exactly is the bug in this case from your point of view?
You start copying a large file over a VPN connection. - We have got no idea what your upload speed is and how long the copy operation will take as a consequence.
You interrupt the process by shutting down T.C.
The target file has not been copied correctly. - This is to be expected because you interrupted the copy operation.
So what exactly is the bug from your point of view?

Kind regards,
Karl

[petermad]

2karlchen

What exactly is the bug in this case

Couldn't pause or quit

I guess this is the bug...

[ghisler(Author)]

This happens with some networks, but unfortunately I don't know why: Windows puts the entire file into its write cache almost immediately, and the operation then hangs at 100% when the file is closed until the cache has been flushed.