Jump to content











Photo
* * * * * 1 votes

Ultimate-Super-Smart-Secret 'Removable' USB Drive with Mega-Booting

multi boot dual partition grub4dos easy2boot removable usb drive iso image uefi uefi multi.exe usb booting winntsetup 3

  • Please log in to reply
77 replies to this topic

#1 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 18 June 2014 - 02:44 AM

             Hello Everyone.......welcome.gif

Specially to 'All Experts'.................

 

First tons of thanks to all Experts for creating 'Easy2Boot', 'RMPrepUSB', 'Modified E2B', 'WinNTSetup3',
'Win8.1UpdateSE x64 boot.wim', 'NUFD FORMAT.exe', 'UEFI MULTI.exe', 'Bootice.exe' etc........

 

I need help of  Experts in order to complete this tutorial so please help me by suggesting Step by Step Procedure............ 


I have a 'Removable USB Drive' which have a FAT32 'Partition 1' and a FAT32 Active 'Partition 2'

Normally 'Partition 1' always be 'Visible' in 'Windows OS' while 'Partition 2' become 'Invisible' in 

'Windows OS'. We can install/integrate a special Windows disk driver (e.g.cfadisk) within 

'Win8.1U1SE_x64_boot.wim' during creation which will trick Windows into treating a

 Removable-media drive as a Fixed-disk drive.


This is the Special Configuration exactly what I want for my 'Removable USB Drive'.

                    - Special Configuration for Removable USB Drive -
______________________________________________________________________

Partition 1 5 GB FAT32 - Visible to Windows OS - will be used only for DATA Storage Purpose

 

Partition 2 - 9.7 GB FAT32 type Active Partition - Invisible to Windows OS but will be Visible for running

'Win8.1U1SE_x64_boot.wim' due to integration of "cfadisk" driver.

"UEFI_MULTI.exe" will be used in order to copy 'Win8.1U1SE_x64 boot.wim' file to Root, an several

other ISO's to directory \imagesmake the Boot files and EFI folder also Grub4dos mbr and grldr 

and make 'BCD option to boot Grub4dos (E2B)'

Easy2Boot Files (.iso , .img , .imgPTN etc payload files with be placed within \_ISO\MAINMENU folder)

+'Win_7/8/8.1_Inst.imgPTNLBAa' will be placed in\_ISO\WIN or \_ISO\MAINMENU folder

WinNTSetup 3 (BootIce included in tools folder).

______________________________________________________________________

 

So that my 'Removable USB Drive' boot directly from 'Partition 2' into UEFI + BIOS mode with 

Boot Manager Menu. Thus 'Win8.1U1SE_x64_boot.wim' will be booted directly from 'Boot Managermenu entry in both UEFI and BIOS mode while 'Easy2Boot' will be booted from 'Grub4dos' menu entry in BIOS/UEFI (UEFI if possible).

 

Ultimate-Super-Smart-Secret 'Removable' USB Drive Mega-Booting should be done in following order-

           -------------------------------------------------------------------------------------------------------------------------------

                Boot UEFI + BIOS with 'Win8.1UpdateSE x64 boot.wim' direct from Boot Manager Menu into RAMDISK
                Boot UEFI - F12 - BIOS - Grub4dos - (Easy2Boot) +/ (Win XP/7/8 VHD - Ramdisk) 

           -------------------------------------------------------------------------------------------------------------------------------

                                        

Note- After booting from USB with 'Win8.1U1SE_x64_boot.wim' , I will use portable App 'WinNTSetup_x64.exe' to mount 'Win_7/8/8.1_Inst.imgPTNLBAa' (within from \_ISO\WIN folder of Partition 2) in ImDisk Virtual Drive.

'WinNTSetup 3' will prepare local harddisk for Install of Win 7/8/8.1

 

Challanges - Currently 'Win8.1SE' package does not contains script for adding/integrating 'cfadisk' driver into'Win8.1U1SE_x64_boot.wim' . I request All related Experts (Specially to 'ChrisR') for adding a

script for 'cfadisk' driver in next release of 'Win8.1SE' package.

 

Is it possible to implement above Configuration in 'Removable USB Drive ?

 

Please study above configuration carefully and give your precious suggestions in order to implement above configuration if possible.......

 

Regards..


Edited by devdevadev, 12 July 2014 - 02:13 AM.

  • r0manas likes this

#2 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 18 June 2014 - 04:17 AM

First lots of honor and regards to 'Wonko', 'jaclaz' and 'HALIKUS' for encouraging me.............


I am using 'Easy2Boot' from a long time which I think is the Best and Unique MultiBoot solution for me. Following are the top features which I love in 'E2B'-

