Monday 21 April 2014

E2B v1.34 and MPI Tool Pack 0.020 now available

E2B v1.34 has a small change to the menu when booting .imgPTN files. It now performs more checks to avoid corrupting the E2B drive and shows what EFI boot files are present in the image. It also now uses Sector LBA30 as the main backup sector (with LBA60 as the reserve sector). This is in case the drive has been formatted with 32 sectors per track. Potentially the directory entries of a FAT32 32-SPT drive could have been overwritten when a .imgPTN file was used in E2B v1.33. Please upgrade to E2B 1.34. There have also been a few cosmetic and text changes and a new \_ISO\WIN folder is now available (it is a Sub-Menu just like \_ISO\ANTIVIRUS and others). If you wish, you can place your Windows .imgPTN fies in the \_ISO\WIN folder and they will be listed in a 'Windows Menu' sub-menu.
To update, just overwrite any E2B USB drive with the non-DPMS version (even if your E2B is the DPMS version).

MPI Tool Pack v0.020 has quite a few changes and improvements.

  • Add size of users CUSTOM  folder to image size calculation
  • Add size of .\csm folder to size calculation
  • Bugfix  - if xcopy fails when copying CUSTOM files now fixed
  • Syslinux 6 added
  • Now updates chain.c32 if present
  • Patch for Ubuntu MBR boot menu added
  • unifont character set loaded for non-ASCII character support in menu.lst
  • menu.lst is in UDF-8 format
  • RestoreE2B and RestoreMBR batch files have been modified
  • menu.lst now checks LBA30 and LBA60 and LBA1
  • bugfix to make syslinux 5 and 6 work (needs to have linux type / in paths!)

Please remake and test all images with these new versions.

I think this version should work and is almost ready for full 'Release' status (famous last words!).

Please contact me if anything does NOT work as expected. The password to unzip the MPI Tool Pack is beta1 as usual.

P.S. To test UEFI booting, clonezilla-live-2.2.2-37-i686-pae.iso has both 32-bit (for non-64-bit UEFI systems) and 64-bit EFI boot files, as well as the normal MBR boot files - the .imgPTN file will boot in all 3 modes.


Saturday 19 April 2014

MPI Pack v0.018 is now available

A few small bugs fixed, menu.lst tweaked to make it easier for people to modify themselves. A few filenames have changed.

Please let me know if you tried this latest version and what you have tried it on.

cheers
Steve

Friday 18 April 2014

MPI Update pack 0.016/0.017 now available

Some more tweaks for using a USB drive as the payload source and also for using your own custom menu.lst file (which you should put in the CUSTOM folder).

0.016 had a minor bug where is listed all the modified menus on the screen, please use 0.017 or later.

By adding your own menu.lst and background file, etc. in the CUSTOM folder, you can change the look of the CSM Menu. Just make sure to use the csm\menu.lst file as a template. When you update MPI, you will not overwrite any of your files in the CUSTOM folder.

I have now made new images of different USB Flash pens that were made using the following programs
  • YUMI
  • PenDriveLinux Universal USB Installer
  • XBOOT (make using Syslinux and use the 'Replace menu.lst' option when asked)
  • SARDU
  • WinSetupFromUSB (use the 'Combine menu.lst' option when asked)
  • LiveUSBCreator (with persistence)
  • Rufus

These images all seem to work OK.

So now on my E2B USB Hard Disk, I can boot from almost any ISO or any image I like and, if supported, in UEFI mode too!


There are 10 types of people in the world the other 8 aren't programmers...

Wednesday 16 April 2014

MPI Update pack v0.012 had a large bug (current pack= 0.015b @ 2014-04-17)!

Please use download the latest version and remake any .imgPTN files that you made with 0.012.
Sorry!

MakePartImage Update Pack 0.012/0.013 available (Note: BUG in 0.012! Please use version 0.013 or later!)

Note: sorry, I introduced a bug at the last minute before uploading this version - linux string replacement was skipped! Please re-make any linux .imgPTN files with version 0.013 or later and they should boot in MBR mode!

I have tweaked MPI to work with more linux ISOs. The following all now work booting in MBR boot mode as .imgPTN files.

  • trinity-rescue-kit.3.4-build-372.iso
  • PandaSafeCD.iso
  • precise-5.7.1.iso
  • Porteus-XFCE-v3.0rc2-i486.iso
  • antergos-2013.11.17-i686.iso
  • liberte-2012.3.iso (requires WinRAR or PowerISO)
  • manjaro-xfce-0.8.9-i686.iso
  • grml64-small_2014.03.iso
  • justbrowsing_20140409.iso

Let me know if you find one that doesn't boot in MBR or UEFI mode (if it supports EFI booting).

Full list of tested .imgPTN payloads here (scroll down to bottom of page).

MakePartImage Update Pack v 0.011 available

I have been unable to find an extraction program that works for all ISOs that is free, unlimited and distributable. MPI v 0.011 uses 7Zip by default, but if that fails, it uses the user-installed version of either WinRAR or PowerIso if present).

