First YouTube video of E2B v2.00 (but in Portuguese!)

Well, it seems it took less than 24 hours after release, for someone to post a You Tube video on E2B+agFM!

Only problem is - it's in Portuguese!

I do plan to make my own YT video soon (if you want to hear about it from the horses mouth).

Meanwhile, feel free to get eBook #4 which is all about agFM and comes complete with instructions on how to add MBR+UEFI bootable AV ISOs, Linux ISOs+persistence, popular WinPE ISOs and Windows Install ISOs + unattended installs.

Easy2Boot v2.00 released

V2.00 is now released.

https://www.fosshub.com/Easy2Boot.html

The main change is that when you make a new drive, it will now download the agFM files and copy them to the second FAT32 partition (if present). This allows UEFI-booting to the agFM grub2 File Manager system. All thanks to 'a1ive' for developing his grub2 branch and agFM.

• Make_E2B.exe and Make_E2B_USB_drive.cmd - downloads agFM if 2nd FAT32 partition is made. If drive is <128Gib then 2nd FAT32 partition of approx 500MB is automatically made. Allow user to define sizes in GB of ptns1, 2 and 3 if Gear Wheel button used. If drive >128GB it always prompts user for partition 1, 2 and 3 sizes and type even if AUTO selected.
• New default wallpaper.
• .isoPE extension now updates the WinBuilder .ini files (e.g. for Gandalf ISOs) - use .isoPE extension if you get a yellow warning triangle on desktop.
• \_ISO\docs\Wincontig folder can now be copied to any volume\folder - e.g. copy to partition 3 so it will make all files on that partition contiguous.
• Update SDI_CHOCO scripts and add chocolatey.nupkg for offline install of chocolatey.
• Add support for windows ISOs on ptn3 in qrun.g4b so can have Windows Install ISOs on ptn3 or ptn2 or ptn1 and use a .mnu file, add $$Install_Win10_from_Ptn2or3.mnu sample mnu file
• Switch_E2B.exe now looks for auxiliary *. files on other volumes at \(path), then \_ISO, then \ - e.g. ptn1:\_ISO\WINDOWS\WIN10\Win10.imgptn23 and ptn3:\_ISO\WINDOWS\WIN10\Win10.
• Bugfix - Latest grldr with bugfix for non-contiguous files
• Bugfix - Fix EXTOFF variable not working in MyE2B.cfg (file extension always displayed in the menu).

Read more: https://www.easy2boot.com/download/e2b-version-history/

E2B eBook #4 on agFM is now available

The first revision v1.00 is now available here for the introductory price of $7 (RRP will be $10).

I hope to release E2B v2.00 in a few days. Please test the Beta versions of E2B v2 and agFM v.1.32 and inform me of any issues ASAP!

Please feedback any comments on the eBook and use the eBook download link that you will be emailed when you complete the purchase, to download any later revisions for free.

agFM v1.32 and Easy2Boot v2.00 Beta now available

agFM v1.32 now includes Clover boot files, so you can now UEFI-boot from the E2B Legacy menu.

Clover does have problems on some systems though, so it is of limited use!

Use the new copy of /e2b/a1ive grub2 filemanager.mnu and copy it to the \_ISO\MAINMENU folder.

The latest agFM version can be found here.

E2B is now v2.00a Beta. 

Changes (Version History) can be found under the Downloads tab on the E2B website.

https://www.easy2boot.com/download/e2b-version-history/
https://www.easy2boot.com/download/agfm-history/

P.S. The new eBook #4 on agFM is almost finished!

agFM v1.31 Beta now available

This version has some bug fixes and I have tidied up the folder structure (now has an \e2b folder).
I have found the AT keyboard scan code maps to cause issues - if you have a non-responsive keyboard then remove the terminal_input at_keyboard and keymap lines in your startup_menu.txt file!

You may need to modify your startup_menu.cfg file for the new folder structure.

I have included a sample submenu for the use Startup menu to show you how you can add more submenus to the first Startup menu.

I have also included a new example .cfg file for installing 64-bit Windows 10 ISO.

WIN10_64_INSTALL_Choose_UNAME_PCNAME_PRODUCTKEY_XML_AgFM.cfg

The sample file should be copied to any folder on the E2B drive (same partition as the ISO) and can be renamed. When run, it will ask you to choose a product key (Edition), an XML file, a user name and a PC name.

It will modify a copy of the chosen XML file  (in memory) for you.

