Mute hash creation problem

[Muter79]

Hello

I have experiencing problems with MFC-Mute (problem with version 0.0.5 and 0.0.6) when it is creating file hashes (place is shared files and flyleaf (i'm not sure is this right word in English, but hope you understand).

I'm sharing 1383 files to Mute network and sometimes when i add more files to shared folder, it takes really long time
before program start again create those hash files and after it have created some hashes then it might just stop
and doesn't do those anymore.

Example now i have waited 1H 15 minutes and program closing/opening does not help.
Could it be possible get somekind of button to this programs, so users can force program create those hashes.

Does anyone else have this problem?


Regards
Muter79

[tobiash]

Hi, I use Mute MFC 0.0.5 too and I am afraid that Mute MFC if not very fast at generating hash's, I have a amd 2800 Barton with 512 ram and Mute MFC only generates 6-8 hash's in a minute or 360 - 480 hash's in one hour that means that if I shared your 1383 files (in my case more like 3223) it would take between 2 hours 52 min. and 3 hours 50 min. 30 sec. 53 sek. to generate all the hash's.

Best regards
Tobias

[Muter79]

Hi again

I have now kept program open since 11:00 and now it is 17:30 and it haven't create any hashes.
Yesterday i move some stuff to share folder and it haven't start create hashes to those files...
Somekind of start hash creaton button would be great.


Muter79

[tobiash]

Try to uninstall mute mfc and install it again.

\Tobiash

[submarine]

there´s a button in the window that displays your files which updates your file list and hashes all files in the sharefolder which have not been hashed yet...

nevertheless some files i recently added to that folder are dipslayed but not hashed, is there any max file number mute mfc can share?

[jrocnuck]

There is a hard coded delay in the thread that hashes files in MUTE.  Every X minutes, the thread that hashes files will search for unhashed files, and then it starts hashing the files.  After so much time (I have to look at the code to give you the exact time) the thread takes a time out and waits for some period of time.

This is all done because it basically will prevent using too many CPU cycles on hashing... thus hashing is done in the background.

If you wait long enough, your entire shared folder will be hashed. 

Older text files out there used to say that you should clear you hash folder often.  THIS IS WRONG.  That was based on bad information that we provided in older versions of MUTE.

[submarine]

ok nice to hear from you jroc

btw: are you working on further improved versions of mute mfc at the moment? despite nates announcements it´s still the client where i get the most stable up/ and downloads...

[Muter79]

Thanks for reply.
Now i understood this hashing, so just wait and tadaa 
And now my almost all files are hashed so let's wait WinXP crash 

Thanks one more time
Muter79

[Zipsel]

I don´t know, if this is a "correct way" - but it works fine on my machine:

If you have very much files to hash, run NapShare 2.2.3 and let it hash your share. It is much more faster than MUTE. When hashing is completed, copy the hash-files to your MUTE hash-directory, start MUTE and click the "Refresh"-button in the "shared files"-tab.
That´s all 

CU,

zipsel