Friday, 12 September 2014

Bug in E2B 1.55 & 1.56beta (XP installs)

E2B v1.55 uses a version of grub4dos which has a bug. If you try to install XP from an ISO using DPMS, then XP Setup complains that it cannot detect any disks! This bug appears to start in grldr 2014-08-19 and later versions but is not in 2014-08-17 and earlier versions. I have reported this to chenall and hopefully he can find the problem.  If you have a later version, you can replace the \grdlr file with the 2014-08-17 version of 0.4.5c from http://grub4dos.chenall.net/categories/downloads/.

Note: As of 2014-09-19 I am still having weird issues with grub4dos later versions (e.g. losing USB drive, not enumerating all items, hanging)


Thursday, 11 September 2014

Bug in E2B v1.56 (in grub4dos)

It seems something is broken in the new version of grub4dos!
If using XP Install and DPMS, you will get a FAT disk I/O error.
I have withdrawn v1.56 until chenall can fix grub4dos.
You can replace \grldr with the 2014-08-17 version if you like, but E2B v1.56 will complain about it being too old.

Wednesday, 10 September 2014

E2B v1.56 released

PLEASE NOTE: Discovered a bug in the new grub4dos version! I have withdrawn v1.56 until a grub4dos is fixed! Please use v1.55 for now.

Changes in 1.56
  • New grub4dos \grldr (20140908) fixes exFAT bug with >4GB files + other small bugs
  • CPU 32/64 bit & Total memory displayed in Main Menu heading and Windows Install menu
  • New Sample mnu Files examples. 
  • Weird characters such as ()!''&| may now work if used in Windows ISO and .imgPTN filenames.
  • 'Boot any key to boot from CD or DVD' Windows install prompt suppressed. 
  • Default Aurora background compressed using lzma (reduced size). 
  • .iso64 family of file extensions recognised (only listed if 64-bit CPU). 
  • Fastload menu has changed (only seen if FASTLOAD is enabled) - now press F8 to refresh the menu instead of the separate REFRESH entry. 
  • Change Automn.g4b and Automn.g4b to use 56MB area of memory instead of 74MB area so can use E2B on systems with 64MB of memory or more.
Let me know if you spot any problems. The F1.cfg Help menu is in English in all languages and also some of the new text in STRINGS.txt (see end of file). Any translations welcome!

Monday, 8 September 2014

Easy2Boot v1.56Beta10 now available for testing

E2B v1.56 Beta10 is now available in the Alternate Download area on the Easy2Boot Download page here. I consider this to be a Release Candidate and will release it as the official v1.56 soon unless anyone spots any bugs. It uses the latest versions of grub4dos which have several new minor bug fixes thanks to Chenall. The E2B version history is here.

To update your E2B drive, just extract all files from the zip file directly onto your E2B USB drive (even if you have the DPMS version on your E2B USB drive, it will still be updated correctly).

P.S. I have updated RMPrepUSB to include the same new version of grub4dos too. Download from here.

Saturday, 6 September 2014

How to make your own linux ISO .mnu files

I was asked today about LXLE with persistence. This distro is based on Lubuntu and the user wanted to get persistence working. There was a lubuntu-13.04-desktop-i386_Persistent.mnu menu available but not one for LXLE.

I thought I would describe how I went about changing this lubuntu-13.04-desktop-i386_Persistent.mnu file to get it working with LXLE.

  • First I copied the lubuntu-13.04-desktop-i386_Persistent.mnu file and the lxle ISO file to the \_ISO\MAINMENU\MNU folder of my E2B NTFS USB drive which I use for testing.
  • Next, I renamed the file to lxle-1404-x64_Persistent.mnu.
  • Next, I edited the .mnu file in Notepad to change all occurrences of the  lubuntu-13.04-desktop-i386.iso file to lxle-1404-x64.iso.
  • Next, I changed all occurrences of the persistent file lubuntu-rw to lxle-rw
  • Finally, I made a persistent ext2 file in the root of the E2B USB drive using RMPartUSB's - Create ext2 FS button. When prompted I used:
               File Name = lxle-rw
               Volume Name = casper-rw
               Size = 500
  • I then ran WinContig on the drive (RMPrepUSB - Ctrl+F2).

Unfortunately, I got an error when I tried to boot from the menu entry in E2B


This indicated that the file \casper\initrd.lz was not actually present inside the .iso file.

Looking inside the ISO file using 7Zip to view it, I found:


Normally, in a linux ISO that uses isolinux to boot, there is an isolinux folder which holds several .cfg files, the main one being isolinux.cfg. If grub is used, there may be a \grub folder containing config files. If grub4dos is used, it may have a \menu.lst file and other .lst files.

I double-clicked isolinux.cfg to open it up in Notepad ++ (if you try to use Windows NotePad, it will merge all the lines together due to a CR/LF problem - see below).

The isolinux.cfg main LiveCD menu entry seems to be:

label live
  menu label live - boot the Live System
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/custom.seed boot=casper initrd=/casper/initrd.gz quiet splash --

So I converted this to grub4dos as follows:

kernel /casper/vmlinuz file=/cdrom/preseed/custom.seed boot=casper persistent quiet splash --
initrd /casper/initrd.gz 

As you can see, we just need to re-arrange a few things. The reason for the error is now apparent, because the file used for the initial ramdrive (initrd) is initrd.gz and not initrd.lz as it was in the Lubuntu .mnu file.

Warning: Do NOT copy and paste whole lines from a linux .cfg file into a grub4dos .mnu file. The carriage-return/line-feed end-of line characters are not the same in a linux file and although it may look OK in NotePad, it won't work in grub4dos due to embedded invisible CR/LF characters! It is better to type them in manually rather than copy and paste in lines from a linux text file!

We need to add in the 'persistent' parameter so that it will look for a casper-rw volume when it boots.

In the end, after tidying up the .mnu file a bit to make it easier to modify for the end user, we have:

# Make a ext2 file using latest version of RMPrepUSB in the root of the drive 
# File Name=lxle-rw  Volume Name=casper-rw
# Place this .mnu file and the ISO in either \_ISO\MainMenu\MNU or \_ISO\Linux\MNU
# This menu will work even on an NTFS USB boot drive
# IMPORTANT: you MUST run WinContig (Ctrl+F2) before booting E2B.
# e.g.
#\lxle-rw
#\_ISO\MAINMENU\MNU\lxle-1404-64.iso
#\_ISO\MAINMENU\MNU\lxle-1404-64_Persistent.mnu


iftitle [if exist $HOME$/lxle-1404-64.iso] LXLE 14.04\n Boot using .mnu file with persistence

