UEFI MULTI - Make Multi-Boot USB-Drive

This is my first post here, so I hope I'm not asking something that's been answered a hundred times before...

Since I'm using Windows 8.1 my current boot method is UEFI.  I stumbled upon these forums while trying to find a way to put a number of different Linux OSes, my Windows 8.1, and some Rescue Utilities onto a 32gb USB.  

The USB drive I ended up with at the end of the process was not recognized by my UEFI.  It was, however, recognized by the CSM but in that situation none of the OSes I put onto the USB showed up!

Here's what I ended up doing, maybe when you look at my steps, you'll be able to tell me what happened and how I can fix it when I try again.

I downloaded UEFI_MULTI_85.exe from http://reboot.pro/fi...boot-usb-drive/.  When I opened the file, it used 7zip to auto-extract everything into a \UEFI-Multi\ folder.  That part I’m pretty sure I got right.  Since it’d be really difficult to do that wrong!  From there, I read the UEFI_MULTI_Help.txt file and though I understood how to use the software.  I inserted the USB drive I wanted to use and ran UFD_Format.exe and believe everything worked perfectly find there as well.  I then had what I think is a properly formatted FAT32 USB drive.

I then went into the \MULTI_BOOT\Images folder.  I put all the OS and Rescue ISOs I wanted to be available:

Windows:

Windows.8.1.blah.blah.blah.iso

Linux:

antergos-2015.04.12-x86_64.iso

archlinux-2015.06.01-dual.iso

Bella-OS-2.2-64bit.iso

black-lab-linux-2015_6-x86_64.iso

black-lab-linux-Xfce4.12-x64_86.iso

bridge-xfce-2014.02-x86_64.iso

chakra-2015.03-euler-x86_64.iso

chaletos14.04.2-feb2015-light-amd64.iso

deepin_2014.3_amd64.iso

elementaryos-freya-amd64.20150411.iso

handylinux-2.1.iso

KaOS-2015.06-x86_64.iso

kubuntu-15.04-desktop-amd64.iso

MakuluLinux-8-LxFce.iso

MakuluLinux-9-Aero-x64.iso

MakuluLinux-9-XfceLite-x64.iso

manjaro-kde-0.8.13-x86_64.iso

manjaro-xfce-0.8.13-x86_64.iso

maui-0.5.1-x86_64.iso

netrunner-16-dvd-64bit.iso

netrunner-rolling-2014.09.1-dvd-64bit.iso

Pinguy_OS_14.04.2-LTS-x86-64.iso

Solus-Beta2.iso

symphonyos-15.0_amd64.iso

wattOS-R9-64.iso

Rescue:

Hiren's.BootCD.15.2.iso

PING-3.02-WithAddons.iso

ubcd535.iso

In total, all of the above was just under 28gb.  Luckily, the USB drive I just formatted had 29gb available.

I then went back to the main UEFI_MULTI folder and ran UEFI_MULTI.exe as Administrator.  I told it that my USB Boot was D: (the USB drive I just formatted) and my System Drive was C: (where Windows 8.1 is currently installed, of course).  I kept the Copy to: Boot Drive option and told it that the Source Folder was \MULTI_BOOT\Images. 

At this point, I might have made the error by selecting all the available options:

✔ Add G4D to Boot Manager

✔ Add XP to Boot Manager

✔ Update MBR Boot Code

✔ Add Boot Win 7/8 System

✔ Update Grub4Dos gldr

✔ Grub 2 EFI Mgr

Should I not have selected everything?  If not, which of those options should I select, and which should I leave alone?

It did its thing and everything seemed fine when it finished.  But like I said at the beginning, when I rebooted my computer the UEFI did not detect the USB and went straight to Windows 8.1.  When I switched my BIOS to CSM, it did detect the USB, but nothing was selectable except for the default options such as editing the Grub4Dos menu.

What can you tell me about what I might have done incorrectly?  Is there anything that obviously jumps out at you?

Maybe someone can walk me through this process again so the next time I will be successful attempt to make a Multi-Boot USB with the above listed OSes and Rescue ISOs.

Thanks a lot!

〜 Ev

Hi. How i can edit created boot menu on USB after build manually? Thanks

@koesherbacon @Lukys

As you stated you thought anything went fine and the ' only ' obvious problem is that Windows 8.1 boots directly in UEFI-Mode without hesitating | showing up the BootMGR-Menu displaying other options

; Have a look at the BCD-Store on the drive you created by plugging in the FlashDrive on a running Windows NT 6+ System, means from Vista upwards ( in your case most likely Windows 8.1 ) and use an administrative Command Prompt to be sure to read out the BCD of the stick by using

: 

bcdedit /store U:\Boot\bcd /enum

: or use your already booted Windows 8.1, whereas you have to use the drive-letter of the system ; mostly

C: 

=INFO

bcdedit

: tool to manipulate the BootCode used by BootMGR

/Store

: Parameter ' Store ' followed by the path to the bcd-file you wish to read | edit

U:\Boot\BCD

: The path to the BCD-Store on your Flash-Drive

 U:

 --- Assuming you used drive-letter ' U ' ( e.g.: U for USB )

\Boot\

 --- Standard-Directory generated by ' bcdboot '-tool when using ' /f ALL ' or ' /f BIOS ' as Parameter for FirmWare-Type of Target-Partition

BCD

 --- Standard-Naming for the BCD-Store created by ' bcdboot '

; The ' Boot '-folder is a hidden- system- -folder so either you have to change your view-settings of Windows Explorer to show up hidden and system files or you just type the path ' <drive-letter>:\Boot\ ' ( e.g.: U:\Boot\ ) directly into the path-|adress- -bar to access the contents of it .

 /enum

 --- enumerates | lists the entries of the BCD-Store you are loading

; That's how you can get an insight of what really is inside , likewise to say you can check if other options have been stored by the script or not

; and if you you find out there are other entries , then you might wish to have a lookout for the options ' displaybootmenu' | ' displayorder ' | ' timeout '

= EXAM

:

Bezeichner              {bootmgr}
device                  partition=O:
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
default                 {default}
resumeobject            {7e05cdb8-3afa-11e5-975d-0022190d3ea7}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30


Windows-Startladeprogramm
-------------------------
Bezeichner              {default}
device                  vhd=[O:]\_ISO\AUTO\WIRT\BMWN63SC\BMWN63SC.vhd
path                    \Windows\system32\winload.exe
description             Hyper-V Server 2012 R2 (VHD)
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {a1c28fef-3ab4-11e5-8124-002264cbf2c3}
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                vhd=[O:]\_ISO\AUTO\WIRT\BMWN63SC\BMWN63SC.vhd
systemroot              \Windows
resumeobject            {7e05cdb8-3afa-11e5-975d-0022190d3ea7}
nx                      OptOut
hypervisorlaunchtype    Auto

bcdedit /set {bootmgr} displaybootmenu yes

--- if you use ' no ' instead of ' yes ' it will not show up .

=EXAM

--- after EDIT

Windows-Start-Manager
---------------------
Bezeichner              {bootmgr}
device                  partition=O:
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
default                 {default}
resumeobject            {7e05cdb8-3afa-11e5-975d-0022190d3ea7}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30
displaybootmenu         Yes


Windows-Startladeprogramm
-------------------------
Bezeichner              {default}
device                  vhd=[O:]\_ISO\AUTO\WIRT\BMWN63SC\BMWN63SC.vhd
path                    \Windows\system32\winload.exe
description             Hyper-V Server 2012 R2 (VHD)
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {a1c28fef-3ab4-11e5-8124-002264cbf2c3}
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                vhd=[O:]\_ISO\AUTO\WIRT\BMWN63SC\BMWN63SC.vhd
systemroot              \Windows
resumeobject            {7e05cdb8-3afa-11e5-975d-0022190d3ea7}
nx                      OptOut
hypervisorlaunchtype    Auto

=INFO

BCDEdit Command-Line Options

; For sure it can be told leaner , but maybe you / another reader is tickled enough to start having some fun by directly editing via a command-line instead of avoiding it and just hoping that scripts and tools do some automagical secret stuff ; the least is comfortable , but if i am using something that i do not understand i ( for myself ) at least like to know what has happened in the end .

=NOTE

--- for those that have gained interest in editing via command line and especially bcdedit

: If you wish to understand what options you have available and how they are used

bcdedit /?

--- general help

bcdedit /? /store

--- displays the help-information specific to the parameter ' /store '

HOPE IT HELPS .

THANKS FOR YOUR INTEREST .

S466531257 BOSS

PAETH CLAUDIUSRAPHAEL

Edited by S466531257BOSS, 05 August 2015 - 08:53 AM.

Well, on UEFI the BOOTMGR may not exist, since what is booted is bootmgfw.efi and the BCD is not in \boot\BCD but rather in \EFI\Microsoft\boot\BCD

Casually Misty recently published a very detailed guide/how to related to BCDediit and BCD stores:

http://reboot.pro/to...and-bcd-stores/

http://www.mistyrebo...Edit/index.html

Wonko

Greetings, I've come back to the tool now and need some things cleared:

If I intend build a drive booting on both BIOS and UEFI systems to :

-Win81SE

-Win 10 installation DVD

-Ubuntu ISO

-Parted Magic (and eventually other Linux-based ISOs)

-Hirens BootCD 15.2

-UBCD 5.3.5

-Paragon recovery ISO based on Win10PE

-Macrium Reflect ISO based on Win8PE

Where all the ISO's (except Win81SE) should be defined?

Does UEFI_MULTI give another option except grub4dos?

Now I tried to perform UEFI_FORMAT on empty USB stick. getting some internal app error (using default presets)

Is it OK to format using standard Windows formatting tool?

If I intend build a drive booting on both BIOS and UEFI systems to :

-Win81SE

 

Now I tried to perform UEFI_FORMAT on empty USB stick. getting some internal app error (using default presets)

Is it OK to format using standard Windows formatting tool?

In what OS environment did you use UFD_FORMAT.exe  and what is exactly the error that you get ?

Does it help when you Uncheck Make Boot Menu ? What type of USB-Stick did you use (is it a removable drive) ?

For Win81SE Builder take care in Build > CdDrive - X: Y: to Select Run ALL Programs from RAM

In UEFI_MULTI Select boot.wim file and boot.sdi file as described http://reboot.pro/to...ve/#entry168079

You use wim booting which is compatible with BIOS and UEFI BootManager menu and you don't use ISO booting.

Win10 Setup ISO is Not installed, but is simply copied to NTFS Drive (can be internal harddisk or second / third partition of portable USB-harddisk - advised for this purpose).

All Windows Setup ISO's can be used by WinNTSetup3 as described http://www.msfn.org/...nntsetup-v3853/

Grub4dos booting is not compatible with UEFI

In case of 8PE and 10PE it is better to use the WIM file for booting from BootManager Menu in BIOS and UEFI.

Grub2 can be used for booting Ubuntu and PartedMagic in UEFI http://reboot.pro/to...ve/#entry168079

UBCD 5.3.5 can be booted in BIOS grub4dos menu as ISO (copied by UEFI_MULTI to USB boot drive).

getting this error 

AutoIt Error

Line 7209  (File "G:\Deposit\Win_Uefi_Multi\UEFI_MULTI.exe"):

Error: Subscript used with non-Array variable.

https://imgur.com/Y2gJmrJ

using win7 x64 sp1

with various settings, same error

https://imgur.com/Y77X1pA

UEFI_MULTI_85.exe is reported as broken.

However, it is a false positive virus warning due to using a SFX Selfextractor !!

So I removed the SFX Selfextractor and simply use zip compression so that the problem is gone.

Download UEFI_MULTI-85.zip from

http://reboot.pro/fi...boot-usb-drive/

and best wishes for 2018

UEFI_MULTI_85.exe is reported as broken.

However, it is a false positive virus warning due to using a SFX Selfextractor !!

 

So I removed the SFX Selfextractor and simply use zip compression so that the problem is gone.

 

Download UEFI_MULTI-85.zip from

 

https://1drv.ms/f/s!...na78xaVPrpcR2sA

 

and best wishes for 2018

@ wimb

When trying to download it says: One drive has detected UEFI_MULTI-85.zip has a virus and stoped the download.

I'm sure it is clean, as I have downloaded and used your Great Tool in the past, so to avoid this I suggest you may use a 7zip high compressed file with password to avoid this false detection.

Thanks in advance

@ wimb

 

When trying to download it says: One drive has detected UEFI_MULTI-85.zip has a virus and stoped the download.

 

I'm sure it is clean, as I have downloaded and used your Great Tool in the past, so to avoid this I suggest you may use a 7zip high compressed file with password to avoid this false detection.

 

Thanks in advance

Hi alacran,

Thanks for reporting the security problem of OneDrive in case of UEFI_MULTI-85.zip

I followed your advice and have uploaded the 7-zip compressed file with password bootwimb85

wimb

Well, if you click (clicked) on the top left "Download" you obtain (could obtain) a "Forum.zip" file containing the UEFI_MULTI-85.zip (the same that provoked the stupid antivirus block)  just fine.

You should contact OneDrive, it seems like a "quirk".

Putting a password to the whole file will likely make the file unusable in the future (when people will have forgotten or misplaced the password, etc., etc.) , unless you put a non-encrypted file within the archive with the actual password or provide a plain text file with the password on the same OneDrive folder.

Wonko

Well, if you click (clicked) on the top left "Download" you obtain (could obtain) a "Forum.zip" file containing the UEFI_MULTI-85.zip (the same that provoked the stupid antivirus block)  just fine.

 

You should contact OneDrive, it seems like a "quirk".

 

Putting a password to the whole file will likely make the file unusable in the future (when people will have forgotten or misplaced the password, etc., etc.) , unless you put a non-encrypted file within the archive with the actual password or provide a plain text file with the password on the same OneDrive folder.

 

Wonko

Thanks for your help.

I have added to the OneDrive folder a plain text file with the password

Please refresh and try again the download link http://reboot.pro/fi...boot-usb-drive/

@ wimb

Just to report download is working fine, with the password no more problems, it was good idea to add a text file with the password, but for future uploads I recomend using as password your user/author name (wimb), this is easy to remember and applicable to all your uploads.

In fact I have a folder (wimb) on my HDD, with almost all your tools, but haven't updated it in a long time (It had Uefi Multi 81), and as I am updating my USB sticks wanted to update the tools too.

Once again, thanks for your Great tools.

alacran

Meh. 

Attached example.

Wonko

If you read this, you have decrypted me.

@Wonko

I took the second of your proposals by adding to the OneDrive folder a plain text file with the password.

From your reply I understand that you prefer the first of your proposals ....   

If you read this, you have decrypted me.

 

@Wonko

 

I took the second of your proposals by adding to the OneDrive folder a plain text file with the password.

 

From your reply I understand that you prefer the first of your proposals ....   

The point only revolves on how much foolproof can a solution be, suggestions were provided in my personal order of likeness to be foolproof.

As Douglas Adams stated:

 

A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.

Questions:

1) Would a common user actually attempt to open a file called ReadMe.1st or ReadMe.txt? 

2) Would a common user actually always download AND store (and move/backup/etc.) the "password file" alongside with the actual encrypted archive?

Answers:

1) Not necessarily, often he/she will post here or somewhere else whining about the archive being password protected and that the password cannot be found anywhere.

2) Not necessarily, often he/she will post here or somewhere else whining about the archive being password protected and that the password cannot be found anywhere.

What will be the average reply by an old, grumpy bastard to the whining?

1) Too bad you didn't also download the password file. Go to the download page and download it <- i.e. maybe there is a solution (or may be there isn't because in the meantime the download is not anymore available)

2) Just §@ç#ing read the ReadMe.1st inside the archive. <- i.e. an easy solution is not only available, but actually "embedded"

Decisions, always decisions ....

Wonko

Well then I combine both options so that the chance of loosing the password file is completely removed 

So the encrypted file UEFI_MULTI-85.zip together with the password file UEFI_MULTI-85.pw.txt are zipped in a new container UEFI_MULTI_85.zip

Download UEFI_MULTI_85.zip http://reboot.pro/fi...boot-usb-drive/

Well then I combine both options so that the chance of loosing the password file is completely removed 

Very good .

Wonko

Do you make UFD_Format and UEFI_Multi both?

Can any cmd line flags be used for the tool?

