Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

it make sense...can u give me a link to configure amule forsolve this problem? or can you give me the procedure?
thanks

You said 'he' referring to another person. If they make excessive requests which can happen from modified clients and it will be banned, which is temporary as its cleared when you restart.

How do you know the problem is aMule? or even on your end? have you done controlled test to verify?

The person who is downloading may have misconfigured client which keep asking for chunks and aMule just filters it and then eventually bans it for excessive requests. I have seen some clients who takes 40-50mins to download few KBs which is isolated only to them nothing to do with aMule.

If you insist its on your end you should share something very popular like linux iso9660 and see.

if my client is banned, why restart amule, download again?

How do you know the problem is aMule? or even on your end? have you done controlled test to verify?

The person who is downloading may have misconfigured client which keep asking for chunks and aMule just filters it and then eventually bans it for excessive requests. I have seen some clients who takes 40-50mins to download few KBs which is isolated only to them nothing to do with aMule.

If you insist its on your end you should share something very popular like linux iso9660 and see.

hi, when I open amule, he starts downloading even at 300kb for each file.
After a few minutes he stops downloading.
I close it and reopen it and it starts downloading again.
It is a pain to close the program and reopen it every 5 or 10 minutes.
Is there a solution to this problem?

Thanks

Hello! Not sure if someone else have this problem with 2.3.3 universal version (running on M1 architecture).

With the previous version (wxWidgets 3.0.5) the interface looks right, but as others have posted before, it is sandboxed.
With the latest version (wxWidgets 3.1.5), it reads my old config again, and it is usable, but the interface is all wrong: some fields appear with their minimum possible size regardless of the window size.

Has anyone else seen this? Has anyone compiled an arm64 or universal version with wxWidgets 3.0.5 and no sandboxing?

Thanks!

Yes, I have seen this behavior for some UI elements, but, I had to switch to wxWidgets 3.1.5 to be able to add support to Dark Mode in aMule, regardless it is not an "officially" supported version in aMule.

Anyway, a new aMule 2.3.3 Universal2 binary, compiled over wxWidgets 3.0.5 (not sandboxed) is already available. It will not have Dark Mode support on macOS, but neither will have those small UI glitches.

Actually, for everyone's convinience, the wxWidgets 3.0.5 binary will force by itself the "light mode" for the application (preventing UI problems if macOS is working in Dark Mode by default).
 

Hello! Not sure if someone else have this problem with 2.3.3 universal version (running on M1 architecture).

With the previous version (wxWidgets 3.0.5) the interface looks right, but as others have posted before, it is sandboxed.
With the latest version (wxWidgets 3.1.5), it reads my old config again, and it is usable, but the interface is all wrong: some fields appear with their minimum possible size regardless of the window size.

Has anyone else seen this? Has anyone compiled an arm64 or universal version with wxWidgets 3.0.5 and no sandboxing?

Thanks!

Yes, I have seen this behavior for some UI elements, but, I had to switch to wxWidgets 3.1.5 to be able to add support to Dark Mode in aMule, regardless it is not an "officially" supported version in aMule.

Finished the last strings that had sprung up since the last update.

This is a really old thread. According to the latest post, it offered a working 2.4.0 version in 2016, however the latest packages in 2022 are still 2.3.3. Why? Did anyone else try this? Were there any problems?

You also need to open the machine firewall for these 2 ports