Jump to content











Photo
* * * * * 1 votes

UEFI MULTI - Make Multi-Boot USB-Drive

aio boot linux uefi wim vhdx ssd windows 10 usb multiboot

Best Answer wimb , 02 March 2019 - 09:49 AM

There is a new version of UEFI MULTI available with new Grub4dos SVBus menu entries.

 

Mapping for VHD WIMBOOT is taken into account for various cases e.g VHD + WIM on USB Or on Internal Harddisk.

 

UEFI_MULTI determines the Drive Number for the MountPoint of the selected NTFS System Drive where the VHD resides.

UEFI_MULTI determines the DriveType and Bus Type of the selected NTFS System Drive.

In this way the program knows where VHD + WIM are located e.g. on USB Or on Internal Harddisk

and the program knows the Windows disk number which is used in menu.lst entries for WIMBOOT mapping in case the VHD + WIM are located on Internal Harddisk.

 

VHD + WIM located on NTFS drive of USB Harddisk Or  Portable SSD

iftitle [if exist (hd0,1)/W10x64_S3.vhd] (hd0,1)/W10x64_S3.vhd - SVBus  RAMDISK  - 2048 MB - map for WIMBOOT
map --top --mem (hd0,1)/W10x64_S3.vhd (hd-1)
map --hook
root (hd-1,0)
chainloader /bootmgr

=

VHD + WIM located on NTFS drive of Internal Disk

title W10x64_NL_1.vhd - SVBus  RAMDISK  - 2.0 GB - map as hd for WIMBOOT
find --set-root --ignore-floppies /W10x64_NL_1.vhd
map --top --mem /W10x64_NL_1.vhd (hd)
map --hook
root (hd-1,0)
chainloader /bootmgr

:cheers:

 

How to Make VHD WIMBOOT on USB and to use Grub4dos menu and SVBus driver for booting from RAMDISK

 

Download: VHD_WIMBOOT and  Manual: 

 

Best Results for speed of Portable VHD WIMBOOT obtained with SAMSUNG Portable SSD T5 250 GB with UEFI/MBR Partitioning with 20 GB FAT32 and 230 GB NTFS partition.

 

[attachment=16488:UEFI_MULTI-2019-03-02_140545.png] == [attachment=16487:W10x64-RAM-HelloWorld-2019-03-01_155130.png] == [attachment=16493:F2-VHD-USB-Ready-2019-03-03_113112.png]

 

With VHD WIMBOOT from USB Portable SSD we can have a full Win10 x64 of Size 600 MB booting from RAMDISK

as very fast Portable and always FRESH Operating System.

 

The only limitation is that booting from RAMDISK requires booting in BIOS mode with Grub4dos.

Hopefully we can have UEFI Secure support when Grub2 in future might be able to load such VHD into memory and launch Windows by chainloading bootmgfw.efi  :rolleyes:  :unsure:

But anyway booting from Windows Boot Manager menu as FILEDISK using Microsoft vhdmp.sys driver is available in BIOS and in UEFI Secure mode.

 

wimlib-clc CAPTURE followed by APPLY is important to reduce the size of the WIMBOOT Operating System from 3,5 GB down to 600 MB 

so that it can be located in VHD of Size 2 GB with total boottime 30 seconds which is OK.

 

Thanks to alacran for pointing me to wimlib of synchronicity (More Info: here) combined with  wimlib-clc of ReTokener    :)

Thanks to steve6375 for --top --mem and Wonko the Sane for (hd-1) and karyonix for (hd) map for WIMBOOT solution in Grub4dos menu   :worship:

 

VHD size 2 GB with full Win10x64 OS + Office Word and Excel + VLC player total size 600 MB in RAMDISK connected to WIM file of size 6 GB on USB NTFS drive

As compared to WinPE the VHD WIMBOOT has the advantage to have support for Office and Printer and any program can be installed which is all not the case for WinPE

 