Thanks for the suggestions for alternatives, I have checked 26 of them so far and none fit the bill. They are either not free or are limited Trialware, don't extract UDF ISOs correctly, cannot be legally distributed or don't accept command line parameters.

The other change is that there is now a CUSTOM folder. Any files you place in this folder will get copied to any .imgPTN file that you create. This allows you to customise each image.
For instance, you can modify the menu.lst file and create a new background for the CSM menu and place the new files in the CUSTOM folder. This will overwrite the files used by MPI.
You could also add any utilities, etc. to the CUSTOM folder (or make a subfolder) so that every image would contain your utilities.

This means I can release new updates which can overwrite your existing folder, but it won't overwrite your files in the CUSTOM folder.

P.S. The only one which did seem to extract ISOs correctly was: ISO Workshop (free but no command line support yet for extraction). Notably, Windows 8.1 Explorer, 7Zip and WinRAR all fail to show the correct contents with some ISO file formats!
A good test is to try extracting the antergos-2013.11.17-i686.iso file. It should work and not be in all uppercase (one of the files in \arch\boot is in mixed case).  PowerISO (trial), WinZip(trial) WinISO(trial) and UltraISO(trial) failed with this one. PeaZip and 7Zip shows lowercase files but these fail on UDF ISOs. ISO Workshop also shows lowercase files and mixed-case files.

P.S. Do you sometimes use YUMI, XBoot,  LiveUSBCreator, PenDriveLinux, SARDU, Rufus, WinSetupFromUSB, etc. Well why not add all of your USB drives to one large E2B drive! Just make an .imgPTN file from each USB stick and then add the files to E2B. Just make sure to use the E2B CSM menu.lst file (or choose the Combine option if prompted).

Tuesday 15 April 2014

All I want to do is extract files from an ISO!

During testing of MakePartImage, I found that 7Zip did not extract a few of them correctly.
I had an ISO which I made of my Win7 Install DVD using MagicISO.
If I viewed or extracted the contents  in 7Zip or PeaZip, I get

README.TXT
Bootable_NoEmulation.img

or

README.TXT
[BOOT]


The ReadMe.txt says that the file is in UDF format,
This disc contains a "UDF" file system and requires an operating system
that supports the ISO-13346 "UDF" file system specification.

Both WinRAR and Windows 8.1 Explorer can view the correct contents, so why can't 7Zip and PeaZip?

So, I changed MakePartImage to use WinRAR. Then I discovered two things:

1. WinRAR had faults extracting some linux ISOs, it converted all the filenames into uppercase and also converted hyphens and multiple dots in filenames ( - and .) incorrectly into underscores! e.g. extracting from antergos-2013.11.17-i686.iso. WinZip also did the same thing on this ISO. Windows Explorer also shows all uppercase names.

2. WinRaR is not freeware, so I can't add it to my download and distribute it!

I tried a few other free unzip utilities that supported a command line, but they also had similar problems.

Who would of thought it is so hard to unzip an ISO reliably in this day and age?

So now I have gone back to using 7Zip, but if it detects a UDF-only ISO that 7Zip cannot handle, I ask the user to download and install WinRAR, so that I can automatically use that to extract the ISO when 7Zip fails.

sheesh!

P.S. ISO Workshop seems to work correctly with all the ISOs, if you need a good ISO extractor - www.glorylogic.com


E2B small update in v1.33


  • There was a small problem when loading .imgPTN files, when it swapped to the new CSM menu inside the image, the menu headings and borders did not display correctly (but were OK if you rebooted). This is fixed in v1.33
  • Also, I have added an autorun.inf file and e2b.ico file so that you can easily see which drive in Explorer is the E2B drive.


The MPI Update Pack continues to improve and the new CSM menu now displays the name of the payload in the menu so you can see what it is going to boot to. The latest pack is v 0.008.


You can change the menu picture by changing the compressed .bmp file in MakePartImage\csm\e2b\CSM_Mode.gz. When you next run MakePartImage, the new bitmap will be used. To change the position and size of the menu and colours, edit the MakePartImage\csm\menu.lst file.
The easiest way to experiment is to switch your E2B drive to one of your .imgPTN images and then edit the files directly on the drive via Windows and test it by booting using VBox. When it is all looking nice, copy the menu.lst and CSM_Mode.gz files to your MakePartImage folder.

If you already have an E2B USB drive with a previous DPMS version of E2B on it, just download the non-DPMS version and extract it to your E2B USB drive - there is no need to download the whole DPMS version as the only difference is the driver pack files which haven't changed.



Sunday 13 April 2014

WinSetupFromUSB and E2B compared

I was asked today how WinSetupfromUSB and E2B compare, now that E2B also supports UEFI booting.

WinSetupFromUSB is a very versatile and clever utility that allows you to multiboot Windows installers, WinPE and linux-based ISOs.

