Suggestion: remove uneccessary messages on loading grldr

[GoogleCodeExporter]

What steps will reproduce the problem?
1. A normal boot of grub4dos produces text messages such as
Try (hd,0,0) : FAT32
then screen clears and you get
Initialize variable space...
starting cmain() ....

even if the grub4dos internal menu is edited to add
debug off
clear

What is the expected output? What do you see instead?
Can the 'Try ... '
    Try (hd,0,0) : FAT32
messages be suppressed by patching a byte somewhere?
Can the 
   Initialize variable space...
   starting cmain() ....
messages be removed as they serve no useful purpose?

What version of the product are you using? On what operating system?

Please provide any additional information below.

This would make for a much cleaner boot to the grub4dos menu.

Original issue reported on code.google.com by Steve6375 on 4 Jul 2012 at 7:02

[GoogleCodeExporter]

This seems to be even worse in newer versions!
At the top of the screen I get
Running menu commands(hangup means you have a problematic config)...

Can this message be suppressed in some way?
Why has this message been put in (it doesn't even display the filename of the 
menu)?

Original comment by Steve6375 on 17 Dec 2012 at 11:15

[GoogleCodeExporter]

>>> Can this message be suppressed in some way?

No. This message is mandatory. It will be displayed right before the menu will 
be displayed. And if the user would have a problematic menu command which 
caused hangup(or just a long delay), then the user will be notified with this 
message, and he will know why.

If there would NOT be any problematic menu commands, then the message will be 
quickly overwritten by the immediately displayed menu. So this design is 
considered NO PROBLEM at all.

Because you did see this message, it is likely you have a problematic menu, 
either preset or on-disk.

For instance, you used (in some way) the "find --set-root" command which 
accesses the floppy and causes hangup or a long delay.

Original comment by tinyb...@gmail.com on 25 Dec 2012 at 3:15

[GoogleCodeExporter]

I see the message because I am using QEMU which is quite slow. Would it be 
possible to clear the screen as soon as possible afterwards. To be of any use, 
it should also display the name of the menu file it is trying to run.
In previous versions this message was not visible under QEMU. Has something 
changed?
Many people use grub4dos as their system HDD bootloader and they do not want to 
see these messages on every boot. It would be nice if there was a way to 
suppress these initial messages (say by patching a byte in grldr somewhere?).

Original comment by Steve6375 on 25 Dec 2012 at 9:23

[GoogleCodeExporter]

>>> Would it be possible to clear the screen as soon as possible afterwards.

Surely possible, but not needed because the full-screen menu will immediately 
be displayed.

>>> it should also display the name of the menu file it is trying to run.

The menu is preset, and no name. The preset menu will gain control, and a 
"configfile" line (if present) in the preset menu will switch to an on-disk 
menu.lst file.

>>> In previous versions this message was not visible under QEMU. Has something 
changed?

Grub4dos is always in developing.

>>> It would be nice if there was a way to suppress these initial messages (say 
by patching a byte in grldr somewhere?).

Yes, there is a way to suppress this message. It is undocumented. You may find 
it by reading the code. But you'd better not make it public.

Original comment by tinyb...@gmail.com on 25 Dec 2012 at 10:25

[GoogleCodeExporter]

Original comment by tinyb...@gmail.com on 13 Jan 2013 at 1:27

• Changed state: Done