georgenistor Posted April 16, 2015 Share Posted April 16, 2015 Hello BitComet, Today I have seen another error. It happens when you have many tasks and you are forced to close Windows. I restart Windows and start BitComet again. I see now first task starts with a HASH check and the next tasks are QUEUED for a HASH CHECK. If I do again a STOP ALL and Exit, than I restart BitComet and do a START ALL, I see the current task without HASH CHECK. In other words if a HASH CHECK IN PROGRESS is stoped and BitComet restarted it does not RESTART the HASH CHECK. It is like HASH CHECK completed successfuly, but it did not complete. The other tasks , those queued restart a HASH CHECK, but if BitComet is restarted if does this behaviour until all tasks are like they are HASH CHECK completed. George Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.