JFYI
I want to share with all of you the following test.
PREAMBLE:
Until now all my MinWin VHDs were manually made as very frecuently I use certain sizes not available in VHD_WIMBOOT, and making them manually also allows me to name them as I prefer, so far all my MinWin VHDs have a 100 MB FAT-32 First Primary Active Partition..
Our fellow devdevadev asked me to check if a MBR - Bios/UEFI VHD made using WinNTSetup is capable to Ramboot in MBR/CSM and UEFI environments by means of respective version of grub4dos + SvBus driver.
NOTE: ONLY partition layout available in WinNTSetup to make a 2 partitions MBR initialized VHD, bootable in Bios/UEFI environments is having the FAT-32 Active Primary Partition as second partition.
Using as source my MinWin-10x64.wim captured with VHD_WIMBOOT as Wimboot LZX compressed (size 812 MB), that already has SVBus driver installed, and it is the same used in all my recent MinWin VHDs.
Made a 1 GB VHD named MinWin-WB.vhd by means of WinNTSetup:
- VHD MBR partitioned, fixed size.
- FAT-32 Second Primary Active Partition 100 MB, named ESP
- NTFS First Primary Partition the rest of the space.
PROCEDURE:
- Decided to make a Wimboot mode installation as it requieres only a very small VHD and the WIM file is applied in just a few seconds.
- Tried to install into the VHD, (NTFS partition), my MinWin-10x64.wim in Wimboot mode using WinNTSetup, it failed to install several times, and always gave me a message saying that wimlib_extact_image 0xF2: Failed to open a file, please see attached photo (it is pending to find the cause of this failure yet).
- Then used wimlib-clc program by Tokener to install MinWin-10x64.wim into the NTFS partition on the VHD in Wimboot mode, all was made perfectly fine.
- After this in an elevated command prompt I created the boot files/folders into the EFI (FAT-32) partition, required for Ramboot.
- I intentionally omited create the external boot files/folders into the HD.
- Using BootIce edited both BCDs into ESP partition first in Easy mode enabling Detect HAL and Kernel and boot in Test Mode, and disabling Metro boot manager, and latter in Professional mode added the option LoadOptionsString = DISABLE_INTEGRITY_CHECKS.
After this I just created the grub4dos entries:
MBR menu.lst:
I created the enty using same commands as usually, but in this case root is (hd-1,1) where the bootmanager resides now.
Applies to a Wimboot VHD located into internal HD (present case)
title MinWin-WB.vhd - SVBus RAMDISK - 1 GB - map as (hd)
find --set-root --ignore-floppies /MinWin-WB.vhd
map --top --mem /MinWin-WB.vhd (hd)
map --hook
root (hd-1,1)
chainloader /bootmgr
Applies to a Wimboot VHD located into a external USB device.
title MinWin-WB.vhd - SVBus RAMDISK - 1 GB - map as (hd-1)
find --set-root --ignore-floppies /MinWin-WB.vhd
map --top --mem /MinWin-WB.vhd (hd-1)
map --hook
root (hd-1,1)
chainloader /bootmgr
UEFI menu.lst:
I created the enty using same commands as usually, in this case I didn't need to edit the commands.
title MinWin-WB.vhd - SVBus RAMDISK - 1 GB - map as (hd)
find --set-root --ignore-floppies /MinWin-WB.vhd
map --mem --top /MinWin-WB.vhd (hd)
chainloader (hd-1)
It Rambooted very fine in MBR/CSM and also in UEFI
CONCLUSIONS:
As long as using the right commands in respective menu.lst, it doesn't matter if the Fat-32 ACTIVE Prinary Partitition is the second partition.
Even if latter is found the cause of the failure in WinNTSetup, and there is found a way to use it to apply my MinWin-10x64.wim that already has SVBus installed for second installation, I assume the BCDs created by WinNTSetup will have to be edited, if not as SVbus driver is not signed by MS the VHD will not be capable to filedisk boot or Ramboot.
EDIT: From: http://reboot.pro/in...422#entry221523
New SVBus_v1.3 signed was just uploaded.
v1.3 uses a different certificate that is not blacklisted so far, so there is no need to edit all the internal and external BCDs
PENDINGS:
Find the cause of the issue that caused that WinNTSetup wasn't able to apply my MinWin-10x64.wim captured with VHD_WIMBOOT to the VHD.
I need to check if VHD_WIMBOOT program by wimb is capable or not to install my MinWin-10x64.wim into a VHD created by WinNTSetup, having the FAT-32 Active Primary Primary Partition as second partition.
If it works fine doing this task, maybe there will be no need to manually edit the BCDs using BootIce. And also maybe could be no need to create manually both menu.lst entries
alacran