Jump to content











Photo
* * * * * 1 votes

UEFI MULTI - Make Multi-Boot USB-Drive

windows 10 ssd wim linux uefi aio boot vhdx usb multiboot

Best Answer wimb , 3 weeks ago

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

 

Manual available: [attachment=16506:VHD_WIMBOOT.pdf]

 

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 10 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 10 GB VHD - Format and APPLY WIM on 1 or 2 GB VHD 
- Next time Boot with 1-2 GB VHD WIMBOOT on USB with Grub4dos menu from RAMDISK on all other machines
The 1 GB VHD will be handy for booting from RAMDISK on 4GB RAM machines, but in other cases a 2 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
207 replies to this topic

#201 wimb

wimb

    Gold Member

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

Posted A day ago

In other words:

Apparently the VHD was not given the name that it should have.

But given that filename, everything is as expected and booting is OK.

 

Can you give me the makebt\wim_info\wiminfo.txt file for that Win 8.1 case ?

 

There is something not as expected in that file, so that parsing goes wrong.



#202 alacran

alacran

    Silver Member

  • .script developer
  • 814 posts
  •  
    Mexico

Posted A day ago

In other words:

Apparently the VHD was not given the name that it should have.

But given that filename, everything is as expected and booting is OK.

 

Well yes, I only wanted to report item by item to let you know all was checked carefully, not only just reporting the first thing saw.

 

alacran



#203 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted A day ago

VHD file was created with wrong name W10x64_ES_1.vhd, it should be W8.1x64_ES_1.vhd or 8.1x64_ES_1.vhd.

 

I would anyway advise against using a multidot file name, W81x64_ES_1.vhd would have BTW the same length of W10x64_ES_1.vhd

 

 

 

:duff:

Wonko



#204 wimb

wimb

    Gold Member

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

Posted A day ago

I would anyway advise against using a multidot file name, W81x64_ES_1.vhd would have BTW the same length of W10x64_ES_1.vhd

 

 

 

Yes you are right. It is Microsoft that introduced this extra dot in the Name. So may be we need to remove it again ...

 

I hope alacran can provide the makebt\wim_info\wiminfo.txt file so that I can see why parsing goes wrong in his case.



#205 alacran

alacran

    Silver Member

  • .script developer
  • 814 posts
  •  
    Mexico

Posted A day ago

Sure:

 

Spoiler


  • wimb likes this

#206 wimb

wimb

    Gold Member

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

Posted 11 hours ago

Download -  VHD_WIMBOOT  New Version 1.1 available for testing

 

@alacran

 

In Windows 7 OS then bcdboot.exe 7/8/10 cannot make the VHD internal BCD entry and that is the cause of the problem that you encountered.

 

I have no solution for this problem and so the program VHD_WIMBOOT needs Windows 10 Or Windows 8 / 8.1 OS.

 

The failure in giving the VHD the right name is solved and for Windows 8.1 the extra dot in the VHD filename is removed.


  • alacran likes this

#207 alacran

alacran

    Silver Member

  • .script developer
  • 814 posts
  •  
    Mexico

Posted 10 hours ago

Thanks for this new version, if the program is not compatible with 7, it may not be a big issue, but it is good we now are aware of that before running it.

About the dot on 8.1 I'm glad you fixed it. but also a warning like:  Do not use dot(s) or espaces on files names could be enough, sorry for the extra work my friend.

 

Just downloaded, I'll run some tests ASAP and let you know of my findings.

 

alacran



#208 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 3 hours ago

In Windows 7 OS then bcdboot.exe 7/8/10 cannot make the VHD internal BCD entry and that is the cause of the problem that you encountered.

I have no solution for this problem and so the program VHD_WIMBOOT needs Windows 10 Or Windows 8 / 8.1 OS.

 

If I get this right, you could boot (Wimboot) Windows 7 but you stop because the BCDBOOT cannot make a "correct" BCD entry for it? :w00t:

 

A possible solution is here (whether you will like it or not is another thing):

http://reboot.pro/to...ch-using-linux/

 

:duff:

Wonko







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

9 user(s) are reading this topic

1 members, 7 guests, 0 anonymous users


    Google (1), alacran