Hey all,
Sorry if this question has been answered before. I did a quick search, but didn't find appropriate results.

My music library seems to reset itself every time I start Limewire. Well, it remembers the shared folder, but seems to have to churn through each and every song every time.

I have 5000+ songs, and it takes limewire 1-2 secs. to recognise to be able to share 1 song. This adds up since it attempts to share all 5000+ songs. This keeps my hard drive very busy, not good.

But this didn't used to be a problem. It used to be able to find and share my files by the hundreds per second.

My only solution is to not share songs. But this seems to defeat the purpose of Limewire, and would be counter-productive to the PtP community. And that's 25 Gigs you woun't have access to.

PowerBook 800
OS X 10.1
512 MB RAM
Limewire 2.8.5

Thanks,
Desprez

No one has anything to say about this? Wow.

Do you ever exit LimeWire forcefully? In that case it would not save the hashes of files it already analyzed.

No. I use file menu quit, just like any other program.

I've even waited for the WHOLE THING to finish before quiting once. Didn't help.

Am I to understand that no one else has this problem? That's odd...
I don't think I've done anything unusual, except my "shared folder" is used by iTunes as well

Here is the structure...
[Root]
[Music]
[...lots of folders by artist...] [limewire] [incomplete]

The folder [music] is the folder itunes organizes all of my mp3s in, as well as the shared folder for limewire. Does that make sense?

Would agree with Desprez that connection speed and sharing files at start up of Limewire is now extremely slow with latest update. Searches are slower as well. Opening up helper apps such as Quicktime, but especially iTunes is painfully slow. Seems like something was changed for the worse in their last update.

Sorry, not a techie. Can't offer any suggestions.

Usually LimeWire analyzes each file only once and then saves the data to a file called "fileurns.cache" so at the next startup LimeWire can just read the data it saved without having to rehash each shared file. Somehow LimeWire doesn't seem to do so correctly. Does LimeWire save your preferences correctly?

If not, there might be a problem with your preferences folder which is usually:
[home]/.limewire

LimeWire will need writing access to that folder.

phtfxr, I haven't seen any slowdown of other parts of the program that you mention, but I have to admit that they were never that speedy to begin with...

@trap_jaw, I'll check that file, but it seems to save my preferences just fine.

This problem happens to me too, it has gotten so out of hand that Limewire will quit out suddenly while trying to share the list of files. At least it did so in 2.8.5. 2.8.6 is a slight improvement, I can almost get limewire working for more than an hour at a time before it quits out.

Just letting you know that I've had that same problem with the last several versions. It starts over every single time.

I downloaded this latest version in hopes that the problem would be fixed. Now I can't run LimeWire at all without it freezing my whole computer.

It doesn't seem like too many people are having these problems though. Feeling alone, I've given up. I just posted a new thread recommending Acquisition, although I now see that there have already been whole threads about it. In any case, Acquisition works much better on my system, which is a G4 500 running OS 10.2.3

^ Hmm....how is it possible that the problem is only isolated among a small group and not everyone? Does it have anything to do with the fact that our machines are older (I know some guy who's got the latest and greatest dual processor G4 and he says limewire works fine).

Acquisition is a good alternative. It ain't perfect but at least it doesn't quit out after 15 minutes.