Hi,
You describe your version as "cvs 2.0.0". Does that mean you are using the 2.0.0 binary that we supply, or that you have compiled from the 2.0.0 source tarball, or that you compiled from a cvs snapshot since 2.0.0?
Well, here are some possibilities:
- You didn't copy the webserver files into ~/.aMule/webserver/default. The necessary files can be found in the source tarball in src/webserver
- aMule can't properly launch amuleweb unless amuleweb is on the search path. When the Finder launches aMule, aMule gets a minimal environment with a minimal search path. It's just "/usr/bin:/bin:/usr/sbin:/sbin:" plus your home directory.
So, you can copy amuleweb to your home directory and it will be launched from there. Or, you can use Terminal to launch aMule and set the PATH beforehand. Or, you can use Terminal to launch amuleweb directly instead of asking aMule to launch it.
- You didn't set the proper External Connection password. Note that if you launch amuleweb manually it will reference ~/.aMule/remote.conf instead of ~/.aMule/amule.conf. You can use the command amuleweb --create-config-from=~/.aMule/amule.conf once to generate the remote.conf with the password you've set up in aMule's Preferences.
- You need to use a version of amuleweb that matches your version of amule (or amuled). By "matches" I mean it was compiled from the same source snapshot.
I hope that helps.
I know that this all makes for a very un-Mac-like experience. We should probably look into improving this some. :)