1- 'Easy2Boot' is very easy to use because of just Drag and Drop of 'Payload Files'.
2- It provide facility of 'Master Password' for 'E2B Menu' so that No other person can easily
either Boot from my 'E2B' USB Drive or Harm/Corrupt/Copy my 'E2B' files.
3- I can easily configure Background, Wallpaper and Menus of 'E2B' according to my interest.
4- 'Pass-Pass' is already integrated within 'Easy2Boot' Directory.
5- 'E2B' allow me to have a '2nd partition' in order to make a 'secret' hidden partition and
protects my E2B files. It also provide 'E2B_PTN_SWAP.mnu' in order to Swap between the
two Partitions. 
6- 'PTN2_Menu.mnu' allow me booting of Payload files (but not Windows Install ISOs) within
from \_ISO folder of Other Partitions or even from, Other Drives
'E2B' also allow to have more than two Partitions in both USB Flash and USB HDD drives.
7- No limit to the number of different Linux, Windows Install, WinPE, etc. ISOs or other payload files
8- I can use a USB Hard disk with two or more partitions and still UEFI boot (even if they are all 
'NTFS' Partitions) - no complex GPT partitions neeed.
9- UEFI booting of Windows Installers and Linux LiveCD payloads via a Partition image 
(and most other UEFI-enabled payloads too, such as KonBoot).
10- I can use 'Win8.1U1_to_GO.imgPTNLBAa' as a Payload file within \_ISO\MAINMENU folder
11- UEFI boot to an NTFS partition (via Clover + first FAT32 ptn). Aso support 
Dual Partition images -e.g. ( FAT32 + NTFS , NTFS +FAT32 )
12- I can use 'E2B' for UEFI/MBR Booting of Windows Installers, ERD, MSDart, warezs, DLCD,
UBCD, KonBoot_2.4, HitMan Pro, Eset, Antivirus, XP Install to SATA Disk, MemTest86+, MS-DOS, 
FreeDos, All LinuxLiveCDs, Linux+Persistance, WinBuilder ISOs, WinPE ISOs, HP ISO Utilities, 
USB Drive Images (e.g. YUMI, XBOOT, WinSetupFromUSB, SARDU, Rufus), and many 100's more..
13- And most important thing for me is that 'Easy2Boot' is developed by 'Steve Si' who is a very 
'Cool and Supportive' person. He always provide update and improvement on regular basis.
He also added lots of feature and improvement for me in various versions of 'Easy2Boot'. 
 

I am using 'Easy2Boot' from one year and I do not prefer any other Multi-boot tool except it because it fulfill my all requirements. Easy2Boot is the Best, Unique and Universal Multiboot tool which I have used ever. But I always have to change BIOS settings (UEFI mode to BIOS/MBR/CSM mode and Disable Secure Boot) two times (Before and After Windows Installation) in order to boot 'Easy2Boot' and load 'E2B Menu' in UEFI based PC which I never want to do. E2B also cannot UEFI boot via System Firmware for Dual Partitioned Removable UFDs.

Actually following is the para which force me to use 'UFD_FORMAT' and 'UEFI_MULTI'

" Win8.1SE x64 boot.wim of size 400 MB is Universal WIM Boot Image file for booting BIOS and UEFI PCs. After booting from USB with x64 boot.wim you can use portable App WinNTSetup_x64.exe to mount XP/7/8 Setup ISO in ImDisk Virtual Drive. WinNTSetup3 will prepare local harddisk for Install of XP/7/8 "

In fact, 'UFD_FORMAT' and 'UEFI_MULTI' are very good tool but both of them does not fulfill my needs. .i.e
'UFD_FORMAT' does not provide 'Partition size' option in order to create a desired size 'Partition 1' and 'Partition 2' while RMPrepUSB allow us to create a desired size 'Partition 1' by 'Partition Size' option. 'UEFI_MULTI' also does not fully satisfy me because it does not allow me to put 'VHD' files in the Boot Partition instead of System Partition. It also does not allow me to boot 'WIM' files through Grub4dos 'menu.lst'. It's why now I have to adopt 'BCD Store editing' in order to modify 'BIOS BCD', 'UEFI BCD', 'bootmgr' and 'bootmgr.efi' so that I can put all my Boot Files (except EFI folder and bootmgr.efi ) and Payload files (ISO, .imgPTN, WIM, VHD etc.) into myHidden Boot Partition in order to BIOS+UEFI booting. Finally yesterday night I found 'GUI DISM.exe' which allow me to add/integrate/inject Drivers (Firadisk , cfadisk/diskmod etc.) into WIM files so that I can access my both Partitions (Data Partition and E2B Parition) of Removable USB Drive within from running'Win8.1SE_x64_boot.wim'.

