Menu

#1579 7zFM 15.11 & Windows 10 badly estimate total size of files in Copy/Move operations

None
open-accepted
nobody
None
5
2015-11-20
2015-11-19
maxpat78
No

When performing a copy/move operation (of about 3.6 GB in 7.000 files and 4 folders) in 7zFM 15.11 under Windows 10 32-bit (both TH1 and TH2), the copy window displays wrong total file size (hundreds millions of Gigas instead of 3.6) and, consequently, millions days remaining to end the task.

Discussion

  • Igor Pavlov

    Igor Pavlov - 2015-11-19

    Do you mean copy opertion from NTFS folder to NTFS folder (without archives)?
    Maybe there is some unusual file there?
    Try to find the file with problem. Reduce the number of files. Try to copy one folder from these 4 folders. Then some subfolder and so on.

     
    • maxpat78

      maxpat78 - 2015-11-20

      Yes, I mean copy of plain JPG files between 2 NTFS drives (left source: 4 selected folders with described contents, JPGs in many subdirectories; right dest: a subfolder, both in NTFS volumes).

      Obviously, in the past/previous 7zFM versions, similar and more complex tasks worked fine.
      Also, copy actually succeeds with usual speed, only displayed size & remaining time are wrong.

      I'll try more tests and report here. However, I thought about some API change in Windows.

       
  • maxpat78

    maxpat78 - 2015-11-20

    The bug seems related to the "Confirm/Overwrite/Rename etc." popup dialog in 7zFM.

    In fact, if I select to overwrite all the previous files with the same names (clicking "Yes To All"), the task continues properly with the right size/time values; when I select "No To All", instead, as soon as the operation resumes, the displayed size changes into an impossible value of millions GB, and so the remaining time.

     

    Last edit: maxpat78 2015-11-20
  • Igor Pavlov

    Igor Pavlov - 2015-11-20
    • status: open --> open-accepted
    • Group: -->
     
  • Igor Pavlov

    Igor Pavlov - 2015-11-20

    OK. It tries to reduce "Total Size" and uses wrong variable.
    I'll fix that BUG in next version.

    Thanks for report!

     

Log in to post a comment.