Many thanks to Phong for reporting an issue and providing a sample .cfg file which I based this version on.

If you want the username and PC name and Product Key substitution to work, all the XML files that you include in your menu choices will need to include UNAME, PCNAME and ASKME-ASKME-ASKME-ASKME-ASKME in the relevant fields.

This could be used with Win10_Pro_US_UNAME_PCNAME_SDI_CHOCO_ASKME.xml for instance. Using this with a modified .cfg file, you will choose the Edition (Home/pro, etc), Computer Name and User Name. You will then create and format the install partitions manually on the target system using the standard Setup dialogue. The installation will then proceed unattended and if you have set up your SDI_CHOCO config and SNAPPY driver folders correctly, it will install all missing drivers and install your desired apps automatically (internet Ethernet connection required if using online app choco installs). You can use the same process for MBR\Legacy or UEFI installs.

If you use an XML which also wipes and creates partitions, the process can be fully automated but you will need one XML for UEFI GPT partitions and a different XML for MBR\Legacy partitions.

More details on XML files can be found in eBook #3.

agFM v1.29 Beta available with keyboard selection

I have added keyboard map files to agFM so that you can use AZERTY and QWERTZ and other keyboards.

The latest agFM version can be found here.

P.S. Using the console set to at_keyboard seems to stop the keyboard from working on some systems! I suggest you don't use this unless you have to!

agFM v1.28 Beta available

This version fixes a bug where the UEFI agFM menu is left on the screen and the Windows Setup form is displayed on the wrong screen so you cannot see it.

The Windows ISO appears to boot correctly and then you just see a blank agFM menu...

The Windows Setup is actually running but it is displayed on an alternate screen. In the case of my IdeaPad 300, this issue occurred randomly about 1 in every 2,3,4 or 5 boots to the Windows Install ISO!

I have now added a 'known issues' list to the end of the agFM page on the E2B website.
Please let me know if you find any more.

Windows could not update the computer's boot configuration

P.S. If you ever see this issue when installing Windows to a clean hard disk, please let me know:

I think this issue may be caused by Windows Setup not liking the BCD file on the FAT32 partition of the USB hard drive you are installing from!

I have noticed that the date&time stamp of the \EFI\Microsoft\Boot\bcd file on the USB drive has changed after Windows Setup stage 1 runs if you UEFI-boot from an E2B USB Hard drive. Setup seems to load the USB drive's bcd to see if it is the 'system' bcd??? It does not seem to change it's contents. My guess is that if it cannot load and parse it successfully the install will fail with this error message.

I started to get this error very consistently at the end of the file copy phase in Windows Setup, when installing to a blank disk in a VM and a real system (UEFI install). I tried for hours to find out what was causing it and then the error magically disappeared - probably after I used BootIce to look at the BCD file on the USB drive's FAT32 partition - but I can't be sure. This error seems to have stumped a number of people on the internet who had the same problem but I could not find anyone who had reliably identified the cause...

Latest Easy2Boot v.1.B9 and agFM Betas - call for feedback

I am thinking of releasing the next version of E2B soon.

I will rename Beta E2B v1,B9m and agFM v1.27 as Easy2Boot v2.00.

The Make_E2B utility will prompt the user to add the agFM files after downloading them.

Please can you send me a quick email with any feedback on E2B+agFM (latest versions).

In particular, I would like to know:

1. Type of E2B USB used: Removable or Fixed/HDD
2. Version tested: E2B and agFM
3. Windows Install tests: UEFI64 Windows install from ISO works OK? XML files work?  WipeDisk+SDI_CHOCO.xml files work?
4. Any issues with any particular payloads? Please give details on how I can reproduce the issue.
5. Any other feedback welcome.

Please email me at steve @ easy2boot.com  with your observations.

Note that Make_E2B.exe will only make the second agFM partition + files if you are using Windows 10 OR you are using any Windows OS plus a Fixed-disk USB drive.  i.e. If you are using Windows 7 or Windows 8 AND a Removable USB drive, then the agFM partition will not be made (because those versions of Windows cannot access a 2nd partition on Removable flash drives).

The more feedback I get, the sooner it can be released.
Thanks
Steve

agFM v1.25 available with UEFI Secure Boot from Windows Install ISOs

Todays version is v1.25 and a1ive has worked some magic and it now seems to be able to boot Windows Install ISOs even in Secure UEFI64-boot mode! (I haven't tested Secure UEFI32 as I don't have a suitable UEFI32 computer).

