Jump to content











Photo
* * * * * 1 votes

UEFI MULTI - Make Multi-Boot USB-Drive -

grub4dos vhd win8 multiboot usb uefi

  • Please log in to reply
47 replies to this topic

#1 wimb

wimb

    Gold Member

  • Developer
  • 2,142 posts
  •  
    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: 20 Feb 2014
File Category: Boot tools

*** 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

More Info here http://reboot.pro/to...multi/?p=168077
and here http://www.911cd.net...showtopic=25269
and http://reboot.pro/to...t-usb-harddisk/

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

UEFI_MULTI - Make Multi-Boot USB-Drive


=
UFD_FORMAT.exe - Tool to format USB-stick for Booting with Boot Manager Menu on BIOS or UEFI computer and
Tool to make USB-Stick having two partitions - FAT32 Boot partition for WIM or ISO and NTFS System partition for VHD.
Option to Install Grub4dos in MBR BootCode, which allows BIOS computer to boot directly from USB with Grub4dos Menu.
Option to make Boot Manager and Grub4dos Menu on UFD to boot UEFI + BIOS directly from USB with Boot Manager Menu.
Windows 7/8 or 7PE is needed to make Boot Manager Menu.
More Info - http://reboot.pro/to...140-ufd-format/
-
Before using UEFI_MULTI.exe you might consider the next 4 Sections as preparation
0. Use UFD_FORMAT to format USB-Stick
1. Prepare USB-Harddisk to have MBR and 3 Primary partitions (always needed)
2. Install Windows 8 on USB-harddisk (option)
3. Create Windows 8 Recovery USB-stick - comparable to WinPE 4.0 (highly recommended)
4. UEFI Multiboot USB - Windows 8 and Linux Parted Magic (option)

Click here to download this file

Attached Thumbnails

  • UEFI_MULTI.png

  • indigo5 and Luckyone like this

#2 wimb

wimb

    Gold Member

  • Developer
  • 2,142 posts
  •  
    Netherlands

Posted 18 February 2013 - 07:11 AM

Before using UEFI_MULTI.exe you might consider the next 4 Sections as preparation
1. Prepare USB-Harddisk to have MBR and 3 Primary partitions (always needed)
2. Install Windows 8 x64 on USB-harddisk (option)
3. Create Windows 8 x64 Recovery USB-stick - comparable to WinPE 4.0 (highly recommended)
4. UEFI Multiboot USB - Windows 8 and Linux Parted Magic (option)
 
================================================================================
 
Section 1. - Prepare USB-Harddisk to have MBR and 3 Primary partitions
 
Preferred is to use Portable USB-harddisk e.g. Western Digital 500GB 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. 50 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 Recovery boot.wim file in folder sources and with folder images for ISO and other small Boot Image files
- System NTFS  - for Windows 8 System and for Portable XP VHD and Win7 VHD Image files running Life from USB 
- Data   NTFS  - for PStart folder with Portable Apps and for all Windows Setup ISO files used by WinNTSetup2 to Install Windows on local harddisk
 
================================================================================
 
Section 2. - Install Windows 8 x64 on USB-harddisk
 
Boot with Windows 8 x64 and use WinNTSetup2_x64.exe and Win8 Setup ISO file (rightclick) 
for Direct Install of Win 8 x64 on USB-harddisk using FAT32 Boot and NTFS System partition
Did not use any other tool. Boot and EFI folder are created on FAT32 partition.
 
Reboot with Windows 8 from USB and when Install is ready then 
use Windows Key + X and press C to get Configuration Screen with Icons
 
Set System Restore and UserAccount Control Off and 
change settings to get rid of pagefile.sys and hiberfil.sys
No pagefile.sys - Run as Administrator in cmd window: sysdm.cpl
and Change Advanced Performance Virtual memory Settings - Set to use No paging file
 
No hiberfil.sys - Run as Administrator in cmd window: powercfg.exe -H off 
 
Disable Hiberboot and Disable Windows Update
 
**** WARNING ****  
In MultiBoot configurations Windows 8 quite often will set the NTFS dirty bit On for ALL local drives. 
Next boot then chkdsk will run on ALL local drives.
Setting of the NTFS dirty bit can be prevented with registry tweak to Disable Hiberboot
Use DisableHiberboot_W8.reg in folder POST_FIX_W8 to Disable Hiberboot
**** END WARNING ****  
 
================================================================================
 
Section 3. - Create Windows 8 x64 Recovery USB-stick
 
Create Windows 8 Recovery USB-stick for booting with boot.wim from RAMDISK (comparable to WinPE 4.0)
 
Computer OFF and Disconnect all USB-harddisks and connect USB-stick
Boot with Windows 8 x64 to create Win8 Recovery USB-stick from Configuration > Recovery Menu
For USB-stick everything works fine, but don't apply this to an existing multi-partition USB-harddisk.   
 
**** WARNING ****  
In case of USB-harddisk then creating the Win8 Recovery Drive will destroy the entire MBR
so that all other partitions are gone (the partition entries in the table are simply zeroed)
**** END WARNING ****  
 
Copy the content of Win8 Recovery USB-stick to folder UEFI_MULTI\MULTI_BOOT
 
