Jump to content











Photo
- - - - -

USB Format Tool and UEFI_MULTI

iso linux wim vhd grub4dos grub2 boot manager format usb

Best Answer wimb , 17 December 2020 - 09:05 AM

Update USB_FORMAT-63 and UEFI_MULTI-63 plus Addons and VHD_WIMBOOT_Trusted-65

 

Download:  from wimb GitHub  -   USB_FORMAT-63 and UEFI_MULTI-63

 

and  VHD_WIMBOOT_Trusted-65 and Win_Reduce_Trusted-52 and SVBus_INST_Trusted-20  and Win_Debloat-28

 

Download File E = Encrypted Password = bootwimb   -   Always Disable Windows Defender when working with signed SVBus driver !!

 

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

 

- Added UEFI Grub4dos  and  a1ive UEFI Grub2 for UEFI booting Mini 7/8/10 x64 VHD from RAMDISK - Use Super UEFI setting for UEFI Secure booting
- Added signed SVBus driver for UEFI booting VHD from RAMDISK

 

Credits and Thanks to:

synchronicity aka Eric Biggers for making wimlib

schtrom for making SVBus Virtual SCSI Host Adapter for GRUB4DOS - signed SVBus driver
a1ive for making UEFI Grub2
yaya2007 and a1ive for making UEFI Grub4dos aka Grub4efi or G4E

a1ive for making Grub2 File Manager

- ventoy for making Linux vDisk Boot Plugin that allows to use Grub2 vdiskchain to boot Linux VHD
alacran for help and support and testing and initialising several important topics
- liuzhaoyzz for help in solving boot_image_handle not found problem in case of UEFI Grub4dos

cdob for making WinSxS_reduce
ValdikSS for making Super UEFIinSecureBoot Disk v3 - More Info on UEFI Secure booting Grub2

chenall, yaya, tinybit and Bean for making Grub4dos

JFX for making WinNTSetup and WofCompress

- Pauly for making BOOTICE

- Mattwatti for making EfiGuard to Disable Driver Signature Enforcement DSE

- erwan.l for making offlinereg
- Nir Sofer for making AdvancedRun (64-bit)
- Sordum for making Defender Control  and  Windows Update Blocker  and  PowerRun  and  Firewall App Blocker

and everyone else that has contributed to these topics - W4RH4WK Debloat PowerShell scripts

and to Erwan.l and Nuno Brito for keeping alive this forum, sometimes called an old lady ....  ;)

 

More Info:  VHD_WIMBOOT Mini 7/8/10 x64  and   Grub4dos for UEFI aka GRUB4EFI Or G4E

 

[attachment=17676:USB_FORMAT_51_2020-12-17_103331.jpg] == [attachment=17677:UEFI_MULTI_51_2020-12-17_103534.jpg] == VHD_WIMBOOT_47_2021-01-04_100522.jpg == Win_Reduce_38_2020-11-30_125950.jpg == UEFI_RAMOS_10_2020-12-26_133815.jpg == UEFI_USB_2020-12-26_101643.jpg == W11x64_2021-10-03_145700.jpg == W11x64_WB_2021-10-03_153529.jpg == Mini-11x64_RAMDISK_2021-10-03_154502.jpg

:cheers:

Go to the full post


  • Please log in to reply
129 replies to this topic

#76 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 29 December 2020 - 10:18 AM

I already downloaded a few hours ago your very last version and saw it still has the UEFI grub4dos 2020-12-15 version.

 

I had that VHD already made with boot files/folders created uncompressed on both partitions manually to test the test version 2020-12-26 on this post, I didn't have the need to re-make it, just used the 2020-12-15 version and it fail.

 

alacran



#77 wimb

wimb

    Platinum Member

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

Posted 29 December 2020 - 10:31 AM

I already downloaded a few hours ago your very last version and saw it still has the UEFI grub4dos 2020-12-15 version.

 

I had that VHD already made with boot files/folders created uncompressed on both partitions manually to test the test version 2020-12-26 on this post, I didn't have the need to re-make it, just used the 2020-12-15 version and it fail.

 

alacran

 

Again what is the WOF Status report made by WOF_Compress_Trusted.cmd of the EFI  folder inside that VHD ?

 

To make conclusion about a program requires to do a complete test ....



#78 wimb

wimb

    Platinum Member

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

Posted 29 December 2020 - 01:18 PM

 

 

