Re: Reading progress of "copy" executed asynchronously

A funny way to cheat would be to simply generate the progress in your program by checking the size of the target file and comparing that to the size of the source file. This avoids needing to read the (console) output of the copy process, but you don't necessarily get any indication of errors that way.

Comment on Re: Reading progress of "copy" executed asynchronously

Replies are listed 'Best First'.
Re^2: Reading progress of "copy" executed asynchronously by SuicideJunkie (Vicar) on Aug 08, 2018 at 14:37 UTC
Windows shows all the disk space as used immediately, and doesn't even update the file timestamps during the copy process. It does update the modification time to be equal to the source file's modification time after the copy completes, but that's not useful. The free space on disk is also set to the final value immediately.	[reply]