No more 0xc000000f BSOD errors and we don't have to create dual FAT32+NTFS .imgPTN files to Secure Boot to large Windows Installers!

By adding your own .cfg file, you can also auto-install directly from a Windows ISO in Secure Boot mode using a suitable XML file and even install Drivers and Apps automatically. If you use the Win10 1909 x64_UNAME_PCNAME.cfg config file, you can specify the Computer Name and User Name before the build starts.

Please let me know if it works for you by using the checkboxes below.

Note: If you have any problems UEFI64 booting and installing Windows directly from a Windows ISO, please let me know,

A1ive has also added an option to recognise Kaspersky ISOs and UEFI-boot to them.

Norton Bootable Recovery Tool - nbrt.iso - no EFI boot files, use the nbrt.grubfm sample file provided for UEFI booting.

agFM v1.24 now available (with support for UEFI64 boot from krd.iso)

Todays version fixes the issue of user input not accepting [BACKSPACE] which made it difficult to type in a string if you make a mistake (e.g. when specifying the computer name or user account name).

It also fixes an issue when trying to UEFI64-boot to the krd.iso Kaspersky Rescue Disk.

All credit should go to a1ive who has made the required changes to grub2 and helped with suggestions.

Note: agFM now supports krd - there is no need for a .grubfm file.

The krd.grubfm filecan be added. Just copy it from the \Menu Files to copy to payload volume folder to the \_ISO\ANTIVIRUS folder where your krd.iso is located.

When you UEFI64-boot to the agFM menu system, select the krd.iso file and then pick the 'User menu' entry.

agFM v1.23 now available with support for modifying XML files

Todays version uses the latest build of a1ive's grub2 and grubfm (the ipxe part is in Beta status, i.e. may have bugs).

The main changes in todays release are:

1. Bugfix in Win10 1909 x64.cfg - due to a change in the a1ives grubfm scripts, this now needed modifying.
2. New Win10 1909 x64_UNAME_PCNAME.cfg config file

The new Win10 1909 x64_UNAME_PCNAME.cfg file allows the user to modify the contents of any XML file.

a1ive kindly helped me with the lua script which was needed for this.

This new .cfg file means that you can use an automated install XML file but change the User Name and Computer Name before Setup runs. This is useful for computer shops who often install the same Windows Edition but need a different user account name and computer name.

The example version uses an XML file which has the user name and computer name set to UNAME and PCNAME. The script will then allow you to change those strings.

Instructions

E2B v1.B9k with grub4dos 'Error 25:' bugfix

There was a bug introduced into some recent grub4dos versions used in E2B v1.B7 and 1.B8.
A typical symptom is 'Error 25: Disk read error'.

To fix the error, it was necessary to make sure all ISO files are contiguous by running \MAKE_THIS_DRIVE_CONTIGUOUS.cmd.

E2B v1.B9k2 has the new grub4dos version (v1.B9k had the old version).

previous versions:

2019-08-09 OK (E2B v1.B5)
2019-09-09 OK (E2B v1.B6)
2019-10-28 FAIL (E2B v1.B7)
2019-12-30 FAIL (E2B v1.B8)
2020-01-28 FAIL (E2B v1.B8A)

Other changes:

• The \_ISO\docs\Wincontig folder can now be copied to any drive volume and be placed in any folder. You can then make files contiguous on that volume by running one of the .cmd files.
• Bugfix - set EXTOFF=1 did not suppress the file extension in the menus.

agFM v1.21 Beta now available

The developer a1ive has yet again done loads of brilliant work and managed to get the contiguous file test working for the partnew command. He has also added multiple language support to the main English version - just press F4 and select a different language or set the language in your user startup_menu.txt file.

F4 Settings Menu (auf Deutsch).

In your startup_menu.txt file, set the desired language:
#set language: en_US, ru_RU, fr_FR, tr_TR, ko_KR, ja_JP, zh_CN, de_DE, he_IL, vi_VN, es_EM, zh_TW
export lang=de_DE

I feel that the UEFI agFM system is getting very near to release status now, so please try it out for yourself.

Try the new version.

agFM v1.20 now available

The main change in this version is that a1ive has added an option to remove filename case sensitivity.

I don't know about you but I find the case-sensitivity of Linux\grub very annoying - especially when you have to verbally tell someone the name of a file and you have to say 'oh - and you have to type it with an uppercase F and a lowercase u'!

