1) Ok. So now we get to wait for LW to hash our files at startup. For whom? I have yet to see a hash number show up for any sort of file in the new version. Who is benefitting from this information?

2) It was bad enough before. Now, LW is being "helpful" in telling me that I am already downloading a file two MB less and with nothing in common with the title. Other less obvious errors are happening with file recognition.

When is hashing going to work for LW (and when are you guys finally going to do something about the Morpheus thing???)

End rant

Correction: what was stopping downloading a 110 MB file was a 25 MB file, again with nothing in common with the name. Also files I haven't even selected are showing up in my incomplete folder at 0 K. What is going on with this new build?????

That happens to me too...

"Hmm... Let's get that one!"
"Hey! It doesn't appear in the 'Downloads' box!"
"Let me get it again..."
You are already downloading **EDIT**!
"What? No!!!"

True... I was trying to download that song... Then I waited for all of my downloads to finish, then tried it again...

Downloading!!!

Try that...

If you have no other downloads, just, maybe, I don't know.

Please further define "bad download". Also what do you mean by "Sometimes I could wait awhile, and then try to download and I wouldn't see it". Wouldn't see what? Are you saying that LW thinks that you are still downloading something which you indeed are not, but if you wait, then you wouldn't see the "You are already downloading" message?

I am talking about files and sizes that have nothing to do with each other, as I said in my earlier post. The two files would not be grouped should they have shown up in the same search, but for some reason LW decides they are the same. The MB amounts are not insignificant differences.

Would it be possible to get around this problem by allowing the user to rename the "duplicate" download? I frequently try to start my downloads from several sources if at all possible (and kill all but the most successful connection), so I don't want LimeWire to tell me that I'm already downloading a similar file. I guess this would result in a lot of "Artist - Song.mp3 (2)" filenames. Maybe LimeWire could remember the original filename and fix it after the download completes.

Personally, I always rename "**EDIT**" to "**EDIT**", but I don't think most users bother doing this.

Brandan L.

Isn't file hashing supposed to take care of the name problem? I have had up to seven different names for the same file -- all in various sizes in my incomplete folder. Big deal on smaller music files, but movies!!! Just when I think I have them all possible permuations covered, someone capitalizes a letter, adds a hyphen, or misspells a word. I know by now I have download GB's of stuff that eventually gets trashed. Think how much network traffic this would reduce?

At least on a Mac, you can make aliases (shortcuts) to the files and LW can read them, so you could have various common names for the files and more people could complete their uploads. Problem there, of course, is the limited number of characters.

I used to change the names of bad files also, until I realized that people were still quite happily downloading them as part of swarmed downloads. If they never opened the grouped list, they never saw the world "BAD", which on a Mac is often the only thing I can add, since "CORRUPT" has too many letters. Also there are some movie files that are garbage on the Mac -- QuickTime Player can't always convert rectangular pixels to square, for instance, and these have to be recompressed (hours of work). Or an avi without a header is utterly useless. Most other vid probs can be solved one way or another.