removal of EFI folder requires Trusted Installer, but renaming of EFI folder as x-EFI can be done as Administrator.

The EFI folder inside VHD is already created by WinNTSetup and cannot be removed simply.

VHD_WIMBOOT Capture and Apply will prevent WOF Compression of EFI folder inside VHD when new WimBootCompress,ini is used as present in VHD_WIMBOOT-43

What I can do is to modify UEFI_MULTI and VHD_WIMBOOT so that in case of 2 Partition VHD that EFI folder is not made in NTFS partition and when present is renamed as x-EFI.

I think this can solve the problems encountered with EFI folder in NTFS partition of 2 Partition VHD's

Also new UEFI Grub4dos version will be used, but give me some time to realise it .....

 

Continue after discussion at MSFN - quote from MSFN

 

Done !

 

Update USB_FORMAT-52 and UEFI_MULTI-52 and VHD_WIMBOOT-44

 

- UEFI grub4dos version 2020-12-26

- in case of 2 Partition VHD then EFI folder is not made in NTFS partition and when present is renamed as x-EFI

 

Download:  from wimb GitHub  -   USB_FORMAT-52 and UEFI_MULTI-52 and VHD_WIMBOOT-44

 

Download File E = Encrypted Password = bootwimb 

 

Manual:  VHD_WIMBOOT.pdf - - Always Disable Windows Defender when working with signed SVBus driver !!


  • alacran likes this

#79 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 31 December 2020 - 02:03 AM

I found a bug in UEFI_MULTI last version, unless I'm wrong and this is not the last, (as there have been three v5.2) but you may check that on attached pictures.

 

The program shows a message and after accepting the message, the program closed and left the VHD mounted, please see attached pictures.

 

NOTE: Mini-10-UEFI.vhd 2046 MB single NTFS partition already had uncompressed Boot and EFI folders, it is the same VHD I was testing from the internal HD, but now I copied it to a USB device and used UEFI_MULTI to make the entries on both external BCDs, both menu.lst and grub.cfg pointing to the new location into VHD-USB folder on U-NTFS drive.

 

EDIT: The VHD was damaged after this, not a big deal, I will copy it again and will make the required entries manually.

 

alacran

Attached Thumbnails

  • UEFI_MULTI-fail.png
  • Program date.png
  • Program date-2.png


#80 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 31 December 2020 - 06:52 AM

I kept thinking about this issue, and I have a suggestion for you:

 

VHD_WIMBOOT

 

I think it will be good to include also under its WimBootCompress.ini

on [ExclusionList]

 

\Boot\*  \Boot  >>> Thanks to wimb, for make me note this mistake, see Posts No. 82 and 83
\EFI\*     \EFI   >>> Thanks to wimb, for make me note this mistake, see Posts No. 82 and 83

\bootmgr

\BOOTNXT

 

And force to use that WimBootCompress.ini always Then during capture those files/folders will not be captured to the WIM

 

Latter after apply the WIM to the selected location, just create the external boot files/folders as always, and the internal (into the VHD) on the respective drive letter of first partition always (which is FAT-32 on 2 partitions VHD or NTFS on single partition), and they will be always fresh and uncompressed this way.

And in the case they exist on an old previously captured WIM file as they are also included under [PrepopulateList] they will be copied uncompressed anyway.

 

UEFI_MULTI

 

The user has to follow your procedure (after all you are the author and you especify the requirements) and it may clearly say,: Use it for VHDs created by VHD_WIMBOOT or something like that, of course I know you can make this warning more friendly.

 

As VHD_WIMBOOT will not allow to have the boot files/folders compressed all will be safe.

 

And then you will not have to worry anymore about decompress compressed files/folders or rename them, etc. and UEFI_MULTI should make only the required external and internal entries and that's all.

 

It seems to me this can simplify a lot your work, and the complexity of your programs.

 

What do you think about this suggestion?

 

alacran



#81 wimb

wimb

    Platinum Member

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

Posted 31 December 2020 - 02:12 PM

Update USB_FORMAT-53 and UEFI_MULTI-53 plus Addons and VHD_WIMBOOT-46

 

Download:  from wimb GitHub  -   USB_FORMAT-53 and UEFI_MULTI-53 and VHD_WIMBOOT-46

 

Download File E = Encrypted Password = bootwimb 

 

Manual:  VHD_WIMBOOT.pdf -

 

Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver !!

otherwise wimlib and Boot errors will occur .....

 