This change means we don't need to use the exact case for any letters used to specify the filenames in any of the .cfg or .grubfm menu files that we make.

There is now an extra option in the F4 Settings menu to enable case-sensitivity if you wish to have it on. You would only need to enable case-sensitivity when the same folder has two files with the same name but some of the letters were in a different case - which is quite unlikely!

agFM is looking quite nice now, however there is one major issue to overcome which I hope a1ive can crack. When using the partnew command to switch in partition images or ISO files, we should check to make sure that the file is contiguous. If it is not then it may fail to boot or it could even result in serious file corruption of the E2B drive! However the grub2 commands used to check if a file is contiguous (blocklist and stat -c) currently take over 1 minute to check a large 3GB file if the file is on an NTFS partition. If there are two files to switch in then it can take even longer. The partnew command currently does not check that the .imgPTN or .ISO file is contiguous.

E2B v1.B9j Beta available + grub4dos bug discovered

This version fixes the issue where Make_E2B_USB_Drive.cmd did not make a CONTIG.ISO file when requested.

It also now searches on Partition 3 for partition image files which have no file extension.

e.g.
Ptn1: \_ISO\WINDOWS\WIN10\Win10 x64.imgPTN23    (FAT32 boot files)
Ptn3: \_ISO\WINDOWS\WIN10\Win10 x64    (NTFS >4GB INSTALL.WIM)

The Win10 x64 file (which has no extension) can either be in the root of the volume or in \_ISO or in the same path as the .imgPTN file. The file name should not have any dot in it or else it will be treated as having an extension.

This means the .imgPTN23 file can be the FAT32 boot partition and the file with no extension can be the NTFS volume containing your large install.wim file. You can secure boot and install >4GB install.wim files in this way. Instructions are on the agFM E2B page here.

Grub4dos bug discovered!

agFM v1.19 now available

v1.19 2020-02-25 - This version has a few bug fixes and improvements. The main one is support of .imgPTN and auxilliary partition images on partition 3 (no extension).

• WinBuilder ISOs (e.g. Gandalf) now should work correctly (no yellow triangle desktop icon) when using (map) option or .isoPE file extension.
• Support multiple .imgPTN files
• Add support for WinPE .ini files and wipe on boot
• Wipe \autounattend.xml and \unattend.xml in case booting from a Windows Install partition
• Latest build of a1ive grub2 - improved File Manager

See the agFM page for more details.

About .imgPTN files

agFM v1.17 available

This version has a few bug fixes, the menu font has been changed too and a1ive has added fat file rename\copy support to grub and the agFM menu system.

ESET + persistent updates instructions now revised

The previous Eset blog article was tested (with much frustration) by 'Pusher' who could not get the Eset SysRescue app to auto-run.

It turns out that my instructions were wrong and the ext3 persistence file must be copied from a working Eset flash drive (as detailed in a previous blog).

I have revised the previous instructions now and provided a download for the persistence file to make it easier to set up.

Sorry for any frustration that this may have caused anyone!

Trouble finding WinPE ISOs?

Recently, it seems very hard to find WinPE ISOs such as Gandalfs PE,  Bob Omb's WinPEs, Medicat, DLC Boot, etc. and some websites (like theoven.org) seem go up and down faster than a tarts knickers!

Other sites just seem to be blocked (by Windows? AV? Browser?) and request a username and password but don't let you sign up first!

Google also seems to have a hard time returning meaningful results too.

After a few hours of looking for various bootable ISOs I eventually found:

https://www.fcportables.com/boot-iso/

They seem to have a good selection and the download is not too hard to get to!

P.S. I am not recommending this site and have no connection with it. Please ensure you take any necessary anti-malware precautions when downloading from it!

agFM v1.16 available

This version has a few bug fixes to the SAMPLE_startup_menu.txt file.
E2B v1.B9i Beta is also available which has a few small bugfixes to the Make_e2b_usb_drive.cmd menu.

agFM v1.15 now supports a user theme menu

a1ive has very kindly added support for a user-configurable theme or a user-specified text+wallpaper menu system.

v1.15 includes a slightly modified theme.

Configure a startup menu with a background for agFM

Currently, the agFM menu system can either use the internal theme ('slack') or you can switch it to Terminal mode

However, you can define a startup menu and populate the menu entry with specific payload entries of your choice.

