Ventoy

Post#1 by **Jack** » 12 Feb 2024, 13:51

Can I run Porteus iso and save changes threw Ventoy? And later can I add more iso to Ventoy?

Post#2 by **AcnapyxoB** » 12 Feb 2024, 13:59

I'm using ventoy with modified porteus.cfg into the iso.
The idea is to point porteusave.dat.

Post#3 by **Jack** » 12 Feb 2024, 14:32

AcnapyxoB wrote: ↑
12 Feb 2024, 13:59
I'm using ventoy with modified porteus.cfg into the iso.
The idea is to point porteusave.dat.

The porteus.cfg did you create it? And what it look like?

Post#4 by **AcnapyxoB** » 12 Feb 2024, 15:22

Jack wrote: ↑
12 Feb 2024, 14:32
And what it look like?

Code: Select all

PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT GRAPHICAL
MENU BACKGROUND ../../boot/syslinux/porteus.png
MENU TITLE Porteus-5.01 64bit

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 12
MENU HELPMSGROW -8
MENU TIMEOUTROW -1
MENU TABMSGROW -9
MENU CMDLINEROW -1
MENU HSHIFT 4
MENU VSHIFT 0

	menu color screen	37;40      #90FFF48D #00000000 none
	menu color border	30;44      #00000000 #00000000 none
	menu color title	1;36;44    #ffffffff #00000000 none
	menu color unsel	37;44      #ff57cbff #00000000 std
	menu color hotkey	1;37;44    #ff8037b7 #00000000 none
	menu color sel		7;37;40    #ffFFF48D #9000254B std
	menu color hotsel	1;7;37;40  #ffaf67f7 #003f7fbf none
	menu color scrollbar	30;44      #00000000 #00000000 none

	menu color tabmsg	31;40      #ff57cbff #00000000 std
	menu color cmdmark	1;36;40    #ffff0000 #00000000 none
	menu color cmdline	37;40      #ffffffff #ff000000 none
	menu color pwdborder	30;47      #ffff0000 #00000000 std
	menu color pwdheader	31;47      #ffff0000 #00000000 std
	menu color pwdentry	30;47      #ffff0000 #00000000 std
	menu color timeout_msg	37;40      #ffc0cdef #00000000 none
	menu color timeout	1;37;40    #ffffa5ef #00000000 none
	menu color help		37;40      #ff57cbff #00000000 std
	menu color msg07	37;40      #90ffffff #00000000 std


LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=EXIT:/porteus/save.dat changes-ro extramod=/porteus/modules vga_detect copy2ram rammod=base cliexec=usermod~-aG~vboxusers~guest
TEXT HELP
    Try to autoconfigure graphics
    card and use the maximum allowed
    resolution. Detects nVidia video
    cards and loads the proprietary
    drivers at startup. Keep saved
    changes in a read-only state.
ENDTEXT

LABEL SAVЕ
MENU LABEL Graphics (saving)
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=EXIT:/porteus/save.dat extramod=/porteus/modules vga_detect cliexec=usermod~-aG~vboxusers~guest
TEXT HELP
    Try to autoconfigure graphics
    card and use the maximum allowed
    resolution. Detects nVidia video
    cards and loads the proprietary
    drivers at startup. Changes will
    persist during reboot/restart
ENDTEXT

LABEL fresh
MENU LABEL Always Fresh
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND nomagic base_only norootcopy noswap
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL copy2ram
MENU LABEL Copy To RAM
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND nomagic norootcopy noauto extramod=/porteus/modules vga_detect copy2ram cliexec=usermod~-aG~vboxusers~guest
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum allowed
    resolution, but first copy all
    data to RAM to get a huge speed
    increase (needs >1024MB)
ENDTEXT

LABEL text
MENU LABEL Text mode (safe)
KERNEL vmlinuz
APPEND initrd=initrd.xz 3 nomagic base_only norootcopy
TEXT HELP
    Run Porteus in text mode with
    no extra modules loading and
    start the command prompt only
ENDTEXT

LABEL pxe-boot
MENU LABEL Porteus as PXE server
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND pxe
TEXT HELP
    Run Porteus as usual, but also
    initialize a PXE server.
    This will allow you to boot Porteus
    on other computers over a network
ENDTEXT

MENU SEPARATOR

LABEL plop
MENU LABEL PLoP BootManager
KERNEL /boot/syslinux/plpbt
TEXT HELP
    Run the plop boot manager.
    This utility provides handy
    boot-USB options for machines
    with vintage/defective BIOS
ENDTEXT

## This option might work with hardware specific info added to APPEND
#LABEL hd
#MENU LABEL Boot from the first hd
#COM32 chain.c32
#APPEND hd0 1
#TEXT HELP
#    Don't start Porteus at all, but
#    rather run any operating system
#    installed on the first partition
#    of the hard drive
#ENDTEXT

LABEL reboot
MENU LABEL Reboot the system
COM32 reboot.c32
TEXT HELP
    Reboot the system
    (may not work in all cases)
ENDTEXT

MENU SEPARATOR

LABEL changes help (this is not a boot option) press ESC to return to main menu
MENU LABEL Saving Changes Help
TEXT HELP
   If Porteus is on a Windows (FAT/NTFS) 
   or other non-posix compatible file- 
   system your changes can not be 
   saved. Once booted use the  
   "Porteus Save File Manager" app
   to create a save.dat file for 
   saving your changes after reboot.  
