| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 13,661
» Latest member: CSA_kid
» Forum threads: 1,676
» Forum posts: 6,728
Full Statistics
|
| Online Users |
There are currently 645 online users.
» 1 Member(s) | 640 Guest(s)
Baidu, Bing, Google, Internet Archive, MBfromOK
|
| Latest Threads |
Live ISO Building ?
Forum: Ventoy Discussion Forum
Last Post: Eliott
10-31-2025, 02:02 AM
» Replies: 1
» Views: 355
|
Menu Spacing
Forum: Ventoy Discussion Forum
Last Post: fan_boy
10-30-2025, 03:49 AM
» Replies: 0
» Views: 161
|
EXT, NTFS in 1st partitio...
Forum: Ventoy Discussion Forum
Last Post: 4hotdogs
10-29-2025, 03:58 AM
» Replies: 0
» Views: 207
|
Boot 32 bit Windows
Forum: Ventoy Plugin Forum
Last Post: 4hotdogs
10-29-2025, 03:27 AM
» Replies: 2
» Views: 7,357
|
Ventoy Linux still does n...
Forum: Ventoy Discussion Forum
Last Post: 4hotdogs
10-29-2025, 03:25 AM
» Replies: 2
» Views: 684
|
Ventoy InjectioN
Forum: Ventoy Plugin Forum
Last Post: 4hotdogs
10-29-2025, 03:12 AM
» Replies: 0
» Views: 153
|
Aomei + Win To Go + Vento...
Forum: Ventoy Discussion Forum
Last Post: 4hotdogs
10-29-2025, 03:02 AM
» Replies: 4
» Views: 11,108
|
Ventoy installation for o...
Forum: Ventoy Discussion Forum
Last Post: FroggieTheGremlin
10-23-2025, 01:09 PM
» Replies: 5
» Views: 973
|
Screen Resolution 800x600
Forum: Ventoy Discussion Forum
Last Post: fan_boy
10-20-2025, 08:32 PM
» Replies: 0
» Views: 347
|
Issues with windows vista...
Forum: Ventoy Discussion Forum
Last Post: johnson
10-19-2025, 04:10 PM
» Replies: 4
» Views: 11,158
|
|
|
| PXE boot via USB Ethernet dongle |
|
Posted by: jeffshead - 03-31-2024, 12:27 PM - Forum: iVentoy Discussion Forum
- Replies (8)
|
 |
Is there a way to PXE boot computers if their firmware does not support PXE booting from any brand USB-to-Ethernet dongle?
The Microsoft Surface Pro 2 is a good example. It does not have a built-in Ethernet port. I have read that you have to purchase a specific Microsoft branded dongle that's compatible with the Surface's firmware in order to PXE boot. Is there a way to use any USB-to-Ethernet dongle on any computer so that you can PXE boot any computer? I guess I'm thinking along the lines of creating a bootable USB drive, booting to a pre-boot environment from it and then PXE booting from there.
Has anyone been able to accomplish this? If so, please share the steps to do this :-)
|
|
|
Injection in live WinPE fails in .wim images |
|
Posted by: vtFred - 03-28-2024, 12:11 AM - Forum: Ventoy Plugin Forum
- Replies (1)
|
|
Hello,
I use ventoy-1.0.97 on Windows 10 22H2 (19045.4170).
I wanted to test the injection plugin in live OS using .wim, namely the Mini_Windows_10_v21.12.wim taken from medicat.
For that, I just used the template from github mentioned here: https://www.ventoy.net/en/doc_inject_autorun.html to create the archive. I didn’t touch or edit any file in it.
Here is the content of the archive:
![[Image: VXZW3yJ.png]](https://i.imgur.com/VXZW3yJ.png)
Then, I added the injection entry point in ventoy.json using VentoyPlugson.exe such as :
Code: "injection": [
{
"image": "/ventoy/_ISO/Live_OS/Mini_Windows_10_v21.12.wim",
"archive": "/ventoy/_ISO/windows_injection.7z"
}
]
The paths are OK.
But when I start the Mini_Windows_10_v21.12_VTNORMAL.wim and explore the X:\ directory, there are no X:\VentoyAutoRun.log or VentoyAutoRun.bat or X:\Windows\system32\test.txt
Can it work with .wim images ?
|
|
|
|
| Theme Backround Image |
|
Posted by: Alim - 03-26-2024, 07:04 PM - Forum: Ventoy Discussion Forum
- Replies (1)
|
|
Hello,
May I know the details of the theme background image's maximum allowed resolution and size?
What I've noticed is that if the image doesn't meet the requirements, then it cannot be booted.
Regards
|
|
|
|
| NVMe to boot |
|
Posted by: Deadhand - 03-25-2024, 08:59 PM - Forum: Ventoy Discussion Forum
- No Replies
|
|
Using ventoy-1.0.97(window) to setup a 4T NVMe drive, the drive failed to show on the boot screen.
It turns out that the VTOYEFI partition was set to "Basic Data Partition", It needed to be "EFI system Partition."
How I solved it the issue:
1. Start CMD in admin mode
2. From the command line run: Diskpart
* Note [x] is number for the drive *
3. Select disk:
a. run: list disk
b. run: select disk [x]
4. Verify the correct drive is selected:
a. run: list disk [x]
b. the selected drive will now how an "*" beside it.
* Note [x] is Number for the Partition *
5. Select partition:
a. run: list partition
b. run select partition [x]
6. Verify the correct partition is selected:
a. run: list partition
b. the selected partition will now how an "*' beside it.
7. To switch to EFI Partition use this CMD line:
SET ID=c12a7328-f81f-11d2-ba4b-00a0c93ec93b OVERRIDE
This corrected my NVMe and I hope you find it helpful.
* Just an interest command, To switch back to Basic Data Partition use this CMD line:
SET ID=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 OVERRIDE
|
|
|
|
| Booting Mint xfce 21.3 with Persistence fails(SOLVED) |
|
Posted by: SmackDown - 03-21-2024, 08:21 PM - Forum: Ventoy Discussion Forum
- No Replies
|
|
I get this error message after grub menu
Quote:FAILED TO START DETECT THE AVAILABLE GPUS AND DEAL WITH ANY SYSTEM CHANGES......FAILED TO START LIGHT DISPLAY MANAGER
I think it is because lightdm is loading before the graphics drivers are loaded
I am using ventoy-1.0.97 on a Ryzen7600x PC with integrated graphics
I have tried persistent Ventoy USBs with Mint 19.3 xfce (no network connection available, programs won't load), Mint Cinnamon 21.3 (various issues), and Ubuntu 20.04(buggy)
I think I need a fairly recent version of OS to support my hardware
EDIT: Tired to sudo update in CLI but ran out of space on USB. The mother board is a Gigabyte B650M AORUS ELITE AX and won't work with older versions of Mint. Just tried Mint 20 Cinnamon and no network connections I think because of motherboard being newish
EDIT 2: tried with mint 21.3 edge ed and same errors as with 19.3
EDIT 3: Made 3 changes. I changed to a different USB stck, changed the port, changed partition table to GPT...... And it worked.Tried USB in same port where I had problems and it still works so either I used the wrong partition table or the old USB stck had problems. Should have tried a different USB stick from the start in stead of wasting so much time on this
|
|
|
|
|
