Hi!

I'm trying to PXE boot into iVentoy from an HPE DL360 G6 and I keep on getting the red screen of death. As far as I can tell, everything is working correctly (meaning the server is getting an IP through DHCP from iVentoy and is able to communicate with it) until iVentoy serves the boot file which shows the list of bootable ISOs.

I'm not really sure where to begin debugging this so if anyone has any suggestions that would be great! Thanks!

iVentoy Logs:

   

Hello

Ventoy is a very good tool, but it would be excellent if it managed media in "advanced format", 4Kn (native 4K i.e. 4096 bytes for the size of the physical sectors, instead of 512 bytes) which is more than 12-year-old.

I had the problem with a JMicron 250GB USB SSD, it's quite frustrating.

"advanced format" (4Kn) is very common with recent SSD.

So, could you please record this ER ?
Is it a big workload ?
How long would it take to make a new release supporting 4Kn ?

I'd be happy to help by testing this new feature when ready.

Thanks.

VToy_Phan

Hi

iventoy 1.0.10 (like the preivous releases) does not start on my Thinkpad running Fedora 38:

When I'm trying to launch Ventoy GUI I got an error

• 2023/07/14 --- 1.0.11 release
  

1. Fix the bug that some kylin OS can not boot.
   
   
2. Since 1.0.11 release, iVentoy Free edition and Pro edition are provided separately. Only Free edition can be downloaded from the website.
   Pro edition will only be provided to the paid users.
   This change has no effect on Free edition users, and the difference between the Free edition and the Pro edition remains the same as before.
   
   
3. Bugfix, comments and suggestions are welcome.
   

First, I'd like to thank you for this PXE boot version ventoy. This is amazing! 

I want to host iventoy on a openwrt x86 system. I got the glibc, libevent2 and etc installed. But still no way to makes it run iventoy. I ldd it and find it has a libwim dependency. But somehow I see a topic about no intention for supporting wim boot. So is it possbile to remove this dependency? Or please kindly provide suggestions on how to resolve this. Thanks. Heres my ldd output. 

ldd iventoy
/lib64/ld-linux-x86-64.so.2 (0x7f26bc78c000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x7f26bc684000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x7f26bc67f000)
libevent-2.1.so.7 => /usr/lib/libevent-2.1.so.7 (0x7f26bc645000)
libevent_pthreads-2.1.so.7 => /usr/lib/libevent_pthreads-2.1.so.7 (0x7f26bc640000)
libdl.so.2 => /lib64/ld-linux-x86-64.so.2 (0x7f26bc78c000)
Error loading shared library libwim.so.15: No such file or directory (needed by iventoy)
libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f26bc78c000)
libevent_core-2.1.so.7 => /usr/lib/libevent_core-2.1.so.7 (0x7f26bc61c000)
Error relocating iventoy: wimlib_decompress: symbol not found
Error relocating iventoy: g_tree_node_value: symbol not found
Error relocating iventoy: wimlib_free_decompressor: symbol not found
Error relocating iventoy: g_tree_node_first: symbol not found
Error relocating iventoy: wimlib_create_decompressor: symbol not found
Error relocating iventoy: g_tree_node_next: symbol not found

First, thank you for this software, and for all of your hard work in improving it. I find it very useful. 

The problem I have is with the unattended scripts. If I add an iso to iVentoy and click refresh under image management it clears out all of my added scripts for the isos. Also since you rapidly release new versions, unattended scripts have to be readded with each release. 

After the second release I began to put my iso and scripts folder in the home folder and just create symbolic link in new releases to those folders. Would it be possible to have some kind of config file for the unattended scripts, similar to the json file we have in ventoy to help with this?

怎么添加WIM文件，从而实现和微软额MDT融合在一起使用。如何能和现有的WDS+MDT融合在一起？

Running iVentoy on Windows Server.

I tried the switches suggested for linux to autostart the program in a running state but they don't seem to do anything.

Is there a way to get this to autostart at login to a running state for PXE?

My end goal is to use NSSM to run this program as a service after every reboot without having to interact with the GUI to get it working.

Thanks!

I saw this version in the other thread, and now I have been able to boot both Kali Live iso, and Ubuntu 20.04 Desktop, but with MX Linux I still get: 

Fatal Error
Could not find file antiX/linuxfs 
       Searched devfices: /dev/nbd0
           Searched types: usb.cd
    All block devices: [ List of devices }

etc... 

p = power off
r = reboot