[Bobo the Red]

Damn the torpedos ... full steam ahead !!!

Love the product ... however (there's always a however) you gotta do something to speed the whole scan your files post install taking forever thing. Me and a few associates are sharing specific information freely (mainily with each other due to some unique naming ), but it has brought my fileshare total to greater than 49,000 ... its taken my RedHat 7.3 Distro box nearly 48 hours to scan all the files. ... I've tried Q-tella ... and frankly its lacking something ... really like the LimeWire and Aqualime (only on windows ... Aqua sux on linux) ... but this is ridiclous. ... BTW of the 49K+ files ... 10K (give or take a few) are MP3's ...

[efield]

From your point, there should be an option in the .props (haven't looked) to set the processor limit of hashing new files. It's low to avoid bogging things down but if you want the hashing to go faster then you could just change the .props.

[Paradog]

Originally posted by Bobo the Red
Damn the torpedos ... full steam ahead !!!

Love the product ... however (there's always a however) you gotta do something to speed the whole scan your files post install taking forever thing. Me and a few associates are sharing specific information freely (mainily with each other due to some unique naming ), but it has brought my fileshare total to greater than 49,000 ... its taken my RedHat 7.3 Distro box nearly 48 hours to scan all the files. ... I've tried Q-tella ... and frankly its lacking something ... really like the LimeWire and Aqualime (only on windows ... Aqua sux on linux) ... but this is ridiclous. ... BTW of the 49K+ files ... 10K (give or take a few) are MP3's ...

Hashing is using lot of cpu ressources and it is supposed to be slow. Maybe you should share less files, maybe those where you are sure that they wont be downloaded.