27 replies to this topic

[Bean123]

Gfxmenu is not easy to configure. The files are bundled in a cpio archive, and the control mechanism is inside a binary file init. It's relatively easy to make basic treak like changing background image, but it's impossible to make big changes, such as changing the menu position, without compiling it from source code.

To make it easier for normal user to do advanced treaking with gfxmenu, I've built a special message file whose behavior can be altered simply by editing the config file gfxboot.cfg. Currently, it understand the following options:

boot_show (default: 0)
if set to 1, show the "Boot Options" box. As grub4dos currently don't use this feature, it might be better to hide it.

xmenu_hide_current (default: 0)
if set to 1, hide the current selection item below the bottom menu.

menu_start_x, menu_start_y
Position of menu

menu_max_entries (default: 8)
Maximum number of menu entry to display.

menu_bar_min_width
The minimum width of menu select bar.

menu_text_normal
Normal text color, use RGB value such as 0xffffff.

menu_text_select
Color of selected text

boot_text_options
Color of boot options label

boot_text_normal
Color of boot options text

infobox_bg
Background color of info box

infobox_text_normal
Text color of info box

menu_bar_color
Color of menu bar

loading_color
Color of load bar

title_bg
Background color of dialog background

hide_reboot (default: 0)
If set to 1, hide the reboot button (F9)

hide_poweroff (default: 0)
If set to 1, hide the poweroff button (F10)

disable_num_key (default: 0)
This message file has added keyboard shortcut function, for example, pressing '1' would choose the first menu item. If you don't want it, set this variable to 1.

hide_help (default: 0)
If set to 1, hide the help button (F1)

hide_lang (default: 0)
If set to 1, hide the language button (F2)

custom_width, custom_height, custom_depth
By default, the screen resolution is 800x600x16, if you want a higher resolution, set these three variables, for example:
custom_width=1024
custom_height=768
custom_depth=16
The mode must be supported by bios, otherwise, it just fallback to default.

panel_normal
Color of panel text

panel_title
Color of panel title

panel_high
Color of panel hotkey (Fn)

panel_bg
Background color of panel pop-up box

panel_border
Border color of panel pop-up box

The above variables are contained in the sample gfxboot.cfg, but they're disable using the comment indicator #. To use them, remove the leading # and set the corresponding value.

Attached Files

•  message_en.zip   315.04KB   10017 downloads

[mr_]

That's pretty cool but it's still a hell for me to edit the cpio archive, see http://www.boot-land...?...ewpost&f=15

If the effort isn't to high, would it be possible for you to get ride of cpio and to switch to a common easy simple read/write/edit-anywhere format like zip?

[was_jaclaz]

Do I get it right that gfxboot.cfg is intended to be outside the cpio file (thus eliminating the need to open/modify the cpio archive)?

Should it go wherever (same directory) of the actual gfx-theme (as defined in menu.lst as gfxmenu=/whatever/gfx_theme)?

jaclaz

[mr_]

No, you can open message_en and see it contains gfxboot.cfg.

I've downlaoded OpenSuse now because the gfxgrub-devel package (containing the tool to create smaller fonts is only inside their and gfxgrub has no real own homepage).

[Bean123]

If the effort isn't to high, would it be possible for you to get ride of cpio and to switch to a common easy simple read/write/edit-anywhere format like zip?

Unfortunately, the choice of archive type is not up to grub4dos. gfxboot is like a standalone program, to use it properly, grub4dos must conform to its interface. So unless gfxboot developers decide to support zip, there is not much we can do.

However, we do have a option of supporting in memory replacement of files, for example, we could support a incremental gfxmenu_add command like this:

gfxmenu_add /message
gfxmenu_add /gfxboot.cfg
gfxmenu_add /back.jpg

[Iamnuts]

This has been fantastic.

How did you manage to figure out so many or did you recompile it? None the less great work.