AFAIK, 'WinNTSetup v3.6.1' is the best and unique tool which allow us to install Windows OS into both Internal Hard-disk and External USB Drives of both MBR-BIOS and GPT-UEFI Partition schemes without converting Partition Scheme GPT to MBR. It's why I want to use 'WinNTSetup v3.6.1' within from running 'Win8.1SE_x64_boot.wim' in order to install WINDOWS OS (Specially install.esd ) into MBR/GPT Partitioned Hard disk drives.

So overall these are the reason WHY a "normal" Easy2boot setup does not work for me, and/or WHY a "normal" UEFI MULTI setup does not work for me and for my goal. So finally I decide to use both 'Easy2Boot v1.50' and 'BOOTICE/BCD Editing' in order to fulfill my Goal.

Regards..............



#3 alacran

alacran

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Mexico

Posted 18 June 2014 - 10:04 AM

You have done same question in other tread, there is no need to open a new one.

 

I just answer it: http://reboot.pro/to...fd/#entry184950

 

Regards



#4 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 19 June 2014 - 04:44 PM


This is my current 'E2B Main Menu Screen'

MY E2B MENU SCREEN 


Edited by devdevadev, 12 July 2014 - 12:08 PM.


#5 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 21 June 2014 - 11:53 AM

 
Today I have injected filter driver 'cfadisk' into 'Win8.1SE_x64_boot.wim', 'boot.wim' and 'WIMBoot.vhdx'.

Now I can boot 'Win8.1U1 Installer', 'W2G+WIMBoot+VHDX' and 'Win8.1SE_x64_boot.wim' within from hidden 'ptn3' through modified
BOOTMGR -> BCD in 'ptn2' .

 

i.e.

BIOS -> MBR -> ptn2:\grldr -> E2B -> ptn2:\_ISO\MAINMENU\Boot Manager.mnu -> ptn2:\(bootmgr, bootmgr1, bootmgr2) -> 

 -> ptn2:\(bcd,bc1,bc2) -> ptn3:\(W2G+WIMBoot+VHDX, Win8.1U1SE_x64_boot.wim, Win8.1U1 Installer)

 

Regards.....


Edited by devdevadev, 22 July 2014 - 10:50 AM.
Replaced complete post #5 on author's request


#6 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 10 July 2014 - 10:43 AM

Greeting of the Day.....

 

Related discussions links are here 

 

http://reboot.pro/to...-removable-ufd/

http://reboot.pro/to...efi-boot-files/

http://reboot.pro/to...ul-combination/

 

Thousands of Thanks and Regards to  :worship: Steve, ktp, alacran, cdob, misty, wimb, JFX, HALIKUS, Nuno Brito Wonko etc........

:cheers:


Edited by devdevadev, 12 July 2014 - 01:59 AM.


#7 alacran

alacran

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Mexico

Posted 10 July 2014 - 11:12 PM

FAT32 maximum file size is 4 GB.

 

Regards


  • milindsmart likes this

#8 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 11 July 2014 - 12:26 AM

FAT32 maximum file size is 4 GB.

 

Regards

 

Hi alacran

 

In Partition 2, there is no file greater than 4 GB. All my Windows ISO are of ESD types. and 'Win8.1ToGO' is also WIMBoot types so there is no change to exceed 4 GB limit. Actually there is no problem of 4 GB limit because Steve provide us a very powerful format which is '.imgPTN'. I can create NTFS.imgPTN of greater than 4 GB if needed. But due to lack of storage , I always prefer ESD types Win_AIO_x86_x64_ESD.imgPTN partition images. When we select a .imgPTN payload file from the E2B menu, then it first backup MBR and then update the USB MBR to a single NTFS Partition. So 4GB limit never panic me. And In case of UEFI , I will first boot to any WinPE/WinToGO and then mount Win_AIO_x86_UEFI Boot_ESD.imgPTN with the help of Imdisk and then use 'WinNTSetup v.3,6.1' in order to apply 'install.wim'/'install.esd' of size greater than 4GB.

 

Acutally UEFI 4GB limit is not a Big problem because of Steve 'Method 1/4' for removable USB Drive. And 'Method 1/2/3' for fixed USB Drive.

 

http://www.easy2boot...er-flash-drive/

 

Regards.


Edited by devdevadev, 12 July 2014 - 12:47 AM.


#9 cdob

cdob

    Gold Member

  • Expert
  • 1336 posts

Posted 11 July 2014 - 02:43 PM

