Introduced sometime after 2.5.0 is the feature that HashCheck now always waits before running concurrent processes unless you manually click "Run now".
Shouldn't this waiting only take place if both processes are running on the same mechanical hard drive?
There are two scenarios I've run into that this waiting still takes place despite it not really making any sense:
- both HashCheck processes are running on an SSD or even a RAMdisk
- both HashCheck processes are running on completely separate mechanical hard drives (i.e. creating checksums on Seagate HDD, verifying checksums on Western Digital HDD)
Introduced sometime after 2.5.0 is the feature that HashCheck now always waits before running concurrent processes unless you manually click "Run now".
Shouldn't this waiting only take place if both processes are running on the same mechanical hard drive?
There are two scenarios I've run into that this waiting still takes place despite it not really making any sense: