www.sarducd.it

[maximus]

I would like to point out what may be a flaw in the way a grub menu is added, and a suggestion of a better way. First I would like to point out that when adding a grub menu (and I think a syslinux menu also), it adds it with the full
file path from the location you pull it from, NOT the path where it should end up on the flash drive. Maybe there are instructions somewhere that explain this, but I find it confusing and problematic that it does this. Anyway…

Let us look at the following ISO_Extra.cfg entries:


label Boot from test_menu_grub1
menu label Boot from test_menu_grub1
MENU INDENT 1
kernel /boot/grub.exe --config-file="/test/test_menu_grub.lst
#
label Boot from test_menu_grub2
menu label Boot from test_menu_grub2
MENU INDENT 1
kernel /boot/grub.exe --config-file=/test/test_menu_grub.lst
#
label Boot from test_menu_grub3
menu label Boot from test_menu_grub3
MENU INDENT 1
kernel /boot/grub.exe --config-file="configfile /test/test_menu_grub.lst
#
label Boot from test_menu_grub4
menu label Boot from test_menu_grub4
MENU INDENT 1
kernel /boot/grub.exe --config-file="find --set-root /test/test_menu_grub.lst ; configfile /test/test_menu_grub.lst



Entry 1, 2, and 4 work on computer#1. Entry 1 and 2 don’t work correctly computer#2 as they find a “menu.lst” that is on the hard drive (same menu is also on computer#1 but it does not find it first). But entry 4 does work on both
computers.

Entry 3 does not work at all on any computer, and it is basically the default for what SARDU creates (except I fixed the path).

So I am suggesting that you add the “find --set-root” to the entry (and consider doing something about the path problem), as otherwise it just seems usless. Also I noticed that your entry had no ending quotation marks, although that did
not seem to affect any of the results.

Please let me know if you have any questions, comments, or would like me to do any specific testing. I really like SARDU, but this about drove me nuts!


Scott

[maximus]

I would like to refine my results from further testing. The following entry in the ISO_Extra.cfg file is created by Sardu when using “Load menu GRUB4DOS (.lst)” to add a grub menu:

Code: Select all

#boot di test_menu_grub
label Boot from test_menu_grub
menu label Boot from test_menu_grub
MENU INDENT 1
      kernel /boot/grub.exe --config-file="configfile /testsardu/test_menu_grub.lst

I cannot get this to work at all in any system. What I CAN get to work in every system that I have to test (both USB and CD) is:

Code: Select all

#boot di test_menu_grub
label Boot from test_menu_grub
menu label Boot from test_menu_grub
MENU INDENT 1
      kernel /boot/grub.exe
      APPEND --config-file=find --set-root /testsardu/test_menu_grub.lst ; configfile /testsardu/test_menu_grub.lst

Notice that this uses APPEND instead of trying to put it at the end of the first line. This makes a big difference it whether or not it works. Also, adding the “find -–set-root” helps it work on some systems. Also note that I left out the quotes. I have actually found that on some systems the quotes cause failure (I do not know why but it did happen). Also note that I did not add "--ignore-floppies”, as that also caused failure on a system from a USB boot.

I also have a suggestion for adding an ISO via the “Add Extra ISO (GRUB)” options. Do NOT include "--ignore-floppies”, as stated above, this can cause failures on some systems when booting via USB. Getting rid of that would help it work for more people.

I am just trying to give suggestions on making SARDU work better for more people out of the box, from my testing experiences trying to get it to work for me.

[davidecosta]

Thanks