Partition 2- FAT32 - Set Active - 25 GB - Invisible to Window - This Partition will contain Win8.1ToGO

K:\WIMBoot.wim
K:\Win8.1ToGO.vhdx
K:\Bootmgr (For direct booting of ‘ Win8.1ToGO + WIMBoot + VHDX’ combo within from E2B Menu )
K:\Boot\BCD (relocated to “Win8.1ToGO + WIMBoot + VHDX” combination and boot.sdi)

I wonder:
How do you mount the vhdx file at the FAT32 partition?
Do you use windows native drivers?
Do you use a third party driver? Does they work in conjunction with WIMBoot?


Another approach:
Instead of several K:\Boot\BC? files, you may create one K:\Boot\BCD. Include all bcd settings to this file.
Of course, it's your choice to use several bc? files instead.

#10 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 12 July 2014 - 01:18 AM

Hello Everyone........
 
 

BUT you can still fake woot.gif that a "flat" .vhd is actually a RAW image with a single sector appended to it (which actually is newwink.gif) and use grub4dos + Firadisk or Winvblock to mount it , it won't be "native" booting anymore, but still it will be booting from .vhd residing on *any* filesystem.
http://reboot.pro/15407/
http://reboot.pro/15997/
http://reboot.pro/16178/

jaclaz

 

Which would be the best and reliable method in order to mount the vhdx file at the FAT32 partition with 'native' BOOTMGR booting along with WIMBoot support ?

 

Will I have to use 'vBOOT' ? Can anybody suggest me a better method for it ?

 

 

@cdob

 

Another approach:
Instead of several K:\Boot\BC? files, you may create one K:\Boot\BCD. Include all bcd settings to this file.
Of course, it's your choice to use several bc? files instead.

 

Hello Sir,

 

I know this approach but I don't want to press 'Enter' button twice. It's why I have to use individual BOOTMGRs and BCDs for WIM, VHD, WTG.  :)

 

Regards.....



#11 cdob

cdob

    Gold Member

  • Expert
  • 1336 posts

Posted 12 July 2014 - 06:53 AM

Which would be the best and reliable method in order to mount the vhdx file at the FAT32 partition with 'native' BOOTMGR booting along with WIMBoot support ?


To emphasize this: How to boot this at UEFI secure boot?

What about a (additional) NTFS partition?

#12 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 12 July 2014 - 11:40 AM

To emphasize this: How to boot this at UEFI secure boot?

 

Why you say this ?

Will above Configuration not provide UEFI secure boot ?

What precautions I have to follow in order to 'UEFI' secure boot ?

 

 

What about a (additional) NTFS partition?

 

I will have to add a 3rd NTFS partition if I become fail to mount the vhdx file at the FAT32 partition with 'native' BOOTMGR booting along with WIMBoot support ?

 

Regards.....



#13 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 12 July 2014 - 12:27 PM

Is a .vhd the same as a .vhdx ? :w00t:

 

HInt:

Read ATTENTIVELY the second post in the first reference you cited:

http://reboot.pro/to...b4dos/?p=137456

had you READ the references you have cited, you might have understood this point:

Something that works on a .vhd BY COINCIDENCE because it was designed for working with RAW images and a "static/flat" .vhd is a RAW image with a sector appended (that is ignored) WILL NEVER work on a .vhdx.

 

:duff:

Wonko



#14 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 12 July 2014 - 01:22 PM

Hello Everyone.....
 

Following will be the content of the ' USB Partitions' .

 

Partition 1 - FAT32 - 5 GB - Visible to Windows - This Partition will be use only for 'Data Storage' and contain bare minimum ‘EFI Files’ hidden by attrib commands.

 

S:\EFI\Boot\bootia32.efi                                       - x86 hardware / firmware

S:\EFI\Boot\bootx64.efi (bootmgfw.efi)              - amd64 hardware / firmware

S:\EFI\Microsoft\Boot\BCD                                 - Relocated to boot.sdi, Win8.1U1SE_x64_boot.wim

S:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf       - Recommended

 

Partition 2- NTFS  -  Set Active - 25 GB - Invisible to Window - This Partition will contain  'Win8.1U1SE_x64_boot.wim',

 'Win8.1U1_x86-install-WIM_x64-boot.WIM_Installer_WTG+WIMBoot+VHDX.imgPTN''Easy2Boot' files and 

many more Payload Files (ISOs, IMGs, .imgPTN etc……) hidden by attrib commands.

 

K:\Bootmgr                            (For direct booting of 'Win8.1U1SE_x64_boot.wim' within from E2B Menu )

K:\Boot\BCD                          (Relocated to Win8.1U1SE_x64_boot.wim and boot.sdi)

