IÂ´m pleased to announce eD2K+KAD support for NAS200 running jac2b firmware. Using aMule you can download your ed2k links directly from NAS200 through a web interface. You can get the package here. Installation instructions for automatic startup: Connect to your NAS200 with SSH, NOT TELNET. If you launch rc.amule from TELNET IT WILL NOT WORK (thanks Pa0l0ne for the contribution) Unpack the tarball under your rc.d directory (/harddisk/volume_X/data/rc.d where X depends on your harddisk(s) configuration). Edit the amule.conf file under /harddisk/volume_X/data/rc.d/amule/aMule with the correct paths for your system Make sure that your home directory exist and is writable (ie: not root dir, "/") if it isnÂ´t, change the home directory of the user to some path in the harddisk (ie: /harddisk/volume_X/conf/root) that can be writable (you can edit the passwd file to achieve this change and then relogin with ssh to get the new value). If you canÂ´t asure this, please donÂ´t continue because amule will not work. Execute rc.amule under /harddisk/volume_X/data/rc.d to run aMule Connect to aMule web interface with your favourite browser on http://your_nas200_ip_address:4711 (the default password is "changeme") How to change the default password for aMule web interface: aMule doesnÂ´t use clear text passwords in the configuration file. Instead it uses a MD5 hash of the password you want to use. To achieve this execute: Code: $ echo -n password | md5sum 56f491c56340a6fa5c158863c6bfb39f - Where password is the password you want to use and the MD5 hash (56f491c56340a6fa5c158863c6bfb39f) is what you need to copy and paste in the "Password=" parameter in the [WebServer] section of the config file. Last but not least, aMule support a lot of options and the configuration file used in this package is just a simple template with almost everything set by default. If you want to know more about them you can find information here. For more details about aMule please check aMuleÂ´s website. ADVICE: amule can be really heavy for the NAS200 CPU. So a good advice is to renice the amuled process after starting it. By "renicing" it you can low down the priority of amuled process so the rest of the services on the NAS can keep working. renice is available in my new version of busybox, check the thread about it. Enjoy it! :thumbup: BTW: please note the big size of the binaries. That is because in order to simplify everything I statically compile them, in order to get rid of libraries dependency.