set ISO=$HOME$/lxle-1404-64.iso
set PER=/lxle-rw

if exist CD echo WARNING: Cannot use partnew command! && pause && configfile (bd)/menu.lst
if "%E2BDEV%"=="" set E2BDEV=hd0 && pause E2BDEV forced to hd0!
#enable parttype output
debug 1
# make empty table entry in 3rd position in ptn table
parttype (%E2BDEV%,2) | set check=
debug off
set check=%check:~-5,4%
if "%check%"=="0x00" partnew (%E2BDEV%,2) 0 0 0
if not "%check%"=="0x00" echo WARNING: PTN TABLE 3 IS ALREADY IN USE - PERSISTENCE MAY NOT WORK! && pause
debug 1
if not exist %PER% echo WARNING: %PER% persistence file not found! && pause
errorcheck off
if "%check%"=="0x00" partnew (%E2BDEV%,2) 0x0 %PER%
errorcheck on
#map ptn 4 to ISO
partnew (%E2BDEV%,3) 0x0 %ISO%
map %ISO% (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz file=/cdrom/preseed/custom.seed boot=casper persistent quiet splash --
initrd /casper/initrd.gz 


This .mnu file will be in the Sample mnu Files folder in the next E2B 1.56Beta download and is also in the Alternate Download area now (though it may be removed later when 1.56 is released).




Friday, 5 September 2014

E2B v1.56Beta9 available

Stephan has emailed me with some suggestions on improving E2B when using FASTLOAD.

As you may know, if you enable FASTLOAD by simply copying the \_ISO\FASTLOAD.YES file to the root of your E2B USB drive, it causes the Main Menu to be cached the first time you boot to E2B. The next time you boot to E2B, it will not need to enumerate all the files in the \_ISO\MAINMENU folder + sub-folders, but will just load the cached menu that was made during the previous boot. This can speed up the appearance of the E2B Main Menu if you have a slow USB drive and lots of files in your \_ISO\MAINMENU folder.

The main changes affect the following files:

\_ISO\e2b\grub\MENU.lst  - small changes to improve messages and set STALE variable
\_ISO\e2b\grub\E2B.cfg  - small text changes
\_ISO\e2b\grub\ENG\STRINGS.txt - new strings $$STRmFS1, $$STRhMFD and $$STRhMFE
\_ISO\MAINMENU\ZZZF8ReloadMenu.mnu - modified to also refresh the cached FASTLOAD menu
\_ISO\MAINMENU\ZZA_FASTLOAD_ON_OFF.mnu - If FASTLOAD is active, this new menu entry will allow the user to enable or disable it. This menu entry can be suppressed using set NOFLDMNU=1 in your \_ISO\MyE2B.cfg file
\_ISO\MAINMENU\ZZZF8$_SHOW_FASTLOAD.mnu - new file to display a non-operational menu entry just above the F8 menu entry which shows the user that they are using a cached (old) menu.

You can, of course, delete any of these .mnu files and/or make a new version to modify their action or appearance (just don't use the same filename as E2B uses or they will be overwritten the next time you update!). You can also make your own STRINGS.txt file to modify the menu entry text.

The new Enable\Disable FASTLOAD menu entry can be suppressed by using the NOFLDMNU variable in your \_ISO\MyE2B.cfg file if you don't want the user to be able to disable it. Alternatively, you can just delete the ZZA_FASTLOAD_ON_OFF.mnu file.

If the \FASTLOAD.YES file is not present, then the Main menu will appear just as it did before.
If the \FASTLOAD.YES file is present, then you will see the Main menu below:

FASTLOAD ENABLED - Menu was loaded from cache on booting.
Note the 'CACHED MENU (FASTLOAD)' warning is displayed in the menu.

FASTLOAD ENABLED - Menu was just Refreshed by user using F8.

FASTLOAD DISABLED - it can be enabled again by the user with '3 Enable FASTLOAD'.

Let me know if you like this new arrangement or not.

I am still waiting for a few more bugfixes in grub4dos before I release v1.56. Chenall is working hard on the fixes and it should be done in a day or so.

Thursday, 4 September 2014

Tiny PXE Server tryout

I had seen Erwans Tiny PXE Server app but tonight I decided to try it out.

I wanted to just boot a WinPE ISO file via PXE as I thought this would be the easiest to get going.

Documentation for getting started is not that well organised on reboot.pro or in his Blog.
I eventually found a Blog post here for booting PE.

Here are step-by-step instructions for how I did it:

1. On My Windows 8.1 x64 PC, I downloaded Tiny PXE Server from reboot.pro (check the download link in this post)

2. I extracted the files to C:\temp\pxesrv on my Windows system

3. I copied a WinPE_x86.ISO file that I had lying around to the C:\temp\pxesrv\files folder.

4. I used NotePad to create a winpe.ipxe text file in the C:\temp\pxesrv\files folder as below:

#!ipxe
dhcp net0
set boot-url http://${dhcp-server}
initrd ${boot-url}/images/WinPE_x86.ISO
kernel ${boot-url}/memdisk iso raw
boot

5. Next I ran the C:\temp\pxesrv\pxesrv.exe file and changed a few settings as show in the red boxes below:


Note that I needed to choose a DHCP server address of 192.168.1.xx to match the subnet address of the router.
The Extra Option also needed to be set to 175.6.1.1.1.8.1.1  -> vendor option is 175.6.1.1.1.8.1.1 (etherboot length 6 code 1 length 1 value 1 code 8 length 1 value 1). More details here http://www.etherboot.org/wiki/dhcpd

When you are happy with the settings - click the Online button.

6. Finally, I connected an Ethernet cable from my router to my EeePC 904HA netbook, switched it on and selected 'Network Boot' from the BIOS Boot menu.. VIOLA! - it started to load the ISO into memory and then booted to it! The EeePC now runs WinFE via PXE boot.

I have not yet experimented any further with Tiny PXE Server, but so far it looks encouraging!

Erwan has more examples on his Blog here and some quick HowTo's are here for different payloads.


Tuesday, 2 September 2014

PassPass for Win8.1 (32-bit and 64-bit)

Add PassPass to your E2B USB drive and get access to any Windows system without needing to know the user account password!

I fixed the issue with 32-bit 8.1 and now the PassPass20140902SS.zip version 1.5 should patch XP -> Win8.1. Not tested on Win8.1 Update (but dll for 64-bit looks same as Win8.1 so hopefully will work).
I suggest you test on a 'test' system and not your work/office/home system (or at least make a backup first!).

Note: Latest version (same filename!) is listed in the E2B menu as (PassPass E2B v1.5) - if yours does not say this please download latest version. The E2B PassPass download  PassPass20140902SS.zip is available in the Alternate Download areas from this page.

Monday, 1 September 2014

PassPass update for Win 8.1

I have tried to update the clever PassPass grub4dos utility written by Holmes.Sherlock and Wonko the Sane from reboot.pro. It should now work for XP through to Windows 8.1.

Note: Latest version will be listed in the E2B menu as (PassPass E2B v1.5) - if yours does not say this please download latest version.

This utility allows you to bypass the Windows user password required for logging into a user account on Windows. It works by hard-patching a Windows dll file before you boot to Windows. Once you have finished with the Windows system, you can Unpatch or restore the dll so that normal password function is restored.

For more details on PassPass, see here.  For Win 8/8.1, it allows you to gain access without using the user's account password, PIN number or picture gestures.

When you unzip the E2B PassPass version, there will be a UTILITY folder. Copy the folder to your E2B USB drive  (e.g. to \_ISO\MAINMENU\UTILITY or \_ISO\UTILITIES\UTILITY). Then move the large PassPass.bak file to the root of the E2B USB drive - for example:

\_ISO\MAINMENU\UTILITY\PassPass.mnu
\_ISO\MAINMENU\UTILITY\PPass.g4b
\_ISO\MAINMENU\UTILITY\wenv
\PassPass.bak

As this version is experimental, I would advise you to test it first on a 'test' system and NOT on a system that you need (or at least take a full backup first). The file \Windows\system32\msv1_0.dll is the only Windows file altered by PassPass.

Download
Look up PassPass in the 'List of tested payload files' page - item 101 for the E2B PassPass download.

PassPass menu entry

PassPass will detect all Windows installations on all disks
Choose which one you want to patch.

You can backup the msv1_0.dll file first before you patch it.
Then run the Patch Windows menu option.

You will be told how many patch areas have been identified.
Press ENTER to patch the dll and then choose the Boot from Internal Hdd menu option
to boot to the patched OS (or reboot the system).

P.S. If you try PassPass and it worked, please tick the 'funny' box below. If it failed, please add a comment and give details of the msv1_0.dll file in your version of Windows (click on Properties).

Sunday, 31 August 2014

E2B v1.56 now recognises .iso64 file extensions

E2B v1.56 Beta6 and later versions will now recognise the .iso64xxxxx file extension and will only list the ISO in the menu if the system contains a 64-bit CPU.

This means that if you boot from a 32-bit CPU, you will not see the menu entries for any 64-bit ISOs if you simply use a .iso64 file extension for them.

Note that this does NOT apply to ISOs under the \_ISO\WINDOWS folder (the Windows Installler ISOs) - for these you must use the .ISO file extension.


Most of the .iso family are supported - e.g. .iso64, .iso64PE, .iso64PE01, .iso64mem, .iso64win, .iso64linux, .iso64grub, .iso64force, .iso6401, .iso64dd, .iso64gz, .iso64e0, .iso64meme0,  .iso64pup and .iso64WB.

You can prevent all the file extensions from being listed in the menus by using  set EXTOFF=1  in your \_ISO\MyE2B.cfg file.

Note: If your menu uses FASTLOAD, you do not need to Refresh the menu when you boot on a different 32/64 bit system. The menu will test for a 32-bit or 64-bit CPU each time it is loaded.



A nice-sounding lady telephoned me yesterday and asked me if  I would like sign up to go on a Meditation Course - I told her I would think about it...

Thursday, 28 August 2014

Adding Unattend.xml files to Windows 7/8 Install UEFI .imgPTN images in E2B

If you want to install Windows Vista/7/8 etc. in MBR\CSM mode, you can just copy the Windows Installer ISO to the correct E2B USB folder, and you can copy over your own Unattend.xml files to the same E2B folder. E2B will then allow you to pick any one of these XML files so that the Windows install uses the correct Product Key (which is required by Win8), or is semi-automated or even full-automated, depending on what is in your Unattend.xml file.

However, if you use MakePartImage to convert the Windows Installer ISO into a partition image (.imgPTN file) so that you can both  UEFI- and MBR\CSM-boot from it, you will not have any of the E2B features to choose your own XML file or automate the install.

I have therefore detailed some instructions here on how to add your own AutoUnattend.xml file to a partition image .imgPTN file.

If you are using an E2B Removable type of USB Flash drive, then you just need to copy the AutoUnattend.xml file to the root of the image. However, if your E2B USB drive is a Hard disk or 'Fixed disk' type, then this will not work because Windows only auto-detects a \AutoUnattend.xml file on removable media like Flash drives, floppy disks (remember those?) or DVDs.

Instead we need to tweak the files inside the \sources\boot.wim file.

If you follow the instructions, you can even offer the user a choice of XML files to use before Windows Setup runs.


Wednesday, 27 August 2014

Detect a 64-bit or 32-bit CPU in Easy2Boot

We can use grub4dos to detect the CPU bitness using the is64bit command.
E2B v1.56 Main  menu heading shows CPU type and total usable system memory

We can use this to make a .mnu file for the MAINMENU folder:



$$$CPU_TYPE.mnu
===============
# Display as menu item if CPU is 32-bit or 64-bit

iftitle [checkrange 2,3 is64bit]   --- INFORMATION: 64-bit CPU ---
errorcheck off


iftitle [checkrange 0,1 is64bit]   --- INFORMATION: 32-bit CPU ---
errorcheck off


To make a menu entry that will allow the user to check it use:

title Check the Processor\n Detect if CPU is 32-bit or 64-bit
checkrange 2,3 is64bit && pause Processor is 64-bit
checkrange 0,1 is64bit && pause Processor is 32-bit
errorcheck off
boot

The 64Bit_Auto_Detect_ISO.mnu file in the E2B Sample mnu folder has an example where either a 32-bit or 64-bit ISO will be automatically run depending on the system CPU:

# Change the 1st, 2nd and 3rd line as required - line 4 may be deleted if no pause required

title Run a 32-bit or 64-bit linux ISO \n Auto-Detect system type and run correct ISO
set ISO=Ubuntu32.iso
checkrange 2,3 is64bit && set ISO=Ubuntu64.iso
pause WILL BOOT %ISO% - Press ENTER key to continue...
/%grub%/qrun.g4b $HOME$/%ISO%
boot

To make a .mnu file for a 64-bit ISO that will only be visible if the system has a 64-bit CPU, we can use:

iftitle [if exist $HOME$/Ubuntu64.iso && checkrange 2,3 is64bit] Ubuntu 64-bit \n Boot from a 64-bit ISO
/%grub%/qrun.g4b $HOME$/Ubuntu64.iso
boot

Monday, 25 August 2014

E2B v1.56 Beta available

A number of people have hit the problem of using Windows Install ISOs which have non-standard characters in the ISO filename, such as ( and ) and ! and & etc. This caused a problem with some of the Windows .cmd scripts which are automatically run when Windows\WinPE boots.

I have attempted to fix this now in v1.56Beta, so you can have names like:

Windows 8.1 32-bit & 64-bit (English).iso

also, I have found a way to suppress the 'Press any key to boot from CD or DVD' prompt which you may see when you boot from some Windows ISOs. This message is caused by the \boot\bootfix.bin file inside the ISO file. If the bootfix.bin file is not present then the code inside it which prompts you to press a key is not run. I found a neat way to prevent this from being run - see here for details.

Please let me know if you find any issues with this Beta version.

Sunday, 24 August 2014

Easy2Boot v1.55 released (at last!)

Quite a few changes in version 1.55, thanks to many others for ideas, improvements, language files and bug reports!

E2B v1.55 changes:
  • F1 Help Main menu added (English only). F1.cfg help file can be translated into other languages.
  • \_ISO\e2b\grub\menu.lst code change to work around incompatibility issue between AMI BIOSes and MyDigitalSSD OTG USB drive - grub4dos losing all variables! Affects HP Compaq dx2400 microtower, Asus M4A89GTDPRO-USB3 motherboard, Asus x550ca - all have American MegaTrends BIOS. Exact cause still under investigation.
  • Portuguese language STRINGS.txt added (thanks Carlos).
  • Romanian language STRINGS.txt added (thanks Anto).
  • French language STRINGS.txt added (thanks Nicolas).
  • New \_ISO\docs\mythemes folder added - supports adding a $Change_Theme.mnu menu file to the Main menu. Read the ReadMe.txt file in the folder for more info.
  • .cfg file extension support added - can now switch themes by copying a MyE2B.cfg-style file to a menu folder.
  • \_ISO\docs\Sample E2B Templates folder name changed to Templates due to path length limitations in grub4dos. If updating, you can delete the old Sample E2B Templates folder.
  • Latest grub4dos grldr versions included in E2B (important long-standing NTFS bug fixed in new version). Longer paths allowed for splashimage, etc. see http://grub4dos.chenall.net/categories/downloads/ for details of fixes.
  • EXTOFF variable added for MyE2B.cfg file - if set to 1, file names are listed in the menu without their file extension.
  • Various small changes to Qrun.g4b, English STRINGS.txt and other E2B files.
  • You can change or remove the menu   arrow marker symbol which indicates the highlighted menu entry, using a new grub4dos feature (see Sample_MyE2B.cfg).
  • If you prematurely abort an .imgPTN file selection, the 4th partition is now cleared instead of leaving it switched in.
  • Sample_MyE2B.cfg has sample code to detect host display resolution and choose different wallpapers.
  • linux fmt.sh script revised so works with older bash shells (thanks Todd).
New files added to \_ISO\docs\Sample mnu Files folder:
  • linuxmint-17-mate-32bit-v2_Persistent.mnu - for new versions of Mint
  • Tails_for_USB_HDD_Persistent.mnu - required if running Tails from a USB HDD or if you want persistence
  • Change_Wallpaper.mnu - allows user to change the wallpaper background from a menu entry
  • Change_Language.mnu - menu entry to change E2B language
  • Change_Theme.mnu - menu entry to allow user to select a theme
  • BlueTheme.mnu  - example of how user can select an alternate Theme template
  • Desinfect_2014_Peristent.mnu
  • Desinfect_2014_with_Updates.mnu
  • A_BlankMenuEntrySeparator.mnu - fancy 3-line separator
  • Win_Vista_7_2K8R2_Direct.mnu - for Win install menu entry with preset XML file
  • Win_Win8_2012_Direct.mnu - for Win install menu entry with preset XML file and/or KEY
  • PTN_LOG1_Menu.mnu - If you have an E2B drive with a Logical partition, you can boot from files on that partition with this menu.
As always, let me know if you find any problems - there are many 1000's of happy E2B users who don't have a problem, so if you do find a problem ,it will probably be due to an incompatibility with your particular system or payload file. Many of these sorts of problems can be worked-around or fixed, but only if you let me know using the Contact Me page on the www.easy2boot.com website!

Let me know what you think of the new changes.

 Please tick 'funny' 'interesting' or 'cool' or add a comment to let me know which posts you most enjoy.

Saturday, 23 August 2014

A problem with a wireless mouse and USB 3.0 flash drives was driving me crazy!

If you have read my blog, you may remember that I had built a new system a few months ago - see here.
On the whole I have been very pleased with the system. It is quiet and fast.

The front panel has four USB ports, the top two are USB 2.0 and the bottom two are USB 3.0.
I specifically wanted this Cooler Master N600 case so that I could have convenient access to both types of ports.


The only problem that I have been having for months now was with the Anker Wireless Mouse and dongle that I have fitted to the front panel USB 2.0 port.

Most of the time it worked just great, but I noticed that when I plugged in a USB 3.0 Flash drive into the USB 3.0 port on the front panel, the wireless mouse started to respond in an unreliable and jerky fashion, particularly just after the USB 3.0 Flash drive had been connected. If left it for a few minutes, the wireless mouse response would improve, but it still gave me trouble and still caused me great frustration (and I now humbly apologise for any physical harm that I may have caused to the poor mouse and the abusive comments I may have shouted in moments of anger)!

My first thought was that perhaps the single AA battery in the mouse was getting flat, I found that if I changed it for a new one, the response did seem to improve slightly, however it still wasn't perfect.

As always, as soon as I unplugged the USB 3.0 Flash drive - the mouse responded perfectly!

I tried many different USB drives and found that:

1. The issue only occurred with USB 3.0 Flash drives  (not external USB 3.0 hard disks which, of course, had a short USB 3.0 lead)
2. The issue only occurred when I connected a USB 3.0 flash drive to the USB 3.0 front port - if I connected the same flash drive to the other spare USB 2.0 front port or rear USB 3.0 port - no problem!
3. If I connected a USB 2.0 Flash drive to a front USB 3.0 port there was no problem.
4. There was no difference in behaviour, whether I connected the USB 2.0 wireless dongle to the front USB 3.0 port or to the front USB 2.0 port.
5. If I replaced the wireless dongle with an ordinary wired USB 2.0 mouse it worked fine.
6. The wireless dongle worked in the rear USB ports (but this was inconvenient if I wanted to use the dongle in another system, because I could not easily get access to the rear of the PC to remove it).

Over the last few months, I have tried updating the USB chipset drivers of my Haswell mainboard but to no avail.

Today however, I Googled for 'USB 3.0 wireless mouse jerky' and found this thread.
It said that USB 3.0 signals can cause interference with the 2.4GHz wireless mouse dongle and that I should separate the USB 3.0 flash drive from the USB 2.0 wireless Bluetooth dongle. It cited an Intel PDF on the subject here (esp. see 4.3).

So I got out a spare, well-shielded USB 2.0 extension cable and used it to connect the wireless dongle to the same USB 2.0 front port as before.

           

Fig. 1   Before (mouse was jerky)    - and -     Fig.2  After (works perfectly)!

The result >>>  the wireless mouse now works fine!

Even if I taped the wireless dongle directly on top of the USB 3.0 Flash drive it still worked without any problems!

Another test was to completely wrap the USB 3.0 Flash drive in tin foil and earth the foil to prevent any wireless interference. Again this proved ineffective.

I also tried inserting a 1m USB 3.0 extension cable between the Corsair GT USB 3.0 Flash drive and the front panel USB 3.0 port with the wireless dongle directly plugged into the USB 2.0 port  (i.e. as in Fig.1 but using a USB 3.0 cable to connect the Flash drive). I placed the flash drive directly next to the wireless dongle so it would cause maximum radiated interference - again the mouse worked fine!

So it seems that merely using a USB extension cable fixes the problem - this may be because the RF frequencies in the USB 3 data lines or power lines are being absorbed by the USB cable's ground shield, so that less electrical RF noise get's back to the front panel PCB via the signal/data wires.

So I am not at all convinced that this is a case of wireless interference - more likely, it is a case of poor grounding and isolation on the USB port PCB that is inside the front panel of the case. It may be that a few high-frequency decoupling capacitors sprinkled around the USB port PCB may fix the problem, but I am going to leave that for another day! Getting rid of high-frequency noise such as 2.4GHz is tricky and often a multi-layer PCB with close ground-Vcc planes is the only way - this would mean Cooler Master would need to make a decent multilayer front panel PCB. Better grounding would also help!

Equally, there may be a lack of high-frequency decoupling inside the USB 3.0 Flash drives too (I tried 3 different makes - Corsair Voyager GT 32GB, a Pretec Rex 100 8GB and a Busbi 16GB, the Busbi USB 3.0 Flash drive had a silver 'metalised' case and did not seem to cause quite as much of a problem). The PCBs inside these pen drives are often simple dual-layer PCBs.


So just bear in mind that if you have  USB 3.0 devices  AND wireless devices such as  wireless mouse dongles, bluetooth dongles or WiFi dongles (or perhaps TV tuner dongles) - keep all USB 3.0 devices away from them. If possible, use rear ports for one and front USB ports for the other.

If you are still having problems, try using short, well-shielded USB cables instead of connecting them directly to the system's USB ports.

If they ever start making USB 3.0 versions of wireless dongles - I can see this issue becoming a BIG problem!

Wednesday, 20 August 2014

Easy2Boot v1.55 can display files in the menu without their file extensions

Files in E2B menus are normally displayed by using their full  filename + extension, as below...


You can use a .txt file to define an alternate menu entry for each file.

However, now with v1.55, if you use  set EXTOFF=1 in the \_ISO\MyE2B.cfg file, all files in all menus will be displayed without their file extensions, as shown below...

You can use spaces in the filename if you wish (see #4).

A Beta7 version of 1.55 is available in the Alternate Downloads area as usual.

It is almost ready for release, I am just waiting for one bugfix to grub4dos 0.4.6a from the developers.
E2B v1.55 will complain if the latest version of grub4dos is not used. Although it may work using earlier versions of grub4dos, some bugs have been fixed recently in grub4dos (one of which was quite serious to do with writing to NTFS files not working), so a new version is 'required'.

Many thanks to the E2B users who have suggested small tweaks and improvements to make E2B even better!

The latest grub4dos also allows you to disable or change the ► symbol that is displayed at the side of the highlighted menu entry - see the \_ISO\Sample_MyE2B.cfg file for details.

P.S. MakePartImage has also been updated to v 0.037 and now includes RMPartUSB.exe in the \e2b folder so you can restore the E2B partition from Windows using the RestoreE2B.cmd script, without needing to boot from the E2B USB drive to the CSM menu.

Please tick 'funny' 'interesting' or 'cool' or add a comment to let me know which posts you most enjoy.

Sunday, 17 August 2014

Add Desinfect 2014+Persistent Virus Updates to your Easy2Boot USB drive

Here are the steps to add the Desinfect 2014 ISO to you E2B USB drive and have persistent virus definition updates too ...

As well as your E2B USB drive, you will need a spare 4GB or larger USB Flash drive that can be wiped - otherwise you will need a previously-made desinfect 2014 bootable Flash drive. This spare drive is not needed once the E2B installation has been completed.

I also had an internet connection (via Ethernet) connected to the system so that I could get the latest updates.

Direct link to .mnu file for persistent updates here and also the .mnu file is in the E2B's \_ISO\docs\Sample mnu Files folder.

If you are new to Easy2Boot, the instructions here may help too.
You can, of course, add 100's of different  linux LiveCD ISO files or Windows Installer ISOs or 100's of other files to the E2B drive as well as Desinfect! See here for a list of tested payload files.

On your E2B USB drive...

1. Make an ext2 file -  the Volume Name of the ext2 file must be desinfSIGS - create a 1000-2000 MB ext2 file using RMPrepUSB - Create Ext2 FS as follows:

File Name = desinfect-rw
Volume Name = desinfSIGS
Size = 2000 MB  (1000MB minimum but I suggest larger to allow for more updates)

2. Add the .ISO to your E2B drive (name must be ct_desinfect_2104.iso) as well as the .mnu file - e.g. you should now have added to your E2B USB drive:
  • \desinfect-rw
  • \_ISO\MAINMENU\MNU\ct_desinfect_2014.iso
  • \_ISO\MAINMENU\MNU\Desinfect_2014_with_Updates.mnu
Don't forget to run WinContig (RMPrepUSB - Ctrl+F2) to make all files contiguous! You can use any of the \_ISO\XXX\MNU folders depending on what menu you want desinfect to be listed in.

3. Boot from the E2B drive to desinfect - this must be done on a real system, NOT a VM.

4. We now need to copy the files from a desinfect bootable USB Flash drive that has been made by the Desinfect 'Create USB' utility. If you don't already have one, then make one now...

Insert a spare 4GB or larger USB Flash drive into the system and click on the Desktop icon to 'Create bootable USB drive with desinfect' - follow the prompts to create a Bootable USB drive - I suggest you untick the  'Kompatibilitat' box as that is what I did when I tested this process but I doubt if it matters.

After the USB drive has been made, you should be asked if you want to copy the latest updates - I chose Yes at this point. If you choose No then there will be no new updates and you will have to update the E2B ext2 partition later anyway. The update download can take quite a while (e.g. 40 minutes to 2 hours!). If you just want to get the E2B USB drive working without waiting an hour or more then choose No.

5. Shutdown desinfect.

6. Remove the spare USB Flash drive and reboot from the E2B drive to desinfect again (English or default German language).

7. Insert the spare USB Flash drive - Ubuntu should now mount all the 3 partitions on that drive including the desinfSIGS partition that is on the spare USB Flash drive and contains the virus signatures.

Note: if you have both a desinfSIGS and desinfSIGS_ volume - you did not correctly follow these instructions! One will be the E2B ext2 volume and the other will be the spare Flash drive volume you just created! Shutdown and try again from step 6 or step 1!

8. The spare flash drive 'signatures' volume should be mounted at /media/desinfSIGS - we now need to copy the contents to our ext2 filesystem as follows:

open a command console window and type the blue text below:

df                                       (find the E2B ext2 partition - e.g. /dev/sdb3)
ls /media/desinfSIGS/       (check you have the desinfect-signatures persistent  lost+found logs config folders and several other files present)
mkdir ss
sudo mount /dev/sdb3 ss  (assumes sdb3 is your E2B ext2 partitition made from desinfect-rw)
sudo cp -purv /media/desinfSIGS/*   ss
sudo umount ss

9. Shutdown desinfect - and now remove the spare USB Flash drive - we won't need this again.

10. Now boot to Desinfect from the E2B drive and click on the 'Viren-Signaturen aktualisieren' shortcut - it should report that you have all the latest updates.


Desinfect shows signatures in RAM or signatures on the USB drive

Tip: Make a backup of the \desinfect-rw file, zip it up and keep it in a safe place. If you ever need to reformat your E2B drive or if the ext2 file on the E2B drive gets corrupted, you can easily restore it!


UEFI booting with persistence

Once you have normal MBR booting working as detailed above, you can convert the image to UEFI-boot as follows:

1. Drag-and-Drop the ct_Desinfect_2104.iso file onto the MPI ToolKit  MPI_FAT32  MakePartImage Desktop shortcut on your Windows Desktop to make a ct_Desinfect_2104.imgPTN file. See here for details.

2. Copy the ct_Desinfect_2104.imgPTN file to the \_ISO\MAINMENU folder

3. Move the \desinfect-rw file to the \_ISO\MAINMENU folder

Note: If you wish, you can put both files in a different menu folder - e.g. \_ISO\ANTIVIRUS.

4. Rename the desinfect-rw file to \_ISO\MAINMENU\ct_Desinfect_2014   (i.e. the file name must be identical to the .imgPTN file name but have no file extension)

e.g. we now have:
\_ISO\MAINMENU\ct_Desinfect_2014                  - was desinfect-rw
\_ISO\MAINMENU\ct_Desinfect_2014.imgPTN   - image partition file

5. The ct_Desinfect_2104.iso file and .mnu file in \_ISO\MAINMENU\MNU are no longer required and can be deleted.

6. (optional) - create a \_ISO\MAINMENU\ct_Desinfect_2014.txt file with whatever menu title you require - e.g.

title Desinfect 2014 with Signature updates (MBR+UEFI)\n Boot in either normal BIOS MBR mode or UEFI mode

7. Finally, don't forget to run WinContig on the E2B USB drive (RMPrepUSB - Ctrl+F2)

You can now select the ct_Desinfect_2104.imgPTN menu entry and it will switch in the new FAT32 partition and display the CSM boot menu.




From the CSM menu you can boot in UEFI-mode using Clover or boot in normal MBR-mode. You can also reboot the computer and then boot from the E2B USB drive in UEFI-mode by selecting the BIOS UEFI USB boot option.

Note: Desinfect does not support 32-bit UEFI booting.

If you want to UEFI-boot from a system that does not allow CSM/MBR booting, you can run RMPrepUSB - QEMU or  VirtualBox+VMUB or MobaLiveCD to boot from the E2B USB drive first under Windows - then you can select the .imgPTN menu entry to switch to the CSM menu before you connect the E2B USB drive to the target UEFI system.

Please tick 'funny' 'interesting' or 'cool' or add a comment to let me know which posts you most enjoy.

Saturday, 16 August 2014

Add Desinfect 2014 + Persistence to your Easy2Boot multiboot USB drive

As with most ISO files, you can just add the Desinfect 2014 ISO file to your Easy2Boot USB drive and boot from it in BIOS/MBR mode - OR - you can drag-and-drop the ISO onto the MPI Toolkit FAT32 Windows Desktop icon to make a partition image file and then add the ct_desinfect_2014.imgPTN file to your Easy2Boot drive, if you want to 64-bit UEFI-boot to Desinfect as well as MBR-boot.


If you want to enable persistence however, you will need to use a special .mnu file as well as the Desinfect ISO file.

Adding a persistence ext2 file allows some Desktop settings to be remembered after a reboot. For instance, any files placed on the Desktop will be preserved. However, the background wallpaper is reset to the Desinfect wallpaper after every boot.

I also could not get the antivirus updates to be persistent using this method, they have to be downloaded each time you boot to Desinfect.

Note: You can have persistent updates, but not with persistence as well - see the next blog post!

Here is the .mnu file. The top lines are comment lines and contain instructions on how to add persistence. The .mnu file is also available in the Alternate Download Area from here.

# Make a \casper-rw ext2 file using RMPrepUSB in the root of the drive using RMPrepUSB
# File Name=desinfect-rw  Volume Name=casper-rw size=500MB or change as desired
# Place this .mnu file and the ISO in either \_ISO\MainMenu\MNU or \_ISO\LINUX\MNU
# This menu will work even on an NTFS USB boot drive
# IMPORTANT: you MUST run WinContig (Ctrl+F2) before booting E2B.

iftitle [if exist $HOME$/ct_Desinfect_2014.iso] Desinfect 2014 PERSISTENT\n Boot using .mnu file with persistence
if exist CD echo WARNING: Cannot use partnew command! && pause && configfile (bd)/menu.lst
if "%E2BDEV%"=="" set E2BDEV=hd0 && pause E2BDEV forced to hd0!
set ISO=ct_Desinfect_2014.iso
set PER=/desinfect-rw
#enable parttype output
debug 1
# make empty table entry in 3rd position in ptn table
parttype (%E2BDEV%,2) | set check=
debug off
set check=%check:~-5,4%
if "%check%"=="0x00" partnew (%E2BDEV%,2) 0 0 0
if not "%check%"=="0x00" echo WARNING: PTN TABLE 3 IS ALREADY IN USE - PERSISTENCE MAY NOT WORK! && pause
debug 1
if not exist %PER% echo WARNING: %PER% persistence file not found! && pause
errorcheck off
set P=0
if "%check%"=="0x00" partnew (%E2BDEV%,2) 0x0 %PER% && set P=1
errorcheck on

#Language
set L=debian-installer/language=de console-setup/layoutcode?=de
echo
set ask=
#English text below can be changed to German
if "%P%"=="1" echo -e PERSISTENCE IS ENABLED: Some settings, Desktop items, etc. will be remembered after reboot.\n\nNote: The background will always be reset back to the Desinfect wallpaper.\n      Virus updates are not persistent.\n      Always SHUTDOWN correctly to avoid corrupting the persistence file.\n

set /p:3 ask=Press E and [Enter] for English (within 3 seconds)... 

if /i "%ask%"=="E" set L=
#set L=debian-installer/language=en console-setup/layoutcode?=en

echo
echo
#map ptn 4 to ISO
partnew (%E2BDEV%,3) 0x0 $HOME$/%ISO%
map $HOME$/%ISO% (0xff)
map --hook
root (0xff)
set A=file=/cdrom/preseed/ubuntu.seed boot=casper 
set B=iso-scan/filename=
set INTISO=/software/desinfect-2014.iso
set C=quiet splash memtest=4 -- 
set D=persistent persistent-path=/
echo
if not exist %INTISO% echo ERROR: INTISO is set to %INTISO% but it is not present inside %ISO% && pause

kernel /casper/vmlinuz %A% %B%%INTISO% %C% %L% %D%
initrd /casper/initrd.lz

Note that the ct_Desinfect_2104.iso file actually contains a second ISO file inside it (/software/desinfect-2104.iso). It is this ISO file that we must use for the iso-scan/filename parameter.



Thursday, 14 August 2014

F1 Help function added to Easy2Boot v1.55

A user requested an F1 help hotkey feature, so I have added this into E2B v1.55.

There is a new .mnu file for the Help Main menu entry and the actual Help text (English only) is held in an F1.cfg file:

  • \_ISO\MAINMENU\ZZZF1SubMenuHelp.mnu
  • \_ISO\e2b\grub\ENG\F1.cfg


Help menu screen (F1.cfg)

Help text is displayed in the console screen.


It is expected that the user will want his own F1 menu, so all they have to do is copy the \_ISO\e2b\grub\ENG\F1.cfg file to the \_ISO folder and edit it to show whatever help text they want for their E2B payload files and hotkeys, etc.

If you do not want a Main menu entry, but you still want the F1 hotkey to work, then you can specify a generic F1 hotkey in the \_ISO\MyE2B.cfg file. The user can then press F1 in any E2B menu and they will see the Help menu and so no Main Menu entry is needed.

There is example code in the Sample_MyE2B.cfg file for this (just uncomment the 3 lines):

# Make the F1 key show the Help Menu from any menu (uncomment 3 lines below) - you can put your own help file in \_ISO\F1.cfg
###if exist /_ISO/F1.cfg   ()/%grub%/hotkey [F1] "configfile /_ISO/F1.cfg" > nul && goto :f1skp
###if exist /%grub%/%LANG%/F1.cfg ()/%grub%/hotkey [F1] "configfile /%grub%/%LANG%/F1.cfg" > nul && goto :f1skp
###if exist /%grub%/ENG/F1.cfg ()/%grub%/hotkey [F1] "configfile /%grub%/ENG/F1.cfg" > nul
:f1skp


The F1 Help menu can be removed from the MAIN Menu by deleting the file \_ISO\MAINMENU\ZZZF1SubMenuHelp.mnu


V1.55_Beta3.zip is available from the Alternate Download links on the Easy2Boot Download page.

Friday, 8 August 2014

New .cfg file extension recognised by Easy2Boot

The new version 1.55 of E2B recognises the .cfg file extension which can be used for changing the 'theme' of E2B  (non-volatile, the change will be remembered on reboot).

Any .cfg files that are in a menu folder (e.g. \_ISO\MAINMENU or \_ISO\UTILITIES, etc.) will be enumerated and listed in the relevant menu.

The contents of the .cfg file should be the same as the contents of a valid MyE2B.cfg file.
When you select a .cfg file from the menu, QRUN.g4b runs and copies the contents of the file to the \_ISO\MyE2B.cfg file (which, of course, must be present).

The \_ISO\MyE2B.cfg file must be at least as big as your .cfg file and the \_ISO\MyE2B.cfg file should be contiguous (due to a bug in grub4dos NTFS file handling - fixed in 2014-08-19 version and later).

To change the menu entry from just listing the filename+extension, you can make a .txt file for each .cfg file (containing a 'title' entry) in the usual way or use the 'set EXTOFF=1' line in the \_ISO\MyE2B.cfg file.

In this way you can switch to any 'theme' from a menu entry.


Jolene.cfg added to MAINMENU

To demo E2B menu capabilities or compare 'themes'  see http://www.easy2boot.com/configuring-e2b/demo-mode/ for ideas.

Thursday, 7 August 2014

Add graphics adapter resolution auto-detection into Easy2Boot

You may want to display your E2B menu in the highest/best resolution possible.
For instance, some odd systems may not support 800x600 mode.

I always advise you to use the most common display resolution so that the menu will appear correctly on all systems. However, you can arrange E2B so that it will cope with a variety of different systems.

You will need a range of wallpaper bitmaps for each resolution (though in some cases the largest bitmap may work for smaller resolution displays).

Auto-Detect highest resolution and use correct wallpaper

The code below can be used in a \_ISO\MyE2B.cfg menu to auto-detect the highest resolution available and then set the graphicsmode and wallpaper for that resolution. 

Note that the position of the menu will remain the same (unless you also add extra code - e.g. if "%GMODE%"=="1024 768 24" set rstart=5) and so will the text colours, etc.

So each wallpaper bitmap should be similar in colour and content because the menu position and text colours will not change.

# allow vbeprobe command to output text
debug 1
# list all available BIOS graphics adpapter modes
vbeprobe > (md)0x220+5
# turn off text output for future commands
debug off
# look for 640, 800 and 1024 modes - be careful to only use x24 or x32 modes for full colour bitmaps
cat --locate=", 640x480x24"  (md)0x220+5 > nul && set GMODE=640 480 24 && set MYWBMPGZ=/_ISO/nice640.bmp.gz
cat --locate=", 800x600x24"  (md)0x220+5 > nul && set GMODE=800 600 24 && set MYWBMPGZ=/_ISO/nice800.bmp.gz
cat --locate=", 1024x768x24" (md)0x220+5 > nul && set GMODE=1024 768 24 && set MYWBMPGZ=/_ISO/nice1024.bmp.gz

# DELETE THESE TWO LINES ONCE IT IS WORKING
cat (md)0x220+5
echo GMODE=%GMODE%  MYWBMPGZ=%MYWBMPGZ% && pause

Add a Change Language menu entry to Easy2Boot

This Change_Language.mnu file will be in the Sample mnu Files folder in v1.55 and later versions.
It allows the user to temporarily change the language strings (until reboot).

Using this and the Change_Theme.mnu, you can demo E2B to your colleagues!

You can modify it by adding or removing languages or write it in a different language other than English (save the file as UTF-8 if using non ASCII characters).

title Change the E2B Language\n Change the standard E2B menus to a different language
echo
echo Change Language
echo -e ===============
echo
echo Only the standard E2B menu entries, headings and some prompts will change.
echo  Note: This does not change the E2B Header or the Footer help text
echo
echo Please choose a language...
echo
echo 1 English
echo 2 Spanish
echo 3 German
echo 4 Brazilian Portuguese
echo 5 Simplified Chinese
echo 6 Traditional Chinese
echo
set ask=
set /p ask=Please enter a number : 
set LANG=ENG
if "%ask%"=="2" set LANG=SPANISH
if "%ask%"=="3" set LANG=GERMAN
if "%ask%"=="4" set LANG=PORTU_BRAZIL
if "%ask%"=="5" set LANG=SIMP_CHINESE
if "%ask%"=="6" set LANG=TRAD_CHINESE

configfile /%grub%/Menu.lst



Note that you can set a default language in your \_ISO\MyE2B.cfg file, but it must be set using a line like this - otherwise the Change Language menu will not work:

if "%LANG%"=="" set LANG=SPANISH



Add a 'Change Theme' menu to Easy2Boot

It is fairly easy to add a .mnu file which allows the user to choose a different background wallpaper:

title Change Wallpaper\n Choose a new E2B menu background
set CHOSEN=
call /%grub%/pickafile.g4b /_ISO .gz
if "%CHOSEN%"=="" configfile (md)0xa000+0x50
clear
splashimage /_ISO/%CHOSEN%
configfile (md)0xa000+0x50

The .gz files must contain a bitmap of exactly the correct resolution size - e.g. 800x600  (801x588 will NOT work!). The actual existing menu text and border positions, etc. is not changed however, so the images that you use should work with the same settings used by E2B as the default (or as used in your \_ISO\MyE2B.cfg file). So you will need to pick your images carefully (plain colour ones work best).


Today, devdevadev asked me if he could have a menu to switch between themes. You can use this to demo E2B, e.g. switch backgrounds, language, font, colours, etc.

A menu would prompt you to pick a .cfg file as shown below:



Here is the .mnu file that I came up with:

# Place all MyE2B.cfg and wallpaper files in \_ISO\mythemes and all rename .cfg files (amd any message GFXBoot file if more than one)
# Edit each \_ISO\mythemes\xx.cfg file so background or GFX has correct path
# e.g. set MYWBMPGZ=/_ISO/mythemes/stripedflat.bmp.gz  OR set GFX=mythemes/message  (note: no /_ISO/ for GFX path)
# Rename \_ISO\Sample_MyE2B.cfg to \_ISO\MyE2B.cfg (must be >1KB and larger than largest xxx.cfg file)
# For the default E2B theme, make a \_ISO\mythemes\Default_Theme.cfg file with just !BAT on the first line
# \_ISO\MyE2B.cfg file must be contiguous due to bug in grub4dos!

title Change Theme\n Choose a new E2B Theme

if not exist /_ISO/MyE2B.cfg echo ERROR: Please create a large \_ISO\MyE2B.cfg file && pause && configfile (md)0xa000+0x50
set CHOSEN=
errorcheck on
debug normal
graphicsmode 3
clear
echo Pick a Theme...
call /%grub%/pickafile.g4b /_ISO/mythemes .cfg
if "%CHOSEN%"=="" set DONEMENU= && configfile ()/%grub%/menu.lst
echo
echo Overwriting \_ISO\MyE2B.cfg file with \_ISO\mythemes\%CHOSEN%...
# fill (rd) with 0's , 0x82d0 is rd-base mem address, Fn24 is memset - fill memory  <addr> <string> <size>
map (md)0x300+200 (rd) > nul ;; read 0x82d0 > nul ;; call Fn.24  %@retval% 0x20  102400 > nul  
dd if=(rd)+1 of=()/_ISO/MYE2B.cfg > nul
if exist ()/_ISO/mythemes/%CHOSEN% dd if=()/_ISO/mythemes/%CHOSEN% of=()/_ISO/MyE2B.cfg > nul
if exist ()/_ISO/mythemes/%CHOSEN% chainloader /grldr
boot

I tested this using these files in the E2B \_ISO\mythemes folder :


The 'graphicsmode 3switch is required only if you use GFX Boot menus such as the sample Jolene_GFX.mnu. You can delete it if you don't have any GFXBoot .cfg files. If you do use GFXBoot menus, you will also need to copy all the \_ISO\docs\GFXSubMenu Files .mnu files into \_ISO\MAINMENU or else some menu entries will be missing from the GFXBoot menu when selected (this applies to any GFXBoot menu).

Both .mnu files will be in the Sample mnu Files folder in v1.55 of E2B and I will also put them in the Alternate Download area for a while too.

v1.55 will have the mythemes folder and a selection of .cfg files to choose from. You will just need to copy a $Default E2B Menu.cfg file to \_ISO\MyE2B.cfg and the .mnu file to \_ISO\MAINMENU.

Notes: due to a bug I just discovered in grub4dos, make sure you run WinContig on the E2B drive to make all files contiguous. It seems there is a problem with grub4dos and NTFS volumes if this is not done (if the target file is fragmented, then only the first 8096 bytes are actually copied when using dd on some files!).

And due to another bug, the full path for the bitmap file needs to be kept shorter than approx 64 characters as the splashimage command cannot handle long pathnames!