In case of VHD WIMBOOT on each machine it takes extra boottime and space to adjust the drivers for that machine
The VHD WIMBOOT solution is Portable, but not as flexible as Win10XPE, where boottime is not dependant on machine hardware
 
For Portability it is good to have two VHD's
- On couple of other machines boot first with  25 GB VHD WIMBOOT as FILEDISK from Boot Manager Menu and  let Win10 Install all drivers
- At Home After booting with Win10 x64 OS then CAPTURE WIM of 25 GB VHD - Format and APPLY WIM on 1.5 GB VHD 
- Next time Boot with 1.5 GB VHD WIMBOOT on USB with Grub4dos menu from RAMDISK on all other machines
The 1.5 GB VHD will be handy for booting from RAMDISK on 4GB RAM machines, but in other cases a 3.9 GB VHD is preferred
 
In this way you have some learning on a couple of machines, but then the WIM has improved and can be used on all machines .... 
That principle of learning, where the SYSTEM registry is improving, is already working since the days of Windows eXPerience
Go to the full post


  • Please log in to reply
241 replies to this topic

#226 wimb

wimb

    Platinum Member

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

Posted 13 April 2019 - 09:22 AM

*** Update UEFI_MULTI - Version 88 ***

 

Download : UEFI_MULTI-88.zip   - password is bootwimb

 

- internal BCD create entry improved - solution also working without default entry present

- external BCD create entry improved so that default entry cannot be overwritten anymore

- Language Version is taken into account in making BCD entries



#227 wimb

wimb

    Platinum Member

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

Posted 24 April 2019 - 06:48 PM

*** Update UEFI_MULTI - Version 88 ***

 

- Solution for missing file Boot\bootvhd.dll in case Boot Manager BCD menu was made earlier by MediaCreationTool

 

File Boot\bootvhd.dll is essential to make the VHD entry appear in BIOS Boot Manager menu.

 

Download : UEFI_MULTI-88.zip  - Encrypted with password =  bootwimb



#228 wimb

wimb

    Platinum Member

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

Posted 20 June 2019 - 07:09 AM

*** Update UEFI_MULTI - Version 90 ***

 

- Grub4dos Updated to version grub4dos-0.4.6a-2019-06-17

 

- Partition Style (GPT Or MBR)  and Firmware (UEFI Or Legacy) detected

- grub4dos and Boot\BCD are NOT added to EFI GPT Partition, but are only added to Boot Drive in case of MBR Partition Style

- In Win 8/10 x64 OS then UEFI Boot Manager menu is created or modified in efi\microsoft\boot\BCD in all cases for booting WIM, VHD and VHDX files

 

- Get Access to your Hidden EFI Boot Drive to Add VHD Or WIM as Boot option to your machine
- In Windows 10 x64 run WinNTSetup x64 so that EFI partition is mounted as drive Z:
- Or use R-mouse to open admin cmd window and mount the EFI partition using mountvol Z: /s

 

Download : UEFI_MULTI-90.zip  - Encrypted with password =  bootwimb



#229 steve6375

steve6375

    Platinum Member

  • Developer
  • 7078 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 20 June 2019 - 07:20 AM

Do you know what the latest grub4dos version fixes? Was there an issue with it?



#230 wimb

wimb

    Platinum Member

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

Posted 20 June 2019 - 07:24 AM

Do you know what the latest grub4dos version fixes? Was there an issue with it?

 

I don't know but simply has updated to latest grub4dos version when updating UEFI_MULTI.

 

Anyway latest grub4dos version was tested by me and is working OK.



#231 steve6375

steve6375

    Platinum Member

  • Developer
  • 7078 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 20 June 2019 - 07:54 AM

Seems that the original code was changed in 2018-12-23 version...

2018-12-23 (yaya)   Fixed reading the disk out of bounds without alarm.

and changed back to pre-2018-12-23 code in this new version!



#232 wimb

