I would like to understand how a change in the default values causes a change in the theme, once uploaded a link that explains in the pictures how a change of each parameter actually affects



# GRUB2 gfxmenu Linux theme
# Designed for any resolution

# Global Property
title-text: ""
desktop-image: "background.jpg"
desktop-color: "#000000"
terminal-font: "Terminus Regular 14"
terminal-box: "terminal_box_*.png"
terminal-left: "0"
terminal-top: "0"
terminal-width: "100%"
terminal-height: "100%"
terminal-border: "0"

# Show the boot menu
+ boot_menu {
  left = 30%
  top = 30%
  width = 45%
  height = 60%
  item_font = "Unifont Regular 16"
  item_color = "#cccccc"
  selected_item_color = "#ffffff"
  icon_width = 32
  icon_height = 32
  item_icon_space = 20
  item_height = 36
  item_padding = 5
  item_spacing = 10
  selected_item_pixmap_style = "select_*.png"
}

# Show a countdown message using the label component
+ label {
  top = 82%
  left = 32%
  width = 30%
  align = "center"
  id = "__timeout__"
  text = "Booting in %d seconds"
  color = "#cccccc"
  font = "Unifont Regular 16"
}

+ hbox{
    left = 30%
    top = 95%
    width = 10%
    height = 25
    + label {text = "@VTOY_HOTKEY_TIP@" color = "blue" align = "left"}
}

+ hbox{
    left = 90%
    top = 5
    width = 10%
    height = 25
    + label {text = "@VTOY_MEM_DISK@" color = "red" align = "left"}
}




I have given here an example of such a file, in case I might not have understood enough


Thank you

Ventoy plays we  with almost all computers/Laptops except about 10 percent of them where I get the Minimal BASH Grub where it says "Minimal BASH-like line editing is supported."


OK In my testing I installed Ventoy on a fresh Large FlashDisk 256 GBs and It gave the Mini Bash Shell.

I Then Burned MediCat (32 GBs Image) as an example directly on the 256 GBs FlashDisk and it worked normally without resizing or moving partitions.

I Moved the Ventoy Partition to the End of the FlashDisk and Bam it happened. Now I get the MiniBash Shell error. I am just asking for Ideas on what to do??

Hi all,

maybe too much info but here goes... Running Linux Mint 19.3 "Tricia" Cinnamon 64-Bit on the system on which the ISOs were tested.
USB devices used: 2 x 32 GB SanDisk Ultra Flair (3.0).

Tested ISOs:

LINUX MINT
1.
Linux Mint 20 "Ulyana" Cinnamon (64-bit)
* Desktop Environment: Cinnamon
* Official: yes
* iso name: linuxmint-20-cinnamon-64bit.iso
* ISO verified: yes (`sha256sum` and `gpg --verify`)

2.
Linux Mint 19.3 "Tricia" Cinnamon (64-bit)
* Desktop Environment: Cinnamon
* Official: yes
* iso name: linuxmint-19.3-cinnamon-64bit.iso
* ISO verified: yes (`sha256sum` and `gpg --verify`)

UBUNTU
3.
Ubuntu 20.04.1 LTS (64-bit)
* Desktop Environment: UNSURE (Unity or GNOME?)
* Official: yes
* iso name: ubuntu-20.04.1-desktop-amd64.iso
* ISO verified: yes (`sha256sum`)

POP!OS
4.
Pop!OS (nvidia installed) (64-bit)
* Desktop Environment: UNSURE
* Official: yes
* iso name: pop-os_20.04_amd64_nvidia_13.iso
* ISO verified: yes (`sha256sum`)

5.
Pop!OS (nvidia not installed) (64-bit)
* Desktop Environment: UNSURE
* Official: yes
* iso name: pop-os_20.04_amd64_intel_13.iso
* ISO verified: yes (`sha256sum`)

