Both these clients seem to get faster, more continuous and consistant connections than LimeWire.

Is it possible to just take the many incomplete files I have in LimeWire and restart them from Poisoned or XNap?

If so, How? I believe both Poisoned and xNap use invisible folders to store their incomplete files and may use some alternate naming convention.

Anybody technical out there able to walk me through making the change over?

Not likely. Trying to resume incompletes even between Aquisition and LimeWire didn't work, and they use the same core.


The T# in front of the incomplete filename is just the expected size in bytes of the complete file. All the other info about the chunks completed and pending is in the downloads.dat file.

Just finish the file with the appropriate client.

Thanks.

Sorry to hear it. LimeWire is so frustrating to use and not worth the results and the tedium of getting them. Is Acquisition any better?

Most of these programs seem to be held together with chewing gum and string and are basically undocumented.

I suppose you get what you pay for.

Acq looks easier, but since the core part that handles the connections, searches, etc. is LW , any differences you see will be based on other factors like your connection and setup. Frustrating!? Where's the problem? Mine turned out to be my ISP messing with p2p connectivity.

The documentation for any p2p application cannot keep up with the all dynamic changes that are going on--even some independent developers have noted they can't keep up with all the code changes, let alone all the changes going on with personal computer systems and internet connectivity in general.

The development of gnutella is certainly not "chewing gum and string"--it's pretty sophisticated and frankly, I'm amazed that so many of us newbies can just jump on and go. Poisoned, for example, is just a current experiment and it will be interesting to see how long its developer can keep on Sharman's 'good' side.

here are some links

http://gui.limewire.org/servlets/Bro...vs&paged=false
http://core.limewire.org/servlets/Br...vs&paged=false
http://www.limewire.org/project/www/...w-summary.html
http://groups.yahoo.com/group/the_gdf/

Thanks for the links I'll look into them.

I have not explored every nook and cranny in these forums but it seems most users are not getting more joy from LimeWire than I have. I am sure there are those more expert at LW but I gave it a fair try out on several machines and set-ups over the last few years. It seems to have the same symptoms and performance wherever and whenever I tried it.

If as you suggest it may be my ISP messing with the p2p connectivity. What can I do about it (let alone detect it) and why would it exclusively effect LW and not the large number of other peer to peer software that I use?

Come to think of it, I am into my 6th or 7th ISP. Is this a conspiracy?

http://www.limewire.com/english/content/netsize.shtml shows most are having quite good success--the people only search out these forums when they have problems, and they are a very small portion of the regular users.

re the ISP problem, others here on the forums generously helped me find out it wasn't LW. Thanks to an upload packet dump analysis and comparisons between two ISP's, my preferred ISP told me they were using the NBAR p2p controls that CISCO supplies with all their routers (not all ISP's turn all or part of its options). They also tried the Sandvine p2p controls for a while.

The solution here was simple--they allowed me to connect through a high numbered port .

I use gnutella to share legitimate content, so could expect my ISP to cooperate and honour my needs, which they eventually did. However, most of the help desk were unaware that the network engineers were experimenting with p2p controls, and I had to learn by trial and error how to set up and configure the systems (Mac only) and home network properly to be sure the problem wasn't at my end, which it often was at first.

My crude methods involved trying several clients (LW and Acq mostly; drumbeat and neo once or twice--ashton hadn't written poisoned then) on several machines for over a year, switching between direct and NAT'ed connections, and all the while trying to keep up with the changes in hardware like router and cablemodem upgrades, up Java, OSX, and other gnutella users. Firewalls are the biggest block to p2p communications.

Too many variables, and probably too little help to you.

Short answer? Focus on uploads first to learn how downloads can get screwed, and find out if poisoned uses port-hopping to get around your ISP's.

Thanks you have given me quite a bit to digest s:-)

I am just trying acqlite and was initially puzzled by it reporting no connection (many others got it too) and failure to search or download. I got past that by a stupid technique. Think I can blame OSX for that.

I don't have any firewall on at all and it is as poor at transferring as LimeWire. Uploads seem to work much better than DLs, but that is no consolation s:-(

Have to give Poisoned its due. It works very well indeed, bar a few bugs in the latest release which i haven't fixed up in Panther.