Supported Operating Systems

List of supported operating systems 

We provide our products with support for the following operating systems for i686 and amd64:

  • Microsoft Windows XP (32b),
  • Microsoft Windows 7 (32b and 64b),
  • Ubuntu 13.10 and higher (32b and 64b),
  • openSUSE 13.1 and higher (32b and 64b),
  • Fedora 20 and higher (32b and 64b),
  • and CentOS 7 (64b).

For all the mentioned operating systems we provide installers or installation packages; where possible in both 32b and 64b version.

Further system requirements:

  • CPU with SSE support (today it's a matter of course but you should still be informed about it)
  • for GNU/Linux, MDS requires GLIBC version >= 2.17




Installation on Microsoft Windows 

Smooth installation on Microsoft Windows is our priority, and it is the most straight forward, simple, and reliable MDS installation you can get for MDS. When you just follow the installer instructions, it will work. If you have 64b Windows, we strongly recommend installing 64b version of the MDS because you get considerably faster operation of simulator and other parts of the MDS than for the 32b version.


Installation on GNU/Linux 

This section deals with the installation process of MDS on GNU/Linux and possible problems related to that. We tested the installation process on various distributions of GNU/Linux, and we even do that on regular basis, the problem is that there are so many different distributions of Linux in so many different versions that it is nearly impossible to test and support them all. For that reason we provide a list of Linux based operating systems which we really support, and for which MDS was tested and works. In case your operating system is not listed among them or your OS version is lower than the required minimum, it is still possible that it will work, however, there might arise some issues. Our packages for GNU/Linux are build as much independent on system libraries as possible, but mainly due to certain licensing issues with some of the open-source licenses, mainly with the GPL and LGPL licenses, we cannot provide a really independent and really reliable universal installation package for GNU/Linux operating system, it is technically possible but in most cases it would be illegal for us to do so. So things get a little bit more complicated... (see bellow).



For Ubuntu running on x86 machines, we provide its native .deb installation packages, one for 64b Ubuntu and one for 32b Ubuntu. In most cases these packages can be installed just by clicking on them and then confirming the installation in your preferred software installer. The package has no dependencies listed in the package itself but it has some "hidden" dependencies. The package depends on "libc6" version 2.17 or higher, and on the X server. If you encounter problems while installing this package, please provide us with detailed description of your problem and output from the following commands:

    readelf -l /usr/bin/mds-ide
    dpkg -s libc6

CentOS, Fedora, and openSUSE 

We provide native .rpm package for all these operating systems, one for all 64b variants and one for all 32b variants. Please make sue that your operating system meet the requirement for the minimum version, otherwise we cannot guarantee that it will work, and it is even likely that it will not work, however, even in such case it is often solvable but it might require some action on your side: like updating some of your system libraries, etc.

Other GNU/Linux distributions & the .tar.bz2 packages 

If you use something like Gentoo Linux or Arch Linux, etc., you might use the tarball to install the MDS. When you install MDS from the tarball we assume that you are a highly experienced GNU/Linux user, you are very well familiar with the Linux environment and Linux commands, and you really know what are you doing and how to do it. So we just provide the following notes to the installation:

  • the tarball can be installed in a chroot-ed environment without problems,
  • please make sure that your system can support this software using ldd and readelf commands on executable binaries contained in the tarball,
  • keep the tarball somewhere so you can later list the files in it for un-installation (tar tfb >tarball<) or just make the list of files somewhere,
  • and please realize that we do not officially support your operating system, we might help you with the installation but there are no guarantees, etc. The tarball is meant to be only the last resort, not a regular installation package.