- bug due to adding WofCompress found and bug removed - thanks to alacran for reporting error

- Update of UEFI Grub4dos to version BOOTX64 2020-12-29, renamed to UEFI_MAN\EFI\Boot\bootx64_g4d.efi 

- in case of 2 Partition VHD then EFI folder is not made in NTFS partition and when present is renamed as x-nnn-EFI  nnn = Random 100-999

- added in UEFI_MAN\EFI\grub folder the UEFI Grub4dos Tools according to alacran

- removed SVBus-signed_2 folder since there are to many conflicts with AV and Defender software

- Instead a separate encrypted SVBus-signed_2-E.zip folder with password reboot.pro is distributed that contains also the essential instx64.exe Installer

 

@alacran

Your proposal to modify [ExclusionList] of WimBootCompress.ini does not work properly - it results in empty Boot and EFI folder in Captured WIM file

 

EDIT: modify [ExclusionList] of WimBootCompress.ini can work if we use -  :)

\bootmgr
\BOOTNXT
\Boot
\EFI
\x-*Boot
\x-*EFI


  • alacran likes this

#82 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 31 December 2020 - 11:16 PM

 

EDIT: modify [ExclusionList] of WimBootCompress.ini can work if we use -  :)

\bootmgr
\BOOTNXT
\Boot
\EFI

 

My mistake, sorry my friend, but copy-paste + 4 or 5 drinks was the cause of the mistake, I will fix my previous post and will add a note, to avoid confusion to future readers.

 

alacran



#83 wimb

wimb

    Platinum Member

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

Posted 31 December 2020 - 11:30 PM

Happy New Year and Best Wishes for 2021    :magic:  :thumbup:  :worship:

 

  :cheers:


  • alacran likes this

#84 wimb

wimb

    Platinum Member

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

Posted 13 January 2021 - 08:05 AM

Update USB_FORMAT-54 and UEFI_MULTI-55 plus Addons and VHD_WIMBOOT-50

 

Download:  from wimb GitHub  -   USB_FORMAT-54 and UEFI_MULTI-55 and VHD_WIMBOOT-50

 

Manual:  VHD_WIMBOOT.pdf - Download File E = Encrypted Password = bootwimb 

 

- Update UEFI Grub4dos - G4E

- Update UEFI Grub2 and Grub2 FileManager

 

- Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver

 

:cheers:


  • alacran likes this

#85 wimb

wimb

    Platinum Member

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

Posted 28 January 2021 - 10:50 AM

Update USB_FORMAT-56 and UEFI_MULTI-56 plus Addons and VHD_WIMBOOT-51

 

Download:  from wimb GitHub  -   USB_FORMAT-56 and UEFI_MULTI-56 and VHD_WIMBOOT-51

 

Update Manual:  VHD_WIMBOOT.pdf  and Win10_Install.pdf  - Download File E = Encrypted Password = bootwimb 

 

- Update UEFI Grub4dos - G4E - grub4dos-for_UEFI-2021-01-22.7z

- Update UEFI Grub2 - UEFI Secure Grub2 booting Enabled in \grub\grub.cfg by using fucksb commands of sbpolicy.mod    :magic:   :worship:

- Added support for Linux VHD booting with Grub2 or Grub4dos and vdiskchain 1.2

preconfigured menu entries in Grub2 \grub\grub.cfg and Grub4dos \menu.lst for Ubuntu.vhd.vtoy and Ubuntu.vdi.vtoy and KALI.vdi.vtoy on 2nd partition of USB

 

Credits and Thanks to ventoy for making Linux vDisk Boot Plugin that allows to use Grub2 vdiskchain to boot Linux VHD   :magic:  :worship:

 

- Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver

 

:cheers:


  • alacran likes this

#86 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 29 January 2021 - 04:38 AM

Update USB_FORMAT-56 and UEFI_MULTI-56 plus Addons and VHD_WIMBOOT-51

 

 - Added support for Linux VHD booting with Grub2 or Grub4dos and vdiskchain 1.2

 

I'm sorry to tell you this my friend:

 

It seems to me your programs have vdiskchain 1.1 which is 2,428,992 bytes from Jan/23/2021, vdiskchain 1.2 is 2,428,352 bytes from Jan/25/2021.

 

Also there is a new a1ive's grub2 released 18 hours ago: [72cbd00]: map/bcd: bug fix (a1ive), I really don't know if you used this fixed version, but I think you better check.

 

alacran

