MaxTyutyunnikov / grub4dos-chenall

Automatically exported from code.google.com/p/grub4dos-chenall
0 stars 0 forks source link

default menu briefly displayed if /menu.lst not found #122

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

empty USB pen with /grub/menu.lst  and grub4dos installed

when it boots, for a brief second you get what seems to be a black&white 
default menu

find /menu.lst, /boot/grub/menu.lst, /grub/menu/lst
commandline
reboot
halt

What is the expected output? What do you see instead?

Is there any way to stop this menu from appearing when using /grub/menu.lst?

What version of the product are you using? On what operating system?
I think all do it

Please provide any additional information below.

if a /menu.lst is present I don't see this screen even under QEMU which is very 
slow. if /boot/grub/menu.lst only is present OR /grub/menu.lst is present, I do 
see this screen under QEMU for nearly a second.
Users have complained about it!

Original issue reported on code.google.com by Steve6375 on 16 Mar 2013 at 4:11

GoogleCodeExporter commented 9 years ago
Then you should place your menu.lst in the root dir, i.e., the same dir as 
grldr.

The accompanying menu.lst takes precedence over other menu.lst files.

Details:

When grldr gains control, it will first run the preset menu. If the preset menu 
has a line of "configfile"(without arguments), then it will try to load the 
accompanying menu.lst (which should be in the root dir of the boot device) and 
transfer control to the accompanying menu.lst. So this accompanying menu.lst 
gains control rapidly. It gains control before the subsequent "find" commands 
run.

If failed in loading the accompanying menu.lst, then the rest of the preset 
menu will continue to run. That means the menu will display and the find 
commands will run one by one.

Original comment by tinyb...@gmail.com on 17 Mar 2013 at 8:41