11-04-2020, 01:41 PM
(This post was last modified: 11-04-2020, 03:42 PM by FroggieTheGremlin.)
OK, after further "extensive" (?) testing, I have come to the conclusion that what I experience, described in this thread, are clearly BiOS issues of some sort. I have tested the above on three different vendor/hardware/BiOS configurations and only one fails as described previously. The failure occurs on an HP 4th gen i7-based machine. Tests on a 3rd gen i7 DELL and 2nd gen i5 Lenovo have no issues at all based on my above problem description. All three of these machines work as expected (E2B multiBOOT or Rufus single BOOT) as far as any other kind of USB BOOTing scenarios are concerned
At this point I would have to say that Ventoy may be BiOS sensitive in its configuration and if so, that issue may be hard to determine as far as Ventoy is concerned as it relates to different BiOS vendors/configurations.
In the meantime, I will use the TEXT mode DEFAULT (CLI) as that appears to work flawlessly with all tests that I have run.
@Longpanda, I have no idea on the best way to move forward with this issue... but it may rear its ugly head somewhere along the way.
At this point I would have to say that Ventoy may be BiOS sensitive in its configuration and if so, that issue may be hard to determine as far as Ventoy is concerned as it relates to different BiOS vendors/configurations.
In the meantime, I will use the TEXT mode DEFAULT (CLI) as that appears to work flawlessly with all tests that I have run.
@Longpanda, I have no idea on the best way to move forward with this issue... but it may rear its ugly head somewhere along the way.