Does anyone know how can I bring ... blank lines in the menu.lst?
How to make skipped the menu bar in gfxboot
1. Make a backup copy of your
main.inc.
2. Open
main.inc with any text editor.
3. Searching for the sample "
/main.input" (without quotes of course) in tne text of
main.inc - This sample is the
beginning of the script that processes the keystrokes
- The opening brace "
{", which goes after the specified text, shows beginning of the script
- A closing brace "
}", which corresponding to a given "
{", is accompanied word "
} def". "
} def" - this is the end of this script. And it is located after the block
dup 0 ne {
"opt" help.setcontext
} if - Inside this script examines pressing various keys. For this reason, the script consists of a set of blocks "
if", which are enclosed between commands
dup Verifiable_Code eq {
....
....
pop 0
} ifWe are interested in blocks of
keyUp and
keyDown.
4. If all the above is clear and you have identified all of the blocks, then we can proceed to modify the script.
=========================
-
Beginning of the script. Block ...
=========================
- BLOCK
keyUp ...
=========================
- BLOCK
keyDown ...
=========================
-
END SCRIPT. Block ...
5. "---" - This is a sample menu bars to be skipped when moving up / down. Can define his own version, such as 7 spaces. Note that the first space after the "
title" is a service and is not part of the menu bar.
Coincidence should be accurate, ie, "
---" And "
--- " is not the same thing.
6. Save the changes to
main.inc, recompile
gfxboot, add to
menu.lst command...
title ---
configfile /menu.lst...and test it.
*********************************************
Notes:1. We are talking about
gfxboot from
"Configurable gfxmenu" topic and similar
gfxboots (version 3.3)
2. All braces "
{" and "
}" must be framed with spaces ("
{ " and "
} ")
3. New and modified commands are highlighted
in red4. Commands from your
main.inc may differ slightly from those listed above. Try to approach creatively to
main.inc editing