Hello

I am trying to boot an old HP dc7700 withj a Ventoy stick without success (screen remains black) 
(F10->System BIOS and Setup Utility, copyright 1982-2006)

Is this PC too old to boout from for Ventoy?

Thank you!

Harry




PS
others/modern PCs can be booted from this stick

• 2022/07/01 --- 1.0.78 release
  

1. Improvement for Boot Conf Replace Plugin now can replace at most 2 files. Notes
   
   
2. Update Super-UEFIinSecureBoot-Disk to v3.4 (#1695)
   
3. .ventoyignore also works in F2 Browser Mode.
   
4. Fix the bug when booting latest KaOS. (#1696)
   
5. Fix a bug when booting TrueNAS Core 13.0. (#1684)
   
6. Fix a bug when booting StorageCraft StorageProtect SPX. (#1683)
   
7. Auto remove the redundant trailing slash when set directory path on VentoyPlugson page.
   
8. languages.json update
   
9. New ISO support (total 920+)
   
10. Document: How To Delete Ventoy Secure Boot Key
    

I have three images in the "ISO" folder .iso, 
Windows_7_&_10_Pro_x86_x64_30.05.2021.iso,
Windows_7_Pro_x86_x64_15.12.2021.iso,
Windows_10_21H2_19044.1766_x64.iso.
I assigned the Windows_1 icon to the last two, and the image Windows_10_21H2_19044.1766_x64.iso.
I want to assign a Super icon_1. 
But I can't do it. Tell me where the error is, what am I doing wrong?

"menu_class": [       
        {
            "key": "Windows",
            "class": "Windows_1"
        },
        {
            "dir": "ISO",
            "class": "Super_1"
        },
        {
            "key": "WinPE",
            "class": "WinPE_1"
        },
        {
            "key": "Memtest",
            "class": "Memtest_1"
        }
    ],

    "image_list": [
        "/ISO/Windows_10_21H2_19044.1766_x64.iso",
        "/ISO/Windows_7_&_10_Pro_x86_x64_30.05.2021.iso",
        "/ISO/Windows_7_Pro_x86_x64_15.12.2021.iso",
        "/WinPE/WinPE_Sergei_Strelec_x86_x64_04.01.2022.iso",
        "/Memtest/Memtest86+_4.3.7_&_9.4.iso"
    ],

    "menu_alias":[
        {
            "image":"/ISO/Windows_10_21H2_19044.1766_x64.iso",
            "alias":"Windows 10      21H2  Pro    x86 x64  19044.1645"
        },
        {
            "image":"/ISO/Windows_7_&_10_Pro_x86_x64_30.05.2021.iso",
            "alias":"Windows 7 & 10  21H1  Pro    x86 x64              30.05.2021"       
        },
        {
            "image":"/ISO/Windows_7_Pro_x86_x64_15.12.2021.iso",
            "alias":"Windows 7            Pro    x86 x64              15.12.2021"
        },
        {
            "image":"/WinPE/WinPE_Sergei_Strelec_x86_x64_19.07.2021.iso",
            "alias":"WinPE Sergei Strelec        x86 x64              19.07.2021"
        },
        {
            "image":"/WinPE/WinPE_Sergei_Strelec_x86_x64_04.01.2022.iso",
            "alias":"WinPE Sergei Strelec        x86 x64              04.01.2022"
        },
        {
            "image":"/WinPE/WinPE_Super.iso",
            "alias":"WinPE Super        ( no boot UEFI )"
        },
        {
            "image":"/Memtest/Memtest86+_4.3.7_&_9.4.iso",
            "alias":"Memtest86+            4.3.7  &  9.4"
        }
    ]
}

Hello

it happend that I selected the wrong OS/ISO to boot the PC from.  In order to interrupt the boot process (of the unwanted OS), I pressed Ctr+Alt+Del. This does infact reset the PC, but the "Ventoy-screen" is not loaded/shown again. It's necessary to power off/on the PC.


Why that? Has that something to do with Ventoy?


Thank's a lot!

Harry

Hello forum,

would like to add a LUKS-partition, preferably between the large NTFS-partition and the 32MB FAT16 partition.
(e.g. with a tool like gparted)

Is this a good idea?


Thank you!

Harry

My system is set for UEFI boot. I made a VHD of medicat (GPT, Ventoy 1.77, NTFS). 
I then created a Ventoy 1.77 USB disk (GPT, NTFS).
I put the medicat.VHD on the Ventoy USB disk, created a /ventoy folder, and put the Windows 10 ventoy_vhdboot.img into the /ventoy folder.
On boot the Ventoy menu appears, but when I select the medicat target I get an error and am unable to boot:
File: \Windows\system32\winload.efi
Status: 0xc000000f
Info: The application or operating system couldn't be loaded because a required file is missing or contains erros.

Note:
- The medicat VHD boots successfully in VirtualBox
- Ventoy (GPT) installed directly onto the USB disk boots fine
- Medicat installed directly onto the USB disk boots fine


I've tried all of the following:
- Partition VHD with MBR
- Partition Ventoy USB with MBR
- Format Ventoy USB as exFat
- Tried the Windows 7 ventoy_vhdboot.img (different failure)
I see the same issue in all cases.

When making a new Ventoy drive or updating a ventoy drive, it would be most convenient if there was a button to automatically add VentoyPlugson files and download and add plugins to the \ventoy folder.

e..g.  in Ventoy2Disk.exe - add new button for:

'Add utilities and plugin files to \ventoy folder'


This would mean we would have the correct version of ventoyplugson and the latest  wim/vhd plugins and scripts on the USB drive.

It makes it easier to find and run VentoyPlugson and scripts.

Also, add button to  Ventoy2Disk.exe to format main partition (can just call Windows format program), so that we can easily convert to NTFS and then click 'Add utilities' button to get utilities and plugin downloads.

Is this practical?

Parent entry does not seem to work - so I added second image entry and that works.
But just single Parent entry does not seem to prompt user to select XML
Only the second entry seems to work. If I delete the image entry in VentoyPlugson, then I am not prompted to select an XML file.
v1.0.77 Legacy MBR USB disk.

提示Boot Fail

在BIOS里面把安全引导关闭也无法引导。

First of all like and enjoy Ventoy very much. But!

Would it be possible (or make sense at all) to enlarge the esp partition to a couple hundred MB and change it to Fat32?

Would that make it possible install other programs on the Ventoy (still large enough) partition and use the enlarged (standardized) ESP partition as usual?

In case of using an external usb hdd (not a pendrive), the Ventoy directory could be changed to NTFS, then devided into multiple partitions allowing to install other bootable OS's.

The pendrive version of the program could be left alone as it is right now.

It is obvious by now, I guess, that I'm a newbie. Thanks for reading