The startup menu will use the same 'slack' theme, but you can change it to use a non-themed menu.

You can specify the resolution (1024x768 recommended), text colours and either a pure colour background or a wallpaper image (stretched or normal and you can use .png, .tga, .jpg or .jpeg).

rev 2.15 of eBook #1 How to make a multiboot USB drive using Easy2Boot now available

The new version has a few small revisions.

Getting started with Easy2Boot_rev2.15.pdf

Use the download link in the email that was sent to you if you want this version.

Latest release of agFM v1.14 and E2B Beta v1.B9h available

agFM has improved support for WinPE ISO booting. If the extension is .ISO then choose the 'Install Windows' option. If the extension is .isoPE then it will automatically use that option.

E2B v1.B9h has an improved Make_E2B_USB_Drive.cmd script (used to make an E2B drive) which allows you to define up to three partitions and automatically downloads and adds the current version of agFM to the new E2B drive.

agFM v1.13 now available

v1.13 2020-02-17 

1. File extensions of .isodef, .isodefault, .isodd, .iso01, .iso32, .iso64, .isoPE or .isoPE01 will now immediately boot the ISO (using Easy2Boot\partnew method).
2. Add diagnostic menu entry to users startup_menu.txt.
3. Support E2B-style MBR-booting of .iso* and .wim files which have spaces in their filenames.
4. Display grub2 menu icons in menu after selecting the ISO (e.g. Manjaro ISO will display Manjaro icon after selection).
5. Clear empty type 0 partitions on boot.
6. Various bug fixes in a1ives grub2 and File Manager.

Most Linux iso will boot if you give them a file extension of .isodef (or .isodefault) in both agFM and E2B menu system. If you leave them as .iso, you will need to pick the required boot method from a secondary agFM menu.

Download Area for agFM Beta here.

If you require a different language, extract and overwrite the files using one of the language .zip files from the Languages sub-folder - Note: you must update to v1.13 first.

agFM v1.12 now available

This version has a new feature to only list bootable\actionable files.

agFM Beta download folder is here.

Now, by default, files such a .XML , .BMP., .JPG., .BAK, .CMD, .GZ, .BAT, .MNU and all other non-bootable files are not shown in the agFM file menu.

This makes it much quicker to navigate the E2B folder structure.

I have also added two new .cfg files in case you want all files to be listed in the agFM menu.

• SHOW ALL FILES (agFM).cfg
• SHOW ONLY BOOT FILES (agFM).cfg

If you want your agFM system to always show all files on startup (as with previous versions of agFM), then create a \boot\grubfm\startup_menu.txt file on the agFM partition and add in this line at the top of the file:

grubfm_set --hide 0

If you do not want a startup menu to be shown, just set the timeout and default to 0.

agFM v1.11 now available

a1ive has made a small change so that we can have an initial boot menu on booting the agFM.

This means it is possible to set a default menu item + timeout.

Here is a sample menu which offers three menu choices and will default to select a Windows 10 ISO on timeout...

To configure your own menu, rename the \boot\grubfm\SAMPLE_startup_menu.txt file to startup_menu.txt.

Here is the contents of the sample menu...

\boot\grubfm\startup_menu.txt

agFM v1.10 now available

a1ive has made some changes to allow us to customise the agFM.

The main change with this version is that when you select a .cfg file, it will immediately run it as a grub2 file without needing to select the 'Open as grub2 menu' option.

Note that the 'Cancel' or 'Back' option in any existing .cfg files that you may have made will now not work correctly and will just reload the .cfg file again - you will need to edit them. Compare your .cfg file with the example files to see what lines have changed...

e.g. change lines in existing .cfg file from...

grubfm "${grubfm_file}"
to
grubfm "${grubfm_current_path}"

Similarly with .imgPTN* files - just select them and they will now immediately run.

Download Area for agFM Beta here.

To update, just extract the files from the .zip file to your FAT32 agFM volume.

Windows 10 'Print' function is now launching OneNote!!!

My Windows 10 system ran a large Windows Update today and now whenever I try to print a document, OneNote launches instead!

The solution is to set the Default Printer back to your desired printer using Control Panel\All Control Panel Items\Devices and Printers.

Right-click on the printer device and choose 'Set as default printer'.

Add ESET + persistence to E2B+agFM

Recent versions of the ESET antivirus ISO have changed the way they use a persistent ext partition.