Attached Thumbnails

  • vdiskchain.png


#87 wimb

wimb

    Platinum Member

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

Posted 29 January 2021 - 06:34 AM

It seems to me your programs have vdiskchain 1.1 which is 2,428,992 bytes from Jan/23/2021, vdiskchain 1.2 is 2,428,352 bytes from Jan/25/2021.

 

Also there is a new a1ive's grub2 released 18 hours ago: [72cbd00]: map/bcd: bug fix (a1ive), I really don't know if you used this fixed version, but I think you better check.

 

 

Thanks for your remark about vdiskchain and Grub2 versions. Everything is Fixed now.

 

- UEFI_MULTI has Update UEFI Grub2 checkbox and VHD_WIMBOOT has Update G checkbox

  that can be used to Update existing Grub2 and Grub4dos and vdiskchain version on GPT and MBR Boot Drive

 

Download:  from wimb GitHub  -   USB_FORMAT-56 and UEFI_MULTI-56  plus addon-agFM and VHD_WIMBOOT-51

 

UEFI_MULTI_Update_Grub2_2021-01-29_090549.jpg == VHD_WIMBOOT_UpdateG_2021-01-30_064101.jpg

 

:cheers:


  • alacran likes this

#88 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 29 January 2021 - 07:44 PM

vhd_wimboot 5.1 working fine too.



#89 wimb

wimb

    Platinum Member

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

Posted 30 January 2021 - 05:38 AM

vhd_wimboot 5.1 working fine too.

 

Thank you for testing  :)



#90 wimb

wimb

    Platinum Member

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

Posted 16 February 2021 - 07:29 AM

Update USB_FORMAT-57 and UEFI_MULTI-57

 

Download:  from wimb GitHub  -   USB_FORMAT-57 and UEFI_MULTI-57

 

Download File E = Encrypted Password = bootwimb 

 

- Update UEFI Grub4dos - G4E - grub4dos-for_UEFI-2021-02-10.7z

- Added support for Integrate Linux Portable distros to U-BOOT with menu entries as given by alacran

 

- Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver

 

:cheers:


  • alacran likes this

#91 wimb

wimb

    Platinum Member

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

Posted 15 April 2021 - 07:30 AM

Update USB_FORMAT-58 and UEFI_MULTI-58 and VHD_WIMBOOT-54

 

Download:  from wimb GitHub  -   USB_FORMAT-58 and UEFI_MULTI-58 and VHD_WIMBOOT-54

 

Download File E = Encrypted Password = bootwimb 

 

- Update a1ive Grub2 2021-03-01

- Update UEFI PassMark Memtest86 V9.0 (build 2000) - added to UEFI Grub2 Menu

- Support booting from MBR NVME SSD with Windows Boot Manager Menu in UEFI mode and in MBR BIOS mode

 

- Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver

 

:cheers:


  • alacran likes this

#92 zammibro

zammibro

    Member

  • Members
  • 59 posts
  •  
    United States

Posted 13 May 2021 - 11:54 PM

 Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver

 

 

Not possible completely, except in Safe mode. I guess you mean some forms of active protection, which are multiple. Eset is a good example - just look in Settings.

 

My question however: Is it possible to use UEFI Multi tool not only for USB drives, but also for internal PC non-removable drives? If yes, can you give some detail examples, like booting an EFI Linux ISO from an HDD on a Legacy Windows PC (How To)? I ask since you often refer to this tool in various topics, despite most are not related to USB drive boot. May be you can add such options to the tool menu, if any required or different?


Edited by zammibro, 13 May 2021 - 11:55 PM.


#93 zammibro

zammibro

    Member

  • Members
  • 59 posts
  •  
    United States

Posted 14 May 2021 - 02:56 AM

I read your VHD_WimBoot.pdf, and it appears to contain some info on adding UEFI image boot options to internal hard drives of a Legacy PC on pages 10 -11 (not numbered though). However, it would help enormously, if you post it here as a numbered sequence, since the info is complex enough and requires good knowledge of your tools. Meanwhile, the actions may be simple enough for manual copy-paste, if source and destination folders are clearly identified in the Instructions.


Edited by zammibro, 14 May 2021 - 02:59 AM.


#94 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 14 May 2021 - 04:36 AM

Please read this post, it may clarify some things for you: http://reboot.pro/in...400#entry218202

 

alacran



#95 wimb

wimb

    Platinum Member

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

Posted 14 May 2021 - 05:21 AM

