How to Dual Boot Porteus Linux with windows 11 without USB Drive or Creating Partition

[tpkusr]

Yes, you can dual boot Linux with windows 11 without USB drive or creating a dedicated partition. You can do it with the help of grub2win and just follow the steps.

* Store a Porteus Linux ISO file on your Windows drive.
* Use Grub2Win to directly launch that ISO.
* Add a persistence file so Linux saves all your settings, files, and installed apps.

The result is a truly non-invasive, zero-partition dual-boot solution. You get a full, persistent Linux experience with absolutely no risk to your Windows 11 system. Let's make the ultimate safe dual-boot!


Pre-Requisites & Setup: Preparing for Boot

1. Configure Windows 11
Before you start, you must disable key Windows features that interfere with any non-standard boot process:

Disable Secure Boot:

While Grub2Win supports UEFI, disabling Secure Boot in your BIOS/UEFI settings is highly recommended to prevent conflicts when booting custom GRUB configurations.

2. Organize Your Files
To keep things tidy and ensure the boot commands work, create a dedicated folder on your main drive (e.g., C:):

* Create a root folder: C:\iso\

Now, place your downloaded Porteus Linux ISO (Porteus-KDE-v5.01-x86_64.iso ) directly into the C:\iso\

With your ISO ready, we can now install Grub2Win and create the custom boot entry.


Part 1: Installing and Configuring Grub2Win

1. Installation
* Download Grub2Win: Get the latest installer zip from the official Grub2Win SourceForge page.
* Run the Installer: Extract the zip and run the setup as an Administrator.
* Complete the Installation: Follow the prompts. Grub2Win will install to C:\grub2 and set up the necessary EFI modules.
* Initial Reboot: Reboot your PC. When the new Grub2Win menu appears, select Windows 11 to boot back into your desktop.
* File Placement: Ensure your Porteus ISO (e.g., Porteus-KDE-v5.01-x86_64.iso) is in C:\iso\
2. Creating the Custom ISO Boot Entry for Porteus
We now instruct Grub2Win to find the Porteus ISO
* Open the Menu Manager: In the main Grub2Win window, click "Manage Boot Menu".
* Add a New Entry: Click the "Add a New Entry" button.
* Add title like “Porteus Persistent ISO”, select “iso boot” from type.
* Select “load sample code” and set isopath, kernelpath, initrdpath and bootparms like this:

# Set the path to your Porteus ISO file

set isopath="/iso/Porteus-KDE-v5.01-x86_64.iso"

set kernelpath='/boot/syslinux/vmlinuz'
set initrdpath='/boot/syslinux/initrd.xz'
set bootparms='from='$isopath' volume=33 reboot=cold extramod=/iso/Modules'

* Save the Entry: Click "Apply" or "OK" to save the new custom boot entry.
Your unique, non-invasive, persistent Porteus entry is now configured!


Part 2: Testing and Using the OS

With Grub2Win installed and the custom Porteus boot entry configured, it's time for the moment of truth.
1. Execute the Dual Boot
* Reboot Your PC: Close all applications and reboot your Windows 11 machine.
* Select Grub2Win: The customized Grub2Win boot menu should appear.
* Choose Porteus: Select your new entry, "Porteus Persistent ISO".
The GRUB script will now take over. It will locate the kernel files. Porteus should then boot into its desktop environment.

Creating persistent save file:

Launch the Porteus Save File Manager
* Once booted, open the Application Menu (usually in the bottom-left corner).
* Navigate to: System \rightarrow Porteus save manager (or sometimes found under Administration or Porteus Settings Centre).
Create the save.dat File
* In the application window, click the "Create" button.
* Enter the size of the container in megabytes (MB). A common starting size is 512MB to 1024MB (1GB), but you can choose a size based on how many programs and settings you plan to save.
* Select the location where you want to save the file. This should be on the same partition where your Porteus files are located. A good location is inside the main /iso/ folder on your storage device.

* Click "OK" to create the file.

Configure Porteus to Use the save.dat
The Porteus Save File Manager often walks you through this step, but it involves modifying the boot configuration file so Porteus knows to look for and use your new save file.

You have to edit boot menu entry like this

set bootparms='from='$isopath' volume=33 reboot=cold extramod=/iso/Modules changes=EXIT:/iso/save.dat'


This tells Porteus to only save your changes when you shut down or reboot, instead of saving them in real-time.




