It automatically selects one of two copying methods, depending on whether the destination directory is on the same hard disk or a different disk as the source directory. To that end, it uses few system resources itself, and it doesn't use MFC or any OS caches. It can copy large files at close to the hardware-defined read/write limit without hogging system resources. It can decrease speed, because it opens not only copying files but also skip files.FastCopy (64-bit) is a slim but powerful freeware file-copying utility for 64-bit Windows editions. It needs 2-4MB per 10 thousand hardlink entity files. (If /linkdest option is enabled, this option is enabled by default.) If you want always to enable, write recreate=1 in fastcopy.ini.ฤก. Change updating behavior "overwrite the target" to "delete and recreate the target". If you want always to enable /linkdest optoin, write linkdest=1 in fastcopy.ini file. If /linkdest option is enabled, /recreate option is enabled tacitly. Personal Comment: Linkdest is best specified only thru command line, but not in main section. If there is no number after / then no HardLinks have been created or /linkdest is not specified. "TotalFiles: 18839/40 (3899)" means 40 HardLinks have been created. (In running, "TotalFiles:" format changes "number_of_files (number_of_dirs)" to "number_of_files / number_of_created_hardlinks (number_of_dirs)") f.e. HardLink can be reproduced as much as possible, if specify /linkdest option in ver1.95 or later. Hardlinks and FC - since the documentation is at times slightly difficult: I use Hardlinks a lot, so for me FC has been a blessing. Fastcopy handles Hardlinks very well, TC doesn't at all, as far as I remember.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |