Jump to content











Photo
* * * * * 1 votes

UEFI MULTI - Make Multi-Boot USB-Drive

aio boot linux vhdx windows 10 wim ssd uefi usb multiboot

Best Answer wimb , 11 May 2020 - 12:18 PM

Update USB_FORMAT-51 and UEFI_MULTI-51

 

Download:  from wimb GitHub  -   USB_FORMAT-51 and UEFI_MULTI-51  and  VHD_WIMBOOT-41 and Win_Reduce_Trusted-40

 

Download File E = Encrypted Password = bootwimb

 

Manual:  VHD_WIMBOOT.pdf  and  Win10_Install.pdf  to make Mini 7/8/10 x64 in VHD with UsedSize about 2 GB

 

At MSFN there is topic USB Format Tool and UEFI_MULTI

 

All my projects are now available for Download as Releases at wimb GitHub

 

Download:  USB_FORMAT  and   UEFI_MULTI  and  VHD_WIMBOOT  and WOF_Compress and  System_Info  and  MBR_Backup

 

More Info:  VHD_WIMBOOT Mini 7/8/10 x64  and   Grub4dos for UEFI  and USB_FORMAT Tool and UEFI_MULTI

 

:cheers:

Go to the full post


  • Please log in to reply
262 replies to this topic

#1 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 18 February 2013 - 06:23 AM

Posted Image

File Name: UEFI MULTI - Make Multi-Boot USB-Drive
File Submitter: wimb
File Submitted: 18 Feb 2013
File Updated: 03 Aug 2021
File Category: Boot tools

Download Encrypted with password for UEFI_MULTI-XX-E.zip is bootwimb
Use R-mouse 7-zip menu to Extract here

-
Download: USB Format Tool and UEFI_MULTI at wimb GitHub
-
More Info: at MSFN Forum in USB Format Tool and UEFI MULTI

-
More Info: Install Windows 10 from USB after booting with WIM or VHDX and UEFI_MULTI
-
Unattended: Attached File  Unattended_Eng.zip   3.69KB   52 downloads
-
YouTube Video: Make VHDX and Make USB Win10 and Make USSD Win10 and USB AIO Linux and UEFI_MULTI-Demo

USB Format Tool - Make Bootable USB Drive with MBR and 2 Partitions
USB Multi-Boot of Linux ISO + Windows 10 VHD + Win10XPE in BIOS Or UEFI Secure mode

1 - Format USB Drive with MBR and 2 Partitions = Active FAT32 + NTFS
2 - UEFI_MULTI can Add VHD or PE WIM File Booting from RAMDISK
3 - Copy Linux ISO files to folder images on FAT32 - Boot UEFI Grub2 and BIOS Grub4dos
4 - USB drive Booting with Windows Boot Manager Menu in BIOS or UEFI Mode

=========================================
Linux ISO Info:
UEFI Secure boot support requires Format Drive using Mint UEFI Or Super UEFI as Grub2 Manager
Copy your Linux ISO files to folder images on FAT32 USB Boot drive U-BOOT

Supported filenames for Linux ISO in folder images are:


linuxmint.iso and kali-linux.iso
runtimelivecd.iso and knoppix.iso
ubuntu.iso and Porteus.iso


Download: Linux-Mint and Knoppix-Live and Ubuntu and Porteus x86_64
and Kali 64-bit Live

Rename your Linux ISO files so that they correspond to supported filenames

UEFI mode - Mint UEFI Grub2 booting with FAT32 file \EFI\Boot\BOOTx64.EFI and \Boot\grub\grub.cfg and \Boot\grub\grub_Linux.cfg

UEFI mode - Super UEFI Grub2 booting with FAT32 file \EFI\Boot\BOOTx64.EFI and \grub\grub.cfg and grub_Linux.cfg Menu
MBR BIOS - a1ive Grub2 installed in MBR booting with \grub\grub.cfg and grub_Linux.cfg Menu

Grub4dos is used for booting in MBR BIOS mode using Menu created with menu.lst and menu_Linux.lst

In case UEFI Grub2 is not available as Boot option in your F8 Boot Menu then you need to use BOOTICE to Add UEFI entry.
Unneeded for USB-Stick, but UEFI Grub2 boot entry is easily lost in case of Portable SSD.
Select as UEFI Boot entry the Linux Mint Grub2 file \EFI\Boot\BOOTx64.EFI

UEFI_Grub2.png
=========================================
a1ive Grub2 File Manager Info:
Not needed since booting straight with Linux ISO using Grub4dos in BIOS mode and Grub2 in UEFI mode is preferred.
But if you prefer support of a1ive Grub2 File Manager - Download Addons at wimb GitHub

Use R-mouse 7-zip menu to Extract here will Add the content of addon to existing folder and confirm Overwrites with yes

In x64 program use Super UEFI as Grub2 Manager setting for support of a1ive Grub2 File Manager
In this way the files of a1ive Grub2 File Manager and Super-UEFIinSecureBoot-Disk_minimal_v3 (more info) are Added to the USB Multi-Boot Drive


=========================================
How to Boot from USB with AIO Boot
- USB_FORMAT - Format USB Drive with MBR and 2 Partitions = Active FAT32 + NTFS
- Download AIOBoot-v0.9.9.8.7z - Unpack and Copy content of folder AIOBoot-v0.9.9.8 to USB FAT32 and overwrite existing UEFI Boot files
- On USB run AIOCreator.exe - Select Integration Linux OS and your Linux ISO
- UEFI_MULTI will Keep AIO UEFI files and Add a1ive Grub2 File Manager to AIO\grubfm and Add Boot Manager entry \AIO\grub\grub2win
=========================================
UEFI_MULTI - Make Multi-Boot USB-Drive
=

=
Win8.1SE x64 boot.wim of size 400 MB is Universal WIM Boot Image file for booting BIOS and UEFI computers
Thanks to ChrisR for making Win8.1SE - http://www.msfn.org/...170546-win81se/

Click here to download this file
  • indigo5 and Luckyone like this

#2 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 18 February 2013 - 07:11 AM

================================================================================

*** UEFI MULTI - Make Multi-Boot USB-Drive ***

Booting with Boot Manager Menu and using Boot Image files - VHD IMG ISO and WIM

================================================================================

UEFI_MULTI.exe is program to make Multi-Boot USB-Drive to boot computers having BIOS or UEFI firmware

Run UEFI_MULTI and Extract to simple path

 