I have made TBx64.exe AutoIt3 program and added to system32 in Win8 Recovery boot.wim
TBx64.exe will search for TBLauncher64.exe found e.g. in in root of USB Boot Drive
Some x64 Apps can be in root of USB Boot Drive and launched from TBLauncher Menu.
Modify TBLauncher.ini to your needs for Portable Apps that you want to Launch e.g. Explorer-x64.exe
On booting from USB then Recovery environment appears auto with TBLauncher Menu.
One can launch e.g. WinNTSetup2_x64.exe and prepare drive for install of any Windows e.g. XP
 
Download WinNTSetup2_x64.exe http://www.msfn.org/...winntsetup-v23/
 
 
***** Procedure to modify boot.wim of Win8 Recovery or WinPE 4.0 *****
 
Download and use Wim Mounter 3.1 to modify UEFI_MULTI\MULTI_BOOT\sources\boot.wim
 
Use Mount > Open > Add TBx64.exe and startnet.cmd - Remove winpeshl.ini > Save
 
Remove winpeshl.ini and add modified startnet.cmd to launch TBx64.exe and Recovery Environment.
TBx64.exe and startnet.cmd are supplied in folder add_boot_wim
 
================================================================================
 
Section 4. - UEFI Multiboot USB - Windows 8 and Linux Parted Magic
 
UEFI Multiboot USB - Windows 8 and Linux Parted Magic - Requires to Disable UEFI Secure Boot
 
UEFI Booting Linux Parted Magic involves two steps:
1. For UEFI Multiboot we use the refind EFI Boot Manager instead of the normal UEFI bootfile EFI\Boot\bootx64.efi
2. In EFI Boot Manager we use Grub2 and select Parted Magic from Grub2 Boot Menu
 
- download latest Parted Magic ISO e.g. pmagic_2013_05_01.iso from http://partedmagic.c...hp?id=downloads
- copy the pmagic folder from the Parted Magic ISO to UEFI_MULTI\MULTI_BOOT folder
 
UEFI_MULTI.exe can be used later to select MULTI_BOOT folder as Source Folder for Copy to your USB FAT32 Boot Drive
Add EFI Boot Manager option will copy folder UEFI_MAN\efi with EFI Boot Manger to your USB FAT32 Boot Drive
UEFI_MULTI\UEFI_MAN\efi\boot\grub.cfg file has Grub2 entry for booting Parted Magic
 
================================================================================
 
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
 
 
XP OS is possible but then Win7 VHD Boot Manager Menu entry and Win8 Boot Menu cannot be made.
In XP OS I can prepare MultiBoot USB-harddisk having Win8 Recovery RAMDISK UEFI Secure Boot support.
But for Secure Boot I must not use EFI Boot Manager and don't have UEFI Linux Parted Magic support.
 
Install of Windows 8 to USB can be omitted and it is Not needed to add UEFI Parted Magic support.
 
Simple solution e.g. always add Win8 Recovery for UEFI support 
and Add Boot Image Files for booting from Grub4dos on BIOS computers.
Use e.g. existing Portable XP VHD Or LiveXP_WIM.iso Or 7pe_x86_E.iso + Linux pmagic_2013_05_01.iso 
 
IMG_XP package - Make XP and Win7 Universal Image files
BOOT_IMG copies Universal VHD Image File to Target System Drive and makes GRUB4DOS Menu on Boot Drive.
Fix XP or Win7 VHD for booting from USB-drive by using USB_XP_Fix.exe or USB_W7_Fix.exe
 
Make_PE3 Program to Create Portable Windows 7 PE
 
================================================================================
 
Section 6. - UEFI Secure Boot - Multi-Boot of Fedora-18 + Windows 8 from USB-harddisk
 
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/
 
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
 
UEFI Secure Boot - Multi-Boot of Fedora-18 + Windows 8 from USB-harddisk
Grub2 EFI Boot Manager instead of REFIND  - in UEFI_MAN rename folder efi_fedora18 as efi
Fedora-18 Secure Boot files efi\boot\BOOTX64.efi and efi\boot\grubx64.efi
and using Fedora vmlinuz0 and initrd0.img in LiveOS folder of Fedora-18 on 2_BOOT partition
 
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 should NOT be default.
For booting Parted Magic Linux it is needed 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
 

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. 
 
================================================================================

  • TheHive likes this

#3 TheHive

TheHive

    Platinum Member

  • .script developer
  • 3,721 posts

Posted 18 February 2013 - 10:09 AM

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



#4 wimb

wimb

    Gold Member

  • Developer
  • 2,142 posts
  •  
    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

      Gold Member

    • Developer
    • 2,142 posts
    •  
      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
    • 727 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

      Gold Member

    • Developer
    • 2,142 posts
    •  
      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
    • 727 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

      Gold Member

    • Developer
    • 2,142 posts
    •  
      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
    • 727 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

      Gold Member

    • Developer
    • 2,142 posts
    •  
      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

      Gold Member

    • Developer
    • 2,142 posts
    •  
      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
    • 727 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

      Gold Member

    • Developer
    • 2,142 posts
    •  
      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
    • 727 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
    • 10,122 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
    • 727 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
    • 10,122 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
    • 727 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
    • 727 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

      Gold Member

    • Developer
    • 2,142 posts
    •  
      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
    • 727 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

      Gold Member

    • Developer
    • 2,142 posts
    •  
      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
    • 727 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
    • 10,122 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: grub4dos, vhd, win8, multiboot, usb, uefi

    5 user(s) are reading this topic

    0 members, 5 guests, 0 anonymous users