Usage of vesamenu.c32 module in the Tiny Core Boot Menu

[Nathan_SR]

Hi,

Is there any specific reason, why menu.c32 is used, instead of vesamenu.c32 module in the Tiny Core Boot Menu ?

As you are probably aware, vesamenu.c32 is capable of producing a nice graphical menu, instead of a text menu, at the cost of just about 120 KB more.

I see that, operating systems like Arch Linux use a vesamenu boot screen, as shown in these pictures :

https://www.addictivetips.com/ubuntu-linux-tips/how-to-install-arch-linux/attachment/arch-linux-boot-menu/

https://www.georgefield.com.au/wp-content/uploads/2017/05/arch-linux-on-virtualbox.png

So, why not utilize its capability, to produce an attractive menu ?

P.S. I am enclosing the vesamenu modules, that I used for remastering tiny core as quick-save-live, should in case, somebody wants to utilize them. Using a good ISO Editor Application should help in copying them across, after taking sufficient backups.

Regards,

Nathan SR

[curaga]

The default iso is 13mb, so 120kb for a pretty boot screen is significant.

[Nathan_SR]

Ok, Got it. Thanks Curaga....

[hiro]

also, what's the benefit of the boot screen being "pretty"?
will it be pretty on a serial console, too?

[Nathan_SR]

Hi Hiro,

If you look at this boot screen : https://www.georgefield.com.au/wp-content/uploads/2017/05/arch-linux-on-virtualbox.png

It conveys a lot more than what mere text can convey. It gives a Professional, Authentic, Unique and Genuine look / touch to the boot menu. I am taking arch linux as an example here, as it matches tiny core, for being light weight distribution. Also, vesamenu module is intelligent enough to display graphical / text menu, depending on the situation.