ESET will now only store the virus definition update files on an ext3 partition with a specific volume name of ESR-USB-DAT and it must be located as Primary Partition 2 (2nd partition) on the USB drive.

This change means that it won't work as a normal xxxx.imgPTN+xxxxx image pair in E2B because the persistent partition is mapped to partition 3 by Easy2Boot.

This means we need to modify the \menu.lst file inside the .imgPTN file.

If you have made an E2B multiboot USB drive with the a1ive grub2 File System on the 2nd FAT32 partition, then you can add a UEFI64-bootable (and MBR-bootable) version of ESET with persistence by using a special .cfg file.

Instructions

agFM v1.9 now available

• Few minor bugfixes
• Improve .imgPTN switching
• Reduced menu font size

Download agFM v1.9

A1ive grub2 File Manager v1.7/1.7A available (with .imgPTN support built-in)

a1ive has now added support for user-definable file extensions, so agFM v1.7A now automatically recognises the following extra file extensions:

• .imgPTN
• .imgPTN23
• .imgPTNauto
• .imgPTN23auto

E2B v1.B8A released

v1.B8 had a few bugs, so v1.B8A fixes these.
v1.B8A does not include the modifications for agFM or user-definable partition sizes as in v1.B9g Beta.

Secure Boot of large Windows Install ISOs with agFM

If your Windows Install ISO is very large and contains a 4GB+ install.wim or install.esd file, then you can still Secure Boot to the agFM then boot from an NTFS partition.

1. Make a .imgPTN23 NTFS image file using the MPI Tool Kit (drag-and-drop onto the MPI_NTFS Desktop icon).
2. Copy it to your E2B NTFS partition.
3. Copy agFM_imgPTN_NTFS_v16.cfg to your E2B NTFS partition (e.g. \agFM folder).
4. Change the name of the .cfg file to whatever you like (keep .cfg extension).
5. Edit the .cfg file to set the file path of your image file and its image type.

Now you can switch in the NTFS image file, reboot and use the F3 menu to boot to (hd0,msdos1).

Note: Later versions fix a few bugs and allow us to simply select the .imgPTN23 file so that a .cfg file is not needed.

E2B v1.B9g Beta available

This version v1.B9g will now ask if you want to download and add the agFM UEFI boot files to the E2B drive after it has been made. The agFM files are then automatically added to the E2B drive for you.

However, it only asks you if the second partition is a FAT partition and it is larger than 60MB.

If you just click the large red arrow button in Make_E2B.exe, then you will get a FAT32 2nd partition of approx. 600MB by default - or use the Gear Wheel button to specify what partition sizes you want.

E2B v1.B9f Beta

This version 1.B9f just has some changes to the Make_E2B_USB_Drive.cmd script which is used to make the E2B drive by the Make_E2B.exe GUI.

Changes are:

a1ive grub2 File Manager v1.5 now available

The 'E2B UEFI File Manager v1.5.zip' latest version is now available from here.

I have modified the RESTORE_E2B.cfg file and there is a new version of agFM_imgPTN_v15.cfg (for switching in .imgPTN files).

Latest grub2 build (todays build)

The second FAT32 partition can be type 0B or type 0C now (some partition tools seem to create type 0B FAT32 partitions).

a1ive grub2 File Manager v1.4 now available (with .imgPTN support)

The grub2 developer a1ive has done some fantastic work and has added more features to grub2 which means we can update partitions even under UEFI.

The 'E2B UEFI File Manager v1.4.zip' latest version is now available from here.

This version allows you to 'switch-in' any .imgPTN file or restore the E2B partitions from within a1ive's grub2 File Manager (agFM).

By switching in a Windows 10 .imgPTN23 file, we can Secure UEFI64-boot and install Windows 10 on a Secure system.

To update, just copy extract the files to overwrite the current files on your FAT32 partition.

Note: This is in Beta development and you could possibly lose all your data on the E2B drive! I haven't lost any data yet however.

It assumes that your first two partitions are:
Ptn1: NTFS Primary (type 07)
Ptn2: FAT32 Primary (type 0C)

a1ive grub2 File Manager v1.3 now available

a1ive has fixed a few small bugs and enhanced the grub2 features.

v1.3 contains the latest grub2 files and I have also added some WinPE files (except for a WinPE 64-bit \sources\SWITCH_X64.wim file which you can add yourself).

