I think not on the speed, but you obviously need to do some research, because you only saw the specs you wanted. Hint - hardware clock speeds and how it effects software.

rkapsi makes a good point and explains well why it takes LimeWire time to load.

But as an after thought-If you want a machine that does fantastic number crunching you should switch to a Mac. They've run circles around PCs for years in that aspect.

Patience is a virtue

As I said, the hashing process is running in a throttled mode. On my G5 approx. 10MB/s => ~600MB/minute. You haven't said how large your files are...

Well, and HL2 and Doom3 have nothing to do with cryptography (former make heavily usage of the GPU - in fact they're known for their excessive usage of the GPU - and the latter is a CPU only process).

60,000 files - pieces of work I created totaling near 170gb...

It feels like its doing 10mb/s

It feels like 10 mb/s...

On Direct Connect it hashed them at over 100mb/s

So... how many files does LW does still need to compute SHA-1? Maybe you should let LW do that in a night (wow 170gb shared, you are really a DC user...). Anyway, welcome to you and your files onto the Gnutella network!

:D

Hi, thanks for the warm welcome :-)

Leaving it on overnight got 16000 total done - then it had a problem, had to restart LW :-/

Well, still no luck - leaving it running all night - its still not done and it encountered 3 problems while running... File hashing did not recommence properly..

Would it be possible for the LimeWire developers to make a small tool that hashed the files and created the database so when you start LimeWire they are automatically shared?

It takes 10 mins for my shared (2.5 k files) to load. It depends not only on the no. of files but also the size of the files & the speed of your computer, & I suspect version of LW & OS. It took much, much longer to load half as many of the same files in Mac OS9 compared to OSX on the same computer.

Your suggestion sounds good. I don't know the practical sides to it.

I would try to separate files in folders of 1000 files to isolate the file that makes LW crash.

Problem is I have all files sorted already..

Practical use of the tool I suggested would basically allow users to hash/share the files before opening LW - If there is a file that has a problem it would tell you which one...