ENDTEXT

All modules that I need are into iso 'modules' folder, nvidia driver is also in iso, but in 'optional'. Some additional modules are in usb-flash 'porteus' folder.

If You use it on a computer with another Porteus. It might be a good idea to specify the boot device.
for example:

Code: Select all

APPEND from=LABEL:VENTOY changes=EXIT:LABEL:VENTOY/porteus/save.dat

Post#5 by **Ed_P** » 12 Feb 2024, 17:15

AcnapyxoB wrote: ↑
12 Feb 2024, 15:22
All modules that I need are into iso 'modules' folder, nvidia driver is also in iso, but in 'optional'. Some additional modules are in usb-flash 'porteus' folder.

So you download the ISO, extract the folders, tweak the files and modules to fit your needs then rebuild the ISO so Ventoy will boot it? What does your Ventoy boot menu code look like? Can you post it? Can you add Porteus cheatcodes to the Ventoy boot menu?

Post#6 by **AcnapyxoB** » 12 Feb 2024, 18:11

Аccording to this information:
viewtopic.php?f=59&t=9865
Porteus should work by creating "ventoy.json", but I tried withowt succes.

Тhat is the reason to modify ISO with ISO Master (archive managers breacks isos)

Ed_P wrote: ↑
12 Feb 2024, 17:15
Ventoy boot menu?

It is actually ventoy.json and is recommended (according to the developer) to use VentoyPlugson for editing:
https://www.ventoy.net/en/plugin_plugson.html

Ed_P wrote: ↑
12 Feb 2024, 17:15
What does your Ventoy boot menu code look like?

Code: Select all

{
    "control":[
        { "VTOY_MAX_SEARCH_LEVEL": "1" },
        { "VTOY_DEFAULT_SEARCH_ROOT": "/ISOs" }
    ],
    "theme":{
        "file": "/ventoy/themes/selectos/theme.txt"
    },
    "menu_alias":[
        {
            "image": "/ISOs/01-Porteus-KDE-v5.01-x86_64.iso",
            "alias": "Porteus v5.01 KDE x86_64"
        },
        {
            "image": "/ISOs/02-linuxmint-21.3-cinnamon-64bit.iso",
            "alias": "Linux Mint 21.3 Cinnamon 64bit"
        },
        {
            "image": "/ISOs/03-kali-linux-2023.2-live-amd64.iso",
            "alias": "Kali Linux Live 2023.2 amd64"
        },
        {
            "image": "/ISOs/04-tails-amd64-5.19.1.iso",
            "alias": "Tails v5.19.1 amd64"
        },
        {
            "image": "/ISOs/05-rescuezilla-2.4.2-64bit.jammy.iso",
            "alias": "Rescuezilla v2.4.2 64bit"
        },
        {
            "image": "/ISOs/06-clonezilla-live-3.1.0-22-amd64.iso",
            "alias": "Clonezilla Live 3.1.0 amd64"
        },
        {
            "image": "/ISOs/07-PartitionWizard-12.8.iso",
            "alias": "Partition Wizard v12.8 Technician"
        },
        {
            "image": "/ISOs/08-Kaspersky_Rescue_Disk_18.iso",
            "alias": "Kaspersky Rescue Disk v18"
        },
        {
            "image": "/ISOs/09-HBCD_PE_x64.iso",
            "alias": "Hiren’s BootCD PE x64 v1.0.2"
        },
        {
            "image": "/ISOs/10-Windows10-Pro-22H2-x64-ESD.iso",
            "alias": "Windows 10 Pro 22H2 x64"
        },
        {
            "image": "/ISOs/ventoy-delete-key-1.0.iso",
            "alias": "Ventoy Delete Secure-boot-key"
        }
    ],
    "menu_tip":{
        "tips":[
            {
                "image": "/ISOs/01-Porteus-KDE-v5.01-x86_64.iso",
                "tip": "Kernel 6.5.5 64-bit ; NVIDIA Display Driver 470.199.02"
            }
        ]
    },
    "persistence":[
        {
            "image": "/ISOs/03-kali-linux-2023.2-live-amd64.iso",
            "backend":[
                "/Persistence/kali-linux-1.dat"
            ]
        }
    ]
}

Post#7 by **AcnapyxoB** » 12 Feb 2024, 18:27

Тhe main reason to use Ventoy is secure boot.
I used this method:
[Solved] Security Boot Fail (Post by Ed_P #67428) (with thanks to Ed_P and others in topic)
but one day after some updates on Win 10 PC it stopped working, so ventoy came to replace it:
https://www.ventoy.net/en/doc_secure.html

Post#8 by **Ed_P** » 13 Feb 2024, 04:37

AcnapyxoB wrote: ↑
12 Feb 2024, 18:11

Ed_P wrote: ↑February 12th, 2024, 12:15 pm wrote: Ventoy boot menu?
It is actually ventoy.json and is recommended (according to the developer) to use VentoyPlugson for editing:
https://www.ventoy.net/en/plugin_plugson.html

Interesting. So Ventoy is not a grub2 interface. Thank you AcnapyxoB.