prpr
Well-Known Member
Yes, you're the janitor.So far as I can see, the only clean-up is when the process completes; any aborted (and unresumed) downloads will hang around indefinitely.
Yes, you're the janitor.So far as I can see, the only clean-up is when the process completes; any aborted (and unresumed) downloads will hang around indefinitely.
Ok, that's not ideal when the average punter (like me) who just uses the supplied packages without knowing what's going on behind the scenes and uses the standard interface can't see the files. I wonder what else I have lying around in there?! Or maybe they'll get deleted once the disk gets full - hopefully before any of my usable files.Yes, you're the janitor.
Indeed. It's got left over, but the date is curious.I'm assuming this is 5GB of unusable file which somehow needs to be deleted?
No, really, they won't. How would anything know what to delete? There is a Humax option to delete stuff, but I've always had that firmly turned off as its functionality very seemed poorly defined in the manual (i.e. WTF knows what it's going to delete and when?) and the software wouldn't expect to see any foreign files courtsesy of the CF processes anyway.Or maybe they'll get deleted once the disk gets full - hopefully before any of my usable files.
Yes, rename or delete ought to be possible with Filezilla (he said, as a non-user).I'm assuming this is 5GB of unusable file which somehow needs to be deleted?
I don't think I've ever filled up the disk that much, however that it was over 5GB again does make me wonder if it was the same problem as I had that started all this off!Just thinking maybe the decrypt failed because the disk ran out of space (at the time).
Clean-up: thinking aloud, is the pattern x.y.z sufficient to identify an unwanted file?
I shouldn't think so. The (hardware) decryption process is not memory intensive, just a case of copying a file from one place to another.does make me wonder if it was the same problem as I had that started all this off!
You're talking about specific whitelists or blacklists... not very flexible, and requiring maintenance.Interesting question, don't 'normal' files have a fairly small number of suffixes?
.hmt, .nts, .ts, .thm, hmi, .mp4 etc.
Similarly anything ending .part or .DECRYPT is presumably a temporary file - or at least not normally usable? (Just guessing really)
That does seem to make most sense.Hence the suggestion that a package capable of generating rubbish should be responsible for identifying it.