I read your VHD_WimBoot.pdf, and it appears to contain some info on adding UEFI image boot options to internal hard drives of a Legacy PC on pages 10 -11 (not numbered though). However, it would help enormously, if you post it here as a numbered sequence, since the info is complex enough and requires good knowledge of your tools. Meanwhile, the actions may be simple enough for manual copy-paste, if source and destination folders are clearly identified in the Instructions.

 

UEFI_MULTI can be used to let internal MBR partitioned SSD make booting with Grub4dos in BIOS mode.

Grub4dos entry is added to Windows Bootmanager Menu

Chainloading from Grub4dos to Grub2 Menu or Linux ISO Menu or vdiskchain and more is available.

 

UEFI_MULTI can be used to let internal MBR or GPT partitioned SSD make booting in UEFI mode with Grub2 or UEFI Grub4dos.

For UEFI mode booting some additional manual steps are needed as described in detail on page 11 of VHD_WIMBOOT.pdf

The reason that manual steps are needed is just a precaution so that only experts can make this happen ....

In that case the computer is booting with Grub2 which can chainload to Windows Boot Manager or UEFI Grub4dos Menu and more options ....

 

The page numbering is visible in the browser as indicated by the red arrow ....

 

UEFI_Secure_Multi-Boot_2021-05-14_065556.jpg



#96 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 26 July 2021 - 06:18 AM

@ wimb

 

Hi my friend, if it is not too difficult for you, I suggest to incorporate ntloader to your programs.

 

It seems to me it have some good advantages, as it works fine to boot PE WIMs, VHDs and OSs without the need to create boot files/folders and in consecuence also no need to edit BCDs, no need to use ntfs_x64.efi.

Its internal default code is prepared for the more difficult escenarios, already takes care of Secure Boot verification, signed drivers verification, etc., also several additional options are available but so far I haven't needed to use them.

 

But it do not work for FAT-32 VHDs made just extracting the WinPE.ISO into them,  which we were using just for fast testing purposes, so this do not matter if we can boot from the WIM file, also do not work for VHD Wimboot (only that option will need to remain using current procedure).

 

For additional info please see this post and 2 following posts.

 

alacran



#97 wimb

wimb

    Platinum Member

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

Posted 26 July 2021 - 08:36 AM

Hi my friend, if it is not too difficult for you, I suggest to incorporate ntloader to your programs.

 

 

I guess ntloader is the successor of ntboot that also avoids the need to load ntfs_x64.efi driver ?

 

UEFI_MULTI makes for VHD the ntboot entry - UEFI Grub2 ntboot SVBus  RAMDISK

You mean you want me to replace ntboot entries by ntloader entries for the case of VHD having 1 partition ?

 

What else is needed for using ntloader ?  What extra files are needed in grub Or EFI\grub folders ?

 

Is it possible to use ntloader in case of VHD having two partitions ?

 

I think for booting VHD as FILEDISK it is preferred NOT to use SVBus driver, but instead to use the Microsoft VHD driver.

Is it possible to use a1ive Grub2 ntloader booting VHD as FILEDISK using the Microsoft VHD driver (without install of SVBus driver) ?

 

VHD booting as FILEDISK straight from Boot Manager Menu now works in UEFI and MBR BIOS mode for VHD having 1 or 2 partitions without the need to install SVBus driver.

I think ntloader will require install of SVBus driver and only works for VHD having 1 partition, which makes ntloader working only in limited cases.

 

VHD with 1 or 2 partitions booting as RAMDISK from UEFI Grub2 or UEFI Grub4dos  or MBR Grub4dos Menu is supported already when SVBus driver is installed.

What would be the advantage of using ntloader in this case ?  I think no need to load ntfs_x64.efi driver in case of UEFI booting VHD with 1 partition.

I think ntloader has disadvantage that it only works for VHD having 1 partition.

 

I think it is interesting to use ntloader instead of ntboot for UEFI booting VHD with 1 partition from RAMDISK thus avoiding the need to load ntfs_x64.efi driver.

That can be implemented.

 

Also ntloader might be interesing for booting WIM files and NT6+ OS straight from UEFI Grub2 menu, which in that case is easier than the need to select first Windows Boot Manager.



#98 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 26 July 2021 - 08:15 PM

@ wimb

 

EDIT: Please see following post I found a big issue.

 

It also seems to me ntloader is the successor of ntboot, and yes it avoids the need to load ntfs_x64.efi driver.

 