Im trying to automate burning a simple PE ISO to a USB with 2 partition format (minimal fat32/max NTFS) then copying the WIM and bootfiles to the fat32 ->without<- a boot menu, followed with the remaining files from the ISO being copied to the NTFS partition...

It sucks theres nothing as simple as Rufus that does this..

Your tool is awesome and can easily do this but its all manual and are more like advanced options than simple...  You could dethrone Rufus in a heartbeat with a 1 click Legacy/UEFI boot USB burner especially if you just pick an ISO and it goes in and finds the WIM for you, and ignores the boot files in the ISO, and hide the advanced options in a submenu to keep your features... (This works great with a marker file on the NTFS partition, like CDDrive X Y plugin for PE SE version that assigns the letter Y to the USB, this makes it super easy for this setup to work)

I have it working but I have to go in and remove the boot menu afterwards(I just set boot-wim to defaut with EasyBCD then skip the timer for both bcds)

Before that I was unsuccessfully trying to select the UFD format created Fat32 partition as the boot partition, then picking the WIM, and  selecting the NTFS partition as the system partition? Then picking "copy to" and "system" and picking the extracted folder from the ISO containing only the files I wanted on the system partition from the but I get an error, maybe I was using it wrong.  But I can manually get the same effect...

Amazing work...

Edited by bob.omb, 22 May 2018 - 02:09 AM.

How to use WinNTSetup with Microsoft USB Boot Media

==  == 

ShowHidden.reg can be used with double click in Explorer++ after booting with Microsoft USB Media

Windows Registry Editor Version 5.00

; Show all hidden files
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"SuperHidden"=dword:00000001
"WebViewBarricade"=dword:00000001
"Hidden"=dword:00000001
"ShowSuperHidden"=dword:00000001

; Show all file extentions
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"HideFileExt"=dword:00000000

FWIW I found a way to multi-boot a Linux system on a Secure Boot UEFI system.  I installed Porteus on a USB drive and it supported booting on BIOS and UEFI systems but Secure Boot had to be disabled for UEFI, which is fine if you own the pc or you can change it's configuration.  But this is not always permitted or possible on some machines.

The solution I found was to add Ubuntu's grub2 files to the USB drive.  Ubuntu's grub2 supports Secure Boot.

This is the bash script I used to copy the Ubuntu grub2 file from a live Ubuntu ISO to the USB system.

#!/bin/bash
# Add Ubuntu grub2 Secure Boot support to Porteus USB system.
 
UbuntuISO=/mnt/sda6/ISOs/ubuntu-18.04.1-desktop-amd64.iso    # Change to fit your system
USBdrv=/mnt/sdb1                                             # Change to fit your system
 
if [ `whoami` != "root" ]; then
   echo -e "Enter root's password"
   su -c "sh $0 $1"
   exit
fi
if [ ! -f $USBdrv/USB_INSTALLATION.txt ]; then               # Change to fit your system
   echo "Porteus USB drive not found."
   read
   exit
fi
if [ ! -f $UbuntuISO ]; then
   echo "Ubuntu ISO not found."
   read
   exit
