Am running 0.7.20 on an XP machine (not by choice), with an NTFS filesystem.Whenever the set disk limit is reached, SabNZBd pauses the current (and future) downloads as expected. However, when space has been cleared and the current download is resumed, it seems that the file that was being processed at the time of the error becomes locked to both system and user. This download will complete, but post-processing fails. No text error is shown, while the mouse-over text first reads simply as needing verification. After the Retry function has been activated, it fails again (still no error text), and shows that the download needs repair. Nothing changes with subsequent retries.
Checking the PAR files manually revealed that there is always one file that is incomplete, however this file cannot be accessed until the system is rebooted. When a reboot is inconvenient I have copied all the other files to a new folder and run the repair manually. I don't remember if I've tried using FileAssassin or similar locked-file-deleters. Anyhow I figured I'd post this now while I have a download in this state. If this isn't just a weird quirk with my aging system I'm glad to provide more info.