2. Confirm Persistence
Once you are on the Porteus desktop, we need to verify that your system is successfully reading and writing data to the save.dat file, meaning your work won't vanish on reboot.
* Create a Test File:
* Right-click on the Porteus desktop and create a new, empty file named Persistence_Test_1.txt.

3. Final Test: Reboot
* Shut Down Porteus: Use the standard Porteus shutdown sequence (do not just hit the power button).
* Boot Back In: When the Grub2Win menu appears, select "Porteus Persistent ISO" again.
Success Confirmation:
* If the Persistence_Test_1.txt file is still on your desktop, your persistence setup is successful!

You now have a complete, functional, persistent Porteus installation that runs safely alongside Windows 11 without taking up a single permanent partition.

The Ultimate Safe Dual Boot
You've mastered the non-invasive dual-boot. By leveraging Grub2Win and the ISO persistence method, you've created a zero-risk testing environment for Linux, keeping your Windows 11 installation pristine.


Now go forth and enjoy the best of both worlds!

[vinnie]

Outstanding tutorial, really compliments!
I don't have windows installed but I guess if I needed to do a dual boot I would thank the luck of having such a tutorial.

[tpkusr]

Thanks Vinnie for your kind words, that really means a lot to me. I am glad that my tutorial can help someone in the future.

[vinnie]

I think this forum is the place where one can get more information about porteus, so be sure that your tutorial will come in handy to everyone who wants to do dual boot with windows

[tpkusr]

I have posted similar tutorial on hashnode for global audience who aren't familiar with porteus Linux yet. It will help them to introduce with porteus Linux and ultimately solved the dual boot problem. Here is the link
https://fixmyos.hashnode.dev/dual-boot- ... -partition

[rych]

tpkusr, Fantastic tutorial, much better than my attempt at a similar topic in [HOWTO] Multiboot Windows and frugal Porteus/X Yours doesn't require "USB drive or creating a dedicated partition", whereas mine starts with "Boot to your current Porteus/X USB. Resize the NTFS C: partition using GParted", it's because I always prefer the dedicated ext4 partition for changes and stuff, and not save.dat. Grub2Win shines in this scenario indeed. Well done, lots of (advanced) Windows users will benefit from this I'm sure.

[tpkusr]

Thank you, rych, for the valuable feedback. I appreciate you taking the time to share your perspective on the dedicated partition approach.

I did see your post, which is a great guide for users who prefer that dedicated ext4 setup. My goal with this particular tutorial was to provide an easy entry point for those coming from Windows or using older hardware, letting them try Linux (like Porteus) without the complexity of partitioning right away.

Since Porteus is so fast and user-friendly, I'm hoping this allows new users to get comfortable quickly before deciding on a permanent setup. Grub2Win definitely makes that possible!

[Ed_P]

After screwing up my new notebook's Windows system and then my backup notebook's Windows system I've had to start dual booting my Porteus USB drive via the F12 key. I've eventually come up with a new option based on a comment someone made here.

All we need from grub2 are 3 files: bootx64.efi, grubx64.efi, and grub.cfg.

How to install grub2 to a Windows 11 UEFI system.
- May work for a Windows 10 UEFI system also

1. Download an ISO system that supports/installs grub2.
I downloaded the Ubuntu-25.10-desktop-amd64.iso
http://mirrors.rit.edu/ubuntu-releases/ ... -amd64.iso

2. In Windows, in a Command Prompt window enter:

Code: Select all

   >  diskpart
   >  list disk

Note the number of the disk you want to install grub2 to.

Code: Select all

   >  select disk=__   < the number of the disk you selected.
   >  list partitions

Note the number of the partition labeled as System.

The numbers usually selected are 0 and 1 and if they match your system
right click on the EFIdrv.cmd noted below with the Run as Admin option.

If the 0 and 1 are valid reply Y which assigns drive letter
U to the EFI drive.

If 0 and/or 1 is invalid, edit the EFIdrv.cmd script to
match the numbers to your system and rerun it.

3. In Windows open a Command Prompt Run as Admin.
In the U:\EFI folder rename the \boot folder to be \bootB4.

4. Copy the ISO file's \EFI\boot folder to the U:\EFI folder.
Copy the ISO file's \boot folder to the C: drive.

5. Edit the grub.cfg file in the U:\EFI\boot folder to be simply:

set menu_color_normal=black/white
set menu_color_highlight=black/light-gray
set timeout=25