fi
mloop $UbuntuISO
#read
mv $USBdrv/EFI/boot              $USBdrv/EFI/Porteusboot           # Backup Porteus EFI
mkdir                            $USBdrv/EFI/BOOT
mkdir                            $USBdrv/boot/grub
cp -ar /mnt/loop/EFI/BOOT/*      $USBdrv/EFI/BOOT/
cp -ar /mnt/loop/boot/grub/*     $USBdrv/boot/grub/
mv $USBdrv/boot/grub/grub.cfg    $USBdrv/boot/grub/Ubuntugrub.cfg  # Backup Ubuntu grub.cfg
echo " "
echo "Now add the posted grub.cfg file to the $USBdrv/boot/grub/ folder."
echo "Customize the new grub.cfg's porteus_parms in the Secure Boot menu."
echo " "
read
ls  $USBdrv/EFI/BOOT
ls  $USBdrv/boot
ls  $USBdrv/boot/grub
cat $USBdrv/boot/grub/grub.cfg
uloop

And the grub2 cfg file I used is:

if loadfont /boot/grub/font.pf2 ; then
# set gfxmode=auto
set gfxmode=800x600,auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
fi
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
set timeout=60
set gfxpayload=1024x768

menuentry " 1. Porteus 4.0 - UEFI Secure Boot" {
    
     set porteus_parms="volume=33 reboot=cold extramod=/Modules;/Modsavedat noload=save.dat;cinnamon" # Change to fit your system needs
     set bootdrv=$root
     search -f /boot/syslinux/vmlinuz
     if [ $? == 0 ]; then
        linux  /boot/syslinux/vmlinuz $porteus_parms
        initrd /boot/syslinux/initrd.xz
     else
        echo "----------------------------------------"
        echo Porteus drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }
menuentry " 2. Porteus 4.0 menu - UEFI system" {
     set efibootmgr=/EFI/Porteusboot/bootx64.efi
     set bootdrv=$root
     search -f $efibootmgr
     if [ $? == 0 ]; then
        chainloader $efibootmgr
     else
        echo "----------------------------------------"
        echo Porteus drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }
menuentry " 3. Porteus 4.0 menu - BIOS system" {
     set bootmgr=/boot/syslinux/chain.c32
     set bootdrv=$root
     search -f $bootmgr
     if [ $? == 0 ]; then
        chainloader +1
     else
        echo "----------------------------------------"
        echo Porteus drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }
menuentry " " { echo }
menuentry " 4. Reboot" {
     reboot
     }

This approach may work with other USB installed Linux systems. 

I found the Ubunto ISO from here:  https://duckduckgo.c...o&t=ffcm&ia=web

ERROR!! When I try booting my Porteus USB drive with the Ubuntu Grub2 on it like posted above on a x86_64 non-UEFI machine it fails to boot.

Initially it failed because it couldn't find a normal.mod file in a /boot/grub/i386-pc folder! Since the machine is x86_64 that was a little strange and if required why isn't in the ISO. My Grub2Win system has an i386-pc folder so I copied it to the USB drive. Now when the Porteus USB drive boots on the non-UEFI machine, and on an older x486 machine, it boots to a GNU GRUB version 2.02 terminal screen stating Minimal BASH-line editing is supported and a grub> prompt. Why it's not finding the grub.cfg it finds when booting on my UEFI machine I have NO IDEA.

Any ideas?

I have added AIOBoot-v0.9.8.17.7z to my USB-stick booting with BootManager as described in Win_Inst_Eng.pdf as given here.

I did not auto install new Bootloader, but kept my Windows BootManager as Bootloader.

I am using Linux Mint files bootx64.efi and grubx64.efi in EFI\BOOT folder for support of UEFI Secure booting.

In file Main.cfg of folder boot\grub make new boot entry for UEFI booting of Windows BootManager

menuentry "[b] Windows 10 x64 EFI USB BootManager" --hotkey=b {
  chainloader /efi/microsoft/boot/bootmgfw.efi
}

I have used BOOTICE to add Grub2 entry to boot\bcd Windows BootManager for BIOS booting support with Boot file \AIO\grub\grub2win

Then I have used AIOCreator.exe to Integrate Linux ISO files.

Now I have Linux Mint and Knoppix Live and Porteus and Ubuntu booting in BIOS and in UEFI Secure mode

YouTube Video: USB AIO Linux

==  ==  ==  == 

The grub2.cfg menu file I've ended up with for booting Porteus with Secure Boot enabled and disabled is this:

if loadfont /boot/grub/font.pf2 ; then
# set gfxmode=auto
set gfxmode=800x600,auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
fi
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
set timeout=60
set gfxpayload=1024x768

menuentry " 1. UEFI Porteus 4.0 system - for Secure Boot enabled" {
    
     set efibootmgr=/EFI/boot/grubx64.efi
     set porteus_parms="volume=33 reboot=cold extramod=/Modules;/Modsavedat noload=save.dat;cinnamon"
#    Change parms to fit your needs.
     set bootdrv=$root
     search -f $efibootmgr
     if [ $? == 0 ]; then
        linux  /boot/syslinux/vmlinuz $porteus_parms
        initrd /boot/syslinux/initrd.xz
        echo " "
        echo " -> "
        echo " -> If /boot/grub/x86-64-efi errors appear, disregard."
        echo " -> Secure Boot has not been enabled."
        echo " -> "
        sleep -i 4
     else
        echo "----------------------------------------"
        echo $efibootmgr NOT found.
        echo
        sleep -i 10
     fi
     set root=$bootdrv
     }
menuentry " 2. UEFI Porteus 4.0 menu - aborts if Secure Boot enabled" {
     set efibootmgr=/EFI/Porteusboot/bootx64.efi
     set bootdrv=$root
     search -f $efibootmgr
     if [ $? == 0 ]; then
        chainloader $efibootmgr
        echo " "
        echo " -> "
        echo " -> If /boot/grub/x86-64-efi errors appear, disregard."
        echo " -> "
        sleep -i 4
     else
        echo "----------------------------------------"
        echo $efibootmgr NOT found.
        echo
        sleep -i 10
     fi
     set root=$bootdrv
     }
menuentry " " { echo }
menuentry " 3. Reboot" {
     reboot
     }
menuentry " 4. Shutdown" {
     halt
     }
menuentry " " { echo }
menuentry " Notes" {
     echo
     echo "To switch the USB drive's boot mode to BIOS mode "
     echo "run the BIOSboot.sh script in the /EFI directory."
     echo
     echo "To switch the USB drive boot mode back to EFI mode"
     echo "run the Secureboot.sh script in the /EFI directory."
     echo
     sleep -i 10
     }

No folders added other than the Ubuntu grub folders that the script above copies to the USB drive.

Two small scripts were added to the /EFI folder.  These are optional for testing the boot options.  

Secureboot.sh

#!/bin/sh
# Switch standard Porteus boot config to UEFI Secure Boot config.
USBdrv=/mnt/sdb1   # USB drive
if [ -d $USBdrv/EFI/UbuntuBOOT ]; then
   mv $USBdrv/EFI/boot         $USBdrv/EFI/Porteusboot
   mv $USBdrv/EFI/UbuntuBOOT   $USBdrv/EFI/boot
else
   echo "  UEFI Secure Boot config already in place."
fi

BIOSboot.sh

#!/bin/sh
# Switch UEFI Secure Boot config to standard Porteus boot config.
USBdrv=/mnt/sdb1   # USB drive
if [ -d $USBdrv/EFI/Porteusboot ]; then
   mv -f $USBdrv/EFI/boot         $USBdrv/EFI/UbuntuBOOT
   mv -f $USBdrv/EFI/Porteusboot  $USBdrv/EFI/boot
else
   echo "  Porteus boot config already in place."
fi

So the system works on both Secure Boot and disabled Secure Boot systems.  But it's not as clean as I would like.

So I've been working with trying to get the automatic switching mode code to work again.  And it still doesn't work in Secure Boot mode..

if loadfont /boot/grub/font.pf2 ; then
# set gfxmode=auto
set gfxmode=800x600,auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
fi
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
set timeout=60
set gfxpayload=1024x768
set SB=0
set efibootmgr=/EFI/Porteusboot/bootx64.efi
set porteus_parms="volume=33 reboot=cold extramod=/Modules;/Modsavedat noload=save.dat;cinnamon"
#  Change parms to fit your needs.

insmod /boot/grub/x86_64-efi/cat
if rmmod -v cat; then set SB=1; fi
#echo SB=$SB; sleep -v 8
if [ $SB == 1 ]; then
   linux  /boot/syslinux/vmlinuz $porteus_parms
   initrd /boot/syslinux/initrd.xz
   boot
   exit
fi
chainloader $efibootmgr
boot
exit

The "home" missing error I was getting previously was due to no home.mod module in the /boot/grub/x86_64-efi folder.  So I changed the name to a file that does exist.  But the various config options I tried with insmod and rmmod failed.  One senario was the Secure Boot code was being executed in both Secure Boot and disabled Secure Boot mode.  Not a bad scenario, just not the desired scenario.

guest@porteus:~$ tree /mnt/sdb1 -d
/mnt/sdb1
├── EFI
│   ├── Porteusboot
│   └── boot

├── boot
│   ├── docs
│   ├── grub
│   │   └── x86_64-efi
│   └── syslinux
├── changes
└── porteus
    ├── base
    ├── modules
    ├── optional
    └── rootcopy

Edited by 911CD.net, 29 November 2018 - 07:17 PM.