Hello,
I'd like to use FastCopy from a file manager such as FAR Manager or muCommander to be able to copy/move files by means of FastCopy.
To invoke FastCopy from a file manager, I use FastCopy's command line options.
Now let's consider the following scenario:
1) I initiate a copying of one huge folder e.g. C:\Data1\HugeFolder1 (an instance of FastCopy is started and is copying the files) from a file manager;
2) Then I initiate copying of another huge folder e.g C:\Data2\HugeFolder2 (another instance of FastCopy is started and is copying the files) from a file manager;
3) As the result, both instances of FastCopy are copying the files simultaneously.
In this scenario, I'd like to avoid several instances of FastCopy to copy files simultaneously to reduce the HDD usage. I.e. I'd like to have only one active instance of FastCopy to actually copy the files, whereas all the further copy operations to be queued or postponed until the already active instance of FastCopy has finished its copy operations.
How can I achieve that using FastCopy command line options?
I tried "
/force_start=1" - no luck. (I was hoping that it means: allow only one active instance of FastCopy, while the others will wait for the first one to finish).
I also tried to specify something like "
/job=job1", hoping that it will create a job for the first copy operation and then assign the next copy operations to the same job thus queuing them - but no, FastCopy expects the job1 to be already created in some other way.
Did I miss something - or am I asking for something new?