Posted March 19, 2006 Statement of problem Many users receive Downloaded tree does not match TTH root while downloading files. Usually when a user updates his/her client to the latest version it may cause the hashdata to become corrupt and therefore have corrupt TTH. Solution Close program.Delete hashdata.dat and hashindex.xml located in the Program files\ApexDC++\Settings folder.Restart program - your share will be rehashedThe problem should no longer exist. ^_^ Share this post Link to post Share on other sites
Posted July 8, 2007 the client or the one that is sharing ? im having that exact problem, i cannot download from many users cause of it :/ Share this post Link to post Share on other sites
Posted July 8, 2007 (edited) the client or the one that is sharing ? im having that exact problem, i cannot download from many users cause of it :/ You have to delete those two files, I think because you have a new TTH-Root after updating your client and the TTH-Root is indexed in those files. greetz Edited July 8, 2007 by Lizard Share this post Link to post Share on other sites
Posted July 12, 2007 OOOI never knew why i get this mesaje thnx for the tip know i know what i have to do :) Share this post Link to post Share on other sites
Posted July 16, 2007 /rebuild should fix it faster, since it won't require all the share to be re-hashed Share this post Link to post Share on other sites
Posted December 5, 2007 I took a look at this error with one in my hub and found that the problem was that the partition with the Inbox was FAT32 on 500Gb disk and I´m pritty sure that that was the problem. Share this post Link to post Share on other sites
Posted December 5, 2007 It may be, this is because, FAT32 can not handle files over 4Gb, however, the problem exists because of the files being corrupt, which double explains the answer. Everyone should use NTFS now anyway. Share this post Link to post Share on other sites
Posted December 6, 2007 Also FAT32 can´t handle partition over 130GB Share this post Link to post Share on other sites
Posted December 6, 2007 Also FAT32 can´t handle partition over 130GB You would notice that when you partition to drive though, surely? Share this post Link to post Share on other sites
Posted December 6, 2007 Not if you try hard enough Windows has a wonderful way of borking itself to such a level as to allow you to do such thing's then winge about it afterwards! Share this post Link to post Share on other sites