| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 333 online users. » 0 Member(s) | 329 Guest(s) Baidu, Bing, Google, Yandex
|
| Latest Threads |
Plugson installation - no...
Forum: Ventoy Plugin Forum
Last Post: Themotte
07-11-2026, 06:23 PM
» Replies: 2
» Views: 259
|
安装Ventoy后U盘的Windows下面识别及其...
Forum: Ventoy Discussion Forum
Last Post: lain
07-10-2026, 08:04 AM
» Replies: 3
» Views: 3,120
|
[iPXE 2.0.0 regression] P...
Forum: iVentoy Discussion Forum
Last Post: matmus06
07-06-2026, 12:18 PM
» Replies: 2
» Views: 295
|
Auto Memdisk Plugin
Forum: Ventoy Discussion Forum
Last Post: jlsupremo
07-01-2026, 01:16 PM
» Replies: 2
» Views: 530
|
[SOLVED] iVentoy 1.0.36 -...
Forum: iVentoy Discussion Forum
Last Post: longpanda
07-01-2026, 10:05 AM
» Replies: 4
» Views: 759
|
Using ks script issues
Forum: iVentoy Discussion Forum
Last Post: longpanda
06-29-2026, 02:40 PM
» Replies: 2
» Views: 355
|
Comparison of Iventoy and...
Forum: iVentoy Discussion Forum
Last Post: crasadure
06-28-2026, 02:08 PM
» Replies: 7
» Views: 2,182
|
Ventoy Plugson bug
Forum: Ventoy Plugin Forum
Last Post: VadimChoi
06-25-2026, 03:38 PM
» Replies: 5
» Views: 854
|
Ventoy-1.1.15 release
Forum: Ventoy Discussion Forum
Last Post: Epictetus77
06-25-2026, 12:03 PM
» Replies: 2
» Views: 1,046
|
Ventoy-1.1.14 release
Forum: Ventoy Discussion Forum
Last Post: pete
06-25-2026, 03:10 AM
» Replies: 5
» Views: 1,262
|
|
|
| Original Windows 10 21H2 ISOs based on "install.wim" do not work in UEFI mode(SB off) |
|
Posted by: JJJKKK - 05-03-2022, 09:34 AM - Forum: Ventoy Discussion Forum
- Replies (1)
|
 |
Original Windows 10 21H2 ISOs do not work in UEFI mode(secure boot disabled), if they are based on the uncompressed install.wim. This includes updated ISOs from MSDN(see examples below) and the ones that Rufus downloads(vanilla RTM 21H2 from November). On the other hand, ISOs based on the compressed install.esd, like the ones that the "Media Creation Tool" creates, work just fine. Tested on an older Gigabyte Z77 and on a new Asus B560. Result is a blinking cursor above the blue Windows logo, and that's it.
Examples of ISOs that don't work: - en-us_windows_10_consumer_editions_version_21h2_updated_april_2022_x64_dvd_a545527b.iso
- en-us_windows_10_business_editions_version_21h2_updated_april_2022_x64_dvd_38bad9d1.iso
- en-us_windows_10_consumer_editions_version_21h2_updated_march_2022_x64_dvd_86f47135.iso
Thank you, Sir!
|
|
|
| Problem with EasyOS |
|
Posted by: pzeta - 05-02-2022, 06:48 AM - Forum: Ventoy Discussion Forum
- Replies (4)
|
 |
I tested EasyOS 3.4.1 with Ventoy and it was OK, no problem.
Today I've tested EasyOS 3.4.7, but it does not boot and give an error and a Kernel Panic.
erro: file '/lib/modules/5.15.35/kernel/drivers/dax/dax.ko' not found.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I tested on two different systems, on ACER EeePC 1015CX, 320 GB HDD and 2 GB ram and on
HP Z220 Workstation 128 GB SSD and 1 TB HDD, 16 GB ram.
To test I used Verbatim Store'n'Go 8 GB and Kingston DataTraveler 100 G3 32GB.
I also verify that the problem appears with version 3.4.3 and is present in version 3.4.4, 3.4.5, 3.4.6, 3.4.7 of EasyOS.
I use Ventoy version 1.0.74.
Writing EasyOS-3.4.7-amd64.img on the same key using Win32DiskImager-1.0.0-binary run OK.
|
|
|
| [Feature suggestion ] Update Ventoy version Automaticly over internet |
|
Posted by: crasadure - 04-30-2022, 01:50 AM - Forum: Ventoy Discussion Forum
- No Replies
|
 |
