Custom Move anomaly prob due to Read-Only set

[Malarki]

XY 25.40.0102 on Windows 10 Pro x64

I usually use FastCopy for big file moves but used XY Custom Copy (Move) this time, between two internal SSDs which otherwise give no problems. I was surprised when Custom Move reported a failure on "overflow" as follows:

Custom Move from 1/3/2024 4:22:42 PM

From: G:\HB\
To: F:\__ToCD\

Files processed: 2 (1 new, 0 over, 0 skip, 1 fail), 1 dir
Bytes moved: 3.88 GB
Transfer rate: 761.34 MB/sec (incl. byte-to-byte verification)
Created folders: 1
Remarks: Custom Move completed in 5.23 secs (verified)
Warnings: There has been 1 failed file.

------------------------------------------------------------------------

Processed files:

New G:\HB\TEST\dropbox link.txt -> F:\__ToCD\_eBay\TEST\dropbox link.txt | byte-to-byte
FAIL (verification failed) New G:\HB\TEST\Antics 1080p.mp4 -> F:\__ToCD\_eBay\TEST\Antics 1080p.mp4 | Overflow

------------------------------------------------------------------------

Created folders:

CreateDir F:\__ToCD\_eBay\TEST\

Both the source and dest MP4 files had the same CRC, so the Copy part worked OK. I eventually realized that the source file was "read-only" which is unusual in my stuff, and is probably the reason for XY not simply deleting that and finishing normally.

In Custom Copy Config I have "Ask before overwriting read-only files" enabled; and "Remove read-only attribute" disabled.

Reporting this as a bug only because the "overflow" message is (?) inaccurate. I think it should just say that the source isn't being deleted because it's read-only; or the process could ask me what to do.

[admin]

1) Did not test yet, but you are using byte-to-byte verification with huge files. This might also be the cause of the overflow.

2) Could you show a screenshot of your Custom Copy settings: Configuration | File Operations | File Operations | Custom Copy Operations | Configure...

* * *

Forget it, I got it. It was the byte-to-byte verification. Fixed in next beta. Good find!