Hello!
I'm trying to boot VMware VM prepared for Windows 10 and getting error on VM (in attach). It appears for some seconds and than vm enters bios.
VM setup:

• Guest OS:Microsoft Windows 10 (64-bit)
  
  
• Compatibility:ESXi 6.7 Update 2 and later (VM version 15)
  

   

Always to the right, how do i make it automatically align to center along with other elements too?

This is the theme.txt file > 
  theme.txt (Size: 1.06 KB / Downloads: 5)

This is a Graphite GTK Theme.

My screen size is 1366x768.

   

I try to boot with Ventoy the resolution is like this, does not display to my full screen 1920x1080.

How do I fix it? Please, help.

@longpanda:
Please send a documentation or a help file how to use the EFI boot files snponly.efi, snp.efi and ipxe.efi, thank you.

I had a computer that had this issue with storage drivers not being found because of missing NIC drivers mentioned in the iventoy documentation. I knew the issue was the NIC driver, because if I connected a USB ethernet adapter the install would go through fine. 

What I did was get a sergei strelec iso and go into \SSTR\DriverPacks\NETWORKDRIVER. Inside that folder are two more folders: NT6x32 and NTx64, and inside those folders are .7z files. I unzipped each of those files (I only used x64 drivers) and used dism to push those drivers into the boot.wim of my windows installer iso. The boot.wim contains two wimfiles. Index 1 is WinPE and Index 2 is Windows Setup. I mounted each of these wims and used the dism /add-driver command to push the drivers into them. I don't know if both needed it, but I didn't want to take the extra time to test each one separately. 

I also put the graphics drivers from sergei strelec, which seems to have fixed the Windows installer still showing "fuzzy" screen with a resolution that is supported by my monitor, and works with sergei strelec, but not installer.

Then I put the boot.wim back into my iso, resaved and and put it back on the iventoy server. 

I tried adding the driver folders to a zip file and use iventoy injection, but there must be something wrong with the way I did it or something, because it didn't work, and for some reason the x:\windows\system32\ventoy\vtoype.log was empty so I couldn't figure out why it was failing.

I am having the issue with getting the driver missing error. I am getting an IPv4 address and the boot management screen is showing the correct MAC address for the machine. I have downloaded and attempted to boot from a new ISO file. I have verified that everything is connected as it should be and I have been able to install on a few machines, but suddenly I have this issue. I ran type X:\Windows\System32\ventoy\vtoype.log      . I have found that for some reason if I manually run 
X:\Windows\System32\ventoy\httpdisk.exe /mount 0 http://10.10.200.10:16000/riso/id/1.iso /cd Y:  it will work. Why is it suddenly happening like this?

Hello,

When opening the website http://ventoypc:16000/user (or iso) I get directory listings for all files and folder underneath. I notice the files have all wrong link refrences pointed to it. This breaks linux wget to obtain the files.

Is this for everone or did I mess this up? All paths to filenames have their directories replaced with the filename. No link works.

I tried to install this theme: Graphite grub2 theme - pling.com by copying necessary files for the theme like theme-1080p.txt and fonts and icons to theme folder. 

My other themes work fine, but when I select this theme, I get the error. Here are my files:

   


  theme.txt (Size: 1.06 KB / Downloads: 2)

Edit: I forgot to add more assets like viewbox.png etc. 

Hello.

I'm trying to run iVentoy on Raspberry Pi OS Desktop 11 and an error appears, on Debian 12 it's normal, no errors. My goal is run iVentoy on Raspberry Pi OS Lite using a Raspberry Pi 4.
Note: I used chmod 777 on the iVentoy folder in both versions



Any tips to solve the problem in Raspberry Pi OS Desktop?

EDIT: Just a note, I'm not familiar with Linux, just the basics.

Hi,

Thank you so much for this tool.

I want to know if this tool supports IA32 PXE client -- meaning, I have IA32 (32-bit Intel CPU) machines/laptops that need to be PXE-booted to discover/test hardware or install OS. 

So, first I tried using Linux version of iVentoy. The client hung after receiving ipxe.bios.0 boot file. I thought, Linux version (64-bit) might be sending 64-bit boot file; so, it makes sense why it would not work. (Note: 64-bit PXE/CPU client booted fine.)

Then, I tried Windows 32-bit iVentoy - thinking that it would send 32-bit ipxe.bio.0. But I encountered the same problem.

So, I suspect that iVentoy only supports 64-bit PXE clients - meaning, irrespective which version of iVentoy software you use (IA32 or x64), ipxe.bios.0 is 64-bit code.

Can you please confirm? If I am correct, I request to support 32-bit PXE client from all iVentoy versions -- especially Linux.

Thank you again.