Hi @ventoy
With the ventoy Update button in the ventoy2disk.exe file, we can manually update our current system to a higher version. How about we make the update process automatically update Ventoy to a higher version by putting an Auto Update button on the interface?
When a new version of Ventoy comes out, it should ask the user if you want to update to the new version. When the Update button is pressed, the system will automatically update the VTOYEFI section over the internet in the background.
In this way, those who want can update their system manually, and those who want can update it automatically over the internet.
|
|
|
How to find the flash drive in GRUB for a cat command? |
|
Posted by: grizzogor - 04-29-2022, 07:05 PM - Forum: Ventoy Discussion Forum
- Replies (2)
|
 |
Hi, I'm using Ventoy for a new recovery disk at my workplace's IT department.
On the extra GRUB menu (/ventoy/ventoy_grub.cfg), I have a menu item that runs a cat command to display what software versions are used on the disk. Currently the menu item entry is programmed like this: (some parts I've pulled from Ventoy's other partition under Linux, like vtInputKey)
Code: menuentry 'Read VERSIONS.txt' --class=F5tool {
cat (hd0,gpt1)/VERSIONS.txt
echo -e "\nPress ENTER to exit..."
read vtInputKey
}
This works on a majority of machines I've tested, a Microsoft Surface Pro 6, a VMware VM, and an HP envy laptop of unknown model. But on some machines, GRUB can't find the file listed. I theorize that the exFAT partition is mounted at a different path depending on the computer's configuration.
Is there a way to figure out where the exFAT partition is mounted, so that the cat command would work every time?
Thanks.
|
|
|
| Problem With Two Monitors |
|
Posted by: Starkebogen - 04-29-2022, 06:32 AM - Forum: Ventoy Discussion Forum
- Replies (2)
|
 |
I started using Ventoy about two weeks ago. It has already been a great help to me. I built a Windows 10 Ventoy USB drive and added Hiren’s BootCD PE to it. This worked well on my two Windows 10 PCs (a desktop with two monitors and a laptop). It also worked on a friend’s PC.
About a week later I added the EaseUS Recovery iso to the Ventoy drive. On the desktop the new iso would not load and caused the system to hang. On the laptop it launched and ran successfully.
Over the next 24 hours I added two more iso files to the Ventoy drive: AOMEI PE and Macrium Reflect Rescue.
All the iso files operated successfully on the laptop, but on the desktop the iso file that is second alphabetically will not run. N.B. Changing the name of the problem iso file so that another file is second alphabetically transfers the problem to the file that is now second alphabetically. I suspect that the second monitor is the cause of the problem.
Has anyone else experienced this problem? Does anyone have any advice?
|
|
|
| How to boot of a third btrfs partion on a usb drive |
|
Posted by: wolf2482#1639 - 04-25-2022, 02:04 AM - Forum: Ventoy Discussion Forum
- No Replies
|
 |
Ok I was wondering how could I install arch linux on to a third btrfs partion and have that as a boot option I assume it is possible because Ventoy uses grub but I don't know how. could anyone tell me what changes in the arch install process I would have to do. I have never messed with grub before so and I struggled installing on my pc and once I got it to work I have no idea why it worked. So anyway what resources would be useful for me to do this?
|
|
|
| Linux updating shell script |
|
Posted by: johnca - 04-21-2022, 08:30 PM - Forum: Ventoy Discussion Forum
- No Replies
|
 |
