Shadow's BLOG

Hello all,

I have requested an new function in BC v1.8. There are real problems in v1.7, so I decided that this was the perfect time to make this request.

Here is a reprint:

Requesting auto scheduled hashcheck in v 1.8

Since the developers have to fix the "Disappearing tasks" problems in v 1.7 anyway, I am requesting a user-settable automatic function to automatically stop a task, hashcheck it, and restart the task. The function should have a default setting of 1 day from the time Bitcomet starts up. The user should be allowed to reset the default to anything from 30 minutes to 30 days.

This has been a systemic problem from the beginning. I have been waiting patiently for the developers to realize the problem and put it on their "To-Do" list. Now, there are so many complaints about this that I feel this is the release to do something about it!

It seems that when a task has been running for a while, something in the system allows......

Bitcomet 1.06 seems to have qute a few changes from previous versions.

Functionality has been reduced in at least one area that I have come across. If you want to manually move your downloads to another partition or drive, you will have quite a few problems in this release.

In previous releases, you could stop the task or stop Bitcomet completely, then manually move the files from one drive or partition to another, restart, then change the destination property of the task, and either manually hashcheck or the program would detect a change and ask if you wanted to hashcheck.

Now, if you move files, when the task or Bitcomet are not running, you cannot just change the destination property and continue. You will get a popup showing that the destination already exists, without presenting the option of hashchecking the new destination. It just makes you stop.

The only work-around is to delete the task, but be sure to uncheck the box for deleting it......