It is now possible to UEFI-boot to the File Manager and select a .cfg file which will then switch in a particular .imgPTN file and then reboot to the new image. You do not need to boot to WinPE to switch in the .imgPTN file.

UEFI64 Secure Boot to a1ive grub2 File Manager to the Windows 10 Installer

The UEFI64 Secure Boot seems to work quite well even on systems which are set to 'UEFI: Microsoft OS only' except when installing Windows 10 from an ISO.

The solution for this seems to be that we must boot from a Windows 10 .imgPTN file, so we

1. Secure UEFI64-boot to agFM
2. Boot to WinPE
3. Run Switch_E2B.exe and switch in our Windows 10 .imgPTN23 image file
4. Reboot from the new partition and install Windows 10
5. Reboot to agFM and switch back in the E2B partition

I have added the instructions on how to add in the WinPE files here.

It would be nice to not have to boot to WinPE and run SWITCH_E2B.exe, but I am not sure that grub2 can do this like grub4dos can (P.S. see agFM v1.3 for a solution!).

The other alternative is to use agFM to boot to WinPE and then run WinNTSetup.exe from WinPE - this can install directly from a Win10 ISO and there is no need to use .imgPTN files.

E2B v1.B9d Beta available

Changes from v1.B8 are:

• The E2B menu system will ignore .grubfm files and .cfg files which are not grub4dos batch files (in case added for a1ive grub2 file manager)
• Bugfix for Windows ISOs + XML files (unattend answer file error fixed)
• Bugfix for firadisk/strelec ISO booting
• Bugfix in NTBOOT for .wim booting when using grub2 File Manager
• Language file for Simplified Chinese STRINGS.txt updated (thanks to a1ive)
• Change to MAKE_E2B_USB_DRIVE.cmd script to leave 100MB+ at end of the USB drive so a 2nd FAT32 partition can be easily added without needing to resize the E2B drive.

