Tuesday 14 May 2019

E2B v1.B1d Beta and MPI Tool Kit 0.095 now available

E2B v1.Bd Beta is now available in .zip format from the Alternate Download Areas.

Changes from v1.B1c are:
  • New version of E2B_Editor now recognises the variables %day%, %month%, %year%, %SIZE_E2B% and %SIZE_HD1% if placed in the HEADER or FOOTER.
  • A new 'Easy2Boot' banner is now displayed on startup.
  • Hungarian language tweaks.
  • Latest version of grub4dos.
Also MPI v0.095 is now released and has additional tweaks for the new DLC2019 release and includes syslinux 6.05 pre-release.

How to remove the new E2B Banner

Sunday 12 May 2019

Make your PC scream when you unplug a USB device!

A recent Hack 5 video detailed a USB Rubber Ducky prank which is rather amusing.

The Rubber Ducky code downloads a scream.wav file and sets the sound file as the 'USB unplug' sound in your registry instead of the usual Windows default sound.

This means that whenever you unplug a USB device (of any type even if its a Bluetooth dongle and even if you first safely remove it or eject it) you will hear your PC scream!

Here is a Windows script which will allow you to set this up without a Rubber Ducky. You can also undo the Registry change too.


The script downloads the scream.wav file from the Hak5 site and it uses the built-in Windows utility 'bitsadmin.exe' to download the file. I was not aware of this Windows utility before. It looks quite useful, however it is much slower than a utility such as wget.exe.

P.S. If you want a different sound, find the file scream.wav on your hard drive (usually at C:\Users\(yourname)) and replace it with a different wave file of the same name (e.g. Woman Screaming).

If you are having problems downloading the file, just place any wave file named scream.wav in your user folder and then run scream.cmd.

Saturday 11 May 2019

grub4dos and non-USA keyboards

Together with Knyght, we have been working on supporting the Hungarian language and Hungarian keyboard for E2B.

E2B v1.B1c Beta includes the latest grub4dos version which adds even more Alt+ key support.

E2B uses grub4dos which, in turn, uses the BIOS to receive key codes from the keyboard. Unlike grub2, it does not have it's own keyboard interrupt handler.

A Hungarian 102-key keyboard produces the same keyboard scan codes as a USA 102-key keyboard or any other 102-key keyboard, the only difference is the engraved letters on the key tops.

This means that grub4dos must 'convert' the keyboard code it receives to generate the same character that is engraved on the key tops. For instance, when the key labelled " on a UK keyboard is pressed (shift+2), it should produce the " character and not the @ character that you would see if the keys had USA keyboard key tops.

grub4dos allows us to 'map' key codes using the setkey command. For instance, E2B uses a batch file to run a series of setkey commands to convert USA key codes to UK key codes:

Wednesday 8 May 2019

E2B v1.B1b Beta available


This new Beta version v1.B1b Beta includes the latest version of grub4dos which has enhanced keyboard support for non-QWERTY keyboards.

Changes in v1.B1b are:
  • Add menu text "(x present)" for number of XP ISOs present in Windows Install menu.
  • New grub4dos setkey command now supports oem102 and Alt+ key chord scancodes.
  • Small changes to Hungarian language files.
v1.B1a had these changes:
  • Add Hungarian language and keyboard support (thanks to Knyght).
  • If the Windows Install ISO filename contains the string 'WimBoot' (not case sensitive) then E2B will not use WIMBOOT to boot the ISO (you must use a Removable USB drive or use a WinHelper Flash drive) - e.g. Win10 Home and Pro x64 1809 Oct English International (NoWimboot).iso

Hungarian keyboard AltGr codes

On the Hungarian keyboard, some of the standard English ASCII characters are produced by using the AltGr key plus a letter or number key (the AltGr key generates a Alt+Ctrl key code).

For instance, the Hungarian keyboard is engraved so that the user expects AltGr+v to generate the @ symbol.

Tuesday 7 May 2019

A Removable-type USB HDD enclosure (+ UEFI-booting from ISOs on a IODD\Zalman drive enclosure)

With the new addition of WIMBOOT to E2B, you now rarely need to use a 'Removable' type of USB drive for E2B.

However, in a few cases where WIMBOOT cannot be used (low RAM or incompatible ISO) then Easy2Boot works better from a 'Removable' type of USB drive (such as most USB flash drives) or if you also connect a small WinHelper USB flash drive to the target system as well as the E2B HDD drive.

A user recently contacted me via the online Chat feature on the E2B website and mentioned that his USB HDD enclosure appeared as a 'Removable' device. He was from Dubai and had purchased a cheap Haysenser USB 3.0 HDD enclosure from his local market.

Saturday 4 May 2019

E2B v1.B1a Beta available with Hungarian language support

v1.B1a changes (download here in Latest Beta folder)

  • Add Hungarian language and keyboard support (thanks to Knyght).
  • If the Windows Install ISO filename contains string 'WimBoot' (not case sensitive) then E2B will not use WIMBOOT to boot the ISO (you must use a Removable USB drive or use a WinHelper Flash drive) - e.g. Win10 Home and Pro x64 1809 Oct English International (NoWimboot).iso
Knyght has kindly done a lot of work translating the E2B language files to Hungarian. There will also be a translation file for the MPI CSM menu too!

Keyboard support

This proved quite challenging because the Hungarian keyboard is not supported very well in grub4dos.

Friday 3 May 2019

Dell 'No boot device found.' error after installing Windows 10?

It seems that newer UEFI BIOSes from Dell now prevent you from MBR-booting from the internal hard disk (e.g. SATA, PCIe NVMe or M.2). However, you can still configure the BIOS to MBR-boot from external boot devices such as USB drives.



Details can be found on Dell Support link.

So, you can boot to the E2B grub4dos MBR boot menu (or MBR boot from a Rufus or other MBR USB drive) and install Windows 10 to the internal hard disk, however, when you reboot from the internal hard disk, you will see a 'No boot device found' error because the BIOS will only allow you to boot via UEFI from internal disks.

It seems that some of these Dell BIOSes were strictly UEFI-only at first, but then Dell released newer versions of the BIOS which included the 'Legacy External Devices' option. So you may need to update the BIOS if your current Dell BIOS does not have this option.

I suspect Dell later realised that a lot of their support utilities which relied on booting from USB or PXE only worked in MBR mode and so had to add this BIOS option!

Disclaimer: I don't actually have one of these systems to experiment with, so this information is just gleaned from the linked articles.

Sunday 28 April 2019

E2B v1.B0A update released

You may encounter an issue in v1.B0 where it reports an error or pauses for you to press ENTER before the Main Menu is loaded.

v1.B0A fixes this issue - please update from v1.B0.

Apart from this bugfix, you may also notice that the E2B drive icon in Explorer has changed (depending on if your system has cached thumbnails or not).



Note: Version 1.B0A still reports itself as v1.B0 in the menu heading.


Wednesday 24 April 2019

Windows 10 May 2019 Update fails with "This PC can't be upgraded to Windows 10" error

The latest Windows update problem from MS!

"This PC can't be upgraded to Windows 10" error on a computer that has a USB device or SD card attached.

The solution apparently is to remove your USB drives and SD cards!



E2B v1.B0 and MPI Tool Pack v0.039 now released


Available from Alternate Download areas here.

New eBook on UEFI multi-booting using WinPE images here.

E2B v1.B0 changes: