hi, @longpanda
Can you help, I want to edit ventoy_x64.efi file
Sorry, I opened the subject to the plugin section

/bin/sh: nasm: no commands
make: *** [/home/koylu/Ventoy-master/EDK2/edk2-edk2-stable201911/Build/MdeModule/RELEASE_GCC48/IA32/MdePkg/Library/BaseLib/BaseLib/OUTPUT/Ia32/ARShiftU64.obj] Hata 127

build.py...
 : error 7000: Failed to execute command
    make tbuild [/home/koylu/Ventoy-master/EDK2/edk2-edk2-stable201911/Build/MdeModule/RELEASE_GCC48/IA32/MdePkg/Library/BaseLib/BaseLib]

build.py...
 : error F002: Failed to build module
    /home/koylu/Ventoy-master/EDK2/edk2-edk2-stable201911/MdePkg/Library/BaseLib/BaseLib.inf [IA32, GCC48, RELEASE]
- Failed -
Build end time: 10:37:43, Mar.08 2021
Build total time: 00:00:12

Hello  longpanda,

Is it possible to have ventoy support floppy disk images such as IMA and IMG?

Thanks

• 2021/03/06 --- 1.0.37 release
  

1. Experimental support for loongson mips64el UEFI. Notes
   
   
2. Add VentoyWebDeepin.sh script for Deepin/UOS. Notes
   
   
3. Add VTOY_MAX_SEARCH_LEVEL option in global control plugin. Notes
   
4. Improvement for UEFI boot compatibility.
   
5. remove the ASSERT warning in UEFI mode when boot fail.
   
6. use uname -m to detect architecture in shell script (PR #774)
   
7. Change the partition configuration dialogbox layout in Ventoy2Disk.exe to fit text area. (issue #769)
   
8. languages.ini update
   
9. Document: Ventoy Search Configuration
   

Hi,

I've installed Fedora 33 on VirtualBox with UEFI enabled, then download vtoyboot, and run on F33.
When I boot from usb sitck and choose the "vdi.vtoy" option it appears a message such as:

I tested (live: Advanced options > Load to RAM) minimalistic distro Miyo Modern x6_x64 20200513 with Ventoy-1.0.36.
By Author: Miyo is simply an acronym for "make it your own".
ISO: miyo-modern-x86_64-UEFI-20200513.iso (0.83GB)
Info: info wiki
Download: download
Boot: UEFI64 (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U AMD Radeon R9 graphic

Attached Files

Thumbnail(s)
       

Hello,
I use Ventoy in treetview mode with iso files. I put ventoy.json and theme.txt with icons, passwords and aliases.
But I was wondering if it was possible to put a different background per folder.
Example: The Antivirus folder will have antivirus.png as background. The Partitions folder will have partitions.png. AND so on...
Thank you in advance

I tested (live) Kali Linux 2021.1 Live amd64 with Ventoy-1.0.36.
ISO:  kali-linux-2021.1-live-amd64.iso (3.3GB)
Download: download  /  download
Boot: Legacy; UEFI (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U AMD Radeon R9 graphic

Attached Files

Thumbnail(s)
   

I tested (live) Netrunner Desktop 21.01 64bit with Ventoy-1.0.35/1.0.36.
ISO: netrunner-desktop-2101-64bit.iso  (2.6GB)
Download: download /  download
Boot: Legacy/MBR, UEFI64 (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U  AMD Radeon R9 graphic

-----------------------------------------------------------------------------------------------------------------------------------
Of'coz - new and old distros, infos etc. always on https://distrowatch.com/

Attached Files

Thumbnail(s)
               

Ventoy has a plugin to work with the debian autoinstaller. Unfortunately, Ubuntu 20 comes with a new auto install method (cloud-init), which works differently. At first, I wasn't able to get it to work with Ventoy, so I made an account to ask for help; in the time it took the account to get activated, I solved the problem however. So here's how to do it in case anyone else has the same problem.

A working auto installer needs two files, one `meta-data` and one `user-data`. These need to be on a partition that has `cidata` as the partition label.

These files can not be put into the same partition that has the iso files, because that partition is locked while the booted software is running.

So, to get it to work:

• When running Ventoy for the first time to install it on the USB drive, leave some space for a 3rd partition. On linux, that's `-r 16` to leave 16 MB at the end of the medium.
  
  Code:

  ventoy-1.0.36/Ventoy2Disk.sh -I /dev/sdX -r 16
• Create a new partition on the medium
  
  Code:

  fdisk /dev/sdX
n (new)
p (partition)
3 (partition number)
press return twice to confirm the sector numbers
t (type)
3 (partition number)
7 (vfat partition type)
w
• format it to vfat, and name it `cidata`.
  
  
  Code:

  mkfs.vfat -n cidata /dev/sdX3
• copy the ubuntu installer iso to the first partition, and your user-data and meta-data to the third partition
  

Hi,
Ventoy is already amazing as it is, and still keeps innovating to get even better.
So I would like to offer some suggestions for innovation in case they may be feasible and welcome… all aimed at helping Ventoy to fit in and integrate more with existing hdd usage, thereby making it even more useful and indispensable.
And at least it can offer some food for thought.

1.  Currently Ventoy can be installed on hdd and preserve some unused space after it, but it could be helpful to have option for allocating a specified amount for Ventoy use, and preserving whatever is remaining.

At the moment Ventoy overwrites the partition table for itself, oblivious to any existing contents, thereby losing bootable access to any remaining existing partitions which may have been deliberately preserved.
So to avoid losing existing partitions and their contents:

2.  Could Ventoy offer an option to detect existing partitions? and if so... 
3.  Could Ventoy have an option to install itself into the first partition to leave the remainder untouched?
4.  Or even better, could Ventoy have an option to select any chosen existing partition to install itself into?

Lastly, with the aim of integrating Ventoy into existing drives:

5.  Could Ventoy 'spoof' a version of windows (or linux) so that it could be recognised by subsequent installers (such as MX) and added to their grub menu? (the resulting menu entry could be changed later, eg: by grub customizer)
(this would allow other OS's to be installed after Ventoy without making Ventoy unbootable)

6.  Instead of always creating a new grub menu, perhaps Ventoy could have an option to add itself as an entry into an existing grub menu file if present?
(this would allow Ventoy to be safely installed AFTER other OS's)

7.  Ideally, could Ventoy offer 'discovery' of existing bootable partitions and add them into its Ventoy menu?
(this last feature would enable Ventoy to be added as a simple boot repair tool allowing non-booting OS's to be made bootable again from the Ventoy menu)

The ability to integrate with existing bootable drives, giving bootable access to all of Ventoy's ISO's as well as any previously installed bootable OS (or multiple OS's), would make Ventoy even more unique and powerful.


Thank you for your amazing creativity,
Robin.