Just tested filedisk booting a 2 partition VHD and it works fine, on same VHD I unistalled SVBus driver and rebooted fine again, and verified SVBus drivers is not there anymore, so I confirmed without any doubt ntloader do not need SVBus driver for filedisk boot, it is only required for Ramboot.

 

The author recommens to copy initrd.lz1, ntloader.i386 (only for x86) and ntloader (only for x64) to the root of the partition holding the file we want to boot, so I followed the instructions on my tests.

 

There is a post from liuzhaoyzz (using an older version of ntloader) with his prefered option for VHD Ramboot, and he puts same files on /EFI/grub folder, I tested this approach with single partitioned VHDs and they Ramboot fine.

I wasn't able to Ramboot a 2 partition VHD with this approach, [even changing (hd-1,0) to (hd-1,1)], maybe I did someting wrong or something else is required.

Perhaps you could prefer liuzhaoyzz approach if you can make it work with a 2 partitions VHD. I didn't tested this approach for filedisk booting. 

 

So far I can confirm:

  • The author states it works on MBR/CSM or UEFI with grub2, a1ve's grub2 and grub4dos. (I only tested using G4D and G4E).
  • It works very fine with PE WIM files and single partitioned VHD files.
  • No need to use ntfs_x64.efi driver.
  • SvBus is only required for Ramboot.
  • BCDs external and internal entries or any other boot files/folders are not required.
  • Additional required files are initrd.lz1, ntloader.i386 (only for x86) and ntloader (only for x64) the author recommends on the root of the partition holding the file we want to boot. But liuzhaoyzz uses /EFI/grub folder, for his Ramboot commands.
  • Also 2 partitions VHDs boot fine as filedisk, I wasn't able to Ramboot 2 partitions VHDs with liuzhaoyzz approach, (maybe my fault).
  • On the ntloader topic is mentioned it do not work for Wimboot VHDs.

All tests were made using a USB device formated with USB_FORMAT, but using grub4dos-0.4.6a-2021-06-02 and  grub4dos-for_UEFI-2021-06-19 (this was the newer when started testing ntloader), and I haven't updated it yet to be consistent.

 

Hope this info can be usefull for you.

 

alacran



#99 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 27 July 2021 - 02:45 AM

@ wimb

 

Please wait before making any change, using same USB device with unchanged menus, tested on another PC and I can't boot anything if ntloader is involved, but the usual BCD entries boot fine same PE WIMs, and the usuall menus work very fine to run VHDs on this problematic machine.

 

On the machine where ntloader do not work the USB device is seen as a USB flash drive (no way to change that on it), so it seems to me this affects the uuid reading, and then the WIM or VHD do not boot, same on MBR/CSM or UEFI

 

I'm very sorry for the inconvenience and make you waste your time, but just now found this issue.

 

alacran



#100 wimb

wimb

    Platinum Member

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

Posted 27 July 2021 - 05:24 AM

So far I can confirm:

  • The author states it works on MBR/CSM or UEFI with grub2, a1ve's grub2 and grub4dos. (I only tested using G4D and G4E).
  • It works very fine with PE WIM files and single partitioned VHD files.
  • No need to use ntfs_x64.efi driver.
  • SvBus is only required for Ramboot.
  • BCDs external and internal entries or any other boot files/folders are not required.
  • Additional required files are initrd.lz1, ntloader.i386 (only for x86) and ntloader (only for x64) the author recommends on the root of the partition holding the file we want to boot. But liuzhaoyzz uses /EFI/grub folder, for his Ramboot commands.
  • Also 2 partitions VHDs boot fine as filedisk, I wasn't able to Ramboot 2 partitions VHDs with liuzhaoyzz approach, (maybe my fault).
  • On the ntloader topic is mentioned it do not work for Wimboot VHDs.

All tests were made using a USB device formated with USB_FORMAT, but using grub4dos-0.4.6a-2021-06-02 and  grub4dos-for_UEFI-2021-06-19 (this was the newer when started testing ntloader), and I haven't updated it yet to be consistent.

 

 

Thanks for the detailed info regarding ntloader.

 

Sure I will do a lot of testing before releasing new version of my programs and will wait until issues are gone ....







Also tagged with one or more of these keywords: iso, linux, wim, vhd, grub4dos, grub2, boot manager, format, usb

13 user(s) are reading this topic

0 members, 13 guests, 0 anonymous users