MANJARO
6.
Manjaro KDE Plasma 20.1.2 (64-bit)
* Desktop Environment: KDE Plasma
* Official: yes
* iso name: manjaro-kde-20.1.2-201019-linux58.iso
* ISO verified: yes (`sha1sum`)

7.
Manjaro XFCE 20.1.2 (64-bit)
* Desktop Environment: XFCE
* Official: yes
* iso name: manjaro-xfce-20.1.2-201019-linux58.iso
* ISO verified: yes (`sha1sum`)

8.
Manjaro MATE 20.0.1 (64-bit)
* Desktop Environment: MATE
* Official: no (community edition)
* iso name: manjaro-mate-20.0.1-200514-linux56.iso
* ISO verified: yes (`sha1sum`)

9.
Manjaro Cinnamon 20.1.2 (64-bit)
* Desktop Environment: Cinnamon
* Official: no (community edition)
* iso name: manjaro-cinnamon-20.1.2-201019-linux58.iso
* ISO verified: yes (`sha1sum`)

10.
Manjaro (i3 window manager) 20.1.2 (64-bit)
* Desktop Environment: Unsure?
* Official: no (community edition)
* iso name: manjaro-i3-20.1.2-201019-linux58.iso
* ISO verified: no (no sha1 provided for 64-bit version on Manjaro Community Edition site, possible bug?)

FEDORA
11.
Fedora Workstation 32 (GNOME) (64-bit)
* Desktop Environment: GNOME 3
* Official: yes
* iso name: Fedora-Workstation-Live-x86_64-32-1.6.iso
* ISO verified: yes (`sha256sum`)

MX LINUX
12.
MX Linux 19.2 "patito feo" XFCE (64-bit)
* Desktop Environment: XFCE
* Official: yes
* iso name: MX-19.2_x64.iso
* ISO verified: yes (`sha256sum`)

13.
MX Linux 19.2 KDE (64-bit)
* Desktop Environment: KDE
* Official: yes
* iso name: MX-19.2_KDE_x64.iso
* ISO verified: yes (`sha256sum`)

CLONEZILLA LIVE
13.
Clonezilla (Live)
* iso name: clonezilla-live-20200703-focal-amd64.iso
* ISO verified: yes (`sha1sum`, `sha256sum`, `sha512sum`)


and here is output from

Tried with latest Ventoy 1.0.26
http://redorescue.com/

Attached Files

Thumbnail(s)
   

Hello everyone!

As many have already told before thanks for the great work!
This piece of software replaces many CDs and USB sticks.

I think I should have read all the documentation by now and except for the persistence feature I could use everything, but how the heck do I get submenus into the main menu?
I have about 60 entries there, you have to scroll forever, I would like to have it more clearly arranged, and I dont want to hit F6 to do it all in my own ventoy_grub.cfg.

Is there another trick?

thanks for your help and keep on the good work

Hello guys, i'm really enjoying this project, but i don't know why from 2 weeks on my Lenovo Yoga 14 ventoy can't boot any Os.

There's not secure boot activate, i tried with csm activate or not, i used 2 different usb keys, i tried 4/5 Os' supported, Ventoy boot (in UEFI) but when i choose an Os it remain a black screen and doesn't do nothing. Did anyone my same problem encountered? Thanks a lot whoever can help me

你好
        请问从IMAC上面加载PE ISO后提示Not a Secure Boot Platform 14 然后就卡在这里了，这个是什么问题

建议作者跟MBROSTool的作者交流下。
http://bbs.wuyou.net/home.php?mod=space&uid=436204
mbr的Secure Boot我测试了下，用的很好。也不用单独操作啥的。

Hello

There is a way (a variable) to know if Ventoy pendrive booted in UEFI mode or in BIOS (legacy) mode, and to select the displayed theme : one for UEFI mode and another for BIOS mode.

Thanks

Is it possible for the developer of Ventoy to make Ventoy2Disk detect as "Ventoy", and allow its updates, Ventoy partitions that have been modified in size, formatting or location ?