If you make a new E2B drive now, it will leave approx. 100MB of free unused space on the drive (or if a >128GB drive, it will make a large NTFS partition #2). This allows the user to easily delete the 2nd partition and make a new FAT32 partition of 100MB, so they can easily add the grub2 a1ive File Manager UEFI boot files.

I may add an option to add the UEFI files into the E2B installer later, but I need a lot more feedback from users on how good (or bad) the new UEFI File Manager is.

Download v1.B9d

So please let me have your feedback on the 'a1ive gru2 File Manager' and let me know what works and what doesn't.

KSGER soldering iron reduced in price!

If you are thinking of buying a new soldering iron, it is now available for less than £30 ($35.55) at the moment (via email offer only)!

Create an account with Banggood and subscribe to get newsletters. Use the link in the email that will be sent to you for over £10 discount!

I recommend getting some extra bits at the same time.

See here for details.

A1ive grub2 File Manager for E2B v1.1 now available.

The latest version has a few improvements and bug fixes to make it more reliable for booting .WIM files.

I have also added a MEMTEST86 folder so that you can boot to the MemTest86 EFI files whenever you like.

Just extract the files straight to your FAT32 2nd partition to update the old version 1.0 files.

v1.1 1Drive Download link
v1.2 includes UEFI32 support

Bugfix in grub_filemanager.mnu (booting .wim files did not work)

If you are using the grub2 File Manager with Easy2Boot and have used the grub_filemanager.mnu menu file in the Main Menu  AND you have an animation on the menu, you may find that direct booting of some WinPE NT6 .WIM files does not work.

To fix this, we need to unmap the floppy drive that the animation uses before we load the grubfm.iso file.

Here is the new grub_filemanager.mnu file (the additional lines are in red)

iftitle [ if exist (hd0,1)/grubfm.iso || if exist (hd0,2)/grubfm.iso ] Grub2 File Manager (a1ive)\nBoot a file using grub2
splashimage --animated=0
map --unmap=0:03 > nul
map --unhook
find --set-root /grubfm.iso
map --mem /grubfm.iso (0xff)
map --hook
chainloader (0xff)
boot

E2B v1.B9b (with bugfix for unattend answer file error when installing Windows)

Alexander reported a problem with E2B v1.B8.

When using an E2B USB Flash drive (removable type), after the Windows Setup 'copy files' stage had completed and the system reboots, if you allow it to boot directly from the internal hard drive, you will see an error message:

'Windows Setup encountered an internal error while loading or searching for an unattend answer file.'

grubfm grub2 menus to install Windows+XML files

I have added two examples to the Alternate Downloads - a1ive grub2 file manager folder.

Direct UEFI64 boot from Tails 4.2/4.16 ISO file using a1ive's grub2 File Manager

Note: Later versions of Tails Live DVD ISO files (e.g. Tails v5.1, now have a UEFI-boot grub2 menu with a 'Tails (External Hard Disk) option. So just use a _.isodef.iso file extension and choose that option if you have an E2B USB HDD - otherwise choose one of the first options.

--------

This .grubfm menu can be added to the same folder as the ISO to get a 'User Menu' option when you select the .iso file. This allows us to UEFI-boot to Tails ISOs.

You must test on a real system (not a Virtual Machine) as it needs to detect a USB boot device.

Note: for Tails 4.6, and 4.16 you must delete the union=aufs parameter (why do the devs keep changing linux parameters every distro?).

As Tails seems to change on every version (!), you should look at the isolinux\live64.cfg file to get the correct 'params' parameters if you have a different version.

Tip: If you are booting from a VM or a Fixed-disk type of E2B USB drive (e.g. USB HDD or Corsair GTX flash drive), then you will need to press TAB at the Tails grub menu and edit the kernel parameters to remove the 'live-media=removable' entry each time you boot. For E2B, you can instead use the Tails_generic_for_USB_HDD.mnu from the sample mnu files folder (copy it and the ISO to the \_ISO\LINUX\MNU folder and edit the .mnu file with the name of your tails ISO file in two places).

tails-amd64-4.2.grubfm

E2B "UEFI version"

I have added a new page to the E2B website.

It describes how to add a second FAT32 partition to your E2B USB drive instead of using a .imgPTN file. This means it is more compatible for E2B Removable flash drives when booting Win7/8.1 ISOs.

UEFI-boot and then directly boot from ISO, VHD and WIM files using a1ive's grub2! 

No need to create .imgPTN files for most payloads. It also supports SDI_CHOCO configuration installs and other XML files.

Download (version 1.0).

Latest a1ive grub2 File manager v1.4 (with Windows 8.1 and XML support)

The new version 1.4 now supports the ability to run a Windows 7/8/10 install ISO with an XML file.

This allows us to:

1. Install any Edition of Windows from a Win7 ISO
2. Install Windows 8.1 without needing to enter a Product Key
3. Install Windows 10 with an unattend.xml file

Just copy your .XML files into the same folder as your ISO

e.g. on your large NTFS partition:
\_ISO\WINDOWS\WIN8  (contains .iso and .xml files)
\_ISO\WINDOWS\WIN7 (contains .iso and .xml files)
etc.

Download and unzip the latest version of the a1ive .imgPTN23 file (e.g. grub2 File Manager v1.4 (by a1ive).imgptn23auto) - see Alternate Downloads - Other folder for this. Place it in the \_ISO\MAINMENU folder.

Download the Sample_WIN8.1_XML_Files.zip, unpack and place in your Win8 folder.

For Win7 - to choose any Edition, use this XML file.

Use the XML file to choose any Edition in the Win7 ISO.

You can also add .xml files for Windows 7 (to install Home from a Pro ISO file for instance, because Win7 Retail ISOs contain all versions of Windows 7).

Win8...

Navigate to your WIN8 folder and choose an ISO file.

Try this UEFI multiboot E2B drive (just add ISOs)

This E2B drive should run most UEFI payloads once you switch-in the a1ive File Manager.

Once it has been made, just copy your .ISO, .VHD, .VHDX, .WIM, .IMG. EFI, .IPXE payload files to the 3rd NTFS partition then run WinContig or Defraggler to make the ISOs contiguous.

You should then have a USB drive which will Secure or non-Secure UEFI64 boot or non-Secure UEFI32 boot (and MBR boot on some systems too).

It will also allow you to run SWITCHPE so that you can switch out the a1ive File Manager partition and switch in a different .imgPTN file should you need to.

This system is much easier to maintain than the E2B grub2 menu system because you just add (or delete) payload files. No other .imgPTN files need to be made. You can create grub2 menus if you wish however (e.g. UEFI\MBR booting Ubuntu-based ISOs + persistence in my previous blog).

Note: Win8.1 ISOs will require you to enter a Product Key. This can be an installation-only generic key (or you can add a \sources\ei.cfg file into the ISO). Version 1.4 or later also accepts XML unattend files too!

See also here for a E2B UEFI USB drive.

Instructions