This entry is a user-made guide and not verified by any eMule developer, but is still a helpfull addition for most users. You you can find questions and comments on this topic in a dedicated thread on our forum.

This document assumes you have a recent Linux installation with an X11-based window manager or desktop environment such as KDE, GNOME, or Xfce.

Install Wine 0.9.40 or later from your Linux distribution's package manager (apt or Synaptic on Debian/Ubuntu, Portage on Gentoo, etc.). If you don't find the latest version there, you should download the appropriate binary package or platform-independent source tarball from http://sourceforge.net/project/showfiles.php?group_id=6241, then consult the official installation documentation at http://www.winehq.org/site/docs/wineusr-guide/getting-wine.

Download the latest eMule installation executable and save it to your home directory (shell alias "~" under most Linux setups). Launch the executable from a terminal:


CODE
wine ~/eMule0.48a-Installer.exe

Wine will first create an emulated Windows environment in ~/.wine then launch the installer. Proceed with the eMule installation as you would under Windows.

To remove eMule from your emulated Windows environment, type the following in a terminal:


CODE
uninstaller

Select eMule from the program list and click Uninstall.

Two options for launching eMule are provided here.

On Linux systems eMule's UploadSpeedSense feature presents users with a security tradeoff since it uses ICMP packets for pinging, something which Linux requires root privileges for. Because of this, if you wish to use UploadSpeedSense you must use eMule under less local security restrictions than you would normally run Linux applications under. Although this risk is not greater than the risk running eMule under a real Windows installation presents, it still means that your entire system can be compromised if an ICMP vulnerability is exploited.

So what is UploadSpeedSense? From the eMule preferences documentation:

QUOTE
USS is a function to monitor the ping times of the connection and to automatically adjust eMule's upload according to this ping value. This ensures that the connection never cloggs [sic] and will try to keep surfing and online gaming fluid.

If you want UploadSpeedSense functionality and understand the risks, use Method 1 below to launch eMule, otherwise use Method 2.

Method 1


From a terminal invoke Wine via sudo like so:


CODE
sudo wine ~/.wine/drive_c/Program\ Files/eMule/emule.exe

sudo will then prompt you for the password of your root account. Enter the password and eMule will launch.

Method 2


During installation the eMule icon may or may not have been successfully installed by Wine to your Linux desktop's launch menu. If you see the eMule icon there, simply click on it. If not, launch eMule from the terminal:


CODE
wine ~/.wine/drive_c/Program\ Files/eMule/emule.exe

When launched for the first time, eMule will prompt you for some initial configuration preferences as usual. When it asks you what version of Windows you're using, select the "Win2K/XP" option so that your Max. connections won't be limited to 100 by default.

• To minimize the risk of .met/.dat corruption in the event of a crash, set Extended --> Safe .met/.dat file writing in eMule's Options dialog to "Always".

There may be areas of the Windows API called by eMule that Wine won't handle correctly. If you notice any problems please report them in this thread.

• Wine Bug 4299 - Text field malfunction in eMule.exe's search tab
• Wine Bug 5844 - tray minimize
  Workaround: Use a universal application docker like AllTray. See this post for tips on configuration (also slightly Debian/Ubuntu-centric).
• Wine Bug 6470 - eMule crashes while trying to hash some files
• Wine Bug 6936 - eMule uses 40% CPU when idle permanently, independent of CPU speed

Official Wine Documentation
http://www.winehq.org/site/documentation

eMule Tracker at the Wine Application Database
http://appdb.winehq.org/appview.php?appId=1065