

Now the second thing is all the ED2K servers are located on t and nodes to bootstrap for KAD is located on nodes.dat the t keeps all known clients valid transaction details of other users the known/t are hash of all the file you sharing. Now that being said that’s all based on your settings and resource. But keep in mind you don't need to hit 0MB disk quota for it to stop as you can have preallocation on which will fully write the chunk/parts to disk before its completed. Well i'm glad everything is back and normal working for you again. I'd also like to understand what the problem was and how I can avoid that in the future. Let me know if you have further tips to minimize aMule being unreactive while it is busy.
AMULE NETGEAR TORRENT
It's below torrent though, so that isn't a bottleneck, either.
AMULE NETGEAR DOWNLOAD
Number of downloads and total download speed is higher than I was used to with (only) Kad connection. The CPU is not the bottleneck since every other application is very responsive. Very often the GUI freezes while aMule is doing stuff (whatever that is). Since I haven't been connected to any server since maybe 1-2 years (only used Kad), this would not make much sense.įirst thing I noticed: I immediately was connected to a server. I did not copy t, t, known2_64.met because I suspect these are places where recent working server IPs are stored. I did set aMule to stop all downloads if that value was reached. See if moving these Blocks of file works as you will still retain your old setting and get rid of the junks, report back if it works or doesn't work. I don't remember which file it was that caused it as I didn't have enough time to investigate. So even if you did clean your disk space its allocated in one of the files and will show and throw error which I have seen once in aMuleD in CLI. The problem is when you ran out of disk space aMule force closed itself once it failed to write.

What you need to do is migrate your old files by copying into new one.īlock1: cryptkey.dat, preferences.dat, preferencesKad.datīlock2: nf, nf, shareddir.datīlock3: t, t, known2_64.metīlock4: ipfilter.dat, nodes.dat, t () So if it works you will have OLD and NEW aMule directories. You will notice you are able to connect now hopefully if thats the same problem which ill explain in few. So that shouldn't be the problemįirst of all locate your default aMule directory and back it up by just renaming it to something else, now restart aMule and then close it. My firewall is configured so I am used to always getting a "connected" status (not a "firewalled" status) with no problems. I also tried servers once more but as last time about 2 years ago, it does not connect to any servers. It also reports that it can't download some version file (amule.cpp(1627): ). In the aMule log I get this warning: "HTTPDownload.cpp(395): HTTP: WARNING: Void response on stream creation" I put this where aMule has the nodes.dat stored in the file system. No sources for any download and on the bottom right of the program window aMule reports that it is connecting, but it never gets connected. I always have active uploads very soon after starting aMule.
AMULE NETGEAR FREE
Now I started them again (there is free drive space on the download drive) but can't get a Kad connection. I was low on drive space and aMule paused all downloads. Connecting to servers hasn't been working for a long time.
