LiLi have a complex algorithm to recognize what source you selected.

For .IMG file, no recognition is made because it's not needed. The file will just be burned on your key, no special processing is needed.

For .ISO file, LiLi needs to know what source it is because for example, Ubuntu and Fedora have to be processed differently in order to create a bootable USB.

First, LiLi will make a text search in the filename to check if it's not a version that will definitely not work (alternate versions, ubuntu 8.04 ...). LiLi search this words : "8.04", "7.10", "alternate", "sparc". If this words are present and it will say that the ISO is not compatible.

Next step, LiLi is looking for filename in the compatibility_list.ini file (located in tools/settings/). If the filename exists and MD5 is set to ANY then it means that MD5 does not need to be checked. This is generally for Alpha versions or daily builds. Only filename count.

If MD5 is set then it will be checked but when MD5 is not recognized. If filename is in the list and MD5 is not good then LiLi will prompt that the ISO has been modified or corrupted.

Last one, if MD5 is not in the compatibility list, LiLi will try to recognize the source with its filename to do a mapping :

• filenames containing "ubuntu", "9.04", "netbook-remix", "fluxbuntu" or "gnewsense" will be installed using Ubuntu 9.04 parameters
• filenames containing "9.10" or "karmic" will be installed using Ubuntu 9.10 parameters
• filenames containing "kuki" will be installed using Kuki 2.8 parameters
• filenames containing "F10" or "F11" will be installed using Fedora 11 parameters
• filenames containing "crunchbang" will be installed using CrunchBang Standard parameters
• filenames containing "mint" will be installed using Mint 7 Main Edition parameters

This behaviour allows LiLi to work on some unsupported or modified ISO.