search -f /boot/grub/grub.cfg --set=root

6. In the C:\boot\grub\grub.cfg file:
After the loadfont Unicode line add:

set gfxmode=800x600,auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm

At the bottom of the cfg file, after the fi last line add:

menuentry ".........." {
root ()
}
menuentry 'Windows EFI Boot Manager ' {
search -f /EFI/Microsoft/Boot/bootmgfw.efi --set=root
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
menuentry 'Computer EFI Boot Menu ' {
search -f /EFI/Boot/bootx64.efi --set=root
chainloader /EFI/Boot/bootx64.efi
}
menuentry ".........." {
root ()
}
menuentry 'Porteus ' {
search -f /grub2/userfiles/Dgrub2.sh --set=root
source ($root)/grub2/userfiles/Eds.configs/Porteus5.0.cfg
}

7. The system should be multiboot functional and the menu maintainable
via Porteus or Windows. No grub2-mkconfig required.

To run the Ubuntu menu entries you need to copy the casper folder to the boot folders drive. If not interested in doing that delete their menu entries.

The EFIdrv.cmd file referenced in step #2 above:

Code: Select all

@echo off&Title Assign U: to system UEFI drv&Color 1F&MODE CON COLS=70 LINES=45

:: https://forum.porteus.org/viewtopic.php?p=104197#p104197
:: Run Diskpart to determine Disk and System Partition numbers

if exist efiscr.txt del /f efiscr.txt > nul

echo list disk            >efiscr.txt
echo select disk      0  >>efiscr.txt
echo list partition      >>efiscr.txt
echo select partition 1  >>efiscr.txt
echo remove letter=u noerr >>efiscr.txt
echo assign letter=u     >>efiscr.txt
echo exit                >>efiscr.txt
echo.
echo Diskpart
type efiscr.txt
echo.
echo  The U: drive will be set to be Disk 0, Partition 1. 
echo  If not right, edit script values above and rerun.
echo.

:: Check for Run as Admin
net sessions >nul 2>&1
if %errorLevel% == 0 (
   echo  Running as Admin.
   echo.
) else (
   echo  To continue, script must be: Run as Admin.
   pause > nul
   exit
)

set ASK= 
set /p ASK= Run this Diskpart script on DISK 0 PARTITION 1 (Y/N) : 
if /i "%ASK%"=="Y" (
   diskpart /s efiscr.txt > efi.log
) else (
   echo "%ASK%" not equal "Y". No letter assigned.  
   pause > nul
   exit 
)
if exist efiscr.txt del efiscr.txt > nul
dir U:
dir U:\EFI
pause > nul
exit

[Ed_P]

menuentry 'Porteus ' {
search -f /grub2/userfiles/Dgrub2.sh --set=root
source ($root)/grub2/userfiles/Eds.configs/Porteus5.0.cfg

Obviously personalize to your system's grub menus' location and cfg names.

Added in 1 day 4 hours 55 minutes 33 seconds:
Problem! What previously worked when installed to a USB drive doesn't work when installed to my notebook's SSD. Grub2 boots but not finding the /boot/grub/grub.cfg file. On the USB drive it's formatted as FAT32, on the SSD the drive is formatted as NTFS. Grub2Win found the grub.cfg file on it when it was installed.

Added in 7 hours 25 minutes 13 seconds:
I copied the EFI's grub.cfg file (234B) from the USB drive over the EFI's grub.cfg file (229B) on the SSD drive and rebooted. It didn't help.

To the grub2 prompt I entered set and see:

fu_path='(hd0,gpt1)/EFI/Grub2'
locale_dir=''
prefix='(hd0,gpt1)/boot/grub'
root='(hd0,gpt1)'

For some reason the EFI's grub.cfg's
search -f /boot/grub/grub.cfg --set=root
isn't being run because the C: drive's /boot/grub folder is not on the same drive as the EFI drive's /boot/grub folder.

Added in 18 minutes 57 seconds:
The USB drive is all 1 FAT32 partition, the SSD drive is multiple partitions. One FAT32, several NTFS.



Got to work on the EFI grub.cfg file.

Added in 1 hour 10 minutes 41 seconds:
Okay, this idea needs refinement because at this point it's not working as laid out. Something is off.

Added in 11 hours 33 minutes 13 seconds:
And so it evolves. "All we need from grub2 are 3 files: bootx64.efi, grubx64.efi, and grub.cfg." which works but the menu's text is very tiny. So you add loadfont and insmods to the grub.cfg and the text is readable so long as grub2 has access to the fonts and modules which are not in the EFI folder.

Need to play with this some more.

Added in 3 hours 57 minutes 48 seconds:
Finally a multiboot grub2 system on my old EFI notebook that works. Details later.

[Ed_P]

OK. The steps for the multboot grub2 on my UEFI Windows 11 SSD system (via Windows):

1. Download an ISO system that supports/installs grub2.
I downloaded the Ubuntu-25.10-desktop-amd64.iso
http://mirrors.rit.edu/ubuntu-releases/ ... -amd64.iso

2. In Windows, I assigned a drive letter to the UEFI partition.
I right clicked on the EFIdrv.cmd from posting #8 above and selected Run as Admin.

3. In Windows I started a Command Prompt with Run as Admin.

4. On the UEFI partition I renamed the u:\boot folder u:\Windows.

5. I copied the Ubuntu EFI\boot folder to the u:\EFI folder.
I deleted the u:\EFI\boot\mmx64.efi file.

6. I copied the Ubuntu boot folder to the u:\ folder.
I deleted the u:\boot\grub\i386.pc folder.

7. I edited/replaced the u:\boot\grub\grub.cfg file with:

Code: Select all

set timeout=60

loadfont unicode

set gfxmode=800x600,auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray

menuentry 'UEFI Firmware Settings' {
	fwsetup
}
menuentry ".........." {
     root 1
     }
menuentry 'Windows ' {
     search -f   /EFI/Windows/bootx64.efi --set=root
     chainloader /EFI/Windows/bootx64.efi
}
menuentry ".........." {
     root 1
     }
menuentry 'Porteus ' {
     search -f     /grub2/userfiles/Dgrub2.sh --set=root
     source ($root)/grub2/userfiles/Eds.configs/Porteus5.0.cfg
}
menuentry 'PorteuX ' {
     search -f     /grub2/userfiles/Dgrub2.sh --set=root
     source ($root)/grub2/userfiles/Eds.configs/PorteuX.cfg
}
menuentry 'ISOs ' {
     search -f     /grub2/userfiles/Dgrub2.sh --set=root
     source ($root)/grub2/userfiles/Eds.configs/ISOmenu.cfg
}
menuentry ".........." {
     root 1
     }

My current grub.cfg file is here: How to Dual Boot Porteus Linux with windows 11 without USB Drive or Creating Partition (Post by Ed_P #104325)

The Porteus, PorteuX and ISOs menus are on my system's D: drive and
from my previous Grub2Win system and are maintainable outside of
the Run as Admin need. Notepad works for me.

Obviously the user menus you want to use and where is up to you.

8. Lastly, I had to reboot my system to my UEFI Firmware menu (F2)
and add the new u:\EFI\boot\bootx64.efi file to my boot options
and I named it Grub2.

The system boots, the menu is readable, not as pretty as my Grub2Win
one was but better than the grub.cfg in the u:\EFI\boot folder option,
I can now boot the ISOs on my D: drive without the need for a USB
drive once again and the EFI drive is stable and secure.



BTW The system has Secure Boot disabled. That's a leftover. At some
point I'll test if it's a need for grub2.

Update: A Windows 11 script I made that automates the steps is posted here:
How to Dual Boot Porteus Linux with windows 11 without USB Drive or Creating Partition (Post by Ed_P #104480)

[rych]

Glad you've made it work, Ed_P. I have a similar setup:

/EFI/boot contains only 2 files: bootx64.efi and grubx64.efi

/boot/grub/ also contains just 2 files as a minimum grub.cfg and unicode32.pf2

Then of course, we tell grub where to find the sweet couple vmlinuz&initrd.zst

So my minimal grub.cfg is as follows:

Code: Select all

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
set timeout=5
loadfont /boot/grub/unicode32.pf2
terminal_output gfxterm

menuentry 'Porteus 1920x1080' {
	linux /boot/porteus/vmlinuz from=LABEL:PortSSD changes=EXIT:/porteus login=root load=1920x1080 fsck zram=33%
	initrd /boot/porteus/initrd.zst
}

(Secure Boot enabled in my case, but I'm using the old grub that came with Ubuntu 18 I think -- it was signed then, and so is accepted by Secure Boot.)

[Ed_P]

Thanks rych. My /boot/grub folder is bigger than yours but so is my menu's text size.

My user .cfgs are a little bigger than yours also.

My Porteus5.0.cfg:

Code: Select all

set timeout=30

# Set the default variable to the submenu entry you prefer
set default=1

     set linux_folder=/porteus5.0

     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-240923.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-241211.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-250130.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-250404.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64.iso"

     set SaveDat=50save.dat

if [ ! -z "${loop}" ]; then
   loopback -d loop
fi     

menuentry " Porteus 5.01 ISO - changes="  --class slackware   --class user-icon-porteus  {

     set Changes=$SaveDat   # porteussave.dat 
     set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules login=guest \
       changes=EXIT:$linux_folder/changes/$Changes \
       noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;mychanges;autonet;pipe;menu1" # ;mychanges"

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz      from=$iso $bootparms
#     linux $linux_folder/BootModules/vmlinuz from=$iso $bootparms
     initrd (loop)/boot/syslinux/initrd.xz
#     initrd $linux_folder/initrd/initrd.xz
     }  

menuentry " Porteus 5.01 ISO - AF'"  --class slackware   --class user-icon-porteus  {

     set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules \
       noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;menu2" # ;mychanges"

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms
#     linux $linux_folder/BootModules/vmlinuz from=$iso $bootparms
     initrd (loop)/boot/syslinux/initrd.xz
#     initrd $linux_folder/initrd/initrd.xz  
     }

menuentry " Porteus 5.01 ISO - AF+"  --class slackware   --class user-icon-porteus  {

     set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules \
       noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;mychanges;pipe;menu3" 

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms
#     linux $linux_folder/BootModules/vmlinuz from=$iso $bootparms
     initrd (loop)/boot/syslinux/initrd.xz
#     initrd $linux_folder/initrd/initrd-20230923.xz
     }
 
menuentry " Porteus 5.01 ISO - AF "  --class slackware   --class user-icon-porteus  {

     set bootparms="volume=33 reboot=cold noload=mychanges;pipe;menu4"
#     set bootparms="volume=33 reboot=cold noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;mychanges;menu4" 

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms
#     linux $linux_folder/BootModules/vmlinuz from=$iso $bootparms
     initrd (loop)/boot/syslinux/initrd.xz
#     initrd $linux_folder/initrd/initrd-20230923.xz
     }


########                                                                                        ########
#
menuentry " Porteus 5.01 ISO - bkup 250404"  --class slackware   --class icon-imported  {

     # https://www.gnu.org/software/grub/manual/grub/grub.html#normal
     set Editnote="If you edit the iso name add normal to the end of the menu."

     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-240923.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-241211.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-250130.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-250404.iso"
     } 

#menuentry " Porteus 5.01 ISO - new 250404"  --class slackware   --class icon-imported  {
#
#     # https://www.gnu.org/software/grub/manual/grub/grub.html#normal
#     set Editnote="If you edit the iso name add normal to the end of the menu."
#
#     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-250404.iso"
#     } 
########                                                                                         ########


if [ -e (hd0,msdos1)/boot/syslinux/porteus.cfg ]; then
menuentry " Porteus USB - EFI" --class slackware   --class user-icon-usb  {

     set bootmgr=/EFI/boot/bootx64.efi          #grubx64.efi    # bootx64.efi

     set bootdrv=$root
     search -f $bootmgr --set=root
     echo USB: $root
     sleep -v -i 4
     if [ $root != $bootdrv ]; then
        chainloader $bootmgr
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }

menuentry " Porteus USB - AF'" --class slackware   --class user-icon-usb  {

     set bootparms="volume=33 reboot=cold extramod=/Modules noload=save.dat;myx"  #;cinnamon" # changes=EXIT:/changes/porteussave.dat"

     set bootdrv=$root
     search -f /boot/syslinux/vmlinuz --set=root
     if [ $root != $bootdrv ]; then
        linux  /boot/syslinux/vmlinuz $bootparms
        initrd /boot/syslinux/initrd.xz
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }
fi

menuentry " Porteus 5.1 alpha2 ISO - Cinnamon AF"  --class slackware   --class user-icon-porteus  {

     set linux_folder=/porteus5.1
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha-x86_64.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha2-x86_64.iso"
#     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha3-x86_64.iso"  
#     set iso="/ISOs/Porteus/Porteus-OPENBOX-v5.1-alpha3-x86_64.iso"   
     
     set bootparms="volume=33 reboot=cold noload=-test;myc;My;50save;Dell \ 
         extramod=$linux_folder/Modules " # ;$linux_folder/Optional/51Mods "

     search -f $iso --set=root
#    * Set hdX0 to hd0 for save.dat update *
     if [ "$root" == "hdX0,gpt4" ]; then
        set bootparms="volume=33 reboot=cold noload=-test;myc;My;save;Dell /
            extramod=$linux_folder/Modules " # changes=EXIT:$linux_folder/ " # changes/51save.dat " 
     fi
#    Other options: https://forum.porteus.org/viewtopic.php?t=569
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms # debug
     initrd (loop)/boot/syslinux/initrd.xz
     }

menuentry " Porteus 5.1 alpha3 ISO - Cinnamon AF"  --class slackware   --class user-icon-porteus  {

     set linux_folder=/porteus5.1
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha-x86_64.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha2-x86_64.iso"
     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha3-x86_64.iso"  
#     set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha3-20251011.iso" 
#     set iso="/ISOs/Porteus/Porteus-OPENBOX-v5.1-alpha3-x86_64.iso"  
     
     set bootparms="volume=33 reboot=cold noload=-test;myc;My;50save;Dell \ 
         extramod=$linux_folder/Modules " # ;$linux_folder/Optional/51Mods "

     search -f $iso --set=root
#    * Set hdX0 to hd0 for save.dat update *
     if [ "$root" == "hdX0,gpt4" ]; then
        set bootparms="volume=33 reboot=cold noload=-test;myc;My;save;Dell /
            extramod=$linux_folder/Modules " # changes=EXIT:$linux_folder/ " # changes/51save.dat " 
     fi
#    Other options: https://forum.porteus.org/viewtopic.php?t=569
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms # debug
     initrd (loop)/boot/syslinux/initrd.xz
     }

#menuentry " loopback tests" --class slackware --class user-icon-gnugrub {
#
#     search -f $iso --set=root
#     loopback loop $iso
#     echo "loop loaded"
#     ls
#     echo " "
#     ls (loop) 
#     echo "loop: " $loop 
#     loopback -d loop
#     echo " "
#    

As such, better kept off of EFI drive. Someplace off of the C: drive is even better if the C: ever needs to be restored.

[tpkusr]

Ed_P,
Hi
Today I successfully booted MX Linux from iso using your boot menu entry given at sourceforge.
Now I wonder how many Linux os you have booted from iso. I think the number is huge.

Can you share us some boot menu entry like Ubuntu, mint, debian so that many people can boot those os from iso.

Thanks
tpkusr

[Ed_P]

Best asked on the other forum tpkusr.

[Ed_P]

BTW EFI x64 Ubuntu's grub2 app doesn't support gnu grub2's limited bash commands.
At least on my system.

It only supports code that follows properly coded bash commands.

This is my current, working, Ubuntu grub2 grub.cfg file.

Code: Select all

set timeout=60

loadfont unicode

set gfxmode=800x600,auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm

set menu_color_normal=white/blue
set menu_color_highlight=black/light-gray

if [ -v linux_folder ]; then
   default=11
fi

menuentry ' Windows ' {
     search -f   /EFI/Windows/bootx64.efi --set=root
     chainloader /EFI/Windows/bootx64.efi
}
menuentry "--------" {
     exit 1
     }
menuentry ' Porteus ' {
     search -f     /grub2/userfiles/Edsconfigs.sh  --set=root
     source ($root)/grub2/userfiles/Eds.configs/Porteus5.0.cfg
}
menuentry ' PorteuX ' {
     search -f     /grub2/userfiles/Edsconfigs.sh  --set=root
     source ($root)/grub2/userfiles/Eds.configs/PorteuX.cfg
}
menuentry ' ISOs ' {
     search -f     /grub2/userfiles/Edsconfigs.sh  --set=root
     source ($root)/grub2/userfiles/Eds.configs/ISOmenus.cfg
}
menuentry "--------" {
     exit 1
     }
menuentry ' UEFI Firmware Settings' {
     fwsetup
}
menuentry "--------" {
     exit 1
     }
menuentry ' Reboot' {
     reboot
}
menuentry "============================" {
     exit 0
     }

The 1st time I have ever tested for the existence of a variable with a -v rather than a value.