In Win 7/8 OS Set User Account Control Off and Reboot
For UEFI Boot support then Windows 8x64 or 10x64 is needed as operating system

 

More Info including Windows 10 is here http://www.msfn.org/...comment=1120509

and http://reboot.pro/to...multi/?p=168077
and http://reboot.pro/to...t-usb-harddisk/

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

 

The zip file is protected with password bootwimb

UEFI_MULTI - Make Multi-Boot USB-Drive


=
================================================================================

Section 1. - Prepare FAT32 USB-Stick Or MBR USB-Harddisk for Booting with Boot Manager Menu

 

In Win 7/8 OS Set User Account Control Off and Reboot
For UEFI Boot support then Windows 8x64 or 10x64 is needed as operating system

================================================================================

UFD_FORMAT.exe - Tool to format USB-stick for Booting with Boot Manager Menu on BIOS or UEFI computer

 

Use UFD_FORMAT in 7/8/10 OS to format USB-Stick with FAT32 and for Booting with Boot Manager Menu
For fast booting into RAMDISK then USB 3.0 is advised e.g. use Kingston 100G3 32 GB

More Info - http://reboot.pro/to...140-ufd-format/

 

FAT32 has size limit of 32 GB for Windows Format -
Use 2nd Partition checkbox when USB-stick has size more than 32 GB, so that first Partition size is below the limit of 32 GB 
 

================================================================================

Or Prepare USB-Harddisk to have MBR and 3 Primary partitions

 

More info on using DiskPart script is here http://www.msfn.org/...comment=1120509

Preferred is to use Portable USB-harddisk e.g. Western Digital 500 GB Elements SE 2.5" Or Samsung Portable S2

Prepare USB-Harddisk to have MBR and 3 Primary partitions
- Boot partition - Primary with FAT32 Format and Size e.g. 20 GB - Set Active
- System partition - Primary with NTFS Format and Size e.g. 100 GB
- Data partition - Primary with NTFS Format and Size e.g. rest of USB-harddisk

Use of the 3 partitions will be
- Boot FAT32 - for Boot files and Win8.1SE x64 boot.wim file and with folder images for ISO and other small Boot Image files
- System NTFS - for Win 7/8/10 VHD files and for Portable XP VHD running Life from USB
- Data NTFS - for PStart folder with Portable Apps and for all Windows Setup ISO files used by WinNTSetup3 to Install Windows on local harddisk

 

================================================================================

 

Section 2. - Prepare Boot Image files - 8.1SE x64 WIM or 8.1 x64 VHD Or IMG Or ISO file

 

More Info on how to make Win10PE and Win8.1SE wim files is found here

http://www.msfn.org/...comment=1120509

 

Download Win8.1SE from http://www.msfn.org/...170546-win81se/

Download Win 8.1 Enterprise Evaluation ISO from http://technet.micro...r/hh699156.aspx
9600.16384.WINBLUE_RTM.130821-1623_X64FRE_ENTERPRISE_EVAL_EN-US-IRM_CENA_X64FREE_EN-US_DV5.ISO

Use imdiskinst.exe to Install ImDisk driver (if not present already).
Mount 8.1 x64 Setup ISO file in ImDisk Virtual drive - use Menu via R-mouse on ISO file

Run Win81SE82_Builder.exe - Select Source Drive with mounted ISO and use Play to make Win8.1SE x64 boot.wim
In UEFI_MULTI.exe you will use boot.wim in ISO\WIM\sources and file boot.sdi from folder ISO\WIM\Boot

 

Additional Info for making other Boot Image files:
The XP/7/8 Mini Windows VHD's of 1.2 - 2.5 GB are loaded from USB into RAMDISK and can be made according to
http://reboot.pro/to...ct-make-mini-8/
http://reboot.pro/to...ct-make-mini-7/
http://reboot.pro/to...tall-xp-in-vhd/
http://reboot.pro/to...t-make-mini-xp/


================================================================================

Section 3. - UEFI_MULTI.exe is used to make Multi-Boot USB-Drive

0. Connect USB-Drive and start computer with Windows 7/8/10 - x64 OS version
1. Run UEFI_MULTI.exe
2. Select USB Target Boot Drive - FAT32 needed for UEFI support
3. Select USB Target System Drive (for USB-Stick use same as Boot Drive)
4. Select Boot Image File - Win8.1SE x64 - Select boot.wim in ISO\WIM\sources
VHD is Copied always to NTFS System Drive - WIM and ISO are copied to FAT32 Boot Drive
5. Click GO to make Multi-Boot USB-Harddisk
6. You can use UEFI_MULTI.exe several times to Add more Boot Image files or to Add extra Source Folder content
Option to Select Source Folder UEFI_MULTI\MULTI_BOOT for Copy to Boot Drive
 

== ==

 



BOOT_IMG can make Grub4dos Menu on Boot Drive for VHD Image Files copied to Target System Drive.
Fix XP or Win 7/8 VHD for booting from USB-drive by using USB_XP_Fix.exe or USB_W78_Fix.exe

 

More Info for Install of Windows:

http://www.msfn.org/...comment=1120509

 

Download Media Creation Tool and use it to make USB-stick bootable in UEFI mode with Setup for Win10_x64

or to make Win10_x64 ISO file that can be used with WinNTSetup for install of Windows 10 on existing GPT partioned harddisk.

https://www.microsof...nload/windows10

 

You can Install Win10 x64 direct in 25 GB VHD located on NTFS partition of portable USB-harddisk having MBR and FAT32 boot drive.
 

After booting with WinPE from USB, then use WinNTSetup_x64.exe

and Win10_x64 ISO file to prepare VHD or internal GPT partitioned harddisk drive for Install of Windows 10 x64

http://www.msfn.org/...inntsetup-v386/

 

After booting from USB you can use portable App WinNTSetup to mount the Setup ISO in ImDisk Virtual Drive.
WinNTSetup will prepare local harddisk for Install of XP/7/8/10 

 

================================================================================

Section 4. - UEFI Secure Boot - Multi-Boot of Linux Fedora-18 + Windows 8 from USB-harddisk (option)

Download Fedora-18-x86_64-Live-Desktop.iso from http://fedoraproject.org/get-fedora
Download and use liveusb-creator-3.11.7-setup.exe from https://fedorahosted...iveusb-creator/
Info http://docs.fedorapr..._USB_Media.html

First prepare Fedora 18 LIVE USB-stick with files vmlinuz0 and initrd0.img from isolinux copied to folder LiveOS
and using in grub.cfg the commands linuxefi and initrdefi and root=live:LABEL=LIVE

