Closed devdevadev closed 2 years ago
Try Ctrl+i
ctrl+i hotkey not working in my PC. Please add i hotkey so I can test....
I will add i
hotkey later, now you can do as follows:
press c
to enter grub shell, run set vtcompat=1
press Enter, and then press ESC to return.
After that select the ISO file and boot.
The above is equivalent to ctrl+i
I have tried set vtcompat=1
But still showing blinking cursor in the screen as before. Same result in WIMBOOT mode also !!!
For reconfirm, use this CI release https://github.com/ventoy/Ventoy/actions/runs/3049532139 and use i
hotkey.
Should show a red Compatible Mode
in the screen when you press i
.
Both Legacy BIOS mode and UEFI mode has this problem?
If the new CI release also has this problem, press c
to enter grub shell and run vtdebug on
and then select the ISO file to boot.
Will pause many times for debug, press ctrl+c to continue as the prompt.
Currently I am testing in UEFI mode. But it also does not boot in MBR mode last time when I tested... Still same problem with latest CI release....
When I used debug on, then it displayed following codes I have to press ENTER to continue
But after pressing many ENTER keys it reach to the same cursor blinking screen...and never booted !!!
Put the ISO file in the root of the USB drive (no parent directory) and it will work.
Doesnt work in root either. 1.0.79 - MBR ptns - NTFS ptn1
1.0.79 - MBR ptns - NTFS ptn1 Hmm, I'm using Bob.Ombs.Modified.Win10PEx64.v4.98.iso and it works well on real DELL Optiplex and AMD X570 machine in UEFI mode.
hmmm - this is very strange! v4.8 ISO was not booting on my Lenovo IdeaPad 300 - either UEFI or Legacy - from either root of USB drive or a folder _ISO\WINPE. Then I copied the v4.98 to the USB drive and that works fine in both UEFI and Legacy and both folders. Then I retested the v4.8 ISO again and it now works legacy and UEFI from both folders! I have no idea why it now works! Same file, same USB drive... The ISO does not need to be in the root for me.
It's been a long time since Ventoy 1.0.2? Bob.Omb.ISO in a folder booted fine but drive Y: did not present. If Bob.Omb.ISO was in the root, drive Y: was present. But you are right, the ISO no longer needs to be in the root. Thanks for the info.
@devdevadev Try this CI release : https://github.com/ventoy/Ventoy/actions/runs/3062312167 when it finish build. Use WIMBOOT mode to boot the ISO file.
Thanks for adding wimboot mode support Bob.Ombs.Modified.Win10PEx64.ISO . Have you added WIMBOOT support for all WinPE type ISO or only for this Bob.Omb ISO ?
Now it boot perfectly in WIMBOOT mode in my Macbook Air. It also boot fine in normal mode in old Dell Laptop and in my Office Dell PC also....
But when I try to boot in normal mode in my Macbook Air then it still stuck to blinking cursor.....
Why Ventoy don't like to boot Windows ISO, WinPE ISO and any other ISOs in normal mode ? While all ISOs works fine in Macbook Air if I boot them using Grub2fm. It's looking Ventoy uses a unique and different machanism to boot ISOs. Is there any clue in above screenshot why Ventoy fail to boot Bob.Omb ISO in normal mode ?
Thanks & Regards...
For WinPE, WIMBOOT now only supports Bob.Ombs.Modified.Win10PEx64.ISO.
As you said, normal mode only fail in some computer, not all the computers. So it may because come computer's BIOS is not standard.
Ventoy uses different machanism to boot ISOs. When you boot Bob.Ombs. ISO by grubfm, the ISO file is not mounted as a CDROM and some tools can not be used. (Put the ISO file in a subdirectory not in the root and you will see the difference as follows)
All programs:
Official FAQ
Ventoy Version
1.0.79
What about latest release
Yes. I have tried the latest release, but the bug still exist.
BIOS Mode
Both
Partition Style
MBR
Disk Capacity
32GB
Disk Manufacturer
Samsung
Image file checksum (if applicable)
No response
Image file download link (if applicable)
No response
What happened?
Hi..LongPanda
Bob.Ombs.Modified.Win10PEx64.v4.8.ISO not seems to boot in Ventoy neither in NORMAL mode nor in WIMBOOT mode. It just stuck at blinking cursor screen for infinite time......
I have also tried the same ISO with grubfm and it boot fine.
Why Ventoy don't like it ?
Thanks & Regards...