Hello,
on my USB-stick I have several LINUX-Systems for tests and can easily boot each.
Now I want to add some files (PDF-Instructions or TXT-Results, which may be updated in subsequent sessions) on that stick, so that I can access it from each running LINUX.
How can a achieve this?
Thanks, Michael

"control": [
        { "VTOY_DEFAULT_MENU_MODE": "1" },
        { "VTOY_TREE_VIEW_MENU_STYLE": "1" },
        { "VTOY_FILT_DOT_UNDERSCORE_FILE": "1" },
        { "VTOY_MENU_TIMEOUT": "8" },
        { "VTOY_DEFAULT_IMAGE": "VTOY_EXIT" }
    ],

   This is my current control from my ventoy.json with 1.0.27 not sure if it is correct. It exits after 8 seconds but I am being put into my boot options menu and stopped there instead of booting into windows directly. Is there currently any method or trick to boot directly into windows by default or could this possibly be included in a future update? My use case is that I have small usb I often keep in the laptop all the time for extra space aswell, so it would be very useful for me to reboot in a fully automated way. 

   Once again thanks for your work and your many additions to the project over the last several updates.

Hello,
Is it possible to have a different layout of the Main Menu (with the list of folders) and sub-folders.
For example, change the background page or the spacing between lines or the font size ...?
If so, where should the changes be made ?

[b]VENTOY GRUB4DOS UEFI SUPPORT ?[/b]

[b]a1ive :                                     http://reboot.pro/topic/22400-grub4dos-for-uefi/[/b]
[b]Source Site:                            http://bbs.wuyou.net/forum.php?mod=viewthread&tid=422652[/b]
[b]Download Grub4DOS-UEFI:  https://drive.google.com/file/d/1liz64jrvmXefWn-Fvo_PLu1LdE2f6xXC[/b]

Is Ventoy will add feature to support chainloaded from other boot manager such as refind in the future?

Hello,

could someone test Bob.Omb's Modified Win10PEx64 v4.8 RS5.


https://1drv.ms/u/s!At_H8TIRYQubfo9IV61I...w?e=iNbLgB

PW: VanVlusen


Boot well with VMWare and on real systems in Legacy and UEFI.

But it's not all integrated programs available.



Tested with Ventoy 1.0.26 and 1.0.27

Hello all,

I'm using this examples from youtube : https://www.youtube.com/watch?v=-j6kEoJjSk0  to install new themes, but I couldnt see the differents icons of windows or linux in the ventoy boot menu in my flash disk, any idea how to solve this issue please.

in the video I could see the small icons but not working for me, even I respected all the simples instructions.

Thank you for help.

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