K:\Boot\boot.sdi

K:\grldr

K:\menu.lst
K:\my.usb

K:\_ISO\MAINMENU\Win8.1U1SE_x64_boot.wim

K:\_ISO\MAINMENU\Win8.1U1SE_x64_boot.mnu

K:\_ISO\MAINMENU\Win8.1U1_x86-install-WIM_x64-boot.WIM_Installer_WTG+WIMBoot+VHDX.imgPTN

K:\_ISO\WIN\WIN 7 Ultimate.imgPTN
K:\_ISO\MAINMENU\Ultimate DLCD Boot 2014 v2-1.imgPTN 
K:\_ISO\MAINMENU\Spotmau BootSuite 2012.imgPTN
K:\_ISO\MAINMENU\Easy Rescue Suite 2014.imgPTN
K:\_ISO\MAINMENU\KonBoot_24.imgPTN
K:\_ISO\MAINMENU\E2B_PTN_SWAP.mnu
K:\Smart Apps\WinNTSetup 3.6.1 (BootIce included in tools folder).

K:\autorun.inf
K:\autounattend.xml
K:\e2b.ico
K:\FASTLOAD.YES
K:\HitmanPro.exe
K:\HitmanPro_x64.exe
K:\Kickstarter.exe
K:\PassPass.bak
K:\Readme.txt
K:\unattend.xml

 

Note-

 

1-  In K:\_ISO\MAINMENU\Win8.1U1SE_x64_boot.mnu , I will put following entries in order to directly boot Win8.1U1SE_x64_boot.wim  within from Easy2Boot Menu in BIOS/MBR mode.

---------------------------------------------

title Win8.1U1SE_x64_boot_WIM

chainloader /bootmgr

---------------------------------------------

 

2-  ‘Win8.1U1_x86-install-WIM_x64-boot.WIM_Installer_WTG+WIMBoot+VHDX.imgPTN’ will contains following files -

 

BOOTNXT

WIMBoot.vhdx                             (Contains Installation files of WIMBoot pointed to sources\install.wim)

bootmgr                                          (Taken from x64 'Win 8.1 U1' for BIOS/MBR Boot Manager)

bootmgr.efi                                    (Taken from x64 'Win 8.1 U1' for UEFI Boot Manager)

boot\bcd                                         (Pointed to boot.wim (x64), boot.sdi and WIMBoot.vhdx)

boot\boot.sdi                                 (Taken from x64 'Win 8.1 U1')

efi\boot\bootx64.efi                    (Taken from x64 'Win 8.1 U1')

efi\microsoft\boot\bcd               (Pointed to boot.wim (x64), boot.sdi and WIMBoot.vhdx)

sources\install.wim                     (Taken from x86 'Win 8.1 U1') 

sources\boot.wim                         (Taken from x64 'Win 8.1 U1')

sources\lang.ini

e2b\CSM.bmg

e2b\menusetting

e2b\RestoreCSM (run as admin)

e2b\RestoreE2B (run as admin)

e2b\unifont.hex

autorun.ico

autorun.inf

grldr

menu.lst

RestoreE2B.exe

 

1- BIOS-   I will use BCD edit function inside Bootice\BCDEdit to edit S:\Boot\BCD for creating boot entries for

                     'Win8.1U1SE_x64_boot.wim' in BIOS mode (winload.exe to be put as loader).

 

2- UEFI-   I will use BCD edit function inside Bootice\BCDEdit to edit S:\efi\Microsoft\Boot\BCD for creating boot entries for 

                     'Win8.1U1SE_x64_boot.wim' in UEFI mode (winload.efi to be put as loader).

 

BIOS mode:  1- BIOS -> MBR -> grubdos -> grldr/menu.lst -> Easy2Boot Menu
                         2- BIOS -> MBR -> grubdos -> grldr/menu.lst -> bootmgr -> s:\boot\BCD -> Win8.1U1SE_x64_boot.wim

 

UEFI mode:      UEFI-> /efi/bootmgfw.efi -> winload.efi -> S:\efi\Microsoft\Boot\BCD -> Win8.1U1SE_x64_boot.wim

 

Note - After booting from 'Win8.1U1_x86-install-WIM_x64-boot.WIM_Installer_WTG+WIMBoot+VHDX.imgPTN'

or 'Win8.1U1SE_x64_boot.wim' in BIOS/UEFI mode. I will use portable App 'WinNTSetup 3.6.1_x64.exe' in order to mount 'Win8.1U1_x86-install-WIM_x64-boot.WIM_Installer_WTG+WIMBoot+VHDX.imgPTN' (within from 
\_ISO\MAINMENU folder of Partition 2) in ImDisk Virtual Drive. 'WinNTSetup 3' will prepare local hard-disk for 
Installing Win 7/8/8.1 .

 

