Hello,

   I have PXE boot working with iVentoy, but boot of SystemRescueCD fails because media isn't found after kernel load. I expected this because it's normal for the kernel to not have access to the PXE virtualized media after loading. I've solved this in other PXE environment by adding kernel parameters to point to HTTP location for media. In iVentoy, I tried to solve this with file injection, but there isn't enough documentation on the file injection feature to understand how or where in the boot process the injection happens. Is there a better way to get this ISO bootable over PXE with iVentoy?

It has been a few months since I gave up trying to get vtoys to work in eufi mode.
Software has updated since then so I thought I would try again. I created 6 different Linux distros following the instructions on the ventoy site. I created new virtual machines using virtual box.
EFI enable True, fixed disk.
Once the OS rebooted I ran the vtoyboot script. I then shut it down. Then copied the vdi to ventoy renaming the suffix to vdi.vtoy
Not a single one worked in eufi mode. All I get is an unblinking cursor at the top left of my screen.
I have tried this on a pure ventoy drive as well as ventoy on easy2boot with the same outcome.
5 of the 6 work fine in Legacy mode (kubuntu, Ubuntu,MX,fedora,Bodhi).
PopOS does not work in either but I was warned when running the vtoyboot script on Pop that it would only work in eufi.
The only reason I chose 6 was to hopefully get a couple that would work. I do not know what I am doing wrong.

Thanks in advance.

比如我在公司用 iventoy 搭一个服务器，配置好各种安装镜像和无人值守的脚本，给客户只要安装一个 ventoy，然后配置好客户那边的 ventoy（指定我的 iventoy 服务器地址）让它启动后在机器能连接外网的情况下直接通过访问 iventoy 服务器转入 PXE 启动流程，全过程不需要用户干预就能完成系统安装。

请问 ventoy 能实现这样的功能吗？

I have a problem when i try to boot PXE from Old PC with Legacy BIOS. I take this error message (image). 
I have used Extrernal Net settings because iVentoy server and the third-party DHCP Server are located in different LANs/VLAN.
I would like to inform you that if I use PC with UEFI all work ok. Could you help me?

Attached Files

Thumbnail(s)
   

I've tried adding the autounattend to both the root of the ventoy drive (have not tried the ventoy boot partition yet just the iso data partition) and the root of the DVD iso file.  Both methods work without using ventoy but fail when using ventoy.  Am I doing something wrong?  I have added Windows PE configuration pass settings and need the answer file to load with the boot environment.  Would loading a command prompt from within the windows PE environment and specifiying the answer file work if the answer file was on the ventoy data partition?  Tried searching the forum but looks like json editing is in order.  Is this correct?  Thanks in advance for any help.

1：服务器可以正常通过PXE安装操作系统；
2：台式机和笔记本不能正常安装，PC终端和服务器同一个网段，能正常获取DHCP信息，但是不能无法进入iventoy界面。

管理员，你好！

VTOY_LINUX_REMOUNT=1 当linux kernel 版本为6.5.0时不生效

ventoy版本 1.0.96,vtoyboot版本1.0.30

测试OS：ubuntu 23.10(kernel 6.5) 及 kali linux 2023.3  (kernel 6.5)。

当Linux启动后不能访问ISO文件所在的分区。

谢谢

I would like to use Ventoy to create digital toolbox, but I'm confused about partitions. Sometimes I would need to move files between Linux (booted using Ventoy) and Android/Windows 8 (separate machine), but I also need ability to install Windows from Ventoy.

If I would keep default exFAT filesystem for partition 1, I think I will be able to access files from Android/Windows 8 and install Windows, but will Ventoy-booted Linux be able to modify files on this partition? If not, do I have any other options?

I have a problem with (the newest) MX-Linux for x86-systems. It does not start, maybe does not find files.
For an old Laptop with 32bit-CPU I have downloaded the newest MX-ISO: MX-23.1_386.iso (from https://sourceforge.net/projects/mx-linu...o/download). Ventoy is the newest 1.0.96. Other ISOs - e.g. Knoppix, Linux Mint, AOMEI-backupper are starting.
I have tried on 1/2 dozend PC, and always the same: Depending on the CPU with or w/o the mandatory option/cheat "forcepae" and disabling "quiet" and enabling the boot-messages: After a lot of booting-messages and
"Loading hardware specific modules ..."
some red error-messages appeared, beginning with
"insmod: can´t insert '/ventoy /mnt/squashfs/lib/modules/6.1.0.13-686-pae/kernel/drivers/md/dm-mod.ko': unknown symbol in module or invalid parameter"
"/prog/misc: No entry for device-mapper found"
and ending with
"TYPE:"
"b Block device"
"c or u Character device"
"p Namend pipe (MAJOR and MINOR are ignored)"
Followed by the message
"Scan usb,cd devices. Look for boot file(s) antiX/linuxfs"
"Filtered devices /dev/mapper/ventoy /dev/sr0"
"Retry for 15 seconds "
and then
"Fatal error"
"Could not find file antiX/linuxfs"
"Searched devices: /dev/mapper/ventoy /dev/sr0"
"Searched types: usb,cd"
"All block devices: /devsr0 /dev/sda3 /dev/sda2 dev/sda1 /dev/sda"
Then it stops and gives the choice to shutdown or reboot.
No difference when testing with "modern" PC and the default start-command-line.
What is the problem, what can I do?
Edit: I have additional tested the previous version MX-21.3_386 and this is starting (in normal mode) and working.