Then prepare Multi-Boot of Fedora-18 + Windows 8 from USB-harddisk as follows.

 

Add Grub2 EFI Boot Manager for UEFI booting of Linux Fedora-18 or Parted Magic

In UEFI_MULTI.exe use Add Grub2 EFI Boot Manager for UEFI booting of Linux Fedora-18 or Parted Magic
Existing file /efi/boot/bootx64.efi of Windows 8/10 is renamed as 8bootx64.efi to enable Multi-Boot of Win8/10 and Linux.
Folder efi with Fedora-18 Secure Boot files is copied from UEFI_MAN to USB Boot Drive.

Fedora-18 Secure Boot files efi\boot\BOOTX64.efi and efi\boot\grubx64.efi are used
and we use Fedora vmlinuz0 and initrd0.img in LiveOS folder of Fedora-18 copied to USB Boot Drive.
The name of the USB Boot Drive with LiveOS folder must be specified and is in my case 2_BOOT

efi\boot\grub.cfg

 

set timeout=10

set default=0

menuentry 'Fedora-18 LIVE USB 2_BOOT' --class fedora --class gnu-linux --class gnu --class os {
linuxefi /LiveOS/vmlinuz0 root=live:LABEL=2_BOOT ro rd.live.image rhgb 
initrdefi /LiveOS/initrd0.img
}

menuentry "Parted Magic 64" --class gnu-linux --class gnu --class os {
  linuxefi /pmagic/bzImage64
  initrdefi /pmagic/initrd.img
}

menuentry "Windows 8 x64 EFI" {
  chainloader /efi/boot/8bootx64.efi
}

 

Windows 8/10 should NOT be default.

For booting Parted Magic Linux it is needed to copy pmagic folder to USB Boot Drive and in UEFI to Disable Secure Boot

Booting in BIOS mode with Fedora LiveOS folder on USB partition with LABEL 2_BOOT
then we can use Grub4dos with entry in menu.lst

menu.lst

 

title Fedora-18 LIVE USB 2_BOOT

find --set-root /LiveOS/vmlinuz0
kernel /LiveOS/vmlinuz0 root=live:LABEL=2_BOOT ro rd.live.image quiet rhgb 
initrd /LiveOS/initrd0.img

 

rhgb = redhat graphical boot - This is a GUI mode booting screen with most of the information hidden

quiet = hides the majority of boot messages before rhgb starts. These are supposed to make the common user more comfortable.

================================================================================

 

After the introduction of Windows 8 in september 2012, then new computers with Windows 8 or 10 are characterized 

by having a GPT partitioned harddisk booting in UEFI secure mode through efi folder on hidden FAT32 boot drive.

XP is not compatible with GPT partitioning and is not compatible with UEFI boot mode.

 

XP can be used on such computers by booting in BIOS mode with grub4dos from FAT32 USB-stick

and using XP installed in VHD located on NTFS partition of second internal MBR patitioned harddisk.

 

Install of XP in VHD is described here

http://reboot.pro/to...tall-xp-in-vhd/

 

- Install of XP or Windows 7/8/10

1. Boot from USB or from Network with Win8.1SE x64 boot.wim selected in Boot Manager Menu
2. Use portable App WinNTSetup_x64.exe and click tab - Windows XP or Windows 7/8
3. Select Installation files - Use R-mouse to mount XP/7/8 Setup ISO file in ImDisk Virtual Drive
4. Select Boot and Installation (Target) Drive for Install of XP/7/8/10
5. Quick Format Target Drive via F or via R-mouse menu in My Computer - use NTFS FileSystem
6. WinNTSetup3 - Setup will prepare Target Drive of local harddisk for Install of XP/7/8/10
7. Reboot from Target Drive and Install XP/7/8/10
8. Open Device Manager via R-mouse on My Computer
9. Install missing drivers XP/7 by using extracted DriverPacks

Win8.1SE - http://www.msfn.org/...170546-win81se/
UEFI_MULTI - http://reboot.pro/to...t-usb-harddisk/
Tiny PXE Server - http://reboot.pro/fi...iny-pxe-server/
PXE wimboot 8.1 - http://reboot.pro/to...e-2#entry182393
WinNTSetup3 - http://www.msfn.org/...612-winntsetup-
DriverPacks - http://driverpacks.net/downloads
Win 8.1 Enterprise Evaluation x64 - http://technet.micro...r/hh699156.aspx

For UEFI + BIOS booting from USB then Windows 8.1 x64 need to be used as Source.
There are now three Universal solutions for booting from USB on UEFI + BIOS computers:
- Win8.1SE x64 boot.wim of size 400 MB booting from RAMDISK
- Portable W864USP1.vhd of size 3.5 GB booting as FILEDISK
- Full Windows 8.1 Pro installed in 15 GB VHD or any Windows 8.1 on USB SYSTEM partition of size 50 GB

================================================================================

How to Install Windows 7/8 in VHD and to Make Mini 7/8 VHD for booting from USB ?

- Direct Install Windows 7 Ultimate or 8 Pro in a 15 GB VHD file on local harddisk created by WinNTSetup_x64.exe with Ctrl + Shift + V
- Boot Drive can be FAT32 or NTFS USB-Stick made with UFD_FORMAT.exe so that normal booting of the internal harddisk is not changed

1. Boot from USB or from Network with Win8.1SE x64 boot.wim selected in Boot Manager Menu
2. Use portable App WinNTSetup_x64.exe and click tab Windows 7/8
3. Select Installation files - Use R-mouse to mount 7/8 Setup ISO file in ImDisk Virtual Drive
4. Use WinNTSetup button VHD to Create 15 GB VHD file on local harddisk
5. Select Boot Drive (USB-Stick) and Installation Drive (mounted VHD file) for Install of 7/8
In WinNTSetup3 - Tweaks - Select all System Tweaks so that UAC is off etc.
6. WinNTSetup3 - Setup will prepare VHD on local harddisk for Install of 7/8
7. Reboot from Boot Drive and Install 7/8 in VHD
8. Open Device Manager via R-mouse on My Computer
9. Install missing drivers by using extracted DriverPacks

After booting with Windows 7/8 VHD then Check to have Switched Off :
UAC + Defender + pagefile + System Restore + Hibernate + Windows Update + Action Center settings Disable ALL options

Hibernate OFF is needed via cmd window with

powercfg -h OFF

Install FiraDisk driver with R-mouse on firadisk.inf in makebt\firadisk-driver- folder
The 64-bit FiraDisk driver requires to boot with testsigning switched on

Open Command Prompt as Administrator:

bcdedit /set testsigning on

Reboot to activate testsigning - Info http://msdn.microsof...y/ff553484.aspx

- After Install then Copy Windows 7/8 VHD file to USB and use USB_W78_Fix.exe to fix for booting from USB-drive


Install 7/8 in VHD and Make Mini 7/8 VHD for booting from USB
http://reboot.pro/to...ct-make-mini-8/
http://reboot.pro/to...ct-make-mini-7/

Install XP in VHD and Make Mini XP VHD for booting from USB
http://reboot.pro/to...tall-xp-in-vhd/
http://reboot.pro/to...t-make-mini-xp/

The XP/7/8 Mini Windows VHD's of 1.2 - 2.5 GB are loaded from USB-Stick into RAMDISK by Grub4dos and using WinVBlock or FiraDisk driver
Grub4dos booting with VHD loaded into RAMDISK cannot be used on UEFI computers.

For UEFI + BIOS booting then Windows 8.1 x64 need to be used as Source.
You can make Portable W864USP1.vhd of size 3.5 GB for booting from USB and direct selected in Boot Manager Menu.

================================================================================

How to prepare XP Setup Source ? - Prepare XP Setup ISO file with integrated UpdatePack and DriverPacks

Take care that your XPSOURCE Folder is located on your Harddisk in a simple Path without SPACES.
Copy the Content of your Windows XP Setup CD to your XPSOURCE Folder on Harddisk