Please reply me if above procedure also work for you……………

 

Please provide me your precious suggestions in order to improve above configuration......

Thousands of  Thanks and Regards to        :worship: Steve, ktp, alacran, cdob, misty, wimb, JFX, HALIKUS, Murphy 78, Wonko etc........

 

Regards...

:cheers:



#15 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 12 July 2014 - 03:07 PM

Who knows?

 

AGAIN, a .vhd is NOT a .vhdx, they use DIFFERENT FORMATS. <- is this so difficult? :unsure:

 

There is Native .vhd booting in some editions of Windows 7.

There is Native .vhd AND .vhdx booting in Windows 8 and similar.

 

BOTH have seemingly the requisite of the filesystem on which they are mounted to be NTFS.

 

If you read, this time ATTENTIVELY the thread you linked to:

http://www.msfn.org/...can-it-be-done/

you will get to here:

http://blogs.technet...-explained.aspx

 

As always, DO NOT trust any info, but rather TRY yourself.

 

 

See (please, please READ it):

http://technet.micro...y/hh825689.aspx

Create a "Native" booting .vhd or .vhdx (depending on the OS used) on a NTFS volume, try booting from it, then repeat but from a FAT32 (of course the image needs to be smaller than 4 Gb). 

 

Does it still work? :frusty:

 

If yes, the mentioned reference is incorrect, if no, then it is correct.

 

The non-native .vhd boot in the reference you provided (as  I tried vainly :frusty: to explain you) is NOT a .vhd boot, but rather a RAW image boot, and it DOES apply to "static" .vhd ONLY AND NOT to any other type of .vhd AND NOT to .vhdx of ANY type.

 

A .vhd booted through grub4dos and Firadisk or Winvblock (i.e. a RAW image boot) can be on a FAT32 fine, but of course since grub4dos does not support UEFI, you need BIOS or CSM.

 

:duff:

Wonko



#16 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 22 July 2014 - 09:51 AM

@ Steve....

1- Create two Primary Partition in your 'Removable USB Drive' with the help of BOOTICE. 'PTN 2' should be NTFS and

    greater than 25 GB(25 GB is minimum size for 32-bit 'WTG', You should use greater for smooth operations).

PTN1 - FAT32 -  5 GB or above  -  DATA

PTN2 - NTFS   - 25 GB or above -  E2B 

2- Make NTFS 'E2B' PTN accessible to Windows with the help of BOOTICE and extract E2B files to NTFS 'E2B' PTN 

    and make USB drive Bootable by installing 'Grub4dos' to MBR with the help of RMPrepUSB.

3- Drag and Drong ‘Win8.1U1_x86.iso’ to 'MakePartImage' desktop shortcut of  ’MPI_v041’ in order to create an 

     NTFS formatted ‘Win81U1_x86.imgPTN’ of approx. 20 GB or AboveAnd then put ‘Win81U1_x86.imgPTN’ file

      into \_ISO\MAINMENU directory of NTFS 'E2B' PTN

4- Now make FAT32 'DATA' PTN accessible to Windows again using BOOTICE. Boot from the your USB Drive and

     select ‘Win81U1_x86.imgPTN’ payload file and switch to CSM mode.

5- Now Reboot to Main Windows OS and open File Explorer and note Drive Letter of your Removable USB Drive

     (Suppose it is K:)

6- Now Delete (or move to any safe place ) following folders and files within from USB Drive (Very Important )-

K:\boot
K:\efi
K:\bootmgr
K:\bootmgr.efi
K:\support

7- Now open ‘WinNTSetup v.3.7.5’ and create dynamically expanding 'WTG.vhdx' of approx. 15 GB or greater

    within any Partition of your Local Hard Disk (assume Root of C: Drive). 'WTG' Partition will be automatically mounted 

    as Z: Drive. Now we will start Installation.
8- First browse ‘install.wim’ file within from your USB Drive K:\sources\install.wim as Source. Then Select USB 

     Drive K: as Boot Drive and 'WTG' Partition Z: as Installation Drive
9-  Check Windows Image File Boot (WIMBoot) " option (Can Ignore if USB Drive is not Ultra Fast) .
10- Press ‘Setup’ button and click ‘OK/Yes’ to start Installation process.
11- After completing Installation Boot from your USB Drive ( K:) 3 times (whenever system restart) until you

       Boot to Desktop of 'Win 8.1U1 to GO'.