Ive been looking through the init file and the gfxboot.cfg, but I cant work out how to change the color of the F keys or the text after them.

Its a real shame as the background I wish to use is white, but the yellow hardly shows up of the fkeys and obviously the text after being white is totaly hidden.

Is there any chance you could assist? Ive not given up im still trying myself.

mtia

[Bean123]

This has been fantastic.

How did you manage to figure out so many or did you recompile it? None the less great work.

Ive been looking through the init file and the gfxboot.cfg, but I cant work out how to change the color of the F keys or the text after them.

Its a real shame as the background I wish to use is white, but the yellow hardly shows up of the fkeys and obviously the text after being white is totaly hidden.

Is there any chance you could assist? Ive not given up im still trying myself.

mtia

The original message file uses fixed value, I modify the source code so that it would query gfxboot.cfg as well.

I've uploaded a new version of message that supports panel color, the color of fkeys are configurable via the panel_high variable.

[orions]

Hi its Iamnuts (im havving trouble logging in so im using a bugme login as orions to say thanks)

Many thanks for that, Im amazed at the speed at which you did that, thanks so much I can now use the white background I wanted. 5***** all the way mate.

Im going to be cheeky now, is it possible to be able to have a variable to change the wording of help to a word of choice.

cheers

[Bean123]

Hi its Iamnuts (im havving trouble logging in so im using a bugme login as orions to say thanks)

Many thanks for that, Im amazed at the speed at which you did that, thanks so much I can now use the white background I wanted. 5***** all the way mate.

Im going to be cheeky now, is it possible to be able to have a variable to change the wording of help to a word of choice.

cheers

Well, it's possible to use variable, but it's best to modify the translation file *.tr. However, this file is binary format, so you need to use the source code.

I've uploaded the source code to:

http://grub4dos.sour...-3.3-custom.zip

To build it in windows, you can use my customized msys package:

http://grub4dos.sour...ge.net/msys.zip

Extract msys.zip, then click "Console.exe", you enter a command windows. cd to the gfxboot directory, and type "make".

The translation is in po subdirectory. bootloader.pot is the default translation (english). For example, to change the translation of help text, you need to locate txt_help and change the msgstr. After you have done, use make to create a new message_en.

BTW, the msys package can also be used to build grub4dos. I've added two script to simplify the task, grub4dos_update is used to sync with the latest svn code, and grub4dos_build is used to build the binary packge (the result is in /build directory).

[Iamnuts]

Words escape me. You truly are a star.

You've now just given me and many other a new toy to be playing with.

Cheers

[niche99]

Excellent work.

Would it be possible to add transparency options.

; menu background transparency (0..255)
menu.transparency=0x20

; main menu selection bar transparency (0..255)
mainmenu.bar.transparency=100

Thanks,
niche99

[Mr.xx]

Well, it's possible to use variable, but it's best to modify the translation file *.tr. However, this file is binary format, so you need to use the source code.

I've uploaded the source code to:

http://grub4dos.sour...-3.3-custom.zip

To build it in windows, you can use my customized msys package:

http://grub4dos.sour...ge.net/msys.zip

Extract msys.zip, then click "Console.exe", you enter a command windows. cd to the gfxboot directory, and type "make".

The translation is in po subdirectory. bootloader.pot is the default translation (english). For example, to change the translation of help text, you need to locate txt_help and change the msgstr. After you have done, use make to create a new message_en.

BTW, the msys package can also be used to build grub4dos. I've added two script to simplify the task, grub4dos_update is used to sync with the latest svn code, and grub4dos_build is used to build the binary packge (the result is in /build directory).

thanx but can Explained in detail more how to trans lang

[tefole]

just a question about the used font 16x16.fnt:
what a kind of file type is that, respectively how can i use a smaller font?
i have no idea

[ireneuszp]

My pack with GfxMenu files for Grub4Dos
http://grub4dos-iren...iles/GfxGrub.7z

[agni]

