| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 13,633
» Latest member: joejames
» Forum threads: 1,672
» Forum posts: 6,720
Full Statistics
|
| Online Users |
There are currently 384 online users. » 0 Member(s) | 379 Guest(s) Applebot, Baidu, Bing, Google, Internet Archive
|
| Latest Threads |
Ventoy Linux still does n...
Forum: Ventoy Discussion Forum
Last Post: bahaedin
10-24-2025, 10:05 AM
» Replies: 1
» Views: 344
|
Ventoy installation for o...
Forum: Ventoy Discussion Forum
Last Post: FroggieTheGremlin
10-23-2025, 01:09 PM
» Replies: 5
» Views: 511
|
Screen Resolution 800x600
Forum: Ventoy Discussion Forum
Last Post: fan_boy
10-20-2025, 08:32 PM
» Replies: 0
» Views: 224
|
Issues with windows vista...
Forum: Ventoy Discussion Forum
Last Post: johnson
10-19-2025, 04:10 PM
» Replies: 4
» Views: 10,813
|
Help $OEM$
Forum: Ventoy Discussion Forum
Last Post: venster
10-04-2025, 03:18 PM
» Replies: 2
» Views: 6,317
|
iso not working HP SSA Of...
Forum: Ventoy Discussion Forum
Last Post: rjc862003
09-30-2025, 02:02 AM
» Replies: 2
» Views: 8,636
|
Lost ISO partition
Forum: Ventoy Discussion Forum
Last Post: abba
09-29-2025, 12:05 PM
» Replies: 0
» Views: 995
|
Remove Version Number
Forum: Ventoy Discussion Forum
Last Post: XxJourdanYxX
09-26-2025, 06:42 AM
» Replies: 2
» Views: 9,241
|
Install Ventoy with a dat...
Forum: Ventoy Discussion Forum
Last Post: odie
09-25-2025, 03:14 PM
» Replies: 0
» Views: 1,379
|
big discussion on OpenSUS...
Forum: Ventoy Discussion Forum
Last Post: Dutchglory
09-21-2025, 12:44 AM
» Replies: 0
» Views: 2,858
|
|
|
| Problem with an old PC |
|
Posted by: Nari - 08-02-2023, 01:49 PM - Forum: iVentoy Discussion Forum
- Replies (5)
|
 |
H!
I'm testing iVentoy (Version 1.0.17 Linux 64-bit) with my two old PCs. Both have Gigabyte motherboards and Realtek NICs.
1st one (newer with Core 2 Duo CPU) has Intel UNDI, PXE-2.1 (build 083) and is able to boot fine.
2nd one (older with Athlon 64 CPU) has Intel UNDI, PXE-2.1 (build 082) and is unable to boot (PXE-E32: TFTP open timeout).
Both PCs are on the same network and I'm using the "External" DHCP Server Mode (DHCP is working fine on the 2nd PC). iVentoy only lists the 1st one in Boot Information.
Any ideas why the 2nd PC is not working?
|
|
|
| Recv an ERROR opcode pkt from client when boot VM |
|
Posted by: Endless-Pony - 08-01-2023, 07:41 AM - Forum: iVentoy Discussion Forum
- No Replies
|
 |
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)
In iVentoy log i see
Code: 2023/07/31 18:36:40.879 [HTTP] HTTP PXE service is running on 172.31.10.11:16000 ...
2023/07/31 18:36:40.883 [TFTP] TFTP write thread is running 1660 ...
2023/07/31 18:36:40.884 [TFTP] TFTP service is running ...
2023/07/31 18:36:40.885 [DHCP] DHCP service is running ...
2023/07/31 18:36:40.886 [HTTP] NBD service is running on 172.31.10.11:10809 ...
2023/07/31 18:36:41.374 [HTTP] API request: <{"method":"query_status"}>
2023/07/31 18:36:41.403 [HTTP] API request: <{"method":"sys_ip_list"}>
2023/07/31 18:36:41.421 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2023/07/31 18:37:02.275 [DHCP] Proc DHCP DISCOVER pkt from client 0050-5687-a236
2023/07/31 18:37:02.275 [DHCP] dhcp_cfg_alloc_ip MAC:00-50-56-87-a2-36
2023/07/31 18:37:02.275 [DHCP] dhcp_cfg_alloc_ip alloc ip from pool i=0 172.31.10.200
2023/07/31 18:37:02.276 [DHCP] Recv DHCP Discover from 0050-5687-a236, response DHCP OFFER with ip 172.31.10.200/255.255.255.0
2023/07/31 18:37:02.276 [DHCP] DHCP boot file is <ipxe.x64.snponly.efi.0>
2023/07/31 18:37:06.065 [DHCP] Proc DHCP REQUEST pkt from client 0050-5687-a236
2023/07/31 18:37:06.065 [DHCP] Recv DHCP Offer Request from 0050-5687-a236, response DHCP ACK
2023/07/31 18:37:06.066 [TFTP] Parse tftp option(tsize,0)
2023/07/31 18:37:06.066 [TFTP] Parse tftp option(blksize,1468)
2023/07/31 18:37:06.066 [TFTP] TFTP RRQ client 172.31.10.200:1697 download <ipxe.x64.snponly.efi.0> start ...
2023/07/31 18:37:06.066 [TFTP] Start send file ipxe.x64.snponly.efi.0 to 172.31.10.200:1697 with blksize 1468, has oack 1
2023/07/31 18:37:06.066 [TFTP] Recv an ERROR opcode pkt from client 172.31.10.200:1697.
2023/07/31 18:37:06.066 [TFTP] Parse tftp option(blksize,1468)
2023/07/31 18:37:06.066 [TFTP] TFTP RRQ client 172.31.10.200:1698 download <ipxe.x64.snponly.efi.0> start ...
2023/07/31 18:37:06.066 [TFTP] Start send file ipxe.x64.snponly.efi.0 to 172.31.10.200:1698 with blksize 1468, has oack 1
2023/07/31 18:37:06.088 [TFTP] Finished send file to 172.31.10.200:1698 with blksize 1468 blks 206
DHCP Server Mode Internal.
Tried all three EFI Boot Files - same.
What could be the reason and maybe some ideas how to fix it?
|
|
|
| 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.
|
|
|
|