I want to share all my mp3's (over 1000 of them) and limewire is uploading them to share 1 by 1, its agonisingly slow, it should just read my mp3 folder, and then instantly allow all the other Limewire users to access them, but instead it goes "sharing 1 of 2"....10 seconds later "sharing 2 of 3" and so on. At this rate it would take days to allow other Limewire users to have ful access to my files! Can anyone explain why? Ive tried using a folder with all my mp3's in to share, and selecting a folder which had all the mp3's divided into subfolders under band names. This made no difference, so i dont think Limewire speeds up when putting files into smaller folders. I dont think its my computer as its a 700 mhz G3 imac, with OSX.1, so not to out of date, I think it might be my internet connection ( just a 56k, fot the next month or 2 , but it would be great if someone could offer a reply.

*also limewire runs slowly, is this my internet connection too? or should I allocate more memory for the app?

Cheers

Limewire is "hashing" the files (creating a unique identifier for each file). I'm no expert, but the waiting is like the "verify disk image" process that takes so long when mounting CD's or .dmg's. Don't worry--it can be very processor intensive at first, but helps others make sure that they get the exact file they wanted.

You could start by just sharing "rare" files: This would be better appreciated and save you the time hashing files most people can get anywhere. This would also save you some frustration if it turns out that your built-in OSX firewall and network connection make uploads very difficult.

File names are easily faked, and would mess up downloads from many sources, so the gnutella net has decided the time taken to create the hashes is worth the wait.

More exact technical answers are around, so post back if you need a better answer.

Short answer--share a few good/rare files until you sense the demand for more, and don't worry about memory--OSX handles it automatically.

In addition to stief's response, it should be noted that the results of the hash computations are saved on disk. Once they have been stored (in fileurns.cache), the time LimeWire takes to begin sharing after launch will decrease. At subsequent launches, it will only need to compute hashes for files that have changed or been added to a shared folder by another application.

Mark
@version@/10.2.4

Thanks guys, this hashing buisness was what i disnt know about. So once all my files have been "hashed" or whatever lime wire will upload all of hem into itself much quicker right? if so then, cool. Should i just leave limewire on for ages until its hashed em' all, and then quit it, to fix this problem then. Thankx again

You've got it. A quick note on the terminology - uploading is sending data; as used in this context, it's sending a shared file or portion thereof.

Once a hash has been computed for a file, LimeWire will make it available for sharing, so others will find it when performing searches, and it will be included in your count of shared files.

Yes, that's an excellent idea.

Mark
@version@/10.2.4

I was intrigued with your earlier post about starting one's sharing folder with some rare tidbits, and then enlarging when you "sense a need for more." Aside from psychic divinations, how would I SENSE it? I want to be a better sharer, I feel like I've mostly been on the receiving end, and the guilt is killing me, but other than that, I have no "sense" of how to tell what people are getting from me.

On another track, I very much have thought, "Hmm, I should get rid of all this boring popular stuff in my shared folder, and put my ultra groovy recordings from 1969 bootlegs, etc..., but what is the easiest way to share that from my iTunes folder. You know iTunes puts music in folders by Artist name. Could I make an alias of one of my rare Artist folders and put that in the Shared folder, would that work for hashing?