12- Reboot and Boot from your Internal Hard disk Partition (C: Drive) . Now copy ‘C:\WTG.vhdx’ file from C:\ Drive to

      the Root of your USB Drive (K:WTG.vhd)
13- Run Command Prompt (CMD) as Admin and type attrib -h -r -s /s /d K:\*.*
14- Now open Bootice/BCDEdit and browse BCD within from your USB Drive K:\boot\BCD
15- Press 'Easy Mode' button and then you will find a BCD entry named ‘Windows 8.1’.
16- Under [Boot Device] ->> Disk: category choose ‘BOOT (WIM)/LOCATE(VHD)‘ option. (Very Important)

17- You can also rename OS title from ‘Windows 8.1’ to ‘Win 8.1U1 to GO’ according to your Choice.

18- Now click ‘Save current system’ and then Click ‘Save Globals’ button.

Optional- If you also want to add 'Windows Installer' along with 'WTG + WIMBoot + VHDX' setup , then you can 

                 copy \boot\boot.sdi file within from 'Win8.1U1_x86.iso' to the K:\boot\ directory of you USB Drive. And 

                 then add a BCD Entry (Windows Installer) pointed to both K:\source\boot.wim and K:\boot\boot.sdi .

                 And then click ‘Save current system’ and then Click ‘Save Globals’ button again....

19- Now move ‘WTG.vhdx’ within from root of C: Drive to any other folder where you like for future use. 

      (Can also Delete)
20- Now Boot from your USB Drive (K:) and choose ‘Win 8.1U1 to GO’ option from Boot Manager Menu.
21- If you successfully Boot to Desktop of 'Win 8.1 U1' then reboot again to Internal Hard disk.
22- And Install ‘Grub4dos’ to MBR of your USB Drive (K:) with the help of ‘RMPrepUSB’.
23- Now Boot from your USB Drive to CSM Menu and then Press ‘Enter’ Button.
24- Choose ‘Win 8.1U1 to GO’ option from Boot Manager Menu and test it once again.
25- If it successfully boot to 'Win 8.1U1 to GO' then you can switch from CSM Menu to E2B Menu as usual.

26- Now it’s......DONE.

Note- Use 32-Bit 'Win8.1U1' if possible otherwise you may have to increase size of .imgPTN and VHDX. The size of my install.wim’ was only 1.6 GB. It’s why I create a smallest VHDX of size 1050 MB. So size of .imgPTN file was only 3.2GB. You can make some experiments with the SIZE of your ‘WTG.vhdx’ so that it can just contains ‘Pointer Files’.

 

Cheers.... :cheers:


  • crashnburn likes this

#17 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 22 July 2014 - 09:59 AM

AFAIK,  UEFI can boot from hidden fat32 'ptn2'. It's why I will keep EFI directory in both fat32 'ptn1' and fat32 'ptn2' . HALIKUS says that PE (boot.wim) only sees the NTFS partition as it's Set Active. But in my case I will inject 'Filter driver' within PE (boot.wim and Win8.1U1SE_x64_boot.wim) and VHDX (WIMBoot.vhdx) so that it will see non-active NTFS 'ptn3' in UEFI mode. In case of BIOS/MBR/CSM mode I had tested that PE (boot.wim and Win8.1U1SE_x64_boot.wim) and VHDX (WIMBoot.vhdx) sees non-active NTFS 'ptn3' without any problem .

Will 'WinPE'(inject with filter drive) see non-active NTFS 'ptn3' in UEFI mode or not ?

Following is my expected UEFI configuration for my 'Removable' USB Drive.

Partition 1- FAT32 - will contains only EFI directory

ptn1:\EFI Directory
ptn1:\EFI\Boot\bootia32.efi                          - x86 hardware / firmware
ptn1:\EFI\Boot\bootx64.efi (bootmgfw.efi)   - amd64 hardware / firmware
ptn1:\EFI\Microsoft\Boot\BCD                       - (Relocated to PTN3 'boot.wim and boot.sdi', 'WIMBoot.vhdx' ,
                                                                           'Win8.1SE_x64_boot.wim and boot.sdi' )

Partition 2- FAT32 - Active - Hidden

ptn2:\EFI Directory
ptn2:\EFI\Boot\bootia32.efi                          - x86 hardware / firmware
ptn2:\EFI\Boot\bootx64.efi (bootmgfw.efi)   - amd64 hardware / firmware
ptn2:\EFI\Microsoft\Boot\BCD                       - (Relocated to PTN3 'boot.wim and boot.sdi', 'WIMBoot.vhdx' ,
                                                                           'Win8.1SE_x64_boot.wim and boot.sdi' )

Partition 3 - NTFS - hidden

