Message files for the GRUB gfxmenu
Message files for the GRUB gfxmenu
Hello candy lovers
I have decided to start this thread for those of you who use the GRUB graphical boot menu (gfxmenu),
it is "Eye Candy" after all (albeit for a few seconds at a time).
I will post some of the message files that i have made (from the message file i compiled from the Suse source files),
any of those i post will be known to work with the GRUB packages i provided in This thread
They will NOT work with the original package i created (since been removed from that thread)
I have made these message files in two sizes: 800x600 and 1024x768
Unfortunately i could not get any widescreen ratio's working,
see next post for how i use GIMP to get around this.
If your display/monitor can handle 1024x768,
then i recommend that you use message files of that size rather than the 800x600 ones, they look better.
To start things off, i am posting two message files in both sizes, in future i will only be posting the larger size,
but using the information in the next post, you should be able to create your own in the smaller size.
You can rename any of the message files to whatever you like,
i only named them the way they are to let you know the size of them.
Please feel free to post your own creations here too,
All the best
CatDude
EDIT:
You might find this app useful BSME-1.0 & 2.0
.
I have decided to start this thread for those of you who use the GRUB graphical boot menu (gfxmenu),
it is "Eye Candy" after all (albeit for a few seconds at a time).
I will post some of the message files that i have made (from the message file i compiled from the Suse source files),
any of those i post will be known to work with the GRUB packages i provided in This thread
They will NOT work with the original package i created (since been removed from that thread)
I have made these message files in two sizes: 800x600 and 1024x768
Unfortunately i could not get any widescreen ratio's working,
see next post for how i use GIMP to get around this.
If your display/monitor can handle 1024x768,
then i recommend that you use message files of that size rather than the 800x600 ones, they look better.
To start things off, i am posting two message files in both sizes, in future i will only be posting the larger size,
but using the information in the next post, you should be able to create your own in the smaller size.
You can rename any of the message files to whatever you like,
i only named them the way they are to let you know the size of them.
Please feel free to post your own creations here too,
All the best
CatDude
EDIT:
You might find this app useful BSME-1.0 & 2.0
.
- Attachments
-
- BSME-2.0.png
- (140.32 KiB) Downloaded 3104 times
Last edited by CatDude on Tue 28 Oct 2014, 19:56, edited 3 times in total.
[img]http://www.smokey01.com/CatDude/.temp/sigs/acer-futile.gif[/img]
- ///////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\
Creating Your Own Message
\\\\\\\\\\\\\\\\\\\\\\\\\ /////////////////////////
To make any changes to the layout, or create your own message file.
(edit the image, change the position of mainmenu or bootoptions, text colour whatever)
This is how to do it.
The message file: pupsta1 ( that is pupsta with a number 1 )
is used in the following Howto.
Step 1.
Unpacking the message file:
- Create a directory to work in. (from now on referred to as WD1)
Put a COPY of the pupsta1 message file into it.
We will now unpack it.
Open a terminal in WD1, (right click: Window > Terminal Here)
and enter:( that is pupsta with a number 1 remember, it's probably easier if you Copy & Paste )Code: Select all
cpio -iv < pupsta1
You can keep this terminal open, for when we re-pack it (if you like).
You should now have the following files inside of WD1.- 16x16.fnt
back.jpg <-------------- this is the main image file (you can edit this, just DO NOT rename or resize it, and keep it as a .jpg)
en.hlp <----------------- this is the F1 Help file (you can edit this if you like, just be careful.)
en.tr
gfxboot.cfg <-------- this contains ALL the settings (you can edit this to change mainmenu position etc)
init
languages
pupsta1 <------------- DELETE THIS NOW or the final message will be bigger than it needs to be, and may not work.
timer_a.jpg
that contains various settings that control the layout of what you see at the GRUB boot screen.
Hopefully you should be able to figure most of it out.
Some of the things you can change are:- The colour of the text.
The position of the menu entries on the grub boot screen.
How many entries are displayed before needing to scroll.
The position of the Boot Options text.
is the F1 Help (in the bottom lefthand corner).
You would need to compile from source to achieve that (see below)
You can change the colour of the F1, but not the Help (it wouldn't for me at any rate)
- EDIT:
I have finally figured out how to change the colour of the Help text (next to the F1)
it appears that there is a typing error in one of the files in the SUSE source code.
So, if you would like to change the colour of said text
this is what you need to do:
After unpacking your message file, open gfxboot.cfg in your text editor
and find the line that looks like this:and change it to this:Code: Select all
panel.fg=0xffffff
That's it, obviously you can change the colour from white to whatever you like,Code: Select all
panel.normal.fg=0xffffff
then re-pack the message file as explained below.
With regard to the position of the F1 Help
As mentioned above, the position of this is not something that can be manipulted via the gfxboot.cfg file,
it needs to be done when compiling.
So for those who may be interested, i have now posted several message files with it positioned in the upper lefthand corner,
some with and some without the animated penguins theme.
Those with the penguins, have been set to a 50% chance of them showing.
- 16x16.fnt
Step 2.
Re-packing the message file:
- After making any changes, we now need to re-pack it.
Before you do that though,
make sure you have deleted the original message file in WD1- TIP:
Select ALL files in WD1 and note the size......(this is how big your new message file will be)
If after running the following command, your new message is bigger than what you previously noted,
DELETE it and then re-run the command again.
Or you could just provide the FULL PATH
for example:Code: Select all
ls | cpio -ov > /root/my-documents/WD1/6pups
enter:Code: Select all
ls | cpio -ov > 6pups
6pups is the name i am giving my new mesage, you can call yours whatever you like.
You will now see a new file (in my case, it is 6pups)
that is your new message file.
TIP 2:
It is a good idea to have a "Virtual Machine" of some sort, so you can test things without needing to reboot,
as it can take several edits before you get it looking right, personally i use QEMU for this.
Just for your information (and as a guide)
Here are some sizes that have worked for me.- back.jpg images ranging up to 815K
Final message files up to 1022K
I am not sure exactly what the limit of either is, but i think this is pretty close to it.
- TIP:
As i mentioned earlier, i could not get any widescreen ratio's working,
so i use GIMP to squash my widescreen images down to 1024x768 as that gives the best result on my monitor.
The resultant image, when stretched to fit my screen doesn't look too bad.
It's best to start with an image the size of your screen (in my case that is 1680x1050),
then i scale image by reducing it to 1229x768 to get the right height, then scale it again,
this time breaking the links to the right of the Width & Height boxes, and reduce the width (only) to 1024.
This technique works better on some images than it does on others, especially if it contains text,
but most of the time it looks better than if i was to use a standard 4:3 ratio image.
- NOTE:
Gimp has a tendency to corrupt images if the subsampling settings are not as shown in the image below.
These settings are in the Advanced Options of the save dialog,
and differ between Gimp versions 2.6.xx and 2.8.xx
- Attachments
-
- my-test-results.png
- (17.92 KiB) Downloaded 3072 times
-
- save-dialog1.png
- (24.41 KiB) Downloaded 3117 times
-
- save-dialog2.png
- (71.32 KiB) Downloaded 3157 times
Last edited by CatDude on Mon 27 Oct 2014, 15:06, edited 3 times in total.
[img]http://www.smokey01.com/CatDude/.temp/sigs/acer-futile.gif[/img]
Ok got here at last....
For grub4dos users the main point is to use version 4.4 which includes gfxmenu support. (and 256 inode and ext4 but not for the partition grldr is on).
The actual splash file is built in exactly the same way as normal grub.
Simply add
gfxmenu /path/to/splashfile
to your menu.lst
and enjoy....now to try and be artistic and get some graphics posted
mike
For grub4dos users the main point is to use version 4.4 which includes gfxmenu support. (and 256 inode and ext4 but not for the partition grldr is on).
The actual splash file is built in exactly the same way as normal grub.
Simply add
gfxmenu /path/to/splashfile
to your menu.lst
and enjoy....now to try and be artistic and get some graphics posted
mike
Ok the ball rolls..these are 1024x768
mike
ps apologies for the messy menus from my test flash stick...
mike
ps apologies for the messy menus from my test flash stick...
- Attachments
-
- splash_mill.jpg
- (112.47 KiB) Downloaded 31677 times
-
- splash_mist.jpg
- (67.64 KiB) Downloaded 37638 times
-
- splash_bird.jpg
- (48.42 KiB) Downloaded 31489 times
-
- splash_gold.jpg
- (23.32 KiB) Downloaded 31655 times
Last edited by mikeb on Thu 17 Dec 2009, 22:36, edited 1 time in total.
@ mikeb
That splash_bird looks pretty smart,
is he a friend of the elephant.
@ trapster
You feel free to hijack mate,
as to "mtpaintsnapshot.sh didn't pickup the mplayer video"
i think that is normal, well it is from my past experiences anyway.
Edit:
@ trapster (or anybody that's interested).
As you are using Mplayer, you could try the following (it worked for me)
Start Mplayer and open Preferences > Video
change the driver from: xv...X11/xv to x11...X11 (XImage/Shm)
CatDude
.
That splash_bird looks pretty smart,
is he a friend of the elephant.
@ trapster
You feel free to hijack mate,
as to "mtpaintsnapshot.sh didn't pickup the mplayer video"
i think that is normal, well it is from my past experiences anyway.
Edit:
@ trapster (or anybody that's interested).
As you are using Mplayer, you could try the following (it worked for me)
Start Mplayer and open Preferences > Video
change the driver from: xv...X11/xv to x11...X11 (XImage/Shm)
CatDude
.
[img]http://www.smokey01.com/CatDude/.temp/sigs/acer-futile.gif[/img]
Here is my grub message...
- Attachments
-
- vellowax2.jpg
- (27.95 KiB) Downloaded 10036 times
-
- vellowax1.jpg
- (58.28 KiB) Downloaded 10025 times
-
- vellowax.jpg
- (33.78 KiB) Downloaded 10039 times
Last edited by vellowax on Wed 23 Dec 2009, 18:23, edited 1 time in total.
Hello vellowax
unfortunately neither of my packages offer splashimage support.
There is this link: HOWTO add splash image to grub
Personally i think in comparison to gfxmenu, splashimages are rather lame (but i would, wouldn't i)
I like your vellowax2, what size images are you using in those message files ?
CatDude
.
If you are referring to GRUB splahimages,vellowax wrote:btw CatDude..how about splash image.
is there any link will guide me there?
unfortunately neither of my packages offer splashimage support.
There is this link: HOWTO add splash image to grub
Personally i think in comparison to gfxmenu, splashimages are rather lame (but i would, wouldn't i)
I like your vellowax2, what size images are you using in those message files ?
CatDude
.
[img]http://www.smokey01.com/CatDude/.temp/sigs/acer-futile.gif[/img]
the original size i've made is 1024 x 768, but i lower it to 800 x 600 for commonly supported resolution in old monitor so others can use. who knows, maybe someone would like it and use it (although-it wasn't good enough to compare with your message)I like your vellowax2, what size images are you using in those message files ?
vellowax
Out of those i posted up above only on the pup-pup did i put any effort into it,
the others are pretty much as they were when i download the images.
CatDude
.
Hey, don't under estimate your own work mate, they are fine.vellowax wrote:.... who knows, maybe someone would like it and use it (although-it wasn't good enough to compare with your message)
Out of those i posted up above only on the pup-pup did i put any effort into it,
the others are pretty much as they were when i download the images.
CatDude
.
[img]http://www.smokey01.com/CatDude/.temp/sigs/acer-futile.gif[/img]
All the pictures i used in that message were taken from various sites.
and I gathered them all in 1 picture or more and do some little editing. only the glass effect that i've made it myself.
# Linux bootable partition config begins
title NOP 431
rootnoverify (hd0,1)
kernel /puppy431/vmlinuz pmedia=atahd psubdir=puppy431 acpi=force
initrd /puppy431/initrd.gz quiet (splashimages)
# Linux bootable partition config ends
where the splashimages is the message file of the gfxmenu message and i did try other possibility (it was my dumb experiment) but still nothing is happen.
Is that what you mean by "neither of my packages offer splashimage support"?
and I gathered them all in 1 picture or more and do some little editing. only the glass effect that i've made it myself.
i'm afraid it isn't what i meant. as you said, it was the comparison of gfxmenu.There is this link: HOWTO add splash image to grub
Personally i think in comparison to gfxmenu, splashimages are rather lame. (but i would, wouldn't i)
i do this with my menu.lstIf you are referring to GRUB splahimages,
unfortunately neither of my packages offer splashimage support.
# Linux bootable partition config begins
title NOP 431
rootnoverify (hd0,1)
kernel /puppy431/vmlinuz pmedia=atahd psubdir=puppy431 acpi=force
initrd /puppy431/initrd.gz quiet (splashimages)
# Linux bootable partition config ends
where the splashimages is the message file of the gfxmenu message and i did try other possibility (it was my dumb experiment) but still nothing is happen.
Is that what you mean by "neither of my packages offer splashimage support"?
Not exactly, i have never seen that way of doing things beforevellowax wrote: i do this with my menu.lst
# Linux bootable partition config begins
title NOP 431
rootnoverify (hd0,1)
kernel /puppy431/vmlinuz pmedia=atahd psubdir=puppy431 acpi=force
initrd /puppy431/initrd.gz quiet (splashimages)
# Linux bootable partition config ends
where the splashimages is the message file of the gfxmenu message and i did try other possibility (it was my dumb experiment) but still nothing is happen.
Is that what you mean by "neither of my packages offer splashimage support"?
what i thought you intended to do was point to a splashimage insted of a message file in your menu.lst
but as i said, my packages do not support splashimages, ONLY gfxmenu message files.
CatDude
.
[img]http://www.smokey01.com/CatDude/.temp/sigs/acer-futile.gif[/img]
OK...I just could not leave it... it's because my curiosity about splash image during boot in puppy.
After a lot of read, there are several ways to do it. I only try bootsplash and splashy.
On bootsplash, it should need to recompile the kernel, since i messed up with .config, after several times trying to figure it out. I gave up.
But there's a simple way to have bootsplash in your box , and i almost there to play with it. With splashy, there's no need to recompile the kernel. Now, i don't have a text running during booting, but neither the splash image too, i think it's because the themes for bootscreen or the lib for jpeg and/or png. I wish i have a lot of time to fix this.
After a lot of read, there are several ways to do it. I only try bootsplash and splashy.
On bootsplash, it should need to recompile the kernel, since i messed up with .config, after several times trying to figure it out. I gave up.
But there's a simple way to have bootsplash in your box , and i almost there to play with it. With splashy, there's no need to recompile the kernel. Now, i don't have a text running during booting, but neither the splash image too, i think it's because the themes for bootscreen or the lib for jpeg and/or png. I wish i have a lot of time to fix this.
Hi
Thought it was about time that i posted a new message file, so here it is.
Basically i took the default wallpapers from Puppy versions 1, 2, 3, 4 and 4.31 (left to right)
put them into the GIMP, gave it a good shake and ended up with this.
CatDude
.
Thought it was about time that i posted a new message file, so here it is.
Basically i took the default wallpapers from Puppy versions 1, 2, 3, 4 and 4.31 (left to right)
put them into the GIMP, gave it a good shake and ended up with this.
CatDude
.
[img]http://www.smokey01.com/CatDude/.temp/sigs/acer-futile.gif[/img]