Have something to say?

Tell Code Sector how they could make the product more useful to you.

Code Sector: ProductsDownloadsPurchase

In Progress

Queue System

How Jobs Are Handled ☑️ Parallel Execution (Default) Multiple file transfer jobs can run simultaneously The system allows up to a configured maximum number of parallel jobs Jobs start immediately if there's capacity Queue Chains (Sequential Execution) When you queue a job "after" another job, they form a chain Jobs in a chain run one after another, not simultaneously Useful when you want specific order or to avoid resource conflicts When Jobs Get Queued Automatically Device Conflicts The system can detect when jobs involve the same storage device To prevent performance issues, it may automatically queue jobs on the same device to run sequentially This behavior depends on your settings (all devices vs. slow devices only (e.g. HDD)) ☑️ Capacity Limits If the maximum number of parallel jobs is already running, new jobs wait in queue When a running job completes, the next waiting job starts automatically User Controls ☑️ Force Start You can override the queue system and force a job to start immediately Useful when you know the system resources can handle additional jobs Manual Queueing You can explicitly queue a job to run after another specific job Creates a chain where jobs execute in your chosen order

Code Sector 22 days ago

2

TeraCopy

TeraCopy4 RC, error in multi-target free space check

In reviewing the postings prior to creating this ticket, I did not see this issue yet described. If this is a know bug, please ignore.] Thank you for the work progress to date! [BTW: Also—many thanks for the ADS xxHash3! This will be very useful. Waiting to release 4.0 to file the purchase order for my next set of licensed copies!] TEST SETUP: Windows 10v22H2, CU 20205.04b. Windows 10 [Version 10.0.19045.5737] Two Target HDD’s, each with 7.4TB of free space. [NTFS, 4KB Cluster size, Fresh Format. WDC external, 8TB USB3 HDD] Source HDD, 16TB Seagate SATA HDD, (NTFS, 4KB Cluster size), with a source directory tree to be copied containing 4.5TB of files. Copy from source to both targets. [Initiated via a RightClick→TeraCopy from DirectoryOpus 13.14], If “Check for free space” is set, then the operation fails with the error: Insufficient free space, need 1.6TB. It would appear the the free space check routine is adding together the allocation of both destination copies and applying this value to the free space available on the Target file systems. [4.5TB + 4.5TB = 9.0TB. 9.0TB - 7.4TB = 1.6TB] The operation completes successfully if the “Check Free Space” option is disabled.

John Schilling About 2 months ago

TeraCopy

TC should wait not error in some cases. (Error 21: Device not ready)

I've been trying to move a huge steam library across to my backup NAS server to rejig my array in my computer. However, I notice that some of the errors I was getting was error 21 device not ready. I know that TeraCopy will wait for a target to come back online on currently active Transfers as it will show this in yellow when this is the case. However, other files seem to just get skipped over when using the multi threading. In these scenarios, I believe TeraCopy should wait for the device to be ready and try again, Rather than just logging it as an error and continuing on. This is because that this problem can persist for thousands of errors until the device eventually reports it's ready again, Meaning thousands of transfers that need to be tried again. This can also be a problem if you get an error for target not found. If you're overwhelming a NAS server, It may drop the service that's facilitating the transfer until it is ready, and then bring it back online. (SAMBA,NFS,ISCSI,etc.) This causes a problem if you want to leave the transfer unattended overnight for it hopefully to be done next day or come back when it's done. It could even be an option where you can set the retry timer and the amount of retries it should do before moving on. This would give a good level of customization to the transfer, and allow you to set and forget when sending to a unstable or slow target such as a network share or Spinning rust. It could even be that these are skipped over in its own separate class of error, and even tried again at the end of the transfer should it be skipped dew to the max wait time being reached. When such an event happens and it is waiting, A clock icon could be shown next to the files affected in the transfer. If the timeout is reached and fails again, It could then have a yellow clock icon Indicating the timeout limit was reached and the software moved on. At the end of the transfer, it then does a last attempt to try again, Counting down till it reaches the max retry limit. Shall this fail. It is then classed as failed and logged as an error. This retry mechanism would also be helpful in circumstances where a drive may just have a transitory error, Something that is likely to happen if you are blasting data at a target.

TheCodeingPadawan 3 months ago

TeraCopy

Much thicker 'overall progress' bar

With the new v4, the overall progress bar at the bottom is barely a hair’s width, making it not easy to see. Please can you thicken it up? And the move to a circular progress bar for the per file progress is also not as clear as it used to be. I’ve been using TeraCopy for years, decades? a looooooooong time… And a license holder for 10 years. Over that time, it’s gone through many iterations, many GUIs. I can’t remember what version it was previously, but you did have a very good, very useful, very clear setup, but you moved away from it. The combination of the transfer speed graph and the progress bar was excellent (v3.0?). The new smoothed graph that’s full width, that squeezes more and more transfer data in as it progresses, sure looks cool, but simply doesn’t give us the same indication. Having these for both the file(s), and the overall progress would be very useful. I’d love to get an option to restore that! We need to know if the transfer speed has dropped… We need to know how far through the current file(s) it is… We need to know how far through the complete job it is… We need to be able to stretch out the window to give us more granularity as needed… We need to be able to know all of this, what’s what at a glance… At the moment, it’s not as clear as it could be. Some of us have to move a LOT of files around, and we need to know all the juicy details that your ‘average’ user doesn’t care so much about… They just want it looking pretty. So, could we have a thicker overall progress bar, please? And an option for us that need more/better info at a glance, which shows v3 style progress/graph combos for both, would be very welcome. Loving the new multi-threaded SSD to SSD copies!

topbanana 5 months ago

3

TeraCopy

Completed

Timestamps aren't completely kept on copy from the first original folders

Any folders copied or at least many I have seen, have a very slight difference in filetime. I will link my post I first made on a different site, then link this post to there so they connect. https://www.voidtools.com/forum/viewtopic.php?t=16126 I will post the timestamp difference at least, this only applies to original folders it seems. So if I copy original to somewhere else then copy that copy to somewhere else, both of the copies have the same time. For TL;DR: Original date created: 2023-03-10 06:27:11:1345075 Copied date created : 2023-03-10 06:27:11:1345168 Also does anyone else’s Firefox lag with this website, specifically ideas.codesector.com..Maybe it’s a NoScript thing I have disabled, Idk. It’s a very slight lag only.

Herkules97 5 months ago

5

TeraCopy