Hello everyone.
Could we update the main scrip for terminal execution?
old scrip
Code: #!/bin/sh
OLDDIR=$(pwd)
if ! [ -f ./tool/ventoy_lib.sh ]; then
if [ -f ${0%Ventoy2Disk.sh}/tool/ventoy_lib.sh ]; then
cd ${0%Ventoy2Disk.sh}
fi
fi
if [ -f ./ventoy/version ]; then
curver=$(cat ./ventoy/version)
fi
if uname -m | egrep -q 'aarch64|arm64'; then
export TOOLDIR=aarch64
elif uname -m | egrep -q 'x86_64|amd64'; then
export TOOLDIR=x86_64
elif uname -m | egrep -q 'mips64'; then
export TOOLDIR=mips64el
else
export TOOLDIR=i386
fi
export PATH="./tool/$TOOLDIR:$PATH"
echo ''
echo '**********************************************'
echo " Ventoy: $curver $TOOLDIR"
echo " longpanda admin@ventoy.net"
echo " https://www.ventoy.net"
echo '**********************************************'
echo ''
if ! [ -f ./boot/boot.img ]; then
if [ -d ./grub ]; then
echo "Don't run Ventoy2Disk.sh here, please download the released install package, and run the script in it."
else
echo "Please run under the correct directory!"
fi
exit 1
fi
echo "############# Ventoy2Disk $* [$TOOLDIR] ################" >> ./log.txt
date >> ./log.txt
#decompress tool
echo "decompress tools" >> ./log.txt
cd ./tool/$TOOLDIR
ls *.xz > /dev/null 2>&1
if [ $? -eq 0 ]; then
[ -f ./xzcat ] && chmod +x ./xzcat
for file in $(ls *.xz); do
echo "decompress $file" >> ./log.txt
xzcat $file > ${file%.xz}
[ -f ./${file%.xz} ] && chmod +x ./${file%.xz}
[ -f ./$file ] && rm -f ./$file
done
fi
cd ../../
chmod +x -R ./tool/$TOOLDIR
if [ -f /bin/bash ]; then
/bin/bash ./tool/VentoyWorker.sh $*
else
ash ./tool/VentoyWorker.sh $*
fi
if [ -n "$OLDDIR" ]; then
CURDIR=$(pwd)
if [ "$CURDIR" != "$OLDDIR" ]; then
cd "$OLDDIR"
fi
fi
new scrip
Code: #!/bin/sh
OLDDIR=$(pwd)
if ! [ -f ./tool/ventoy_lib.sh ]; then
if [ -f ${0%Ventoy2Disk.sh}/tool/ventoy_lib.sh ]; then
cd ${0%Ventoy2Disk.sh}
fi
fi
if [ -f ./ventoy/version ]; then
curver=$(cat ./ventoy/version)
fi
if uname -m | egrep -q 'aarch64|arm64'; then
export TOOLDIR=aarch64
elif uname -m | egrep -q 'x86_64|amd64'; then
export TOOLDIR=x86_64
elif uname -m | egrep -q 'mips64'; then
export TOOLDIR=mips64el
else
export TOOLDIR=i386
fi
export PATH="./tool/$TOOLDIR:$PATH"
echo \
"
**********************************************
Ventoy: $curver $TOOLDIR
longpanda admin@ventoy.net
https://www.ventoy.net
**********************************************
$(lsblk)
==============================================
run: umount /dev/sdX*
if necesary
"
if ! [ -f ./boot/boot.img ]; then
if [ -d ./grub ]; then
echo "Don't run Ventoy2Disk.sh here, please download the released install package, and run the script in it."
else
echo "Please run under the correct directory!"
fi
exit 1
fi
echo "############# Ventoy2Disk $* [$TOOLDIR] ################" >> ./log.txt
date >> ./log.txt
#decompress tool
echo "decompress tools" >> ./log.txt
cd ./tool/$TOOLDIR
ls *.xz > /dev/null 2>&1
if [ $? -eq 0 ]; then
[ -f ./xzcat ] && chmod +x ./xzcat
for file in $(ls *.xz); do
echo "decompress $file" >> ./log.txt
xzcat $file > ${file%.xz}
[ -f ./${file%.xz} ] && chmod +x ./${file%.xz}
[ -f ./$file ] && rm -f ./$file
done
fi
cd ../../
chmod +x -R ./tool/$TOOLDIR
if [ -f /bin/bash ]; then
/bin/bash ./tool/VentoyWorker.sh $*
else
ash ./tool/VentoyWorker.sh $*
fi
if [ -n "$OLDDIR" ]; then
CURDIR=$(pwd)
if [ "$CURDIR" != "$OLDDIR" ]; then
cd "$OLDDIR"
fi
fi
|
|
|
|