For MBR booting of linux ISOs, it now uses the same trick as E2B - it maps the ISO to a partition table entry - this works 99% of the time with nearly all linux ISOs.

For Windows XP OS's however, WinSetupfromUSB extracts the contents of the ISO and places them in separate folders on the USB drive - as well as copying the whole unmodified ISO to the FAT32 USB drive. For XP, this is probably going to be more reliable than E2B's approach of mapping the XP ISO on the USB drive (WinSetupFromUSB uses my modified DPMS2 batch file for auto-generation of the F6 driver floppies). It does however take longer to prepare the USB drive.

For Windows Vista/7/8 Install ISOs, WinSetupFromUSB extracts the contents to make a boot.wim file,  and then modifies the boot files and also the BCD, and uses bootmgr to give the user the choice of which one to load. Once the boot.wim loads, ImDisk is used to mount the original ISO file as a virtual DVD. The advantage of this is that if you are running from a USB Hard disk, you don't need another USB Helper Flash drive like you did with E2B. However, with the new v1.32 of E2B, you can make a .imgPTN file from each Windows Install ISO. This now allows you to boot a Windows Install (or any WinPE) from a Hard disk without needing a USB 'Helper' Flash drive (as a FAT32 image, it will even boot in UEFI mode - as an NTFS image, you can only boot in MBR mode but it will support files > 4GB).

With regards to UEFI booting, WinSetupFromUSB needs to be on a single-partition FAT32 USB disk. However, it can only multi-boot Windows-based OS's in UEFI mode, because it uses bootmgr and a BCD entry for UEFI booting - E2B does not rely on bootmgr and so can boot virtually any FAT32 image.

Here is a feature comparison between WinSetupFromUSB v1.4 (WSFUSB) and E2B v1.32+:
  • WSFUSB will probably be more successful when installing XP onto a wider range of different systems than E2B
  • WSFUSB XP installs only require one boot to the USB drive
  • WSFUSB is more flexible with XP installs (in some ways) than E2B
  • E2B can use the latest XP mass-storage driver packs (though WSFUSB will probably catch up soon!)
  • E2B supports a range of user-selectable winnt.SIF files and unattend files for the same XP ISO
  • E2B supports a range of user-selectable product key and unattend file installations from the same ISO
  • You cannot easily remove 'payloads' from a WSFUSB drive
  • Making a WSFUSB drive and adding payloads can take a lot longer time than making an E2B USB drive which is just drag-and-drop.
  • E2B supports linux booting in UEFI mode (or anything that can UEFI-boot as FAT32) whereas WSFUSB doesn't
  • An NTFS-formatted E2B drive can boot ordinary (<4GB) Windows Install images and linux images via UEFI. With WSFUSB, if you want Windows UEFI booting, the whole USB drive has got to be a single FAT32 format volume and the ISO must be less than 4GB in size.
  • FAT32 is more compatible for some things (like Hirens boot CDs) than NTFS. A FAT32-formatted E2B drive can still boot large Windows Installs by using an NTFS partition image. But with a FAT32 WSFUSB USB drive you cannot have large Windows install files
  • E2B can support multiple different Hirens (or other) FAT32 images on an E2B NTFS USB drive.
  • You can have multiple partitions on an E2B drive (FAT32 or NTFS) and can still UEFI boot -WSFUSB must have only a single (FAT32) partition.
  • E2B supports multiple linux ISOs, each with their own persistence file.
  • WSFUSB is faster to boot to the USB menu than E2B (although E2B can be speeded up a lot using a pre-cached menu)
  • You can make a USB Flash drive using WSFUSB and then make an image of it and add it to your E2B USB drive. Thus you can use WSFUSB from within E2B and use all the other E2B features too.
  • E2B can also use a grub2 menu and can UEFI-boot to many linux ISO files (even if they don't officially support UEFI-booting!)
  • E2B can be set up to automatically install Windows 7/8/10 using an unattend.XML file and install drivers + applications + Windows updates automatically using the SD_CHOCO feature (v1.82+).

 (please correct me if I am wrong on any point or have missed a key feature - I am not very familiar with WSFUSB!).

So, there is no clear winner - it's 'horses-for-courses' really, why not use both!


Easy2Boot v1.32 Released

v1.32 2014-04-13
  • XP install enhancements (new chkpci utiity, win2k,2k3 driver support)
  • XP ISOs can use a .SIF file for unattended installs, etc.
  • .imgPTN recognised for UEFI image booting. 
  • USB 'Helper' Flash drive no longer required for USB HDDs (if .imgPTN used)
  • List PCI IDs changed to use grub4dos utility (no reboot required)
  • Utilities menu has XP driver search menu entries.
If you prepare a partition image using MakePartImage (download the MPI_Update_Pack), then you can reboot to a single-partition. This allows you to add to your E2B drive linux and Windows Installs in UEFI mode. You can also install Windows from an NTFS E2B USB HDD without needing a Helper Flash drive.
The Update Pack is still in Beta and password protected - please email me for the pwd.