ptn3:\boot\boot.sdi
ptn3:\sources\Win8.1U1SE_x64_boot.wim     (Injected with 'cfadisk' drive and taken form 64-bit 'Win8.1SE.iso')
ptn3:\sources\boot.wim                                  (Injected with 'cfadisk' drive and taken form 64-bit 'Win 8.1 U1')
ptn3:\sources\setup.exe
ptn3:\sources\install.wim                                (taken form 32-bit 'Win 8.1 U1')
ptn3:\WIMBoot.vhdx
ptn3:\BOOTNXT
 
 
Above UEFI configuration will boot in following sequence-
 
UEFI -> /efi/bootmgfw.efi -> winload.efi ->(ptn1/ptn2):\efi\Microsoft\Boot\BCD ->  ptn3:\ Win8.1U1SE_x64_boot.wim
        -> /efi/bootmgfw.efi -> winload.efi ->(ptn1/ptn2):\efi\Microsoft\Boot\BCD ->  ptn3:\ Win8.1U1 Installer
        -> /efi/bootmgfw.efi -> winload.efi ->(ptn1/ptn2):\efi\Microsoft\Boot\BCD ->  ptn3:\ W2G+WIMBoot+VHDX

 

Will above expected UEFI USB configuration work or not ?

Please give me your precious suggestions regarding this configuration.........
 

Regards.........

 


#18 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 27 July 2014 - 06:09 PM

Since I was senselessly solicited to provide my "precious opinion/suggestion" via PM on this:
 

Will above expected UEFI USB configuration work or not ?

Please give me your precious suggestions regarding this configuration.........

Here is my "opinion/suggestion" (cannot really say if "precious" :unsure:):

Who knows? :dubbio:
Just §@ç#ing try doing it! (and see what happens)  :ranting2: 

:duff:
Wonko


  • devdevadev likes this

#19 saddlejib

saddlejib

    Frequent Member

  • Advanced user
  • 270 posts
  •  
    United Kingdom

Posted 27 July 2014 - 08:12 PM

You're getting increasingly impatient........(just an observation)....


  • devdevadev likes this

#20 saddlejib

saddlejib

    Frequent Member

  • Advanced user
  • 270 posts
  •  
    United Kingdom

Posted 27 July 2014 - 08:14 PM

p.s still a wealth of wisdom... (much appreciated by me at least)


  • devdevadev likes this

#21 saddlejib

saddlejib

    Frequent Member

  • Advanced user
  • 270 posts
  •  
    United Kingdom

Posted 27 July 2014 - 08:15 PM

I'm returning to somnambulism now....


  • devdevadev likes this

#22 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 28 July 2014 - 12:55 AM

You're getting increasingly impatient........(just an observation)....


Hello Sir,

Are you talking about me or anyone else ?

Please mention @..........because it's confusing ?

Regards........

#23 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 28 July 2014 - 07:39 AM

You're getting increasingly impatient........(just an observation)....

Yep :), though I do have my specific reasons for this increase.

 

@devdevadev

Don't worry, it was directed at me, saddlejb woke up from his sleep just to highlight how snappy was my reply in post #18.

 

By convention, if not explicitly directed at someone/something, a reply is related to last post on the thread before the reply.

 

:duff:

Wonko


  • devdevadev likes this

#24 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 01 August 2014 - 04:54 AM

http://reboot.pro/to...e-2#entry186244



#25 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 406 posts
  •  
    India

Posted 01 August 2014 - 05:05 AM

 

 By Murphy 79, on 12 Jul 2014, -11:47 PM, said in PM

 

The bootmgr.efi and bootia32.efi from the 32-bit image are useless since there are no supported Windows OS versions. I think they have a win32 tablet version that uses uefi, but it's not available to anyone except oems. I haven't seen that one for myself, only heard about it in the wimboot thread.

 
Anyhow, if you are going to use a boot.wim from the x64 image, just use the bootmgr.efi and bootx64.efi files from the x64 image.It might be a little confusing to trash one bootmgr.efi for another bootmgr.efi, but trust me, they are not compatible. the one from the 32-bit image will not work at all.

 

It means there are two 'bootmgr.efi'. Both 32-bit and 64-bit 'bootmgr.efi' are different. Only name is same. So I have to use 64-bit 'bootmgr.efi' and 'bootx64.efi' files from the x64 image in order to UEFI booting of 32-bit OS in 64-bit firmware/system.

 

Regards.......







Also tagged with one or more of these keywords: multi boot, dual partition, grub4dos, easy2boot, removable usb drive, iso image, uefi, uefi multi.exe, usb booting, winntsetup 3

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users