[can't reproduce] persisted until totalcmd restart: <error> Verifying | Cannot open file for reading!

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
Design
New Member
New Member
Posts: 1
Joined: 2022-12-28, 14:25 UTC

[can't reproduce] persisted until totalcmd restart: <error> Verifying | Cannot open file for reading!

Post by *Design »

Win10 (x64) + TotalCmd 10.00 (x64)

Moved and renamed a lot of files before this error pop up without any problem. Until:
1. I created a folder in a usb flash drive j:\@DOWNS NEW
2. Marked some files of ssd drive in g:\@DOWNS NEW
3. Pressed the move key
4. The file copied successfully in j:\@DOWNS NEW but a dialog kept appearing after every moved file until I restarted the total commander:

<error!>
Cannot open file for reading!
j:\@DOWNS NEW\logo.jpg
[ignore] [ignore all]
[abort]

Compare by content and synchronize directories worked fine with these files after the copy/move. It was a glitch in Verify after move/copy.

totalcmd.log:
12/24/2022 11:21:31: NewFolder: j:\@DOWNS NEW
12/24/2022 11:21:46: Move(Skipped): g:\@DOWNS NEW\logo.jpg -> j:\@DOWNS NEW\logo.jpg
12/24/2022 11:21:46: Test(Error: CRC error): Trg hash error: -1
Had to use the ignore button a few times and then aborted it just to be safe. That error persisted for any folder and file I attempted to move or copy afterwards. After restarting the program all seems okay.
Post Reply