Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 315 online users. » 0 Member(s) | 312 Guest(s) Bing, Google, Yandex
|
Latest Threads |
Marking up an NTFS or exF...
Forum: Ventoy Discussion Forum
Last Post: Steve2926
08-03-2025, 07:55 AM
» Replies: 1
» Views: 311
|
Subdirectories in Part 1 ...
Forum: Ventoy Discussion Forum
Last Post: VentoyMic
08-02-2025, 04:18 PM
» Replies: 1
» Views: 247
|
还是希望能有支持国芯架构的安排吧。
Forum: Ventoy Discussion Forum
Last Post: lizhuojian
08-02-2025, 01:55 PM
» Replies: 2
» Views: 1,933
|
Ventoy enroll key manager...
Forum: Ventoy Discussion Forum
Last Post: GlenTech83
08-01-2025, 01:11 PM
» Replies: 27
» Views: 39,776
|
Failure to boot into USB ...
Forum: Ventoy Discussion Forum
Last Post: BKPB
07-31-2025, 03:45 PM
» Replies: 4
» Views: 64,707
|
Updating Windows on vhd i...
Forum: Ventoy Plugin Forum
Last Post: pioj
07-28-2025, 03:27 PM
» Replies: 1
» Views: 796
|
Acronis iso will not load...
Forum: Ventoy Discussion Forum
Last Post: Epictetus
07-24-2025, 12:14 AM
» Replies: 6
» Views: 1,447
|
Ventoy is genius!
Forum: Ventoy Discussion Forum
Last Post: tenshikohaku
07-17-2025, 03:45 AM
» Replies: 1
» Views: 1,432
|
Ventoy的QQ群 945752978 什么时候...
Forum: Ventoy Discussion Forum
Last Post: alcy
07-11-2025, 06:18 PM
» Replies: 0
» Views: 410
|
iso not working HP SSA Of...
Forum: Ventoy Discussion Forum
Last Post: Steve2926
07-01-2025, 03:12 PM
» Replies: 1
» Views: 676
|
|
|
My work around for Windows installer driver issue |
Posted by: markadms - 07-28-2023, 05:45 PM - Forum: iVentoy Discussion Forum
- No Replies
|
 |
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.
|
|
|
Directory listings is messed up |
Posted by: Boelie - 07-26-2023, 12:20 PM - Forum: iVentoy Discussion Forum
- No Replies
|
 |
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.
|
|
|
Support for IA32 PXE client |
Posted by: iventoy_user - 07-25-2023, 12:05 AM - Forum: iVentoy Discussion Forum
- Replies (3)
|
 |
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.
|
|
|
|