right click context menu 'copy' not intercepted

[avantuser1114]

is it a natural behavior of MC to not intercept the copy operation done through right click->copy then paste?

[Mathias (Author)]

Yes.

[avantuser1114]

can you add an option to make it intercepted?i like the file operation offered by MC, it's one of the things that attracted my attention..i'm tired of windows 'just copy' function without any advanced feature..but why is it that MCs copy operation is slower than windows?

[Mathias (Author)]

No. not directly. To much information is lost using cut/paste.

It depends on you HW and/or settings. My computer is much faster using MC then windows. But it depends on what you read data from and write to and also what OS. and Windows does sometimes lies when it says it is done copying.  It says it is done when it has written data to its write cache. but the data is not written to the drive yet. by default MC bypasses the cache. But you can tweak and change read/write strategy in copy dialog.

[avantuser1114]

any tips then to make it faster?i'm using windows 7 home premium 64 bit, i5 processor but the first generation, 7200 rpm hard disk..by the way thanks for the info about the way windows do copy..and though in my system i feel MC is slower, i'm still more comfortable using it..

[Mathias (Author)]

It is often network or usb devices that messes up the performance. But some drive perform a little better with higher data chunks and other does not like it.

It is a try and test and measure game. (But system/drive caches can mess with the measurements)

Windows does not give many variables to play with all of them are exposed to the user to tweak with in the Read/Write Strategy options that you find in the copy to dialog.

MC will try to auto detect what read/write strategy to use. (based on src/target device types) and you can then modify them. In Core settings you can disable the auto detect. It will then Always use 'Normal' strategy for all different devices.

System Cache
If the Data that is read/written should be stored in the system cache. For large file you do not what this. for small file that will soon be read
again this is good.
But for writing it will also lie to you and say that it is finished before the data is actual written to the drive and if you are copying a lot of
data you might get short delays when everything looks to stop/halts for a while. That is because the system cache gets full and it now has to wait until the data is actually written before continuing.

Drive Cache
Use the drive cache when read/writing. This option is up to the device driver to support. some device driver will ignore it. On Large files you might get better throughput if you disable it. But it is up to the drive and device driver.

Chunk Size
How many bytes to read/write at once. For optimal performance the size should be divided by 512.
But to large chunk and it may block other operation and to small can be a waste.
Windows Default is 64KB.  but some USB memory stick likes bigger and some network devices what smaller.

Sync, Asyncrone
If read/write are on two physical different harddrives then async copy will allow for writing while at the same time it is reading.
(of when copying to network from local drive)
But doing this when read and write are on the same drive, and the performance drops like a stone.

Internal Buffer
This is mostly useful if for asynchronous operation. So that multiple read request can fit in the buffer until it has to wait for write operation to finish.