eMule\VerboseDebug=1 is also required
This is called eMule for histrical/compatibility reasons I guess? It's not an auto-generated line if there is no config file tot start with. I assumed it goes in the [Debug] section. I edited both remote.conf on my desktop and amule.conf on the server to have debugging turned on.
Anyway, the debug builds are worse. Right now after I click connect, nothing happens and the process stays running in the background.
What appears on the amuled log:
2010-03-12 21:41:34: ExternalConn.cpp(260): New external connection accepted
aMuleGUI log:
2010-03-12 21:46:27 (remote-GUI): amuleAppCommon.cpp(329): Initialising aMuleGUI SVN using wxMSW VC v2.8.10 (Debugging) (Snapshot: rev. 10045)
2010-03-12 21:46:27 (remote-GUI): amuleAppCommon.cpp(375): Checking if there is an instance already running...
2010-03-12 21:46:27 (remote-GUI): amuleAppCommon.cpp(406): No other instances are running.
2010-03-12 21:46:38 (remote-GUI): amule-remote-gui.cpp(292): Connecting...
2010-03-12 21:46:38 (remote-GUI): amule-remote-gui.cpp(266): Going to event loop...
Then after I kill the daemon on the server:
2010-03-12 21:59:22 (remote-GUI): amule-remote-gui.cpp(307): Remote GUI EC event handler
!2010-03-12 21:59:22 (remote-GUI): amule-remote-gui.cpp(309): Connection failure
2010-03-12 21:59:22 (remote-GUI): amule-remote-gui.cpp(314): Going down