Ventoy Download Old Version
Kristee Summerford
With Ventoy, you don't need to format the disk again and again, you just need to copy the iso file to the USB drive and boot it. You can copy many iso files at a time and ventoy will give you a boot menu to select them. Both Legacy BIOS and UEFI are supported in the same way. 420+ ISO files are tested. A "Ventoy Compatible" concept is introduced by ventoy, which can help to support any ISO file.
You can see some sample configuration files in the \ventoy\Sample Ventoy config files folder on Partition 2. These can be copied to the \ventoy folder on Partition 1 (the NTFS partition).
Hi,
I'm the developer of Ventoy (www.ventoy.net). I add support to OpenWrt in the latest release.
So we can just copy the OpenWrt img file to the USB stick and boot it through Ventoy.
But Ventoy needs the dm-mod module which is not included in the img by default.
So I have to provide a package to collect dm-mod file for all the versions. ( )
In the new release I will check the img file to check that whether the needed kernel modules are included already. If so then will NOT check the ventoy_openwrt.xz.
For test you can download the current ventoy_openwrt.xz to the USB and boot your img file even you have included the modules in the img file.
Ohh.
After you install Ventoy to the USB. The 1st partition is empty.
You need to create a ventoy directory and download the ventoy_openwrt.xz file and put it under the ventoy directory. Then you put the openwrt img file to the same partition and boot it.
There is nothing about the json file. I just mention the ventoy.json to say where to put the ventoy_openwrt.xz file.
download ventoy_openwrt.xz file from
ventoy is MOUNTING the image and then booting (so a virtual usb stick ).
That virtual stick is in case of easy-3.4.7-amd64.img 1,3G and will not grow (as ventory and easy is not made for that).
If you make the image itself bigger by say 2G before first boot , then easy can grow the second partition by 2G and have space to copy the sfs file.
For the time being, I'm just going to use the Easy 3.4.7 I have on the independent USB, not on the Ventoy multiboot USB. I'm carrying on my 'campaign' on the Ventoy forum in the Ventoy forum thread that solved the dax problem w/ the ventoy CI tweak. Ventoy currently thinks the Easy problem is solved, but it is not; I'm addressing that.
Part of the reason I'm posting about this in the ventoy forum is to correct some misinformation there. Ventoy has a high success rate, but it isn't 100% and there is a table which lists those distro/s which don't work along w/ those which do.
For example, on my machine, I ran:
sudo ventoy -I /dev/sda -r 50000
Which installed ventoy with 3 partitions: The normal ventoy partition, the hidden 30mb ventoy partition, and 50gb of unallocated space at the end.
Then, create a new folder called ventoy
Unzip the ventoy_vhdboot.zip file you downloaded, and locate the .img file (ventoy_vhtboot.img)
Copy the ventoy_vhdboot.img into this folder.
Make a new text file named ventoy_grub.cfg and also place it in the ventoy folder, with these contents:
Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. Both Legacy BIOS and UEFI are supported in the same way. Most type of OS supported (Windows/WinPE/Linux/Unix/Vmware/Xen...)
Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)/EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. You can also browse ISO/WIM/IMG/VHD(x)/EFI files in local disks and boot them. x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI and MIPS64EL UEFI are supported in the same way. Most types of OS supported (Windows/WinPE/Linux/ChromeOS/Unix/VMware/Xen...)
When Ventoy loads a Windows ISO, it injects code into the X: boot image which automatically loads the ISO as a virtual DVD. This allows Windows Setup to access the \Sources\Install.wim or Install.esd file. Vtoyjump32.exe and Vtoyjump64.exe (located in the \ventoy folder of the VTOYEFI 32MB partition) are responsible for this.
The Visual Studio C code in Ventoy-master\vtoyjump\vtoyjump\vtoyjump.c will check for a ventoy grub2 bootloader in the LBA0 of each disk. If the MBR boot code in your USB drive is not the official Ventoy code then you will need to edit the vtoyjump.c file and then recompile both .exe files:
4. If you wish to re-pack the Ventoy download zip file, then copy the vtoyjump32.exe and vtoyjump64.exe files into the CentOS VM at .\Ventoy-master\INSTALL\ventoy. Then run the all_in_one.sh script (or maybe just the ventoy_pack.sh script if you have already compiled) to make a new ventoy-1.00.xx-windows.zip file.
The Windows app for configuring the ventoy.json file is VentoyPlugson.exe and it checks for a Ventoy drive. The Partition 1 must start at sector 2048 and it also checks the MBR boot code to make sure it is a Ventoy drive.
Ventoy is available for both Linux and Windows. On Linux, however, the program is currently only available in Arch Linux and its Manjaro derivative. Ventoy is found in the Arch User Repository (AUR). To install, you will therefore need to use an AUR helper like Yay, where you load the program into your system by typing yay -S ventoy.
For other distributions, use the release packages provided by the developers [2]. To install, download the ventoy--linux.tar.gz archive from the project's GitHub page, unpack the tarball, and then run the ./Ventoy2Disk.sh command. Ventoy shows the structure of its syntax and an explanation of the individual parameters. Listing 1 shows the process for the 1.0.18 version, current at the time of writing.
The Ventoy installation routine now automatically partitions the disk. A small partition is used by the boot manager to start the system; you cannot and never should change anything here. The program searches for ISO images on the partition labeled ventoy and formatted with exFAT. It does not matter how you organize the images there. You can move the ISO files directly into the root folder or organize them in subfolders. The only conditions are that the file names can only contain ASCII characters and spaces can't be used.
i did not know ventoy before. I gave it a try and played arround with that tool. Very nice!
Such a simple way for running iso bootable things. I tried with Service Pack Proliant and a lot of other iso's i have. All boot up wonderful. Thank you for that nice tool tip
hi, i use ventoy as bootloader on my computer, then use configfile (grub command) to load nixos grub menu. it is succes, i can enter to nixos grub menu from ventoy.
my problem is, with that schema i cant use OS prober on nixos. help me to create the configuration.nix
this is my configuration.nix
1.) i have some live iso file that i use daily so i need ventoy as bootloader.
if i use virtualbox it too heavy for my computer, only 2 core cpu, 2gb ram.
if i use flashdisk it too slow, only usb v2 port.
If you want to upgrade the ventoy version (e.g. to support more images), it is the same procedure as installing. Just run the installer and upgrade. The operation is stated as safe, your data partition will not be changed, but I still would recommend to backup your files, just in case something goes wrong
As opposed to recreating a new ISO with the unattend file inside, this only involved importing the .xml file into a directory within the USB specified in the ventoy.json config and pairing it to the desired .iso image. Very straightforward and, in all honesty, much easier than the standard method which apparently doesn't work well in tandem with Ventoy.
760c119bf3