Weird, somebody posted a similar problem in the german forum yesterday (
link). That person claims that the "Contents/MacOS" folder only contains the ed2k helper script but not the other binaries.
Then there is also
this guy, who claims that he can only start amule trough the terminal but not via double-click in the Finder.
My fist suspicion was that somebody accidentally messed with the 2.0.3 binaries, but they seem to be fine.
chupacabras:
In addition to what ken has said, you can also try to start aMule through the terminal and see whether that works.
Here are some instructions (* shamelessly recycling a post for the second time *):
Originally posted by lionel77
To get a better idea what is going on, let's run aMule through the command line, so we get more feedback:
- First, download the official 2.0.3 release for the Mac (see here), unzip it and put it in your Applications folder.
- Then we need a Terminal window, so open Applications -> Utilities -> Terminal.
- Now, drag the aMule application icon from the Applications folder and drop it onto the terminal window. Terminal will paste the path to the application onto the command line for you. It will also add a space after the path.
- Delete the space at the end of the path.
- Add "/Contents/MacOS/amule" to the end of the path and press return.
- aMule should now start and generate some output in the Terminal window.
- If aMule crashes, copy the last 4 or 5 lines of this output and post it here on the forum. This will gives us a much clearer idea at which point aMule fails on your machine.
