NOTICE: Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by Arbor, July 30, 2013, 05:16:36 PM
Quote from: Arbie on November 20, 2015, 10:21:16 AMReporting again... 2.5 more years with no delayed write failures. Faster hardware is probably helping, but I think Process Lasso's ability to prioritize I/O is key. Posting here in hopes that Google searches for Windows "delayed write failed" solutions will find it.
Quote from: Jeremy Collake on November 20, 2015, 12:31:32 PMGreat to hear .I'm in agreement with Ed here. What you are seeing in Process Lasso (or rather yourself via Process Laaso!) fix a bug in FastCopy. It probably starts itself via the Task Scheduler and is unaware that when applications do that, they inherit the Task Scheduler's low I/O priority class.
QuoteSpecify "Full Speed", "Auto Slow"(*1), "90%"~"10%", "Suspend".If you feel it is hogging resources, it is recommended to set to "Auto Slow" (If it detects mouse moving/active window changing (and FastCopy window is not foreground), it is slowed down).If "Full Speed" is not selected, low process priority class is set.(This setting is not saved by job manage)