First Integrate ServicePack SP3 in your XP-SP2 Source (don't use here nLite).
http://www.helpwithw...ice_Pack_3.html
Download from - http://www.microsoft...aylang=en&id=24

In Command Window use for English version and XPSOURCE folder on drive E:

WindowsXP-KB936929-SP3-x86-ENU.exe /integrate:E:\XPSOURCE

Siginet's RyanVM Integrator 1.6 can then be used to Integrate Windows UpdatePacks in the XP-Source.
http://integrator.si...ex.php?download
Download preferred version RVM Integrator 1.6.1 Beta 2.1

Windows XP UpdatePacks and Addons:
Onepiece XP Post-SP3 AIO Update Pack FINAL - http://www.ryanvm.ne...opic.php?t=6438
Onepiece XP Post-SP3 AIO International Update Packs FINAL - http://www.ryanvm.ne...pic.php?t=10445
Dutch Update Pack - http://www.ryanvm.ne...opic.php?t=8428
RyanVM Forum - http://www.ryanvm.net/forum/

For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE DriverPack Massstorage with TXT Mode Enabled.
http://driverpacks.net/downloads
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the
XP Setup BootFolder $WIN_NT$.~BT on Install-Drive and can prevent a lot of XP Install Boot Problems.
Use DPsBase.exe to Integrate DriverPacks Chipset + Processor + MassStorage + LAN + WLAN DriverPacks
which will then be located in OEM Folder in your XPSOURCE folder
Always first use RyanVM Integrator and then use DPsBase to Improve your XP-Source
DPsBase makes presetup.cmd in folder I386 and changes the I386\winnt.sif file for use of DriverPacks

presetup.cmd in folder I386 will start decompression of DriverPacks located in OEM folder
at the beginning of GUI-mode of XP Setup, which does NOT take to much time for the 5 DriverPacks

You should select to Keep The Drivers for Chipset + Processor + MassStorage + LAN
Then WINDOWS\DriverPacks is about 135 MB which is acceptable and provides a lot of extra driver support
which is useful to make XP Universal and adapt easily to very different hardware.
In that case the DevicePath is set accordingly in key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
so that XP can automatically make use of these drivers for adjusting to New Hardware

When you don't use nLite, you can copy the supplied $OEM$ folder to your XP Source folder
Change $OEM$ folder to your needs for UserAccounts and Registry Tweaks and Adding Drivers
CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
Info see: http://unattended.ms.../unattended.xp/

Use DriverForge.v4.5.4.exe to Install from C:\Drivers at T-9 of GUI XP Setup (just for the last Reboot).
DriverForge.v4.5.4.exe was made by kickarse http://www.msfn.org/...howtopic=110783
At end of TXT-mode XP Setup the folder $OEM$\$1\Drivers is copied to C:\Drivers
and $OEM$\$1\Install\DriverForge.v4.5.4.exe is copied to C:\Install
For Auto Use of DriverForge at T-9 add uncompressed driver folders in $OEM$\$1\Drivers
and Uncomment two rules by removing ; in winnt.sif file copied from winnt_sif to your I386 folder
This is very useful for Install of your well known Audio and Video driver during GUI-mode of XP Setup.

[SetupParams]UserExecute = "%SystemDrive%\INSTALL\SetupPar.cmd"

================================================================================

How to make XP Setup ISO File ?

- Use BBIE (see below) or Isobuster to Extract Boot Image bootsect.bin from Original bootable XP Setup CD
bbie will make image1.bin that you can copy as bootsect.bin to XP Setup source folder
- Reduce Size of XP Setup Source folder (if needed to fit on CD then remove folders LANG WIN9XMIG WIN9XUPG)
- Use ImgBurn and bootsect.bin to make Bootable CD

1. Remove 3 folders LANG WIN9XMIG WIN9XUPG - reduction in size = 135 MB
2. Run ImgBurn - Portable Tool in PStart Menu - IMG_XP\MULTI\PStart\Progs\ImgBurn
- Select Write files/folders to disc
- Output - Select Image File
- Browse Source folder and Select your XP Setup Source folder
- Browse Destination file - Give Name e.g. XP-Setup.iso
- Labels ISO 9660 - Give Name e.g. XP-Setup
- Advanced Restrictions - ISO9660 - Select Level X and DOS CharSet with 4x Checkbox On (allow ...)
- Bootable Disc - Make Image bootable - Checkbox On - Browse Boot Image - Select bootsect.bin file
- Bootable Disc - Emulation Type = None
Load Segment = 07C0
Sectors to Load = 4


BOOT_USB\makebt>bbie M:\XP3_1307.iso
BBIE - Bart's Boot Image Extractor v1.0, © 2001, Bart Lagerweij
will make BOOT_USB\makebt\image1.bin that you can rename as bootsect.bin

================================================================================

PXE wimboot is very handy and fast for booting of Win8.1SE boot.wim from Network

How to make Win8.1SE boot.wim
http://www.msfn.org/...170546-win81se/

Download Tiny PXE Server - http://reboot.pro/fi...iny-pxe-server/

Using iPXE and wimboot, you can boot into Windows PE via HTTP.
http://ipxe.org/wimboot

In case of Windows 8 then bootmgr.exe must be used instead of bootmgr
http://blog.devicenu...ver-2012r2.html

More Info on how to use Tiny PXE Server for booting WIM and VHD from Network via iPXE
http://reboot.pro/to...twork-via-ipxe/
http://reboot.pro/to...iny-pxe-server/

I copied folders Boot and sources from Win8.1SE_2014-01-30\ISO\WIM folder to pxesrv\files folder

XP-W7-Setup\pxesrv\files\wimboot.ipxe is auto used by pxesrv.exe when the given config.INI is used

wimboot.ipxe

#!ipxe
set boot-url http://${dhcp-server}
kernel ${boot-url}/wimboot
initrd ${boot-url}/bootmgr.exe                  bootmgr.exe
initrd ${boot-url}/Boot/bcd                     bcd
initrd ${boot-url}/Boot/fonts/segmono_boot.ttf  segmono_boot.ttf
initrd ${boot-url}/Boot/fonts/segoe_slboot.ttf  segoe_slboot.ttf
initrd ${boot-url}/Boot/fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd ${boot-url}/Boot/fonts/wgl4_boot.ttf     wgl4_boot.ttf
initrd ${boot-url}/Boot/boot.sdi                boot.sdi
initrd ${boot-url}/sources/boot.wim             boot.wim
imgstat
boot

Or make Entry in menu.ipxe for PXE wimboot of Win8.1SE boot.wim file

:w81x64_wim
kernel ${boot-url}/wimboot
initrd ${boot-url}/bootmgr.exe                  bootmgr.exe
initrd ${boot-url}/Boot/bcd                     bcd
initrd ${boot-url}/Boot/fonts/segmono_boot.ttf  segmono_boot.ttf
initrd ${boot-url}/Boot/fonts/segoe_slboot.ttf  segoe_slboot.ttf
initrd ${boot-url}/Boot/fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd ${boot-url}/Boot/fonts/wgl4_boot.ttf     wgl4_boot.ttf
initrd ${boot-url}/Boot/boot.sdi                boot.sdi
initrd ${boot-url}/sources/boot.wim             boot.wim
imgstat
boot || goto failed
goto start

F12 hotkey can be used for PXE boot when LAN PXE Boot ROM is enabled in BIOS
F8 hotkey can be used to select PXE boot in BIOS Boot Menu

http://reboot.pro/to...e-2#entry179107

================================================================================


  • TheHive likes this

#3 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4197 posts

Posted 18 February 2013 - 10:09 AM

:thumbsup: If i get some time . Hope to test this.



#4 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 25 March 2013 - 08:50 AM

-
*** Update UEFI_MULTI Version 7.4  ***
 
  • Update  - Fedora-18 Grub2 UEFI Secure Boot in folder UEFI_MAN\efi_fedora18
  • Update  - BOOT_IMG - FileSize of Boot Images in Grub4dos Menu
  • Changed - Program Version - latest version is 7.4
  •  
    Download  - UEFI_MULTI
     
    :cheers:
     

    • indigo5 likes this

    #5 wimb

    wimb

      Platinum Member

    • Developer
    • 3756 posts
    • Interests:Boot and Install from USB
    •  
      Netherlands

    Posted 11 May 2013 - 08:24 AM

    -
    *** Update UEFI_MULTI Version 7.5  ***
     
  • Update  - AutoIt3 version 3.3.8.1
  • Update  - VHD Boot Menu also made for VHD already existing on System Drive
  • Update  - Improved text for some WARNING Message's
  • Changed - Program Version - latest version is 7.5
  •  
    Download  - UEFI_MULTI_75
     
    :cheers:
     


    #6 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 26 June 2013 - 04:57 PM

    @wimb

    I am new to UEFI and I am experimenting a lot using your excellent UEFI_MULTI package.
    Following are my reports and understandings. Please correct me if needed.

    I have an USB hard disk with multiboot-capability with only one partition, MBR mode, NTFS format, using grub4dos (called OLD_MULTIBOOT).
    With UEFI/GPT, I understand that grub4dos does not support GPT, so I cannot use it for GPT disks (for example for internal hard disk of systems with Windows 8).
    My USB HDD is MBR, so grub4dos is OK but since it is in NTFS, it cannot boot on UEFI system, so I use your UEFI_MULTI
    where the first partition (bootable) must be in FAT32, and contains EFI directory and files, to be able to boot on both
    UEFI and non-UEFI (=BIOS) system.

    So I understand that using UEFI_MULTI I can boot some UEFI-aware systems (like Parted Magic, Fedora, Ubuntu and Windows 8-64).
    Important question : Once booted UEFI Windows 8-64, in BCD there is an entry for grub4dos, does it mean that I can then boot all entries listed in my menu.lst on my existing USB HDD OLD_MULTIBOOT? If the answer is yes, then this is fantastic!
    In other words, this would mean:
    a- on BIOS systems, I can boot directly grub4dos and everything in my working menu.lst

    b- on UEFI systems, I can boot some UEFI-aware OSes, then by chainloading grub4dos from UEFI Windows boot manager, I can boot everything as in a).
    Could you confirm or infirm?

    Now about UEFI_MULTI procedure.
    I did not understand the need for 4 partitions. So I use only 2 partitions: one primary in FAT32 about 20 GB,
    the other primary in NTFS. All in MBR mode. The new multiboot USB HDD is called NEW_MULTIBOOT.
    In FAT32 partition, I copied the /boot directory and bootmgr from OLD_MULTIBOOT USB HDD. The FAT32 partition has grub4dos installed in MBR.
    In NTFS partition, I copied my existing VHD bootable from my menu.lst.
    Then I run UEFI_MULTI.exe: checked Add EFI Boot manager, Add grub4dos to Boot manager. Add VHD and add Boot Win7/8 are greyed out.
    Boot image file: make_pe3 iso file. I manually copy pmagic and images directory to FAT32 partition. After completion, I tested in UEFI system.
    - Refind EFI boot manager is OK
    - Parted Magic 64 hang on black screen at boot
    - Parted Magic 32 is OK
    - I cannot boot Win8 x64 EFI. 8bootx64.efi not found.
    So I take it from bootx64.efi from existing Win8-64 system (hidden partition). Reboot: got message:
    ---
    failed to start
    Status: 0xc000000f
    \EFI\Microsoft\Boot\BCD
    Info: The Boot Configuration Data for your PC is missing or contains errors.
    So I copied \boot from FAT32 partition to \EFI\Microsoft (directory to be created first). Then reboot, choose Win8 VHD entry: the system reboots instead of booting Win8 VHD!

     

     

    If I choose the grub4dos - XP entry, I got the message :
    File: \grldr
    Status: 0xc000007b
    Info: The application or operating system couldn't be loaded because a required file is missing or contains errors.
    ---
    In FAT32, there is boot.ini created by UEFI_MULTI with content:
    [Boot Loader]
    Timeout=20
    Default=C:\grldr
    [Operating Systems]
    C:\grldr="Start GRUB4DOS - XP Menu"
    ---

    So I am stucked now.
    Please comment, thank you.
     

    Edit: I made few progressions.

    The missing 8bootx64.efi file, the missing \boot directory etc... problem were due to the
    fact that either Win8 must be installed on USB system drive, or the Win8 USB stick recovery content
    must be copied to UEFI_MULTI\MULTI_BOOT directory. Then in the program select copy to boot drive
    with source folder UEFI_MULTI\MULTI_BOOT.

    Since I also have a VHD to boot, I use EasyBCD to add this entry to the BCD. You need to add to FAT32
    \boot and \efi\microboot\boot.

    So now on UEFI boot, I have 3 entries: Win8 VHD, Windows Setup, and grub4dos.
    - Win8 VHD entry gives reboot!
    - Windows setup entry works.
    - grub4dos entry give 0x7B error with \grldr!



    #7 wimb

    wimb

      Platinum Member

    • Developer
    • 3756 posts
    • Interests:Boot and Install from USB
    •  
      Netherlands

    Posted 27 June 2013 - 06:05 AM

    UEFI-mode needs FAT32 Boot drive and does NOT allow to boot with Grub4dos.
    BIOS-mode is required to boot with Grub4dos
     
    You do a lot of manual copy steps that are not part of the described Procedure.
    Please first follow more exactly the description and let UEFI_MULTI do the work.
     

     

    Section 5. - UEFI_MULTI.exe is used to make Multi-Boot USB-Harddisk
     
    0. Connect Portable USB-harddisk and start computer with Windows 7/8 - x64 version
    1. On first use then Format your USB Boot Drive with FAT32 - Boot files will be renewed by UEFI_MULTI.exe
    2. Run UEFI_MULTI.exe
    3. Select FAT32 Boot   Drive of USB-harddisk
    4. Select NTFS  System Drive of USB-harddisk (has Windows 8 Installed to USB System Drive)
    5. Select Source Folder UEFI_MULTI\MULTI_BOOT for Copy to Boot Drive (will add soources\boot.wim and pmagic folder)
    6. Select Boot Image File - VHD is Copied always to NTFS System Drive - ISO is copied to Boot Drive
    7. Optionally Add EFI Boot Manager for UEFI booting of Linux Parted Magic - Requires to Disable UEFI Secure Boot
    8. Click GO to make Multi-Boot USB-Harddisk
     

     



    #8 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 27 June 2013 - 09:06 AM

    @wimb

    I tried again without any manual procedure, except the preparation like pmagic, System recovery stick.
    Then I copied them as instructed to UEFI_MULTI\MULTI_BOOT directory, then run section 5, using boot image file a VHD.
    Of course option "Add VHD to boot manager" is then not greyed out and checked. Then I click on GO.

    The BCD produced in case of BIOS and UEFI are:
    BIOS : \boot\bcd with entries :
    - VHD (VHD, .vhd)
    - Start Grub4dos (partition, \grldr)
    UEFI : \efi\Microsoft\boot\bcd with entries :
    - Windows 8 (partition, \windows)
    - Windows setup (ramdisk, boot.wim)

    I can boot successfully in both BIOS and UEFI modes. But I have some remarks:
    1- I do not check 'Add grub4dos to boot manager' option, this entry is still added to BIOS BCD !
    2- the VHD entry is added in BIOS BCD but not in UEFI BCD! In UEFI BCD, there is an entry for Windows 8 instead that I did not ask! (I do not have Windows 8 installed in the "system" drive: second partition of USB HDD, NTFS-formatted).
    I have to edit this entry to point to the desired VHD.

    3- the Windows setup (= repair) entry is not present in BIOS BCD.

    I hope that the problems above would be handled in future version.
    Currently I plan to repartition my existing USB HDD (single MBR NTFS partition) so it can be multibooted (BIOS/UEFI). :clapping:
     



    #9 wimb

    wimb

      Platinum Member

    • Developer
    • 3756 posts
    • Interests:Boot and Install from USB
    •  
      Netherlands

    Posted 27 June 2013 - 09:34 AM

    I can boot successfully in both BIOS and UEFI modes. But I have some remarks:
    1- I do not check 'Add grub4dos to boot manager' option, this entry is still added to BIOS BCD !
    2- the VHD entry is added in BIOS BCD but not in UEFI BCD! In UEFI BCD, there is an entry for Windows 8 instead that I did not ask! (I do not have Windows 8 installed in the "system" drive: second partition of USB HDD, NTFS-formatted).
    I have to edit this entry to point to the desired VHD.

    3- the Windows setup (= repair) entry is not present in BIOS BCD.
     

     

    OK, you made a lot of progress then ....

     

    Grub4dos entry is always added to BIOS BCD when grldr.mbr is not found (see caption in running UEFI_MULTI.exe)

    So that is normal behaviour, because it is always desired to have Grub4dos support in BIOS mode 

    and it provides a means to avoid having Win8 as default in BCD which would cause other options to be inaccessible.

     

    What kind of VHD did you select as Boot Image file and what driver does it have and can you boot that VHD from USB in UEFI-mode ?

    In UEFI-mode you can boot (flat) Win8 x64 from \efi\microsoft\boot\BCD

    So VHD like Win7-  are not bootable in UEFI-mode and so NOT added to EFI Boot Manager Menu.



    #10 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 27 June 2013 - 03:31 PM

    @wimb

    OK finally I made good progress.
    What I said previously was wrong : the UEFI BCD does have Win8 VHD entry, but since it is labeled Windows 8,
    I thought it was the flat Win8, not the Win8 VHD I requested. So the only problem remaining is no Windows setup (repair) entry
    in BIOS BCD.
     

    />So VHD like Win7-  are not bootable in UEFI-mode and so NOT added to EFI Boot Manager Menu.

    Oh really? What is the reason, since Win7-64bit could be installed in UEFI mode?
    Without knowing that, in UEFI mode I tried to add Win7PE Wim (Win7PE iso) and Win8PE wim (from Win8PE iso).
    It boots, but then I got:
    - for Win7PE wim: \windows\system32\boot\winload.efi 0xC000000f. OK my Win7PE is 32-bit, So I add the 2 files winload.efi and winresume.efi taken from Win8 to Win7E wim, and reboot: same problem.
    - for Win8E wim (32-bit). It does have winload.efi already. Still Got message : 0xc0000359 \windows\system32\boot\winload.efi.

    If I could replace Win7PE and Win8PE with their 64-bit version and use their wim, I wonder whether they can be booted in UEFI mode?
    I have no 64-bit wim to try.


    To summarize what I understand by using UEFI_MULTI:
    a- with BIOS system, no problem for multiboot using known loaders (grub4dos, bootmgr, syslinux, ntldr...)
    b- with UEFI system, if you can disable Secureboot and enable CSM (compatibility support modules), then same booting capabiliy as in a).
    If CSM disabled, and Secureboot enabled/disabled, you can boot EFI compatible systems as grub2, Win8-64, rEFInd, PartedMagic, Fedora, Ubuntu etc...
    Win8-64 could in flat OS ou in VHD.

     



    #11 wimb

    wimb

      Platinum Member

    • Developer
    • 3756 posts
    • Interests:Boot and Install from USB
    •  
      Netherlands

    Posted 27 June 2013 - 06:19 PM

    What I said previously was wrong : the UEFI BCD does have Win8 VHD entry, but since it is labeled Windows 8,
    I thought it was the flat Win8, not the Win8 VHD I requested. So the only problem remaining is no Windows setup (repair) entry
    in BIOS BCD.
    .........

    I have no 64-bit wim to try.
     

     

    You have tested already x64 boot.wim :)

    Win8 x64 Recovery boot.wim (Windows Setup entry) is working for me in UEFI but also in BIOS-mode.

    Strange that the entry in Boot\BCD for BIOS-mode booting is missing for you.

     

    The Win8 x64 VHD entry is NOT yet made for UEFI booting by UEFI_MULTI.exe , but I will make changes to make it appear.

    Strange that you say that the entry labeled Windows 8 is working for you to boot Win8 x64 VHD in UEFI-mode  :hyper:

    It is not yet in the program. Did you use in some way bcdboot to make it happen ?

     

    VHD_W8_Compact.exe is already able to make such entry for booting Win8 x64 VHD from USB in UEFI-mode.

     

    In UEFI-mode then Grub4dos booting does NOT work, it is only available in BIOS-mode.

     

    :cheers:



    #12 wimb

    wimb

      Platinum Member

    • Developer
    • 3756 posts
    • Interests:Boot and Install from USB
    •  
      Netherlands

    Posted 28 June 2013 - 07:17 AM

    *** Update UEFI_MULTI_76.exe *** 

     

    Download from http://reboot.pro/fi...t-usb-harddisk/

     

    Changes:

    - UEFI Boot Manager entry for Win8-x64 VHD is made.
    - Update Grub4dos to version grub4dos-0.4.5c-2013-03-03.7z
     
    :cheers:
     
    @ktp
    Boot Manager entry for Recovery boot.wim is made in Section 3 when Recovery USB-Stick is made.
    When entry in Boot\BCD is missing then the origin of the problem is NOT in UEFI_MULTI
    but in making Recovery USB-Stick.
    Please check if Stick has file Boot\BCD and check that USB-Stick can boot in BIOS-mode. 


    #13 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 28 June 2013 - 06:55 PM

    Good news! I succeeded to boot in UEFI mode through rEFInd EFI manager -> Windows 8-64 bootmager EFI + booloader EFI a Win8PE-64 rescue environment (using the Win8PE-64 wim taken from its ISO file).

    So now in any UEFI system I can boot either:
    - Windows 8-64 setup/repair
    - Windows 8-64 VHD
    - Windows 8-64 PE
     

    Notes: I can also boot in UEFI mode Fedora 18, and Parted Magic, but they hang randomly (black screen) after some boot time activity.



    #14 wimb

    wimb

      Platinum Member

    • Developer
    • 3756 posts
    • Interests:Boot and Install from USB
    •  
      Netherlands

    Posted 29 June 2013 - 05:25 AM

    Good news! I succeeded to boot in UEFI mode through rEFInd EFI manager -> Windows 8-64 bootmager EFI + booloader EFI a Win8PE-64 rescue environment (using the Win8PE-64 wim taken from its ISO file).

    So now in any UEFI system I can boot either:
    - Windows 8-64 setup/repair
    - Windows 8-64 VHD
    - Windows 8-64 PE
     

    Notes: I can also boot in UEFI mode Fedora 18, and Parted Magic, but they hang randomly (black screen) after some boot time activity.

     

    Win 8-64 PE is included in Win 8-64 Repair boot.wim

    It is nice that you can boot 8-64 PE boot.wim in UEFI-mode but it does not add something new,

    since the 8-64 Repair boot.wim gives already that functionality and that boot.wim is made much easier using Configuration > Recovery menu

     

    Do you have now also Win8 Repair boot.wim booting in BIOS-mode from Boot\BCD ?

     

    :cheers:



    #15 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 29 June 2013 - 05:48 AM

    @wimb

    Yes, the latest UEFI_MULTI 7.6 works very well, I no longer have any problem.
    The Win8 Repair boot.wim is present in both BIOS and UEFI modes. Idem for Win8 VHD entry if checked in the application.
    Thank you for your great package.

    You are right, booting in UEFI Win8-64 PE is not new from booting boot.wim (Win8-64 Repair), just I am used
    to boot and get quickly a PE environment with some convenience tools for rescue (shell, imdisk, network, audio, .NET framework...).The remaining function is provided by portable apps/Pstart so they are common to WinPE environments (mini-XP, mini-Win7, mini-Win8).
    What is new and fantastic is that on UEFI systems, thanks to UEFI_MULTI, without changing BIOS setup to boot in legacy mode, I can still boot either Win8-64 VHD or Win8PE-64 for rescue. :thumbsup:


    • wimb likes this

    #16 Wonko the Sane

    Wonko the Sane

      The Finder

    • Advanced user
    • 16066 posts
    • Location:The Outside of the Asylum (gate is closed)
    •  
      Italy

    Posted 29 June 2013 - 08:57 AM

     some convenience tools for rescue (shell, imdisk, network, audio, .NET framework...).

    First time ever :w00t: that someone in his right mind catalogs "audio" or ".Net framework" among "convenience tools for rescue".

    Actually I am further surprised :hyper: that ".Net framework" can be considered a "tool" and a "convenient" one. :ph34r:

    O tempora, o mores !

     

    http://en.wikipedia....empora_o_mores!

     

     

    :cheers:

    Wonko



    #17 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 29 June 2013 - 09:18 AM

    Well I am not using .NET Framework directly, but some of my "portable" applications require it :-).

    By the way, with this wonderful 1TB universal multi-boot USB 2"5 HDD with 1 FAT32 + 1 NTFS partition used inside the Zalman ZM-VE300 (requires FAT32 firmware), I am very pleased with it.

     

    Edit:

    The is however a problem of some big iso (> 4 GB) that have to be put on second NTFS partition. But they usually can be booted with grub4dos or used after mounting with Imdisk (for Windows installation with WinNTSetup). The ZM-VE300 has also HDD write-protect function if needed, in case of use with infected systems.



    #18 Wonko the Sane

    Wonko the Sane

      The Finder

    • Advanced user
    • 16066 posts
    • Location:The Outside of the Asylum (gate is closed)
    •  
      Italy

    Posted 29 June 2013 - 09:29 AM

    Well I am not using .NET Framework directly, but some of my "portable" applications require it :-).

    Subverting basic equations :w00t::

    • .Net Framework = Evil Bloat
    • .Net Framework 4.0 = Evil Bloat, but more bloated
    • "portable" application needing .Net framework = NON-portable application

     

    :whistling:

    :rofl:

     

    :cheers:

    Wonko



    #19 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 29 June 2013 - 09:35 AM

    How about Java applications? They can use portable Java run-time (cf. portableapps.com) which is the Oracle equivalent for MS .NET framework as far as I understand?



    #20 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 29 June 2013 - 02:18 PM

    Another good news: I succeeded to boot Win7PE-64 in UEFI mode. :happy_dance:



    #21 wimb

    wimb

      Platinum Member

    • Developer
    • 3756 posts
    • Interests:Boot and Install from USB
    •  
      Netherlands

    Posted 29 June 2013 - 02:46 PM

    Another good news: I succeeded to boot Win7PE-64 in UEFI mode. :happy_dance:

     

    That is good news. How did you make it happen.

     

    Booting boot.wim from RAMDISK has probably less restrictions than booting Win 7-x64 VHD as Filedisk which always failed for me in UEFI-mode.

     

    :cheers:



    #22 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 29 June 2013 - 02:57 PM

    @wimb

     

    I just take an existing Win7PE-64 iso, extract its wim then create a new entry WinPE (ramdisk) in UEFI mode (\efi\microsoft\boot\bcd) with EasyBCD, then use BcdTool under Win7PE-32 (7pe_x86_M) to change winload.exe into winload.efi.

     

    Note: BcdToold does not work under 64-bit environment :-(. EasyBCD works fine in all environement (real, or PE), 32 ou 64-bit, but it does not aware that UEFI is involved so it uses winload;exe instead of winload.efi).

     

    What tool do you use to edit BCD (apart from bcdedit command line)?

     

    Now I have to build 7pe_x64_M.iso by using your Make_PE3 package, it seems that it is allowed.

     



    #23 wimb

    wimb

      Platinum Member

    • Developer
    • 3756 posts
    • Interests:Boot and Install from USB
    •  
      Netherlands

    Posted 29 June 2013 - 03:53 PM

    What tool do you use to edit BCD (apart from bcdedit command line)?

     

    Now I have to build 7pe_x64_M.iso by using your Make_PE3 package, it seems that it is allowed.

     

    Thanks for the Info.

     

    I use 7/8 bcdedit.exe and Win8 bcdboot.exe in admin command window and no other tool.

     

    For VHD mounted as drive V: you can make Boot\BCD and efi\microsoft\Boot\BCD on Boot Drive T:

    by using Win8 bcdboot.exe with /f ALL option to support BIOS + UEFI firmware

     

    bcdboot.exe V:\Windows /s T: /f ALL

     

    May be can you try if Win7-x64.vhd can be used to boot in UEFI mode.

    For me it was refused always ....

     

    Certainly 7pe_x64_M can be made with Make_PE3.exe  :)

     

    :cheers:



    #24 ktp

    ktp

      Silver Member

    • Advanced user
    • 773 posts

    Posted 03 July 2013 - 03:11 PM

    @wimb

     

    Good news: I test UEFI booting of my USB hard disk on another newer UEFI system delivered with Windows 8 (my previous tests were done on an older system, which has UEFI compatibility but mainly is BIOS, it does not have CSM or Secure boot).

     

    On this newer UEFI system, everything is OK, with or without CSM enabled: Win8-64 full, Win8-64 VHD, Win8-64 PE, Parted Magic 32 and 64-bit, Ubuntu 64-bit (installed with BIOS mode). Fedora 18 boots OK but then the mouse is not reacting correctly, but it could be Fedora-related problem, not booting one.

     

    By the way, I now use full Win8-32 VHD or Win8-64 VHD for rescue, boot time is fast, even faster than Win7PE, it could be even faster by booting directly from USB3.0 port (which Win7PE and earlier could not do). By using full VHD, there are many advantages over PE methods. Sample booting time: 1'03" to boot on external USB 2.0 attached HDD with Win8-64 VHD. Win7PE-32 is longer: 1'15".



    #25 Wonko the Sane

    Wonko the Sane

      The Finder

    • Advanced user
    • 16066 posts
    • Location:The Outside of the Asylum (gate is closed)
    •  
      Italy

    Posted 03 July 2013 - 04:44 PM

     boot time is fast, even faster than Win7PE, it could be even faster by booting directly from USB3.0 port (which Win7PE and earlier could not do). 

    Are you really sure-sure they could/can not? :dubbio:

    AFAICR it is just a matter of USB 3.x drivers :unsure:

     

    :cheers:

    Wonko







    Also tagged with one or more of these keywords: aio boot, linux, vhdx, windows 10, wim, ssd, uefi, usb, multiboot

    2 user(s) are reading this topic

    0 members, 2 guests, 0 anonymous users