Hi

Trying to extend persistence size by ExtendPersistentImg.sh, command ends in error as given below:

pop-os@pop-os:~/Downloads$ sudo bash ExtendPersistentImg.sh persistence_pop-os_osint.dat 16384

persistence_pop-os_osint.dat not exist.

Also, tried giving full pathname to the persistence file.

Thanks
Neo

How to fix? iVentoy VM pxe boot artefact on VNC viwer

Attached Files

Thumbnail(s)
   

1.0.18 httpdisk 找不到网络的问题还存在，好像比1.0.17更严重，一些1.0.17可以正常的主机，在1.0.18就不行了

New user here, so i may be unaware of how this forum works.
I was wondering if anyone knows of any possible reason why VentoyPlugson would open a non-default browser? My current default browser is Brave but when i click "Start", it opens Firefox instead. Clicking "Link" does the same thing. But on Ventoy2Disk.exe, opening links opens in Brave. Im on version 1.0.94.

• 2023/08/13 --- 1.0.18 release
  

1. Fix a bug about CentOS boot failure (introduced since 1.0.15)
   
   
2. Fix a bug that iVentoy can not start if the machine has only 1 cpu core.
   
   
3. Bugfix, comments and suggestions are welcome.
   

Hi there.

I am working on some translations for Ventoy, and I stumbled across this sentence:
"Communication error: remote abnormal"

I don't think I've seen this error before, and I was just curious as to what the context is for this error.
As it stands, I am not quite sure how to translate it.

Is it an input error in terms of a remote host? Incompability?

Thanks!

可信吗？360报木马

Attached Files

Thumbnail(s)
   

Iventoy works flawlessly in BIOS mode with this specific mainboard (gigabyte ga-b75m-hd3)
But when i try to boot in IPXE mode, screen freezes with the message:  iPXE initialising devices.
Switching the DHCP mode to external / externalNet still crashes. with the message: Start PXE over IPv4
-Logs file attached. for the internal and external dhcp boot modes
-Screenshots with with the messages on screen:




internal dhcp mode:








external dhcp mode:










Iventoy 1.0.17
Thank you!

Attached Files

  logs.zip (Size: 7.42 KB / Downloads: 0)

Hi all,

I have an Iventoy server running on 1.0.17 and it is working. I already successfully managed to deploy Windows 11 with and without unattend.xml answer files.

The Problem:
However, on some machines when trying to deploy either Windows 11 21H2 or 22H2, after PXE started the setup, setup claims there is no disk to be found due to a "missing driver".
The hardware to deploy to is an Asus X570 Prime and the SSD is a SATA Samsung Evo 850 1TB drive.

I have tried various options in Bios, such as enabling/disabling CSM compatibility, etc.

The weird part:
Funnily enough: the C: partition (there is an active NTFS partition on the drive with data) is even being shown during setup when you select "browse" to supply a driver for the system, so it clearly DOES see the drive.
Using the console with Shift+F10 during Windows setup I can use diskpart and it shows the drive correctly.

Just Windows setup will not accept this disk to install to and it claims there is no disk in the system.

When I run Windows 11 setup via USB stick, this error does not occur and it will detect the disk and its partitions correctly during setup -- as expected. While some exotic drivers, esp. for Raid, are sometimes to be supplied, I haven't ever had to supply a driver since Windows 10 for simple storage devices.

The question(s):
Has anyone run into a similar issue or did I miss a critical piece of documentation?

I'd be grateful for any pointers as I am stuck on this issue for 2 days straight.

---
My plan for tomorrow is to get an M2 SSD and see if the SATA makes a difference.
Maybe also try to get a newer Bios.

But that's currently all I can think of. :/

Hello everyone ? How are you ?
Why booting (Windows 8.1, Windows 10, Windows 11) ISOs in ventoy is slow takes 2-3 minutes to boot while Booting (Windows 7)ISO is so fast to boot
I made bootable usb and Hdd hard drive installed ventoy on it
is due to old bios board ? is there any way to boot (Windows 8.1, Windows 10, Windows 11) ISOs faster