Once it gets to 100/100, the hashing will be finished. This can take quite some time (it's really painfully long for old java clients like in Mac OS 9).

The drive *shouldn't* matter . . . you could just test by copying the \mp3\lime folder to the same drive as your LW app and see how long it takes to hash if you share it from there. If the drives don't matter then it will take the same amount of time.

btw--hashing, as you correctly noted, is very CPU intensive. On a quick machine, it takes about 10 minutes to hash 1 GB. Each file will now have a unique ID, so that if even 1 bit changes, the file will have a different hash. This allows files (and even parts of the file) to be securely shared. Once done though, the results are saved in the fileurns.cache preference file, and don't need to be repeated on each startup.

cheers--happy sharing