Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 07-13-2016, 01:18 AM   #1
Registered: Jan 2006
Posts: 72

Rep: Reputation: Disabled
YUMI Multiboot menus

I have a small number of bootable usb sticks (Tiny core Linux, DOS, Dell diagnostics, memtest etc) that I have consolidated onto one microsd card using YUMI.

Each time I add something to the disk it puts an entry onto the main menu screen. If you click on the entry it takes you to a second screen with an entry that launches the chosen OS.

For example, (taken from the YUMI syslinux.cfg file)DOS falls under the category of "system tools"....

label System Tools
menu label System Tools ->
CONFIG /multiboot/menu/system.cfg
then from /multiboot/menu/system.cfg
#start balder10
LABEL FreeDOS (balder10)
MENU LABEL FreeDOS (balder10)
KERNEL /multiboot/memdisk
APPEND initrd=/multiboot/balder10/balder10.img
#end balder10
I want to be able to launch from the first screen and to do away with the second screen so I have copied the lines from system.cfg and pasted them into syslinux.cfg. This allows FreeDOS to launch from the first screen (ie from syslinux.cfg) It all works fine, except for my Dell diagnostics program. I cant seem to copy the 'code'(?) from the system.cfg to syslinux.cfg and get it to launch. Its because I don't understand fully what each line is doing. Please could someone help me combine these two files.

For Dell Diagnostics, the first menu file reads...

label GRUB Bootable ISOs
menu label GRUB Bootable ISOs and Windows XP/7/8 ->
KERNEL /multiboot/grub.exe
APPEND --config-file=/multiboot/menu/menu.lst
then from /multiboot/menu/menu.lst
#start diags
#Modify the following entry if it does not boot
title Boot diags.iso
find --set-root --ignore-floppies --ignore-cd /multiboot/ISOS/diags.iso
map --heads=0 --sectors-per-track=0 /multiboot/ISOS/diags.iso (hd32)
map --hook
chainloader (hd32)
#end diags
I can't simply copy the code from menu.lst into syslinux.cfg and I have tried inserting all sorts of combinations of adding and deleting lines from each menu file.

Thank you for any help

Last edited by devavictrix; 07-13-2016 at 01:20 AM.
Old 07-14-2016, 09:25 AM   #2
LQ Guru
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19 MATE
Posts: 5,839
Blog Entries: 2

Rep: Reputation: 1864Reputation: 1864Reputation: 1864Reputation: 1864Reputation: 1864Reputation: 1864Reputation: 1864Reputation: 1864Reputation: 1864Reputation: 1864Reputation: 1864
YUMI mostly launches ISOs using syslinux, but chainloads to GRUB as a fall-back, as it does in the case of Dell Diagnostics.

The .cfg files contain syslinux commands. The .lst files, on the other hand, contain GRUB commands.

Copying commands from one format to another is doomed to failure.
Old 04-15-2018, 10:09 PM   #3
LQ Newbie
Registered: Apr 2018
Posts: 1

Rep: Reputation: Disabled
I realize the thread is 2 years old, but I found it while googling for the same issue, so I figured my workaround might still be of help to someone.

I will use Acronis True Image as an example.

Add your GRUB ISOs using YUMI.
Make a copy of menu.lst located under \multiboot\menu and rename it AcronisTI.lst
Edit AcronisTI.lst and delete any info related to other GRUB entries.
Also change these lines:
default 2 <- this selects the entry that is selected when entering the menu.
timeout 0 <- this makes the menu not wait for user input

It should look close to this:

# This Menu created with YUMI
default 2
timeout 0
title --- Unlisted ISOs Bootable via GRUB ---
title <-- Back to Main Menu
root (hd0,0)
chainloader (hd0)+1
rootnoverify (hd0)
#start AcronisTrueImage2018_10410
#Modify the following entry if it does not boot
title Boot AcronisTrueImage2018_10410.iso
find --set-root --ignore-floppies --ignore-cd /multiboot/ISOS/AcronisTrueImage2018_10410.iso
map --heads=0 --sectors-per-track=0 /multiboot/ISOS/AcronisTrueImage2018_10410.iso (hd32)
map --hook
chainloader (hd32)
#end AcronisTrueImage2018_10410
The first YUMI menu is the easiest part, just make an entry that looks like this:

label AcronisTrueImage2018_10410
menu label Acronis True Image 2018
KERNEL /multiboot/grub.exe
APPEND --config-file=/multiboot/menu/AcronisTI.lst
Now just repeat the process for each entry.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
How to remove boot from YUMI susja Linux - Newbie 3 05-20-2016 05:27 PM
[SOLVED] YUMI for Arch? itscience Arch 3 08-08-2015 03:16 AM
problem creating multiboot in linux mint using yumi mia_tech Linux - General 4 03-13-2015 07:42 AM
[SOLVED] YUMI (Your Universal Multiboot Installer) boot loader image digitaldefector Linux - Software 5 05-19-2014 10:30 AM
YUMI multiboot linux persistence / persistent question lordloki Linux - General 4 06-08-2012 11:40 PM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 07:55 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration