Are fingerprint sensors really secure?

Many years ago when fingerprint sensors first started to appear on the market, it seemed a really useful security feature.

The company I worked for (RM plc) made PCs, notebooks and tablets for schools. The use of passwords was a common problem in schools. The password needed to be long enough and complex enough to be secure, but also easy to remember. Also, the crafty kids would often watch a teacher type in their password and so learn their admin password. The kids would also forget their passwords, which meant that teachers or the IT admin guys were constantly having to reset their passwords and create new ones for them. Kids would write down their password and other kids could find them and copy their homework, etc. Passwords were a real headache.

So fingerprint scanners seemed to present an ideal solution and as everyone's fingerprint is unique - so it is foolproof, right?

Windows command line TAB auto-completion tip

I came across this tip yesterday. You can specify a file using wildcards and then use TAB auto-completion in a Windows command shell.

For instance:

If you are working at the Windows cmd shell and want to edit a .txt file (for instance), type

notepad *.txt

You can now press the TAB key until you see the file you want.

This works with more complex wildcards to such as  p*.t* and with network shares too.

RMPrepUSB v2.1.732 now available

I have updated RMPrepUSB to use the new version of mke2fs. It now asks you to specify  ext2, ext3 or ext4 format when you use the Create Ext2/3/4 FS button.

This makes it more convenient to create ext3 or ext4 files. I will remove the mke2fs files from Easy2Boot as there is no need for them now.

For persistence files with E2B, I recommend ext3 because ext2 files can become easily corrupted. I suggest you avoid ext4 because grub4dos may not be fully compatible with ext4 and I don't think there is much advantage over ext3 (but I might be wrong!).

Download here.

E2B v1.83c Beta available

v1.83c - changes from 1.83a in bold

• bugfix grub4dos 0.4.6a so does not absorb key presses before menu is displayed. 
• Make_E2B_USB_Drive (run as admin).cmd now checks for more versions of bootmgr (whitelist has new additions). 
• Warning message if try to use .imz file extension (need to convert to .ima).
• Add \_ISO\docs\E2B Utilities\Format_as_ext3_or_ext4 folder for re-formatting ext2 persistence files as ext3 or ext4 under Windows. (removed from 1.83 release version)
• Add sample .mnu files for Remix OS x86 with persistence (thanks Sergio!). 
• Small changes to German language files (thanks Frettt). 
• Add fmt_ntfs.sh script and udefrag utility to docs\linux_utils folder - can now make and maintain an NTFS E2B drive under linux.

Note that I have discovered (thanks to a post by Shiv Manas on Google+) that the udefrag linux utility will make files on an E2B USB drive contiguous (provided you have enough free space on the drive). This means that linux users can make and maintain an NTFS E2B USB drive. See ReadMe file in the linux_utils folder for more details.

E2B v1.83a Beta available

v1.83a 

• bugfix grub4dos 0.4.6a so does not absorb key presses before menu is displayed. 
• Make_E2B_USB_Drive (run as admin).cmd now checks for more versions of bootmgr (whitelist has new additions). 
• Warning message if try to use .imz file extension (need to convert to .ima).

Available from Alternate Download Areas as usual.

Anyone tried the SDI_CHOCO feature yet?

Convenient way to run MS-DOS utilities directly from an NTFS E2B drive

If you have several different DOS utilities (to flash a BIOS perhaps or run a DOS-based diagnostic) which are provided as .exe or .com files, then you may have trouble adding it to an NTFS E2B USB drive.

Usually, you would have to make a DOS-bootable floppy disk image or perhaps make a bootable USB flash drive and then 'capture' the flash drive as a FAT32 .imgPTN file using the MPI Tool Kit (MakePartImage). Actually, E2B will try to boot to IO.sys or Kernel.sys, so you do not have to 'SYS' the floppy image, just ensure that the correct boot files are present inside the image file.

Today, I found some DOS floppy disk images which contained NTFS drivers on a Russian site (www.bootdisk.com seems to not provide free downloads any more). This means that all you have to do, is copy your DOS utilities to a new folder on your NTFS E2B USB drive, boot to the floppy disk image and then run the DOS utility straight from the NTFS E2B drive.

Note: The FreeDOS floppy image included with E2B v1.83+ now includes a DOS NTFS driver, so you can access an NTFS E2B USB drive as drive C:. Because FreeDOS is used and not MS-DOS 8.0 however, long filenames are not displayed correctly and so it is not quite as good as the DOS4NTFS.IMZ image.

Add a 'factory' recovery partition using Aomei One Key Recovery

Whilst looking at the Aomei Backupper utility (horrible name!) in a previous blog, I saw the free Aomei One Key Recovery product on the Aomei website and decided to try it today.

The website has a lot of 'Chinglish' sales talk and very little information about how it works. Here are the main points for you techies!...

E2B v.1.82 is now released

v1.82 2016-08-13

• New grub4dos 0.4.6a 'E2B.cfg missing' bug fix + others. 
• SDI_CHOCO (automated driver and apps install for Win 7/8/10) added. 
• Support for WSUS Offline update in SDI_CHOCO added. 
• New Win8/10 SDI_CHOCO XML files (+ some older XML files re-named). 
• Fix for Windows Setup refusing to install to internal hard disk if using E2B HDD+WINHELPER flash drive combination, with some systems. 
• Install from XP ISO hang/reset grub4dos bugfix. 
• Small tweak to \_ISO\e2b\grub\menu.lst to remove extra screen clear. 
• Improve LOADISO.cmd routine when searching for virtual Win7/8/10 ImDisk DVD drives. 
• Added two new bootmgr versions to 'whitelist' for VHD booting.
• Update script now lists the files that are updated by robocopy

Download E2B v1.82, unpack to a new folder and then use the \UPDATE_E2B_DRIVE.cmd script to update your E2B drive.

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

Note: I just noticed that the new version of grub4dos has a small bug. It soaks up key presses, so if you press Ctrl+U whilst the Main menu is loading, E2B does not go straight to the Utilities menu. You have to wait for the Main menu to display before you press Ctrl+U. Hopefully this will be fixed by the developers in the next version of grub4dos. P.S. Fixed in v1.83.

Which free Disk Backup software to use?

I was interested in finding a free offline disk backup and restore utility that I could boot from E2B and quickly make a full 'bare-metal' disk backup or restore of any (Windows) system.

I found a good article on a Raymond.cc blog post here, which tested 20 different backup utilities, but many were not free.

I decided to quickly test some of these using a Windows 10, Lenovo IdeaPad 300 notebook containing an SSD internal drive (13GB of files) and booting from an E2B SSD in an Inateck FE2007 USB 3.0 drive caddy. Well, I didn't want to spend days using spinny-things and slow USB 2.0 drives, did I?

My results tallied fairly well with the Raymond-site results (see the nice tables of free software further down this page).

My results (booting from E2B) were:

YouTube video on SDI_CHOCO feature in Easy2Boot v1.82

There is a live demo near the end of the video.

Full automated Windows 10 install + a few drivers + Teamviewer in 12 minutes.

Simple to set up the E2B drive.

Once you have added the Driverpacks to your E2B drive, you can use E2B+SDI_CHOCO to install any version of Windows 7/8/10 Install ISOs. Just add the Windows ISOs and choose one of the ***SDI_CHOCO.XML files.

'INACCESSIBLE BOOT DEVICE' error from Windows 10 - and you won't believe the cause (I didn't)!

In the last few weeks, my Asus Z87 Haswell PC has started to display the dreaded 'Inaccessible boot device' BSOD error on start-up (it was the more friendly Windows 10 graphical version with QR code).

Now the PC was actually starting to boot. I would get the spinning circle of white dots and I could see the HDD LED blinking. Then the HDD LED would stop flashing, and after displaying 30 seconds or so of more spinning dots, I would get this blue screen error.

The thing was, if I rebooted the PC a few times, it did eventually manage to boot, so I continued to use the PC for a few weeks and just put up with this issue. I tried the Windows Troubleshooter and the Repair option and also ran BCDBoot manually, but it didn't fix it.

A few days ago, I fitted a new 2TB Hitachi SATA HDD drive to my system for extra storage, so I decided to investigate this issue further (also I was now getting the BSOD error more often!).

Since I had just connected a new SATA HDD, the first thing I did was to disconnect it, but I kept getting the same BSOD.

Next I disconnected all the SATA HDDs (2) and the single SATA DVD drive, I just left the first Samsung 500GB SATA SSD boot drive connected.

The result was a perfect boot into Windows 10. I tested this several times, switching the system off and on again - all perfect!

So, the problem was due to one of the SATA drives that I had disconnected. I re-connected them back one-by-one until the problem re-appeared.

And you'll never believe the cause!

And the culprit was (drum-roll....)

How to run an SDI_CHOCO install using a .imgPTN Windows Install file

I have now added instructions to the E2B website on how you can automate a Windows 8.1/10 install using the SDI_CHOCO feature from a .imgPTN file.

This means you can perform both an MBR or UEFI installation with an unattend.xml file and use the automated SDI driver installer + install apps using choco + add WSUS Offline updates automatically.

If you have an E2B Removable drive, it is quite easy. Just add a \Unattend.xml file to the inside of the .imgPTN file. The XML file must contain a Specialize section which runs \e2b\Stage1.cmd (see the example XML files in the e2b folder for examples).