My pack with GfxMenu files for Grub4Dos
http://grub4dos-iren...iles/GfxGrub.7z

What is the difference in your pack compared to BlueLife's Pack?

[Mr.xx]

My pack with GfxMenu files for Grub4Dos
http://grub4dos-iren...iles/GfxGrub.7z

can re-upload file again because the file corrupt

[steve6375]

Gfxmenu is not easy to configure.
To make it easier for normal user to do advanced treaking with gfxmenu, I've built a special message file whose behavior can be altered simply by editing the config file gfxboot.cfg. Currently, it understand the following options:

Thanks for this very useful feature, which I am playing with now. It all seems to work except...

I cannot seem to get these 2 settings to work though...

#Background color of panel pop-up box 0xd8deed
panel_bg=0xff0000
#Border color of panel pop-up box 0xeff2f6
panel_border=0x00ff00

Also 'Language' seems to come in a different color than expected?

Also I am not sure what this option does...
#loading color 0x295202
loading_color=0xff00ff


Also, I know that the / in /n for help text is the wrong way round in the screenshot, but \n does not show the help text at all in gfx menu - is it supported?

Has anyone had any success with these? Here is my test gfxboot.cfg file and a screenshot of what I get.

http://sites.google....ons/gfxboot.cfg

[Klaus21]

Is it possible for different screen resolutions in the gfxboot.cfg install?
If the monitor size queried?

For example:
[1280x1024]
screen.size = 1280.1024
[1024x768]
screen.size = 1024.768
[800x600]
screen.size = 800.600

Regards Klaus

[ded]

gfxboot.cfg

custom_width=1024
custom_height=768
custom_depth=32

[Klaus21]

Is it possible to give all three resolutions in one gfxboot.cfg?

Can you tell me how can I work with @ DED-LEGO @ ??

Does anyone know how can I bring headings and blank lines in the menu.lst?

Like
title == Heading ==

Regards Klaus

[ded]

 

Is it possible to give all three resolutions in one gfxboot.cfg?

If you have the source code of your gfxboot, then have a look at the script common.inc. You might be interested in these parts of common.inc:

false "custom_width" getgfxnum dup {
0 "custom_height" getgfxnum 16 "custom_depth" getgfxnum findmode setmode
} if

not {
800 600 16 findmode setmode not {
800 600 32 findmode setmode not {
640 480 16 findmode setmode not {
640 480 32 findmode setmode not {
false .end
} if
} if
} if
} if
} if

Topic to the discussion of inc-scripts is HERE

Can you tell me how can I work with @ DED-LEGO @ ??

Please post questions about @DED-LEGO@ in the topic "GFXboot, editing, animation, @DED-LEGO@ examples" 

Does anyone know how can I bring headings and blank lines in the menu.lst?

This question can also be solved with the inc-scripts editing.

Edited by ded, 10 December 2010 - 08:19 AM.

[Klaus21]

@ Ded
Thank you for your reply.
However, I have no idea where to change gfxboot.cfg in the what. With the title, I at first a small solution.

***
title Several Virenscanner
lock
find --set-root /menu.lst
configfile /menu.lst

[ded]

 

I have no idea where to change gfxboot.cfg in the what.

This is a text file (like menu.lst). To edit it you can use any text editor.   

***
title Several Virenscanner
lock
find --set-root /menu.lst
configfile /menu.lst

Grub4dos uses menu.lst by default. If you want to use multilevel menu, then pay attention to the topic of "Multilevel Enclosed Menus in Grub4DOS" 

Edited by ded, 10 December 2010 - 12:20 PM.

[ded]

Does anyone know how can I bring ... blank lines in the menu.lst?

Solution described here

[nierewa]

Man kann ja mit n für die einzelnen Einträge einen Erklärungstext eingeben.
Also z.Bsp.: title Boot first HarddisknMit Enter wird von der Festplatte gestartet

Ist das auch mit gfxmenu möglich?
Und wenn ja, wie?