Multiboot Creators: SARDU versus YUMI

I will admit right up front that I am an ardent SARDU fan (Shardana Antivirus Rescue Disk Utility) and only recently discovered YUMI (Your Universal Multiboot Integrator).  Originally I thought that there was no contest between the two, SARDU would win, but they both have pros and cons.  In the end though, I will continue to use SARDU, it is in my opinion a superior product. I would probably switch to YUMI from SARDU (well maybe) if it wasn’t that the menu system was sooooo bad (yes that bad). So what do they do and what makes them differ?  I knew someone would ask, hence this article.  So let’s go through this step by step. I decided to try both of them from scratch, just to be fair.


Both of the softwares have their own websites and (although this last is more of a subdirectory of the site). But is it a little more difficult to find the download link on the SARDU site (I don’t know what it will look like on the new site for SARDU 3.x since as of this writing it is not yet available).  Also it is a lot easier to click on a “downloader” link for something that is being advertised rather than the SARDU application itself.  Although this didn’t used to be the case, I can see how this might be financially necessary.  I finally did download both software applications, so on to step two.


This is another mixed bag.  YUMI wins this one hands down, but I am kind of comparing apples and oranges here.  YUMI is not actually an installation – and this is good!  YUMI and it’s predecessor, UniversalUSBInstaller, Never really installed they just ran.  SARDU does need to be unzipped and then the setup needs to be run.  This would not be so bad except that like the download, the installation is loaded with adware.  Make sure you DECLINE the 3 requests that occur during installation.  Read the text, they are trying to install other software that will redirect your browser!

Initial Run/ease of use

Once you have the software downloaded, and installed in SARDU’s case, you will want to run it (they both will automatically run after installation). There are several aspects to running these applications.

  • GUI or Graphical User Interface – SARDU has one and YUMI does not – end of story
  • ISO images needed for creating this multiboot device – you need to download the image beforehand with both apps.  Both SARDU and YUMI do give you the option of downloading within the application, this is sometime best since the naming will be correct – just know where you are downloading the image to.

Image Files

Which brings me to another point – the image name – both applications require that the image name be what the application expects, although the wildcard character of * is used to denote anything (thisimage_*.iso could be thisimage_version-70f8.iso) , which can be helpful in keeping track of which image is which (one of mine is named Win7Rescue_spotmau2012.iso because SARDU expects Win7Rescue_*.iso). Note that the creation of the multiboot device/ISO happens slightly differently. SARDU makes sure you have everything listed and creates all at once (if you don’t have enough space for the entire amount of data as a temporary file in the temp area – generally the drive you installed SARDU to – SARDU will generate an error and quit). YUMI, on the other hand, creates the image one ISO at a time.  The other side to this is that with SARDU you can set it and leave it, while with YUMI you must be there to choose each of the distributions you want to install, after the previous one has completely finished. The one problem with doing it all at once like SARDU is that if the program gets stuck extracting one of the ISOs, it hangs and there is nothing to do but start over.  With YUMI’s one at a time strategy, that particular image won’t install, but you will still have the others.  Once you create either an image or a bootable device, either program will easily update it.  SARDU goes farther with a tool to just update the menu. You might be wondering if after you create all these bootable images on a USB stick, can you put your own licensed images there (see above I put my spotmau image on)?  The answer is YES for both applications.  It is easier with YUMI as long as you know if the image uses syslinux, GRUB or GRUB from RAM.  With SARDU you can do the same, and it is fairly easy if you replace one of the expected images with your own (as I did with the spotmau image).  If you want to add your image and not use the replace option that becomes a little more complicated, although it is doable.

Image Directory

This may not sound like a big deal, but it is.  When you start collecting ISO images, you realize that you have gigabytes of them (I have close to 50gb in just SARDU’s ISO directory, which doesn’t count the almost 100gb of images I have in another directory).  This is problematic if you are having to copy them, then you have repeats.  With SARDU all the images have to be in one Directory.  Because it is doing it all at once, I believe, you can only define where the image directory is located, not where each image is located.  With YUMI it doesn’t matter, each image can be housed anywhere.

Resulting Menu

So did they both work? Yes. But how do they look and how usable are they? Both utilities produce a DOS like interface (white lettering on a black background with some graphics).  Nothing surprising there. But the real difference shows up when you look at the submenus. A SARDU created boot device has submenus that reflect exactly what was shown in the interface of the program that created the device.  For instance if it is called Windows 7 PE in the menu to create the boot USB then that is what you see when you use the USB. With YUMI all windows install disks are called the same thing – Windows Vista/7/8 Installer – I have 4 entries on the YUMI created boot disk with the same exact name, which is needless to say USELESS!  The rest of the entries on the YUMI created device bear the name of the ISO that was used to create them, which can be equally confusing.  My version of AVG is called avg_arl_cdi_all_120_120525a5064.iso so the entry is called avg_arl_cdi_all_120_120525a5064, while my Linux mint distro is called linuxmint-14-mate-dvd-32bit.iso and even though YUMI has a choice for Linux Mint, the resulting menu calls it linuxmint-14-mate-dvd-32bit.


What do you do if you need help (other than asking me I mean 😀 )?  YUMI has an extra help link that sends you to their website.  I didn’t find a lot of help there.  SARDU has a help link that opens a help file, which is blank. SARDU does have a great Help Forum.


So my conclusion is that SARDU is the better product and hopefully version 3.0 will be even better and without adware.  Any software that works better than SARDU, but produces gobblety-gook at the end is useless. SARDU does have several problems, not the least of which is the adware that one could easily install during installation of the program.  Read everything carefully and you will be okay.  You don’t need to agree to any of the third party EULAs in order to install SARDU.

Leave a comment

Your email address will not be published. Required fields are marked *