If your E2B USB drive is a fixed-disk (hard disk) USB drive, you will need to modify the boot.wim file (or simply add a small Removable Flash drive that contains the correct files - but don't use a WINHELPER flash drive or the XML file will be erased by E2B!).

I have added the required files to the MPI Tool Kit v0.067 (Note: use the new version dated 2016-08-08, if you downloaded it yesterday, you may not have the \e2b\Stage1.cmd and Stage2.cmd files!).

Using a .imgPTN file is tricky because once the E2B USB drive has switched to the .imgPTN partition image, the E2B partition (and all the SDI, DRIVERS, APPS, WSUS folders, etc.) are no longer accessible!

I get around this by automatically switching the partition back to the E2B partition when the Specialize phase is reached. Stage1.cmd is inside the .imgPTN partition and copies the files to the target hard disk, Stage2.cmd then runs from the target hard disk and switches back the E2B partition to allow access to the CHOCO_SDI folders.

You can find the instructions at the bottom of this page.

Note that the XML file needs to be named \Unattend.XML if it does NOT contain a WindowsPE configuration pass, or \AutoUnattend.xml if it does contain a WindowsPE pass.

P.S. It seems the first release of the Windows 10 Anniversary install ISO has the same bug as the Windows 10 TH2 first release - internet access does not work in the Specialize pass! I fix this by running and then killing msoobe.exe. This sets up the network stack and host name correctly. Microsoft fixed this bug in the later TH2 versions, but they seem to have regressed when they released the Anniversary edition!

If you want to install choco apps in the Specialize pass, then you will need internet access. If you only install choco apps using MyStartup.cmd, then you can add a NoInternet.tag file to prevent SDI_CHOCO from trying to run msoobe to fix the internet connectivity.

MPI Tool Kit v0.067 released plus E2B v1.82h Beta available

The MPI Tool Kit now supports a MyCSM.cfg menu configuration file, so that you can use the E2B_Editor GUI utility to design your own custom CSM menu. It also supports GFXBoot menus. You can add files to the CUSTOM folder in the MPI Tool Kit and any .imgPTN file you make in future will have your custom menu. For instructions, see here. Download from the Alternate Download Areas.

Sample MyCSM.cfg file with (nasty-but-small-file-size) pink jpeg wallpaper.

Also, E2B 1.82h Beta is released. It includes the latest grub4dos 0.4.6a which has three bugfixes and SDI_CHOCO. This is a 'release candidate' and will be fully released as the official v1.82 in a few days - please try it and feedback if you find any issues. SDI_CHOCO allows you to easily completely automate the installation of Windows 8.1 or 10 using an unaltered Microsoft Install ISO and automatically install drivers, Windows Updates and applications.

P.S. If you have previously donated or contributed in other ways to E2B and don't like the new Easy2Boot website page format (and all the ads!), please contact me for a way to get the original www.easy2boot.com site layout.

No-More-Ransom - A useful Anti-Ransomware website

www.nomoreransom.org looks like a useful anti-ransomware site where you can find decryption tools, information and advice.

The “No-More-Ransom” website is an initiative by the National High Tech Crime Unit of the Netherlands’ police, Europol’s European Cybercrime Centre and two cyber security companies – Kaspersky Lab and Intel Security – with the goal to help victims of ransomware retrieve their encrypted data without having to pay the criminals.

P.S. If you found this useful, please tick one of the Reactions boxes below.

Upgrading Win7 to Win10 still works! + weird 'Unable to install Windows to the hard disk' issue solved.

I was playing around with PSUs yesterday and temporarily 'borrowed' the PSU from my old Dell Inspiron 530 to test it with another system.

Dell Inspiron 530

After confirming that it worked on the other system, I replaced it back in the Dell 530 when I realised that the 250GB hard disk in the Dell was actually running Windows 7 (the Dell was originally installed with Vista, but I later installed Windows 7 Ultimate many years ago using a Retail product key).

I decided this would be a good chance to see if the Windows 10 Upgrade offer was still working, so I booted from my E2B drive (an Inateck FE2007) to a Windows 10 Pro TH2 VHD, typed in the Windows 7 Product Key (which I had obtained using ShowKeyPlus previously) - and voila! I had one activated Windows 10 Pro system.

So as of 2016-08-05, I can confirm that you can still use a Win7 retail product key to activate Windows 10.

Problems installing Windows 10!

I decided to do a fresh install of Windows 10 from an ISO file using my E2B hard disk (FE2007 + Samsung SSD) and a 'Helper' USB flash drive. As you may know, if E2B is on a hard disk, we need to add a Removable USB drive so that Windows will 'pick up' the AutoUnattend.xml file from the Removable drive during Setup and that we can make ImDisk run and load the ISO as a virtual DVD drive. The FE2007 hard disk enclosure has three USB 3.0 ports built in, so the flash drive is always connected to the E2B hard disk.

So, I booted to E2B and selected the Windows 10 ISO (actually the latest 'Anniversary' version) and got to the Disk\Partition selection screen as usual. BUT I then got stuck on a problem - Setup refused to install Windows onto the internal hard disk!

Every time I got the message:  'We couldn't create a new partition or locate an existing partition'.

Easy2Boot v1.82g Beta available

This v1.82g Beta includes SDI_CHOCO and the new grub4dos (beta) version which fixes the "E2B.cfg missing" error which a handful of users have experienced on certain systems containing certain partitions.

I have also renamed the E2B Win8 and Win10 XML files. When you perform an E2B Update, it will delete the old v1.81 XML files and add the new ones. If you have previously installed an SDI_CHOCO beta, I suggest you first delete all the old .XML files (that are E2B ones) and then do an Update.

As usual the download is available in the Alternate Download Areas.

Any feedback welcome.

Has the free Windows 10 upgrade really finished?

According to a Martin Brinkman blog post here, you can still get the free Win10 upgrade.
If this is true, can you also do a clean install of Win10 and use a Win7 or Win8 Product Key? Presumably the same activation process will still work as before and the trick of simply booting from a USB drive to Win10 will still work.

P.S. 2016-08-05 I booted to Win10 TH2 Pro on a Windows 7 Ultimate system today and used the Windows 7 Ult key to activate it - it worked fine!

grub4dos - good news, very good news and not so good news!

YaYa has fixed two bugs in grub4dos 0.4.6a

1. Issue #122 - Replacing strings in a file using cat --locate=xxx --replace=yyy sometimes didn't work
2. Issue #119 - grub4dos crashes when it access certain partitions (this is the “\_ISO\e2b\grub\E2B.cfg is MISSING!” issue)

Bug #122 has a workaround and this has been added into E2B v1.82 so that we can use older versions of grub4dos if we need to (useful for testing different versions, etc.). The bug was only found due to the new SDI_CHOCO feature in v1.82 and so did not affect previous versions of E2B.

Bug #119 is great news. Many people have helped in investigating this bug but a special thanks to Norbert who spent a lot of time to prepare a Virtual Machine in VBox which allowed the developer (YaYa) to see the problem and enabled him to fix it!

The not so good news, is that I discovered a new bug to do with certain types (joliet?) of XP ISOs crashing when accessed (e.g. using a cat command on a file inside the ISO). The bug report is Issue #123 and affects grub4dos 0.4.6a versions after 2016-04-10 (so does affect E2B v1.81 which used 2016-07-04 and E2B v1.80 which used 2016-04-26, but not E2B v1.79 which used 2016-03-26). A genuine MS XP3 ISO does not seem to be affected though and it only seems to happen with some ISOs on some systems (TBD). Hopefully, YaYa can find the problem and fix it. Then we will have a new version of grub4dos with all the major outstanding bugs fixed.

2016-08-04 - YaYa has fixed the bug. Next version should have all fixes!

Add Parted Magic 2016 with SAVE feature to E2B

Here is the .mnu file for the PMagic 2016 ISO with the SAVE feature supported.

SDI_CHOCO page now added to E2B website

The SDI_CHOCO feature allows you to fully automate a Windows install + install drivers + applications + Windows updates completely unattended.

Once you have it set up, when a new version of Windows is released, just copy the new Windows Install ISO onto your E2B USB drive and use that instead of the old ISO! No need to change anything else.

See here for details.

You can have multiple configurations for different systems or configurations. You can install your own custom drivers or applications too.

For instance, a full Windows 10 installation with drivers and a few applications can take about 12 minutes from first boot to the E2B USB drive to the final user Desktop (watch the video).

Hope it is not too confusing!

P.S. If you found this useful, please tick one of the Reactions boxes below.

How to activate Windows 8/10 automatically

You can use the following cmd script to get the OEM key which has been programmed into the BIOS by the manufacturer and then activate Windows with it automatically. Of course, the OS must match the OEM key (e.g. Windows Home OS <> Windows Home Product Key).

AutoActivate.cmd  (run as admin)

@echo off
pushd "%~dp0"
set PKEY=
get_win8key.exe > WINKEY.txt
set /p PKEY=<WINKEY.txt
if not "%PKEY%"=="" (
echo Activating using key %PKEY%
cscript //NoLogo %systemroot%\system32\slmgr.vbs /ipk %PKEY% > act.log
cscript //NoLogo %systemroot%\system32\slmgr.vbs /ato >> act.log
type act.log
)

popd

get_win8key.exe can be obtained from here. It also works on Windows 10 systems.

P.S. after downloading get_win8key.exe - right-click on the file - Properties - and tick UnBlock. Otherwise Windows Powershell may refuse to run it.

How to automate the installation of Windows and Lenovo drivers using SDI_CHOCO

Here is how I modified SDI_CHOCO on my E2B drive so that instead of using Snappy to install generic drivers, it installs all the correct official Lenovo drivers and applications.

New user files are created by the end user to modify the install behaviour, so updating E2B to the latest version will not delete these new files because only the original E2B files are updated.

If you have several different models of PCs and Notebooks to install, then the XML file and SDI_CHOCO folder structure should be duplicated, renamed and modified accordingly, for each different model.

Easy2Boot v1.82SDIf Beta now available

Version 1.82f does not install any choco applications by default now (i.e. Google Chrome and TeamViewer are not installed by default).

I think that v1.82 is getting good enough for release now, so please test and provide feedback.
I am still waiting for a grub4dos bugfix though.

E2B v1.82SDIe Beta with WSUS Offline Update support

This new version includes support for the WSUS Offline Update utility.

You can download and extract WSUS Offline Update to the \_ISO\WINDOWS\INSTALLS\wsusoffline folder of your USB drive and then run updategenerator.exe - pick the OS's you want to support - e.g. Win 8.1 x86 & x64, Win 10 x86 and x64 - and then download the updates (this may take quite a while!).

Easy2Boot v1.82SDId Beta available

The v1.82d Beta version has a few new XML files added for Windows 8 and 10 ISO installs:

• Win10_Choose_a_key_SDI_CHOCO.xml
• Win8_Choose_a_key_SDI_CHOCO.xml

These allow you to do a manual install of any Win8/10 ISO and choose the Product Key that you want to use (i.e. the same as the default Option 0 choice, but it also runs the SDI_CHOCO install, so it will install drivers and applications). These two new XML files do not contain any other configuration settings and are not 'automated'.

There is also a new E2B feature for Windows 8 and Windows 10 (and 2016) installs from an ISO. 

E2B v1.82SDIc Beta now available

This new version just has a few changes to improve the SDI_CHOCO.cmd script if you want to use WiFi instead of Ethernet to connect to the internet during installation.

If anyone has tried the new Snappy+Chocolatey XML files yet, please let me know how you got on!

Have you discovered the surprise yet (clue: you will need to test using a notebook or PC with speakers!)?

E2B 1.82 SDI Beta b version now available (Snappy+Chocolatey)

This is a new, slightly tweaked version of the previous SDI+Choco version. It is available in the Alternate Downloads Areas as usual. Read the previous blog post for how to get it working.

It now includes sample XML files for Win 8.1 Pro, Win 8.1 Home, Win 10 Pro and Win 10 Home for both USA and English International versions of the ISOs.

• For 'English' ISOs use the 'US' XML file
• For 'English International' ISOs use the 'UK' XML file

You can remove the E2B USB drive when you see the CAPS LOCK and SCROLL LOCK LEDs lit.
I have added better logging and tidied up the cmd scripts a bit.

There is a little surprise added too - leave a comment when you find out what it is!

Note: If you have modified any of the original E2B files in the \_ISO\WINDOWS\INSTALL folder (naughty, naughty!), then when you update E2B with this new version, it will obviously overwrite your modified files. So rename any folders you want to keep first. if you have some Driverpack downloads in the SNAPPY folder, they will not be affected when you update.

E2B is Snappy and Chocolatey!

E2B v1.82SDIa_Beta is available for download in the Alternate Download Areas.

Once you have downloaded and added the driverpacks, you will be able to perform a fully automated install of Windows with all drivers and any apps you want too, using an unmodified MS ISO and one of the xxxxxxx_CHOCO_SDI.XMl files on your E2B USB drive.

E2B progress report

I recently received a nearly new pre-owned Lenovo 300 IdeaPad i5 2TB 8GB notebook. It was a refurbished laptop which I won on eBay (exdemolaptops if you are interested). One of the main requirements for me was a bottom hatch that allows me to quickly swap the hard disk and of course, USB ports!
It has one USB 3 port and two USB 2 ports. I swapped over the 1TB spinny-thing for a 120GB SSD so that I could do Windows Installs as quickly as possible for testing the new Snappy+Choco version of E2B. A completely automated Win10Pro install, including installing 19 drivers and 2 applications takes under 15 minutes.

Thankfully, CSM and UEFI-booting are easily selectable (via Fn+F12) and booting to E2B is really fast on the USB 3 port too!

Automatically install drivers with Snappy Driver Installer

Today I discovered Snappy Driver Installer (SDI). It has been around for a while but I had not heard of it before.

If you don't have all the DriverPacks it needs, SDI will download them via torrents, but it can take a while...

You can download this utility to a USB drive and just run it from any Windows system (XP->Win10, 32-bit or 64-bit). It will look at your hardware and current Windows drivers and then search for a better driver within it's Driverpacks and then install it. The downloads are in 'Driver Packs'. A full download will take 13GB of drive space if you want all the driver packs, or it can be asked to download just the ones you need.

The nice thing about SDI is that you can also run it from the command line and it can be automated.

So using SDI and a few scripts, I added some new folders to my Easy2Boot USB drive.

The folder structure on the E2B USB drive is currently:

\_ISO\WINDOWS\INSTALLS
      \APPS - contains installers and scripts to execute them
      \DRIVERS\904HA\WIN1032 - contains scripts and special drivers to copy to HDD
      \SNAPPY    - contains the SDI files
      \CONFIGS - contains main .cmd file specified in RunOnce portion of XML file

Add post-install files to a Windows Install (using an unaltered MS ISO)

I have added a bottom section to my previous blog here, detailing how you can inject files and folders automatically into a Windows Install (7/8/10) by using an entry in an XML file. The .iso file is not modified at all. All files are copied from the E2B USB drive.

This means that as well as a fully automated install using an unattend.xml file, we can also cause it to transfer over any files we like (e.g. drivers, apps, registry tweaks, etc.) from the E2B Removable USB drive, without needing to modify the original MS ISO in any way.

It also allows us to add in a \Windows\Setup\Scripts\SetupComplete.cmd file, if required and even run a StartUp.cmd file for first user logon.

The next version of E2B will include a test sample XML file (\_ISO\WINDOWS\WIN10\Auto_WipeDisk0_Win10ProUK_setupcomplete_demo.xml), with some dummy .cmd files which happen to be in \_ISO\e2b\firadisk, so you can test and modify it for yourself if you wish.

This means you can use the same ISO to install different models of PCs with different drivers and applications just be selecting the correct XML file. Your E2B drive can contain folders for machine-specific drivers and different folders for applications, so that you can copy over only those folders that you need.

Of course, how you install the drivers and apps from a cmd file is usually the tricky part, but I leave this up to you!

Add Gentoo + Persistence to E2B

Here is how to boot from a Gentoo ISO file with persistence.

I used the livedvd-x86-amd64-32ul-20140826_gentoo.iso download.

The cheat code needed is in the form aufs=/dev/sdX3  where X is the USB drive.

Since the USB drive number will vary from system to system, we have to try to guess what Gentoo will assign the USB drive as!

Instructions

Bug in E2B v1.81 - Please update to v1.81A (bugfix in MAKE_E2B_USB_DRIVE (run as admin).cmd script)

A bug was reported in the v1.81 MAKE_E2B_USB_DRIVE (run as admin).cmd script which causes it to prematurely abort if  C:\bootmgr is not found. After copying over the files, the script checks the size of bootmgr and then copies it to the E2B drive if it is a compatible version - unfortunately if C:\bootmgr does not exist then the script just aborts, and so it does not install grub4dos, leaving you with an unbootable E2B USB drive ('bootmgr is missing' error).

This is now fixed in E2B v1.81A.

The E2B menu will still display "v1.81" because only the make script is affected.

Easy2Boot v1.81 is now released

QR code contains the URL of 'List of tested payload' page on E2B website.

Version 1.81 contains 3 bugfixes (in bold) and a few tweaks...

As always, just download and extract E2B to an empty folder and run the \UPDATE_E2B_DRIVE.cmd file to update all your E2B drives.


v1.81 2016-07-09

• New grub4dos \grld 0.4.6a 2016-07-04 (grub4dos USB driver may now work better?)
• $$AddWin2Main.mnu bugfixes for direct booting of Windows Install ISOs from Main menu. 
• Bugfix for .isope path problems and + make work if iso on 2nd partition (note: .isoPExxx extensions only work correctly on Removable Flash drives, otherwise convert to .imgPTN files). 
• SWITCH_E2B.exe v1.0.12 bugfix for syslinux booting (also supports .imgptn*2* as well as .imgptn*23* extension for special users - .imgptn*2* is NOT supported by E2B though!).

Which USB 3.0 SATA disk drive enclosure is best for E2B (six enclosure shoot-out)?

USB 3.0 controllers are designed to operate at fast speeds, so it makes sense to buy a USB 3.0 drive enclosure, even if you are going to connect it to a USB 2.0 port. Because I do a lot of work with USB drives, I mostly use a USB 3.0 drive caddy containing an SSD hard disk for maximum speed. I also use a UASP HDD enclosure to get the best possible speed with an SSD drive under Windows.

However, for booting a wide range of systems with E2B, a UASP HDD drive may not be the most compatible option...

Creating fully unattended XML answer files for Windows 10 Install ISOs for E2B

I detailed in a previous blog here, how to create and modify an XML file to fully automate the installation of Windows 7 and 8.

The process is identical for Windows 10. You need to specify a Product Key in the XML file (same as Win8), although not all ISOs may need it (e.g. some MSDN or Volume Licence ISOs).

The process is:

Adding 'multiboot' WinPE ISOs (such as GeekSquad MRI_5_10_2.ISO) to E2B

If you have an ISO file which contains bootmgr and boots to WinPE, then you can use it with E2B by renaming the file extension to .isoPE or .isoPE01. This only works if you have a Removable E2B USB drive (you should convert the ISO file to a .imgPTN file if your E2B USB drive is of the 'fixed disk' type).

Note: There was a bug in previous E2B versions when using .isoPE and .isoPE01 file extensions (the blue LOADISOPE.cmd console window stopped with an error and the ISO was not loaded). You will need a recent version - e.g.  E2B v1.81 Beta from the Alternate Download Areas (see side bar).

However, if you use the .isoPE file extension, it will cause E2B to immediately load and run bootmgr and so the ISO will boot straight to WinPE and you won't see the non-Windows boot menu, if one was present inside the ISO.

Make a basic Easy2Boot MyE2B.cfg configuration file.

If you already have an E2B USB drive, you can easily update it by downloading the latest version of E2B and then run the UPDATE_E2B_DRIVE.cmd script.

Newer versions of E2B have a new version of the MAKE_E2B_USB_DRIVE (run as admin).cmd script, so that when you make a new E2B USB drive, it also asks you some questions about how you want to configure E2B - e.g. language, keyboard, if you want the file extension to be displayed in the menus and if you want the rotating E2B logo to be displayed (with Boiler Plate or QR code).

If you have already made your E2B USB drive, you can run the same script to create a new \_ISO\MyE2B.cfg file by running the \_ISO\docs\Make_E2B_USB_Drive\Make_MyE2B.cfg.cmd script. It will ask you to select a USB drive and then will run through the same questions that MAKE_E2B_USB_DRIVE (run as admin).cmd asks.

QR code in E2B v1.81f

E2B v1.81f will allow you to add a QR code 'STAMP' to the menu wallpaper when you run \MAKE_E2B_USB_DRIVE (run as admin).cmd to make a new E2B drive.

The QR code contains the URL for the E2B website's 'List of tested ISOs/payloads' page, so you can use your mobile phone's QR reader to quickly look up the recommended way to add any payload to your E2B drive if your first attempt did not work!

If your mobile phone does not already have a QR reader, there are many free apps that support QR code scanning. Try it out on the screenshot below now...

Directly boot to .VHD, .VHDX and .WIM (NT6) files with E2B

E2B can directly MBR-boot to dozens of .VHD, .VHDX and .WIM (NT6) files. Just copy them to one of the standard E2B boot folders (e.g. \_ISO\WIN) and boot to E2B. They do not need to be contiguous either.

E2B uses chenall's NTBOOT.MOD grub4dos scripts to modify a BCD file which is copied to a virtual floppy disk in memory, so that it contains the correct path to point bootmgr at the boot file.

There are a few caveats however:

1. A compatible version of bootmgr is required.
2. There must be no spaces in the filename or path.

If you use the \MAKE_E2B_USB_DRIVE (run as admin).cmd script to make your E2B drive, it will copy bootmgr from your Windows system to the E2B drive. If you did not use the script, then you will need to ensure that you copy the bootmgr file to the \_ISO\e2b\grub\DPMS\NTBOOT.MOD folder yourself.

Until recently, I thought that only Windows 10 versions of bootmgr were incompatible, but I have now tested over 20 different versions (renamed to show what symptom I got with each one when booting a VHD):

RMPrepUSB v2.1.731 and grub4dos 0.4.6a

RMPrepUSB v2.1.731 will install grub4dos 0.4.6a when you use the 'Install grub4dos' button.

Under some circumstances, you may hit the grub4dos 0.4.6a bug where it does not like a certain partition on one of the drives in your system and fails to boot to grub4dos. This is the same issue as you may sometimes get when you boot to E2B and get a E2B.cfg file missing error.

The solution is to use an older 0.4.5c version of grub4dos.

In the case of RMPrepUSB, simply copy the required 0.4.5c version of grldr to the RMPrepUSB folder (press F3 in RMPrepUSB and it will open the correct folder). For E2B, replace the \grldr file.

I suggest you use the 2015-05-18 version of grldr 0.4.5c (I have not validated later versions of 0.4.5c, so they may have bugs).

Note that 0.4.5c has some missing features.

Version 0.4.6a has:

• A fast USB 2.0 rd/wr driver
• .jpg image file support for backgrounds
• ext3/4 support
• Better ISO, Joliet and UDF support
• Can boot from non-contiguous files (if not too fragmented) using map command
• Large font support
• Stamp and Animated graphics support
• Many bug fixes, incl. NTFS file write bug fix
• Better debugging
• Extra commands

The bug in 0.4.6a is difficult to reproduce, but we won't find it by using 0.4.5c all the time. If you find a system which shows the problem, please try to narrow down which partition it is that is causing the problem (e.g. change the partition type to 0 - then see if you can boot to grub4dos - repeat for each partition until you find which one is causing the issue, then make an image of the bad partition and send me or the developers the image + the MBR .bin file so that we can reproduce the problem). The bug is reported here.

How to pre-activate all your Win7/8 systems for Windows 10 without actually installing Windows 10 (even after 2016-07-29)!

Time is running has run out! However, you can still activate Windows 10 using a Windows 8 or Windows 7 Product Key even though the 'upgrade' deadline has expired!

Note: This will probably not work after 2017-12-31 - see here.

Microsoft have said that Win10 will probably be their last version of Windows, because they will release continuous updates for Win10.

So even if you don't like Windows 10 now, you may like Windows 10 a lot more in 6 months time or in 3 years time. Unless you activate and register each system now, you will have to pay for it later!

If you are still running Win7, you should definitely upgrade to Win8.1 or Win10 because Win7 has reached 'end-of-life'. Manufacturers are no longer releasing peripherals with Win7 drivers, so any new peripherals you purchase may not run on Win7 if it requires a special driver.

Tip: You can check the Windows version by running 'winver' from the Start - Run box.

As I have mentioned before in previous blogs, you don't have to install Win10 onto a system's internal hard disk in order to get it registered with Microsoft for Windows 10. All you need to do is boot the Win7/8 system from a USB drive which has Windows 10 To Go on it. Here are the steps:

New versions of E2B, MPI_Tool Pack, RMPrepUSB available

The fix for SWITCH_E2B.exe is now added and seems to work.
I also found a small bug in my code which also affected RMPartUSB, so I have re-released RMPrepUSB (which contains RMPartUSB).

• SWITCH_E2B v1.0.11 - bugfix to adjust hidden sectors
• E2B v1.81c - has new RMPartUSB v2.1.731 and new SWITCH_E2B.exe v1.0.11
• MPI Tool Pack + Clover Lite 0.066 - has new SWITCH_E2B v1.0.11
• RMPrepUSB v2.1.731 - new RMPartUSB 2.1.731

New versions are in the Alternate Downloads Areas (see side bar).

If you already have made .imgPTN files and they have been booted at least once using the E2B menu system, then you don't need to update them.

SWITCH_E2B.exe bug found!

For a number of months now I have been experiencing odd issues with .imgPTN files, especially with syslinux-bootable images. Sometimes they worked fine and I could MBR-boot to syslinux using the first MBR-Boot option and also the other 1 or 2 syslinux boot options, but on other occasions, when I made a new .imgPTN file, I found they would only boot via the syslinux PBR option (#2) and not the default boot option #1 or the syslinux PBR.BIN backup file option #3.

Menus #1 and #3 may not work until you use grub4dos to select the .imgPTN file instead of SWITCH_E2B.exe.

Whilst setting up the slackware+persistence tests in the previous blog, I came across this behaviour again and I have finally found out what is going on (after nearly going crazy)!

I realised that if I used SWITCH_E2B.exe to switch to a new .imgPTN file that had never been booted via grub4dos and E2B, then I had this boot problem in the CSM menu. However, if I switched to that .imgPTN file (once!) using the E2B grub4dos menu, then from then on it would work using SWITCH_E2B.exe and using the E2B menu system.

The reason for this is that the E2B menu uses grub4dos and the partnew command which modifies the partition boot record hidden sector values (at locations 001C-001F if you are curious). SWITCH_E2B.exe does not do this.

So you must always use the E2B menu system first to switch in your .imgPTN. You only need to do this once - after that you can use SWITCH_E2B.exe if you wish.

Also, if you 'move' the .imgPTN file's position on the E2B disk (e.g. defrag it or copy it), it will obviously not alter the hidden sector values inside each .imgPTN file. So you will need to boot using the E2B menu (once) to make them work.

I will look at fixing SWITCH_E2B.exe so that it also modifies these hidden sector values.

P.S. SWITCH_E2B_v1.0.11.zip is now available from the Alternate Downloads area and has the hidden sector update fix.

Add Slackware+persistence to E2B

Slackware will use either a \persistence folder or a \persistence.img file (by default) for persistence.

However, it appears that this needs to be in ext4 format.

I could not find a way of pointing the LiveCD ISO to the persistence file when booting directly from an ISO, so here is how I went about adding Slackware with persistence to my E2B USB HDD.

1. Drag-and-drop the slackware64-live-mate-current.iso file onto the MPI_FAT32 Decktop shortcut to make a slackware.imgPTN file - when prompted for a size, add enough for your persistence requirements - e.g. add 500MB (max. you should add is 4GB because we are using FAT32 for the partition so we cannot create a persistence.img file larger than 4GB in step 5 below).
2. Copy the slackware.imgPTN file to your E2B drive (e.g. \_ISO\LINUX folder)
3. Switch to the slackware.imgPTN file (e.g. by booting to the E2B menu).
Do NOT use SWITCH_E2B.exe to switch to the slackware.imgPTN file for the first time as it can cause problems with syslinux booting. Once you have booted via E2B once, you can use SWITCH_E2B.exe afterwards.
4. The files in the new partition should now be accessible to Windows.
5. Run RMPrepUSB - Create Ext2 FS and create a new persistence file on the USB partition called persistence.img   (note: case sensitive). Make the size as big as any remaining free space on the partition (e.g. approx 500MB). Any Volume name will do.
6. Now boot to slackware (to the CSM menu) by choosing boot option #2 (the #1 entry may not work unless you are using SWITCH_E2B.exe v1.0.11 or later) and boot to slackware.
7. Log-in as root (pwd=root) and run a terminal window
8. Type the following commands:

  mkfs.ext4 /mnt/livemedia/persistence.img
  tune2fs -m 0 -c 0 -i 0 /mnt/livemedia/persistence.img

9. Now when you next boot, persistence should be working.

Tip: Use CTRL+S during booting when you see the 'SLACKWARELIVE:' text, to check that the persistence.img file has been found (CTRL+Q to resume):

Note: Slackware would not boot from my USB HDD  UASP drive caddy (e.g. Inateck FE2005) on my Z87 PC. It reported it could not find the 'livemedia' during booting. Using fdisk -l  , it did not list the E2B USB hard disk. If I removed and re-inserted it, it did not allocate a device name, but if I inserted a USB 3 Flash drive, it reported sdd1 was found. I conclude from this that slackware does not contain a UASP driver, so you cannot MBR-boot from USB 3 UASP drives/caddies (I tried both USB 2 and USB 3 ports).

10. I recommend you take a backup (at least of the persistence.img file) in case of later boot problems!

UEFI-Booting

You should also be able to UEFI-boot via Clover or your system firmware in UEFI-boot mode.

How to add Phoenix OS+persistence to E2B

Here is how to add Phoenix OS to E2B with an ext2 persistence file (data.img)

New Desktop folder 'Steve' is persistent.

You will need to extract the contents of the downloaded PhoenixInstaller exe file. I used 7Zip on PhoenixOSInstaller-1.0.7-beta.exe.

E2B drive added files:
\phoenix\initrd.img
\phoenix\kernel
\phoenix\data.img
\phoenix\(other files from ISO)
\_ISO\LINUX\Phoenix_Persistent.mnu

 Then you need to use the Phoenix_Persistent.mnu file as below.

# Extract PhoenixInstallerxxxx.exe contents to \phoenix folder on E2B drive
# Use RMPrepUSB to create ext2 or ext3 data.img file and move to \phoenix\data.img
# Copy this .mnu file to any E2B menu folder (e.g. \_ISO\LINUX)
# file/folder names are case-sensitive!
# On first boot - 'system initializing, please wait...'

title Phoenix OS with persistence\n Boot to android Phoenix OS
kernel /phoenix/kernel root=/dev/ram0 androidboot.hardware=android_x86  DATA=/phoenix vga=788 SRC=/phoenix quiet
initrd /phoenix/initrd.img
boot

Create a data.img file using RMPrepUSB and move it to the \phoenix folder.
Note that paths are case sensitive.

If the data.img file becomes corrupted, Phoenix OS may not boot until you delete or remake it.

Alternative (image a flash drive)

1. Use the PhoenixOSInstaller (e.g. PhoenixOSInstaller-v3.6.1.564-x64.exe) and make a bootable USB flash drive (FAT32 partition is required by the installer).
2. Drag-and-drop the Flash drive letter icon (e.g. D:) onto the MPI_FAT32 Desktop icon (MPI Tool Kit)
3. The suggested size can be used which should be approx. 4GB. I used Syslinux 5 and AUTO-convert (defaults).
4. Name the file as .imgPTN23 so it can be used with E2B+agFM. Persistence should work and well as UEFI64 booting (UEFI32 untested). Note: It does not seem to UEFI-boot under VirtualBox but does on a real system.

All in One System Rescue ISO (Paul Vreeland)

Paul Vreeland has made available his 682MB Rescue ISO for all to use.

The LiveCD part is based on Ubuntu 64-bit and so is not suitable for 32-bit systems. It contains a few useful utilities (all legal to use by businesses), but the most useful part appears to be the Windows utilities that are within the ISO.

You can use the ISO directly in E2B (e.g. name it .iso64 so you don't try to use it on 32-bit systems), or make a .imgPTN64 file from it with the MPI ToolKit for 64-bit MBR and UEFI-booting.
The most useful part comes if you can mount the ISO in Windows (or switch to an .imgPTN image containing the ISO contents) and then you can run AiO-SRT.exe to start the GUI. This means you will often need to download and install the utilities onto the same Windows system that you are trying to fix.

     The AIO System Rescue utility changes the Windows Desktop background and runs a GUI.

See here for a list of utilities. An internet connection seems required for many of the utilities. Some apps require .Net to be downloaded and installed. Many of the buttons just lead to a website where you need to download and install the application onto the system (if it is not too infected!).

He has plans for a Lite version with 100% scripted automated task too (and hopefully a 32-bit LiveCD version?).

P.S. Use the torrent link for a download if possible and don't forget to donate to his site!

Happy Birthday to E2B!

According to the E2B Version History page here, after many Beta versions, E2B v1.00 was finally released to the world on 2013-06-18, so that means that E2B is 3 today - so Happy Birthday E2B!

Yes, believe it or not, the idea for developing Easy2Boot first started on the reboot.pro forum over three years ago! If you are really interested (or suffer from insomnia or are just plain nosey), you can study the progress of the various E2B Betas and how Sambul61, cdob, Scooby, Wonko the Sane, Rootman, DanialCollinet, halikus, libranco, h3xl3y and many others, contributed to it's development here.



Warning: Old joke alert!


A small boy was walking with his parents in London, just as an old man was being released through the main prison gates of Wormwood Scrubs, having just finished an 18 year(!) sentence. The old 'lag' was naturally exuberant and he ran up to the family shouting 'HURRAY, HURRAY, I'M FREE, I'M FREE', to which the small boy replied 'So what mister, I'm four!'.






Family story #1 (true story)!
Many years ago in the early 60's, when they were a young married couple with two small boys, my parents ran two supermarkets, two post-offices, two off-licences, a taxi service and a grocery delivery service. They worked really hard, 18 hours a day, every day. Every day that is, except for Sundays, when they had a well-deserved 'lie-in' in the morning. 

So my younger brother and I knew that hung on my parent's firmly-shut bedroom door every Sunday morning, was a large but invisible sign that said 'Do not disturb - on pain of death!'.

My brother and I generally got on quite well with each other, but early this one particular Sunday morning when our parents were 'resting', we got into an argument in our bedroom, which led to a loud shouting match, and then soon afterwards, to actual fisticuffs!

On hearing this unholy racket, my father was forced to leave my mother in their matrimonial bed and attend to the matter. He stormed into our bedroom and grabbed us both, gripping the back of our small necks tightly in each of his huge hands. My brother and I could tell from his expression that he was not at all pleased at being 'disturbed' and that we were probably going to get a good walloping, very soon!
My father turned to me and asked me angrily 'What do you think you're doing?', and I replied...'fighting'.

He then turned to my younger brother and said to him even more angrily, 'and what do you think you are doing?'
My brother looked up at my father and replied tentatively, 'Helping him?'.

There was a pause... I could hear my mother giggling from their bedroom across the landing. My father's mouth almost broke into a smile and we escaped a spanking that morning - thanks to my little brother!

Family story #2 (true story)!
Our family house has an all-glass and PVC steel conservatory (i.e. no brick walls) and we had just adopted a lovely little black kitten named Jemima, which was currently using a litter tray in the corner of the conservatory to perform her somewhat smelly ablutions.
I turned to my father and said 'Hey Dad, how can we make a cat flap in a glass conservatory?'
He looked up at me, and with a twinkle in his eye replied, 'Easy son, just kick it up the ass!'.
Well, it was funny at the time...

Cracking BIOS passwords (Dell, HP, Fujitsu, Compaq, Insyde, Phoenix, Sony, Samsung)

Many old BIOSes have a preset but secret backdoor password.

But I happened to stumble across this page today.

It describes how to crack the BIOS password on those systems which print a code if you enter the wrong password too many times. It also offers a range of Windows executables (.exe files) for each model which can translate that code into the original BIOS password!

Fujitsu-Siemens BIOS pwd cracker

From the user comments, it appears to work for many systems (I have not tried it 'for real' myself).

This seems like a useful addition to a Techies toolkit (the exe files need .NET and a Windows OS), especially if the customer has forgotten their BIOS password and you need to change the settings.

There is also a simple 'unlocker' web page here which contains the same code but for all types of system (obviously needs internet access and a browser).

Another useful web page (with unlocker script which doesn't seem to work for me?) is here.

Install OpenBSD from Easy2Boot

You can download and install OpenBSD by adding the cd59.iso network install ISO to E2B.

OpenBSD 59 Desktop

However, if you want to use the non-network installer, install59.iso, you will find that OpenBSD installer script/wizard will not be able to find the installation files (which are, of course, hidden inside the ISO).