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

Hi

I just bought a mac mini late 2014 and installed aMule 2.3.2.

aMule works ok at the beginning, but as soon i add some files to download it goes unresponsive or extremely low (more than a minute to respond to any action or click).

Same happens to me on my previous mac mini, this is why i was using previos version of aMule, but for Hig Sierra it looks only 2.3.2 version can be used.

Anyone with same issue? an y idea on haw to fix? there is any way to use previous version on hig sierra?

More Info:
   - System is really celan, since just brand new...
   - other applications works fine
   - I tried with different locations of the temp files

thanks

Before the Internet was common and cheap enough here in NZ, I was doing TCP/IP (very slow but still effective, 1200b/s half-duplex) by Ham Radio. On 386 and 486 machines (even 286's?) running DOS 5-ish, JNOS gave a semblance of linux's functionality and language (Slackware Linux could be up to 30x 1.4MB floppy-disks!, and required 386 or better processor), and with radio's fragile connections an occasional 'tcp kick' could refresh a connection. I'd venture a similar command could still be useful: 0.1 kB/s connections timing-out...
... or is this OS-level stuff? The internet's data transport is pretty much all Linux ...
Failing that, could there be a 'refresh' of search per file? a re-search without disconnecting existing connections? I've found some sources with long queues will allow me to re-join closer to the 'head' if I 'Stop' the file and 'Resume' - others re-join (if at all)  at the tail If a parallel search turns up shorter queues one could re-join there.
What think y'all?
F Bt

>Maybe we could use a pop-up message box when starting the client, saying "You're still using the default nickname. It's recommended to change in preferences."
As a friend of mine used to quip (in exaggerated Iris brogue): "Good t'inkin O'rourke - yer foired!". Excellent suggestion. And each 2nd? 10th? subsequent until  change.
F Bt

Since setting a unique nickname is not necessary to make the client work, it isn't required to change. Maybe we could use a pop-up message box when starting the client, saying "You're still using the default nickname. It's recommended to change in preferences."

Though this would annoy those using the GUI client, it wouldn't make any noticable effect for those using the daemon as a service. Requiring to change it (and refusing to run until then) would make all daemons to stop working suddenly.

Those 2 mentions mean we continue to get interminable duplicate names. My suggestion was to get individual IDs on the readable listings. Yes, I know each client gets a number, but 50 sources with the same nicknames in listings of Friends means you have to dig to sort out who's who, and as Flanders and Swan said: "you r-eally ought to k-now w-hoo's w-hoo".

I think you'd get better answers sooner if you'd ask it on the wxWidgets forums or IRC channel.

Everything is as good as anything else for the default username. We could generate random usernames, or set it to "aMule User" or something else.

Two things to mention:
1. we won't leave the default username empty
2. we won't force our users to change the default username

In aMule preferences you can find a setting to prevent the system entering sleep mode while aMule is running.

Did you compile just amuled or wx, too? Did you get an wx update recently?

Hi there, My name is Gozzi
I getting this when I try sto start amuled

Starting amule daemon: Fatal Error: Mismatch between the program and library build versions detected.
The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,wx containers,compatible with 2.4,compatible with 2.6),
and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,wx containers,compatible with 2.6).
-bash: line 1: 20824 Avbruten (SIGABRT)      /usr/local/bin/amuled -f แทงบอลฟรี



Recompiled, but no avail.

Thank you
using wxBase 2.8.10