The Windows utility, E2B_Editor.exe will help you to make a custom menu for your own custom wallpaper.
First, copy an uncompressed .bmp wallpaper file onto your E2B USB drive in or under the \_ISO folder (e.g. \_ISO\Mary\Special_800x600.bmp)
Always run E2B_Editor.exe directly from the \_ISO folder on the E2B USB drive.
If you don't have a .cfg file, load the \_ISO\Sample_MyE2B.cfg file directly from the E2B USB drive.
E2B will only use the configuration file if it is called \_ISO\MyE2B.cfg.
You should find E2B_Editor.exe in the \_ISO folder inside the E2B download or download the latest version from the Alternate Downloads Area.
The page below relates to the latest version (and not necessarily the version in the E2B download which may be older).
A Windows system
1152 x 768 pixels or larger monitor (if the vertical height is less than 900 pixels - e.g. 768, then E2Bed will use a borderless version of the GUI).
1024x768 will (just\almost) fit and E2Bed will be usable, 800x600 displays are not suitable!
For the wallpaper, you will need a 800x600 or 1024x768 24-bit .bmp bitmap file (or a non-progressive .jpg file if using E2B v1.72+) - do not use a compressed .gz file!. Lots of progressive format wallpapers can be found here (note: Load into MSPaint and re-save as non-progressive .jpg). Tip: 800x600 (4:3) is best - not all systems support 1024x768, e.g. most netbooks. Copy the wallpaper file to the E2B USB drive\_ISOfolder (or any sub-folder).
E2B_Editor.exe must be run from a writeable drive because it creates temporary files on the same drive.
Should be run from the \_ISO folder on the E2B USB drive - otherwise you will not get the Language and Keyboard boxes populated correctly.
E2Bed will accept ANSI or UTF-8 .cfg files and will create UTF-8 .cfg files.
If testing E2B using QEMU or VBOX+VMUB, quit E2B_Editor.exe first, because the VM may make the files on the USB drive inaccessible which will cause E2Bed to display an error.
E2Bed does not support Chinese/Japanese/Persian glyphs - you must edit the .cfg file afterwards using a text editor if you want non-ANSI characters to be saved in the .cfg file for the heading or footer text.
E2Bed can be used to create a \MyCSM.cfg configuration file for use with the CSM Menu found in .imgPTN files (MPI v0.067+).
If you have a low-res display (e.g. 1024x768) ensure the Windows Display DPI setting is set to the Normal setting (96), otherwise it may not fit on the display and will be out of proportion.
Using the E2B_Editor (E2Bed)
When you first run the E2B_Editor (aka. E2Bed) it will ask you to:
Select a .cfg file (e.g. Sample_MyE2B.cfg or MyE2B.cfg) Normally, you will have aready made a \_ISO\MyE2B.cfg file by copying the \_ISO\Sample_MyE2B.cfg file - however, if you do not have a .cfg file, just select the \_ISO\Sample_MyE2B.cfg file and a new file will be written when saved (either as New_MyE2B.cfg, or MyE2B.cfg if one does not already exist).
Select a wallpaper background file (if applicable) N.B. THE FILE SHOULD BE LOADED DIRECTLY FROM THE E2B USB DRIVE (otherwise the path in the MyE2B.cfg file will be wrong when you save it!)
E2Bed will parse the specified .cfg file for the menu parameters and the Language and Keyboard settings. By default, ENG will be set as the language and no keyboard country will be selected (unless the settings are in the .cfg file).
E2Bed will then populate two listboxes with the languages folders and the keyboard translation KEY_xxxx.g4b files in the X:\_ISO\e2b\grub\ folder (where X: is the same drive as the .cfg file). If you are not running E2Bed from the E2B drive, then it won't be able to populate these listboxes.
E2Bed will look for a 'set MYWBMP=xxxx' entry in the chosen .cfg file and attempt to load the bitmap that is specified. If no file is specified or if the file specified cannot be found, then E2Bed will look for a \_ISO\MyBackground.bmp file (uncompressed). If this cannot be found, then the user will be prompted to select a wallpaper bitmap file.
E2Bed cannot load a compressed .bmp file.
You can load a .jpg file into E2Bed. Note that Progressive jpg files (e.g. SOF2) will load in the Editor but will not work when you boot to E2B - try re-saving the .jpg using MSPaint if it does not load in E2B.
Note: Only E2B v1.72+ versions and only grub4dos 0.4.6a 2015-08-05 and later versions support .jpg files - so switching to an older version of grub4dos may not load the .jpg file - I recommend using .bmp files (you can compress them later using the LZMA encoder tool if you wish, to reduce their size and increase load speed).
Once you have the E2Bed GUI displayed, you can use the controls, as follows:
GRID - superimposes a grid over the image
NUMBER - numbers the x and y axes over the image
SHIFT PICTURE UP - shifts up the image window so that it will fit on a low resolution display (e.g. 1360 x 768) - in this mode the HEADING, HELPTEXT, language and keyboard fields will be hidden.
FOOTER HELPTEXT - this is the footer help text that is normally displayed at the bottom of each menu (e.g. Reboot [F9] Power Off [F10]) - but it can be used to display text anywhere on the screen. You can use the [email protected]%, [email protected]%, %VER%, %B64% and %^LANG%variables in the text. Do not use leading spaces as they will be ignored by E2B (but not by the editor). Adjust the position using HEADPOS instead or use preceding \x20 strings instead of a space character.
MENU - these parameters control the position, size and colour of the menu entries
BORDER - these parameters control the colour of the border and the thickness (0-4) of the border
HEADING - these parameters control the position and colour of all menu headings. CENTREHD = 1 will cause all menu headings to be centred over each menu.
Note: The centre position will be shifted to the right if you use a HEADPOS that does not end in 00.
FOOTER HELPTEXT - these parameters control the position and colour of the footer HELPTEXT text - normally at the bottom of the display but can be anywhere on the screen or even off-screen.
Language listbox - highlight the language that you want E2B to be displayed in (languages folders must be present on the same drive as E2Bed)
Keyboard listbox - highlight the keyboard scancode conversion file that you want E2B to use (kbd files must be present on the same drive as E2Bed)
Other E2B Options - you can select or deselect various advanced configuration options here
(config file path) - click on this to edit or view the current .cfg file in Notepad
(image file path) - click on this text to launch the .bmp file (view\edit) - depends on Windows file association for .bmp on your system
Load Config (*.cfg) - this button will allow you to load a E2B .cfg file (a new bitmap may also be loaded if it is specified in the .cfg file)
Load Bitmap (*.bmp) - this button will allow you to change the wallpaper bitmap without changing the menu parameters - .jpg files can also be loaded.
Save .cfg file - this button will always create a temporary file (MyE2B.tmp) in the same folder as E2Bed.
You will then be asked if you want to update the existing (or new) .cfg file. If you answer 'No' then E2Bed will open the MyE2B.tmp file for you in Notepad. If you answer 'Yes' then E2Bed will:
Backup the old .cfg file into a MyE2B.bak file
Overwrite the old .cfg file with the new values (or make a new file)
Copy all lines that occur after the line containing '-- ADVANCED MENU SETTINGS ---' to the .cfg file. If the special line does not exist, you will be warned.
Open the updated .cfg file in Notepad for you to view and edit if required.
Undo (CTRL+Z) - Undoes the most recent menu position change. If you accidentally clicked on the bitmap window and thus moved\resized the menu, this will restore the previous values! It only has a memory of 1 change though - think of it as an 'Oops' button!
Draw a menu box with the mouse
You can use the mouse to draw a menu. Note that the menu border (if enabled) will be drawn around the outside of the menu area that you draw with the mouse. The Undo button will restore the previous menu size and position.
24-bit colours (e.g. FF00FF)
These must be 6 hexadecimal numbers (0-9, A-F), the first two characters are the Red value, followed by the Green value and then the Blue value (i.e. RRGGBB). Hex value 00 would mean no colour, FF would mean full colour, 80 would mean half-full colour.
000000 is therefore Black. FFFFFF is White, 808080 is grey, FF0000 is Red, 00FF00 is Green, 0000FF is Blue, 00FFFF is Cyan, FFFF00 is Yellow and so on.
Any value between 000001 and 0000FF will automatically have a Green 01 value added because 24-bit colour values must be greater than 0000FF in order to work correctly with the grubdos color command.
When in graphics mode (i.e. E2B is displaying a bitmap), all grub4dos text will have a transparent background so that the picture can be seen underneath the text. However, the menu highlight text (selected menu item = highlight) and the console text (standard), can display a background colour - e.g.
color highlight=0xFF0000 < this is overridden by the next line
color highlight=cyan/red < foreground/background pair
will display the cyan highlighted menu entry with a red solid bar background behind it.
color highlight=cyan/red < this is overridden by the next line
will display a red (RGB = FF0000) highlighted menu entry with a transparent background (because the background colour is 000000 (0xFF0000 == 0x0000000000FF0000).
You can use a 64-bit value to set both the highlight background colour and the text colour:
color highlight=0x0022222200FFFF00 < yellow 00FFFF00 + background will be 00222222 (v. dark grey/black) - see screenshot below:
Tip - Instead of colour pairs, you can set a foreground/background pair using a value of 255 (FF) or less, e.g. color highlight=0x1c will set a light-red text (c) on a blue (1) background.
Note: E2Bed does NOT display a background highlight colour. It always uses a transparent highlight background.
4-digit colours - HCOLOUR and FCOLOUR (e.g. 0103)
These must be in the format of ABCD where:
A = 0 or 1 where 1 = blink - E2Bed only allows 0 (Note: It won't blnk if using a VM/QEMU).
B = 0 or 1 where 1 = bright/intensity on bit
C = 0-7 background colour (E2Bed only allows 0 = transparent)
D = 0-7 foreground colour
If you click on one of these fields, E2Bed will allow you to choose from 16 colours and will automatically enter the correct value.
Note that Black (0) is treated as 'transparent' by E2B if defined as a background colour.
Tip: If you want some text hidden (e.g. menu help text), then you can use one of the following methods:
Use a rectangle in your bitmap background that is the same colour as your text, so that the text cannot be seen against that area of the background.
- or -
Specify the start position for that text to be outside of the display area - e.g. setting tophelp=37 for a 800x600 bitmap, will place the menu help text off-screen.
4-digit positions - HEADPOS and HBTM (e.g. 3201)
These must be in the form YYXX, e.g. 3201 will draw the text starting at 32 lines down and 1 character across.
Note: I suggest that HEADPOS normally ends with XX=00 (e.g. 3200) because E2B will pad out the headings assuming they start at offset 0. HEADPOS will affect both Main menu and Sub-Menu headings.
CENTREHD=1 for centering headings, assumes the XX position is 00. If it is not 00, then the centre position will be shifted to the right by the amount specified in HEADPOS. e.g. CENTREHD=1 and HEADPOS=0108 will cause the headings to be shifted 8 spaces over to the right of the true centre position above the menu on line 1 (the 2nd line from the top).
HBTM is an absolute YYXX position for the FOOTER help text and is not padded out by E2B in any way. It can be used to place text anywhere on the display.
Advanced Menu Settings
E2Bed will look for a special line of text in the source .cfg file - it must contain the string "-- ADVANCED MENU", e.g.
# ----------- ADVANCED MENU SETTINGS ------
all lines below this line will be copied to the new .cfg file when you update it. Any E2B settings that are already supported by E2Bed will be removed before the lines are copied to the new .cfg file.
If you have any special settings, e.g. font or hotkeys, etc. then place them below this special line and they will be preserved when copied over to the new .cfg file.
The Sample_MyE2B.cfg file already contains this special line (v1.65+).
E2B Options (pwd, EXTOFF, AUTONUM, etc.)
Note: Most of these option checkboxes do not cause the E2B_Editor display to change, but they will add entries to the .cfg file and thus affect E2B when you boot from it.
Only the AUTONUM and EXTOFF settings affect the menu that is displayed by E2Bed.
If you want to disable the grub4dos menu password (pwd) then you must tick the password checkbox before saving the .cfg file.
To override any pwd setting with your own password, place your 'set pwd=xxx' line below the -- ADVANCED MENU SETTINGS -- line.
AUTONUM=0 causes the menu numbering down the left-hand side of the menu to be suppressed/removed.
The checkbox will be automatically ticked if your .cfg file contains 'set AUTONUM=0' or 'set AUTONUM=0x0000'.
I recommend that you do not tick the redir or redirp boxes unless you are an experienced E2B user and have tested all the E2B ISO's, etc. These options will suppress useful user tips, information and warning messages which may help you to fix problems with some 'difficult' payload files.
Displaying File Extensions in the Menus
If you have no \_ISO\MyE2B.cfg file, E2B will only display the file names in the menus and will not display the file extensions.
However, when you run E2B_Editor, the default will be to show file extensions in the menu (unless you load a .cfg file that has EXTOFF=1).
If you want E2B to show the filenames without their extensions, tick the Other E2B options - EXTOFF=1 checkbox.
Note: The .cfg file may contain more than one 'set' command of the same type:
(some lines here)
The last setting will always be the one to take affect (so no file extensions will be show in the E2B menu, in this example).
Note: As with most variables, EXTOFF=0 is the same as EXTOFF=1 or EXTOFF=99. You must use EXTOFF= to clear the variable if you want to see the file extensions in the menu.
E2Bed will use either a normal Windows form with the usual top border and min/max/exit icons or a borderless form if your display does not have enough resolution for a 1024x768 bitmap.
The borderless form cannot be moved (it will be located at 0,0 which is the top-left of the display).
You cannot resize or maximise the form.
Use the 'SHIFT PICTURE UP' checkbox to move the bitmap to the top of the screen if you don't have a large enough display.
Tip: If you cannot see the Exit button (e.g. on a 800x600 display) - press ALT+X to Exit E2Bed.
Compress the wallpaper bitmap
Once you have the .cfg file working, you can compress the .bmp file to a .gz file (e.g. using 7Zip) or, even better, use LZMA for even greater compression.
To compress a file using LZMA, just drag-and-drop the .bmp file onto the \_ISO\docs\E2B Utilities\LZMA\LZMA_ENCODE.cmd file. It will compress the orginal file but not change it's filename. A backup will be made of the original file which you can choose to delete.
If you wish, you can even compress the .cfg file using the same LZMA_ENCODE.cmd script file!
E2B v1.72+ also will accepted standard (non-progressive) JPEG files which are usually much smaller than .bmp or .bmp.gz files. You can use MSPaint to convert a .bmp file to a .JPG file.
For best image quality, I suggest you always work with .bmp files in your graphics editor. Once you have finished all editing of the .bmp file, you can convert it to a .jpg file using MSPaint- Save As - JPEG.
Note that even though E2B will automatically decompress gzip and LZMA-encoded files, theE2B_Editor can only work with uncompressed files!
Using the E2B_Editor without needing a USB drive
To work fully, the E2B_Editor needs to be run from the \_ISO folder on the root of a drive which has the E2B download files on it .
You can copy the whole _ISO folder from the download to the root of one of your system drives (e.g. D:\_ISO) or you can 'map' a virtual drive as follows:
1. Use the WindowsKey+R key chord to open a Run box and type cmd, then type
subst Z: C:\temp\Easy2Boot
where your extracted Easy2Boot files have been copied to C:\temp\Easy2Boot.
2. Now go to Z:\_ISO in Windows Explorer.
3. Copy your .bmp (or .jpg) files to the Z:\_ISO folder (or anywhere you like under Z:\_ISO).
4. Run E2B_Editor. Check that you now have the Language and Keyboard boxes populated correctly.
Note: The Z: drive will be lost if you reboot your system, but the files will still be in C:\temp\Easy2Boot.
Test different .cfg files (multiple Themese/Skins)
See the \_ISO\docs\mythemes folder and read the ReadMe.txt file for instructions.
This allows you to easily test many different configurations without needing to reboot each time.
Copy the $Default E2B Menu.cfg file to the \_ISO folder.
Then add the $Change_Theme.mnu file to the Main Menu which will allow you to choose any .cfg file.
You can add more .cfg files to the \_ISO\docs\mythemes folder or edit the .mnu file to get .cfg files from a different folder.