by siavoshkc » 31 Jul 2010 12:36
Let me tell you whole the story:
I had a 120GB HDD which was faulty. It didn't corrupt data just used to stopped working sometimes. But yesterday it became more dangerous as it stopped Windows. So I got a new 500GB HDD and copied incomplete on it. Disconnected old HDD and ran Shareaza, changed incomplete from D:\Incomplete to E:\Shareaza\Incomplete (new location) then restarted Shareaza to read new folder. When started Shareaza only showed name of the dls and green line which indicates the part of dl which is verified. I started to merge using advance properties with incompletes. It was fine till I restarted Shareaza to see everything was OK, but it was like I didn't merge, all progress was gone again. I copied incomplete folder to my other PC and ran a Shareaza debug build on it. Again Shareaza couldn't detect progress. It was when I posted here and you told me to check privileges. I don't know why Windows made newly installed HDD read-only, and more strange that I was able to copy incomplete and other folders on it while my user account should haven't had write privilege by that time. Anyway I reconnected my old HDD and I'm downloading on it. It had letter F: when I connected it but Shareaza couldn't make preview of it. After investigation I found out Shareaza is using old path (D:\Incomplete) instead of new F:\Incomplete for previewing. So I changed drive letter to D: and everything was fine then.
What I guess now is everything may would be OK if privileges was right when I was merging and the other thing is Shareaza won't read incompletes correctly if their path is changed. But why?