wimb

    Platinum Member

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

Posted 20 June 2019 - 08:21 AM

Seems that the original code was changed in 2018-12-23 version...

 

Yes I know, but that was already fixed in previous UEFI_MULTI version having grub4dos-0.4.6a-2019-03-25 version

 

Needed for booting expandable VHD from RAMDISK using grub4dos and SVBus driver, See also here and here



#233 steve6375

steve6375

    Platinum Member

  • Developer
  • 7078 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 20 June 2019 - 08:55 AM

No - you misunderstand.

In the 2018-12-23 version, some code was change in disk_io.c (to do with accessing a file outside of partition)

This appears to have introduced a bug because the old code lines were restored back again in the 2019-06-17 version.

So all versions from 2018-12-23 to 2019-06-13 apparently have this bad code.

As far as I can tell however, you would only see the affects of this buggy code if there was a file very near the end of a partition.


  • wimb likes this

#234 wimb

wimb

    Platinum Member

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

Posted 20 June 2019 - 09:08 AM

Ok thanks for giving explanation.



#235 wimb

wimb

    Platinum Member

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

Posted 12 July 2019 - 08:02 AM

*** Update UEFI_MULTI - Version 91 ***

 

- VHD  can be in Folder max 8 chars located on NTFS System Drive

- VHD is never Copied to System drive, but must be located in Root or Folder of NTFS System Drive

- Solved - Failure in Windows PE to create fresh working Boot Manager on empty disk

 

Download : UEFI_MULTI-91.zip



#236 wimb

wimb

    Platinum Member

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

Posted 12 September 2019 - 09:23 AM

How to Add Windows 10XPE as Boot Option to your Internal Harddisk Or SSD

 

1. Create on your Internal Harddisk / SSD the folder Win10XPE with files Win10XPE.wim and boot.sdi
2. Run BOOTICEx64.exe of BOOTICE v1.3.3.2 or as given by alacran and select BCD of current system in Easy mode
3. Add New WIM Boot entry and Select Disk and Partition of Win10XPE and Edit File, SDI file and OS title as indicated
4. Save Current System and Close
5. In BOOTICEx64.exe select BCD of current system in Professional mode
6. In Win10XPE entry with R-mouse Add New element - BootMenuPolicy with setting Legacy
7. In Win10XPE entry with R-mouse Add New element - LoadOptionsString with value DISABLE_INTEGRITY_CHECKS
8. In {ramdiskoptions} or other guid entry use doubleclick on SdiDevice to Select Boot disk and Boot part
9. In {ramdiskoptions} or other guid entry use doubleclick on SdiPath to edit and give value \Win10XPE\boot.sdi
10. Edit normal Windows 10 entry so that BootMenuPolicy is Legacy, which allows on booting straight to select Windows 10 Or Win10XPE 
 
How to make Win10XPE WIM file for booting from RAMDISK  is described in Attached File  Win10_Inst_Eng.pdf   1.78MB   50 downloads

 

W10XPE_Easy_2019-09-12_104342.png == W10XPE_2019-09-12_102847.png == W10XPE_ramdiskoptions_2019-09-12_112052.png
 
Booting with Win10XPE from RAMDISK loaded from Internal SSD is powerful, convenient and extremely fast  B)

  • alacran likes this

#237 alacran

alacran

    Gold Member

  • .script developer
  • 1127 posts
  •  
    Mexico

Posted 12 September 2019 - 11:33 PM

Hi wimb

 

Nice finding, my friend, LoadOptionsString = DISABLE_INTEGRITY_CHECKS let us disable the integrity check for this especifical item in BCD, keeping the integrity check enabled for all the other entries.

 

I don't know if you could implement this on UEFI MULTI for all entries added by the program to BCD (on internal or external) storage device, but it seems as a good improvement if possible.

 

I like to boot my VHDs, *.wims and/or Isos from internal disk/drive as much as possible, nevertheless I always have also an UEFI MULTI USB device just in case.

 

