Print

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

[dr.ananas]

many had mentioned this before in this forum and i posted a few times that i had the same problems as others, but there where no real solutions given. if there's a thread solving this - so please delete this after telling me where it is(i havent found any).

i have a 1gig ram powerbook running and there cannot be any problem with the hardware ressources.
after updating my amule 2.0.3 to 2.1.3 (mac os x tiger power pc) nothing worked anymore. minutes to load the download list or the servers. this problem was solved with deleting my application support amule folder. but i still was unable to open the properties window. amule crashed everytime and was impossible to quit.
has anybody a clue how i get my amule working again?

 :baby:

[pleur]

run the daemon instead and use webserver to control your aMule

[Kry]

Try a recent CVS build from lionel.

[lionel77]

Well, amule is not "totally unstable", in fact in runs very reliably on my machine and on the machines of many others. BUT it has become enormously more resource hungry since 2.0.3 (see here for instance), which in turn makes it difficult to run aMule on anything less than a G5 or dual G4, which unfortunately includes even relatively recent Mac models, like the PowerBooks, iBooks, and G4 Mac minis. I've invested a huge amount of time trying to profile aMule and to identify if there is anything in particular, that is slowing it down, but to no avail so far.

As pleur has suggested, a workaround for people with less powerful Macs could be to use amuled (the core-only version of aMule), because it is less resource demanding. Unfortunately, amuled does not run stable on OS X right now, because we have focussed our Mac resources primarily on the regular aMule client. We are however in the process of trying to get amuled to run decently on OS X, so users of less powerful machines will have an alternative to the regular aMule client.

[dr.ananas]

ok, so u have to use dual processors with 2gig minimum ram. this works as a joke.
to run just a downloading application. this shouldnt be the reality. i love the emule thing since years, but now i have to forget about it? it seems so. in my definition an application can be declared unstable if it needs a ridiculously amount of ressources. ahh sorry about thinking loud, i am disappointed now. so guys, next version will be ok again?

[lionel77]

I just got my hands on a PowerBook G4 1.25ghz with 768mb, and even though somewhat sluggish (opening the preferences window takes 4-5 seconds or so), aMule does seem to run stable on it. I haven't tried downloading a lot, but the problems you described were regarding the basic functionalities of aMule anyway.

So I'm thinking now, what you are experiencing must be caused by something else than just the speed of your cpu (btw., what is the exact speed anyway?). The most likely candidate is old settings that for some weird reason make aMule choke.

So, could you please shutdown aMule and try renaming/deleting the file "org.amule.aMule.plist" in "~/Library/Preferences/"? Just to be on the safe side, you might also want to rename/delete the folder "~/Library/Application Support/aMule" again. IIRC, those are the only locations where aMule stores its settings on OS X.

Please let us know if this fixed your issues or not. If not, we will have to do a little more digging.

[dr.ananas]

ok i deleted the org.amule.aMule.plist and the apllication support amule folder. but still it denies to open the properties. the weird thing about this is just that everything worked brilliant until i did the fatal mistake to update it.

by the way: g4 powerbook 1,67 ghz cpu, 1 gig ram, power pc, osx tiger.

thx

[lionel77]

Hmm... weird...

Let's try the following: Create a new dummy user account in System Preferences -> Accounts. Then log out of your regular account and into the dummy account. Then download a fresh copy of aMule 2.1.3 with that account, unzip it and start aMule. If aMule works without problems now, we can try to figure out what in your regular user account might cause aMule to choke. If aMule still does not work, well, then I need I will need an aspirin.