I was under the impression that that was part of the feature set of this tool - ie that if you modified resume.dat that the tool recalculated the fileguard hash value so utorrent would be happy with it.
And yes, thanks Ultima - but am I missing something? People in this thread talk about using it to modify resume.dat, but noone else has asked about the hash issue?
IE - Am *I* doing something wrong? or am *I* misunderstanding what the tool does?
And further, if the hash isn't right, is it expected that utorrent will go ahead and use it anyway ?!
Oh and PS - I was using the 0.4.1 unicode version. FYI - It seemed to work on W2K except that the drop downs on the find/replace dialogue had no options (but I ended up doing the edits on an XP system)
jewelisheaven - re: your other questions (wrt the bug report) - I've added the msg to it, and yes I'm sure the .old wasn't involved as I moved everything out the directory when experimenting.)
I'm a bit confused about this tool wrt resume.dat
I have a resume.dat that utorrent doesn't like (after a system crash) ie - When starting, utorrent logs "Warning: file integrity check failed (hash doesn't match): ...\resume.dat", renames the file .bad and I loose ALL torrent info.
I pulled this resume.dat up in this editor. The editor does NOT report any hash error. (huh?)
I deleted the last torrent, then saved the file. The fileguard hash value did NOT change.
I started utorrent using the modified resume.dat.
Again, I got the SAME error in the utorrent log, BUT, utorrent went ahead and used the resume data anyway - ie I did NOT loose everything (just the one torrent I deleted with the editor).
Is this the way everything is SUPPOSED to work?
When does this editor recompute the hash?
Why does utorrent say the hash fails (both orig and modified), but the editor doesn't?
Why does utorrent go ahead and use the modified 'bad' file, but not the original?
BEncode Editor
in General
Posted
I'm a bit confused about this tool wrt resume.dat
I have a resume.dat that utorrent doesn't like (after a system crash) ie - When starting, utorrent logs "Warning: file integrity check failed (hash doesn't match): ...\resume.dat", renames the file .bad and I loose ALL torrent info.
I pulled this resume.dat up in this editor. The editor does NOT report any hash error. (huh?)
I deleted the last torrent, then saved the file. The fileguard hash value did NOT change.
I started utorrent using the modified resume.dat.
Again, I got the SAME error in the utorrent log, BUT, utorrent went ahead and used the resume data anyway - ie I did NOT loose everything (just the one torrent I deleted with the editor).
Is this the way everything is SUPPOSED to work?
When does this editor recompute the hash?
Why does utorrent say the hash fails (both orig and modified), but the editor doesn't?
Why does utorrent go ahead and use the modified 'bad' file, but not the original?
???