I have an Intel NUC that refuses to boot iVentoy unless the boot menu resolution is set to 800x600. However, if I set the resolution that low, then every WinPE .iso I boot has a garbled display after the Windows boot logo, so I still can't get it to work. When I try higher resolutions I get errors like attached. Any ideas?
I used the guide on how to install this using windows and all methods in "When Ventoy2Disk.exe Failed To Install" worked except the VM which just stagnated on the loading screen. However when I installed the program to install ventoy gpt or mbr it always failed to install to my 1tb usb 3 generic flash drive gpt or mbr
I think this is a problem with Windows 10 ISOs.
httpdrive cant mount iso to drive y: - because of the problem with the ip configuration.
The problem does not exist on Windows 11 isos.
The iVentoy system can be reached via ping and the manual mounting of the ISO works in the recovery console of Windows Setup. I also can access drive y:
X:\windows\System32\ventoy\httpdisk.exe /mount 0 http://192.168.50.2:16000/riso/id/13.iso /cd Y:
I it possible to change your script for this configuration to wait some more time for configuration?
I already tried it with WinInjection but without solution.
IPv4-Adresse . . . . . . . . . . : 192.168.50.82(Vorläufig) or IPv4-address . . . . . . . . . . : 192.168.50.82(Tentative)
Says that a conflict check is currently being running and that probably takes too long for your script (no wait times)
(see last entrys in the log)
Here is the log file (its a german system)
==========================
[...]
Try 18 ...
X:\windows\system32>ipconfig /all
Pinging 192.168.50.2 with 32 bytes of data:
PING: Error during transmission. General error.
Ping-Statistik f r 192.168.50.2:
Pakete: Gesendet = 1, Empfangen = 0, Verloren = 1
(100% Verlust),
X:\windows\system32>if 1 EQU 0 goto NETFINISH
X:\windows\system32>goto START_LOOP
X:\windows\system32>if 20 EQU 20 goto END_LOOP
X:\windows\system32>if 20 EQU 20 goto NETFINISH
X:\windows\system32>X:\windows\System32\ventoy\httpdisk.exe /mount 0 http://192.168.50.2:16000/riso/id/13.iso /cd Y:
HttpDisk: The network address is not reachable. For more information about troubleshooting network problems, see Windows Help.
X:\windows\system32>if exist Y: (echo httpdisk mount OK ) else (echo httpdisk mount FAILED )
httpdisk mount FAILED
Basically that's a Batch Script loaded via winpeshl.ini asking for user input.
Which works really well when the iso is loaded via USB (both plain USB or classic Ventoy). However, when loading the same iso via iVentoy it seems to be ignored / skipped and goes straight to the auto installer part.
I also tried via injection, but it's the same (though I can see in the log that VentoyAutoRun.bat is being executed, but no Shell window opens).
Host OS for iVentoy: openSUSE Linux
Version 1.0.18 Pro Edition
ISO: Windows 11 22h2
My dear illustrious Leaders and Senior Members of Ventoy,
I have used Ventoy to boot several Live ISOs and am really impressed by its performance. I am a new member to the ventoy forums, having registered only yesterday.
Having used Knoppix since 2007 and being enamoured by the System, I gradually learnt to boot from the Live ISO and also have a persistent set up, that is, I could add or remove packages and data from the system, using another partition to save the files required for the altered set up. I works wonderfully for me still.
My only problem is that the leaders I knew and interacted with are no longer active. They were very aged already, so I fear for the worst. It appears that none has taken up the project from Prof. Klaus Knopper, which is really sad. The forum is no longer as active as it was.
This persistence of Knoppix (or puppy Linux) never fails to amaze me. If Ventoy could support booting from a Live ISO, it could perhaps also help with persistence using another HDD partition for such persistence, like knoppix did.
I have a couple of posts in the Knoppix forums that has this idea of persistence captured.
The most important file for using persistent in Knoppix:
knoppix-data.inf
with one line within the file:
3 /KNOPPIX-DATA ext4
Assume that the knoppix iso is extracted in the ext4 partition /dev/sda2 and persistent is planned to be in the ext4 partition /dev/sda3 within a directory /KNOPPIX-DATA. I will quote from the aforesaid post:
Quote:If you want to use your ext4 partition (guessing it's /dev/sda3) as persistent storage for Knoppix, you must create a file /dev/sda2/KNOPPIX/knoppix-data.inf with this content:
Code:
3 /KNOPPIX-DATA ext4
This tells Knoppix to mount partition 3 on this hard disk on mountpoint /KNOPPIX-DATA as an ext4 file system. ...
The above post in knoppix forum and the other: http://knoppix.net/forum/threads/31412-s...lash-Drive
helps in setting up a persistent drive with the ISO as the base. The set up makes the system very very fast in comparison to the usual HDD set up.
The following page could be looked into regarding steps to prepare for creating such ISO CD: Knoppix Remastering Howto
I am sure that this adventure would be embarked upon for any Live ISO.
Best wishes,
Rajib
An FSF and a GNU-Linux enthusiast
I post as rajibando in Knoppix forums and bkpsusmitaa in the Debian forums and MLs