alacran



#238 wimb

wimb

    Platinum Member

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

Posted 13 September 2019 - 04:56 AM

LoadOptionsString with value DISABLE_INTEGRITY_CHECKS solution for Win10XPE and other PE was given by JFX long ago (around 2013 ?) 

and has been implemented in UEFI_MULTI since then for making boot entries for Windows PE located on FAT32 boot drive for booting from RAMDISK.

 

For the internal harddisk the existing FAT32 boot partition is mostly too small to accomodate Win10XPE and the FAT32 drive is hidden and not easily accessible.

In the present solution the Win10XPE can be accomodated on the Windows NTFS partition or other primary NTFS partition.

BOOTICE can modify the BCD of the current system to Add entry for WIM file and allows to indicate disk and partition where the Win10XPE.wim and boot.sdi file are located.

 

Loading Win10XPE from internal SSD is extremely fast whereas loading from USB can be rather slow, however a portable SSD is also fast.



#239 alacran

alacran

    Gold Member

  • .script developer
  • 1127 posts
  •  
    Mexico

Posted 13 September 2019 - 05:16 PM

Sorry, I use bootIce a lot, but as almost all can be done on easy mode and I rarely use professional mode never noticed is was implemented on UEFI MULTI for .wim(s) located on FAT-32 pàrtition, so this LoadOptionsString = DISABLE_INTEGRITY_CHECKS was new for me.

 

alacran



#240 wimb

wimb

    Platinum Member

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

Posted 14 September 2019 - 07:27 AM

*** Update UEFI_MULTI - Version 92 ***

 

- Win10XPE or other PE WIM file + boot.sdi file can be located (also in folder) on NTFS System Drive  :thumbup: e.g. of Internal Harddisk / SSD

- The Hidden FAT32 EFI Boot Drive of Internal Harddisk / SSD is auto mounted as Drive Z: Y: S: Or T: so that it can be selected in UEFI_MULTI

 

This allows to add simply Win10XPE or other PE WIM as boot entry in BCD of Boot Manager menu for your Internal Harddisk or SSD

 

Loading Win10XPE.wim size 775 MB from Internal SSD into RAMDISK takes only 3 seconds  :w00t: and 7 seconds from Portable SSD connected via USB 3.0

 

Total Boot time for Win10XPE is then about 30 seconds from Boot Manager menu until Desktop.

 

 

Download : UEFI_MULTI-92.zip and Attached File  Win10_Inst_Eng.pdf   1.78MB   46 downloads

 

How to make Win10XPE WIM file for booting from RAMDISK at MSFN Forum

 

Win10XPE-2019-09-14_133643.png

 

:cheers:


  • alacran likes this

#241 wimb

wimb

    Platinum Member

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

Posted 30 September 2019 - 07:09 AM

*** Update UEFI_MULTI - Version 93 ***

 

- Calculation of Overflow improved for case of Win10XPE located on NTFS System Drive

 

Download: UEFI_MULTI-93.zip



#242 wimb

wimb

    Platinum Member

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

Posted 2 weeks ago

*** Update UEFI_MULTI - Version 94 ***

 

The selected USB Boot Drive of USB Fixed Disk with MBR partitioning is always Set Active

- bootsect.exe is used if needed to Fix the MBR and PBR Boot code of USB Boot Drive for booting in BIOS mode with Boot Manager Menu

- Update MBR Boot Code checkbox will force to use bootsect.exe on USB Boot Drive of USB Fixed Disk

- removal of old stuff like MbrFix64.exe MBRWiz.exe and grubinst.exe and more ....

 

Download: UEFI_MULTI-94.zip

 

For USB Boot Drive P: of MBR partitioned disk we can Fix the MBR and PBR Boot code for booting in BIOS mode with Boot Manager Menu using:

bootsect.exe /nt60 P: /mbr






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

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users