FWIW, 0.5.8.5 broke re-checking for me.

As I mentioned already , my Deluge setup suffers from the need to recheck some torrents at every start-up. What is annoying is that Deluge complains(via messagebox) if the size of the torrent it is going to re-check is larger than the available disc space, even though the torrent is already download...

The obligatory rechecking is still there with 0.5.8.1, though the situation seems to have improved somewhat - only one torrent is usually rechecked.

Thanks, I'll try that, but it's only a palliative. Another observation: sometimes Deluge fails to notice that I've deleted the downloaded files(manually) and keeps on "seeding"..even though there are no files to seed. And when it finally finds out that those files are missing, it begins do...

Another observation: sometimes Deluge re-checks _some_ torrents on next startup even if I haven't booted into Windows since last time(so uTorrent had no chance to alter their modification time). And sometimes there is no re-check even after I've used uTorrent. Maybe this is a bug somewhere on a bord...

If some torrents have been fully checked, then there is no need to start checking the whole list from the beginning - it shouldn't be very hard for Deluge to remember that. deluge writes its fastresume file on shutdown, but only if the torrent is in a stable state (iow, isnt being checked). if you'...

Thanks for your answer, that's because utorrent changes the modified time of the file, so deluge notices that it's different. Actually, in this case utorrent changes only the "Time accessed", not the "Time modified". That's what I see in Windows properties dialog. and yes, you ne...

I have a problem using Deluge together with uTorrent - every time I start Deluge after I've ran uTorrent(under Windows), it thinks that my files(which I share between the clients) have changed and goes on to re-check the hash. It is very annoying. Another problem is that Deluge doesn't seem to remem...