Has anyone else noticed that there is never a response from anyone on the Slimewire staff? Most people responding are computer geeks (plz be aware I use term in non insulting manner) offering advice that they "think" is correct, yet Swinewire staff remains strangely silent on all topics with the exception of cash offers. Why is this? RIAA maybe? Confound and confuse all on gnutella systems maybe? What happened to my other negative posts? Is Jackie related to that famous Bruin, Ed? What color are my undies? Why did I become a Lumberjack? What is my name? How did I get here? Who owns this beautiful house? whose is this beautiful wife? must remember medication...................toodles for now fellow revolutionaries. Viva La' Mardi Gras!!!!!!!!!!!!!!!

*What about sberlin? isn't he LimeWire staff?

OK--I'll bite. Yeah, I noticed too. Once I realized that my expectations were a pompous presumption, I learned to appreciate the open community nature of gnutella.

$10 gets you about 5 minutes of first level support. The help here is free and once I learned how to use the search button, I realized what an intolerable ignoramus I can be. Learning how to read these posts helps: the "thinkers" have often given me some good advice, and taught me to realize who the "knowers" are.

Good luck getting beyond vent. Hope you can help someone someday.

motrhed3 - you are right. I've had 4 messages saying I have a bug and to report same to bugs@limewire.com - no response other than from a technician saying I was yelling because I wrote in capital letters and if I did that again I would get no help. Well, I STILL have no response from bugs...
I also wrote to the CEO and some other shm..cks at Limewire- no response.

'file not found' only effects the uploads also. it means that someone sent a request for a specific file index (every shared file is given a certain index) but gave the wrong filename for that index. there's two reasons this can happen: one is because the person who is serving the file happened to hit 'refresh' in the library, causing limewire to reorganize its library. the other is because there's a problem with the person sending the request -- it got confused somehow.

like i mentioned earlier with the XYZ.doc and ZYX.doc answer, limewire doesn't use index or filenames anymore when it doesn't have to -- it uses the unique hash of the file (when it can), which means that even if someone hits refresh and the library is reorganized, the request will still work. it also lowers the chance of buggy requests, because all you have to keep track of is the hash, not the name and index.