E2B Users Forum

No not unless you use a GFXboot menu

I'm used menu wich looks like that:

http://4.bp.blogspot.com/-osqd4BhlrB8/UZEXSLPRSnI/AAAAAAAAAS8/ECWAxhSXHiQ/s1600/TEST_MyMenu.lst.jgp.jpg

It is gfx menu??

No, GFXMenu is an example of a GFXBoot menu
\_ISO\docs\Templates\GFXMenu
Read
https://easy2boot.com/configuring-e2b/gfx-menu-support/

P.S. E2B now supports large 24-pixel high fonts!

Hello Steve.
How to change the font size in my menu?

hi face a problem with easy2boot usb during process make multiboot usb plz u tell me how we can send a large file up to 4 gb in our easy2boot usb fat32 file system from our ntfs windows 7 os without split files i,m waiting sir.....?

https://easy2boot.com/add-payload-files/adding-windows-install-isos-without-needing-a-helper-flash-drive/
If that doesn't help, please give exact details (payload, large files, what you are trying to do, etc.)

The way I read the instructions, I should be able to create .imgPTN files and place them in the directory, then E2B more or less does the rest. However, for Windows installs, the E2B menu does not show the .imgPTN files. Rather, I always have to do Switch_E2B to boot into them via UEFI. Am I just reading the instructions wrong?

Yes - you are probably reading the instructions incorrectly. Try reading them again!
https://easy2boot.com/add-payload-files/

OK, I think I finally get it. ISO files go into the WINDOWS subdirectories while imgPTN files go into the WIN (or some other) directory. I don't understand why, but at least I think I understand the what.

Starting with E2B v1.75BetaB you can now add .imgPTN files to the \_ISO\WINDOWS\xxxx folders (except XP folder).

Hi, thank you for all the stuff you made here :)

I was trying to create an imgPTN of Openelec :
1. Use of RMPrepUSB to create USB Stick Openelec from Openelec.img. Ok, drive L:
2. Drag icon of L: on MPI_FAT32 shortcut. Ok.
After typing size and pathname of imgPTN, some errors appears :
SOURCE = "L:\"
RAMDRIVE = U:
NEW IMAGE = "c:\temp\essai.imgptn"
FORMAT = FAT32
VOLUME NAME = EASY2BOOT
IMAGE SIZE = 185MB (Source=166MB)

CREATING AND MOUNTING RAMDRIVE U: as "c:\temp\essai.imgptn"

Running: imdisk -a -s 185m -m U: -f "c:\temp\essai.imgptn" -x 63 -y 255 -p "/FS:FAT32 /Q /Y"
Error defining drive letter: Descripteur non valide
Creating device...
Created device 0: U: -> c:\temp\essai.imgptn
ImDisk operation failed to mount "c:\temp\essai.imgptn"

After this message, i press enter and then 2 more messages but too fast to copy "Il manque une opérande" then the window close and ImDisk opens, with the file in the list. No drive created, no files copied i guess, fileSystem indicates N/A.

I have no clue of what happens :/
Im' using imdisk 2.0.6, and MPI_Tool_Pack_Plus_CloverLite_055 on Windows 10 Biuld 10565.

If you have some ideas :D

Hi
When you create the USB stick containing Openelec, what files can you see on the USB stick? Are they accessible to Windows?
If you want to have Openelec, why not follow my blog posts on how to create an Openelec and OpenElec-Live image?

Hello, thanks for your answer.

I'm following this tutorial (maybe old) :
http://rmprepusb.blogspot.fr/2013/10/how-to-add-openelec-installer-to.html

If I create USB Stick from Openelec image with Win32DiskImager or REMPrepUSB, i see the 2xxMB partition with all files needed to boot and begin Openelec installation (what i did last night).

To be totally clear, this is not Openelec wich cause metrouble, because as you can see, there is alternate option to add it to easy2Boot.

But if imdisk is not working on my PC, i could not be able to add Windows 7, 8 and 10 install as i need imgPTN to do this (if I fully understood what I read on easy2boot website).

I forgot to list files on USB Stick, sorry. Result of list l:\ /s /b
l:\syslinux.cfg
l:\KERNEL
l:\SYSTEM
l:\EFI
l:\EFI\BOOT
l:\EFI\BOOT\bootx64.efi
l:\EFI\BOOT\ldlinux.e64
l:\EFI\BOOT\syslinux.cfg
l:\System Volume Information\IndexerVolumeGuid

Is U: a free unused drive letter?
Try rebooting Windows.
Try copying the files from the USB flash drive to an empty folder and then drag-and-drop that folder onto the MPI_FAT32 desktop shortcut.

Hello,

Reboot done, same problem.
u: unused, "subst u: c:\temp" creates u: drive.
"subst u: /delete" frees hit.

I copy files in folder then drag-drop and error message changed only one time :
"Accès refusé" (access denied)
after that, all trys show precedent error message : "Descripteur invalide"

I'm able to create c:\temp\essai.imgPTN with imdisk GUI in control panel : 28MB, drive U:. Windows says after that i have to format drive u: before use it...what i did with success.

I will try to disable antivirus when i come back. thanks for your time.

It may be your AV - what AV do you have?

I cannot free U: with imdisk control panel because imdisk cannot create U:.

My AV is Comodo : i disabled all comodo parts, and even exclude imdisk files, exe, cpl and sys, in system32 and syswow64. No change.

When i try to create imgPTN file and imdisk failed to create U:, i cannot delete imgPTN file created, because it always mounted in imdisk : if i remove it, imdisk warns me "can not lock file...." i can click ok and remove it.

I opened cmd as Admin and type :
"imdisk -a -s 280m -m U: -f "c:\temp\essai.imgptn" -x 63 -y 255 -p "/FS:FAT32 /Q /Y"
same error : "Descripteur invalide"

When I said i can create file in control panel, yes I can, but if i put files in it, they are not saved when I re-mount the file, and i cannot use "Save image File..." because "acess denied"...

:/

I have had ImDisk problems with 10565 build - I think it is Win10 10565 problem?
What Edition are you using? I had problems on 10565 Enterprise with ImDisk.

You right i guess, I'm using Windows 10 insider 10565.

I tried to stop insider program, but this is not working, maybe because stable 10565 not in live.

The problem is persistent with b10576...
My hope is an update of ImDisk now.

10576 is not released - you should report issue to MSoft.

Of course b10576 is released in the insider fast ring, the day I posted :D

imdisk dev Olof already had knowledge of my problem, caused by -p switch.

I modified the batch MakePartImage.cmd to format drive AFTER imdisk created letter, with format command and by passing parameters from -p switch. It is a little more dangerous for sure.
here the modifications of MakePartImage.cmd :

REM Modification for suppress Windows 10 build 10565&10576 error
REM Following 3 lines had been commented, then following 5 lines had been added

REM --------------------Commented------------------------
REM echo Running: imdisk -a -s %MYSIZE%m -m %SPAREVOL% -f !MYIMG! -x 63 -y 255 -p "/FS:%MYFMT% /Q /Y"
REM imdisk -a -s %MYSIZE%m -m %SPAREVOL% -f !MYIMG! -x 63 -y 255 -p "/FS:%MYFMT% /Q /Y" > imdisk.log
REM if errorlevel 1 type imdisk.log & echo ImDisk operation failed to mount !MYIMG!! & pause & goto :unmount
REM ----------------End of commented---------------------

REM ----------------------Added--------------------------
echo Running: imdisk -a -s %MYSIZE%m -m %SPAREVOL% -f !MYIMG! -x 63 -y 255 then only if no error FORMAT %SPAREVOL% /FS:%MYFMT% /Q /Y
imdisk -a -s %MYSIZE%m -m %SPAREVOL% -f !MYIMG! -x 63 -y 255 >imdisk.log
if errorlevel 1 type imdisk.log & echo ImDisk operation failed to mount !MYIMG!! & pause & goto :unmount
format %SPAREVOL% /FS:%MYFMT% /Q /Y >>imdisk.log
if errorlevel 1 type imdisk.log & echo ImDisk operation failed to mount !MYIMG!! & pause & goto :unmount
REM ------------------End of added-----------------------

This is not for modification of easy2boot (bug or undocumented modification, Olof have no idea as MS did not respond to him), but could be added in the faq ?

I tested a fresh install of Windows 10 Pro insider preview 10565 32-bit under VBox and the MPI Tool Kit 0.055 seems to work OK without needing your additions??

I don't know why you experienced this, Olof did not be surprised, and show me immediatly where was the problem I encoutered :/
Maybe something on some PC.
But finally, the problem is fixed on my PC, and i'm happy with that :D

Hi!

I am trying to boot an imgPTN (image of an USB-Key)- file direct into the memory, like under isolinux with the keyword memdisk. Is something similar like this possible with Easy2Boot?

I am trying around with zip but that's not working for me. The key itself is about maximum 200MB large.
Thanks and Greetings!

No. What image is it and why do you want it in memory?

I dont understand your question... It's an image of an Service-USB-Key provided by an manufacture. It's supposed to scan system. To detach the usb-key after the scan has started I need to run it from memory. Under isolinux / syslinux it's working like I said. Now i am looking for an possible way by Easy2Boot as well.

I got it working finally, and want to let you know what i did:

I made an Compressed Image File of the USB-Key (img.gz), done by the tool "USB Image Tool". Just place this file where you want, such as in _ISO/UTILITIES.

Easy2Boot is doing all by itself.
Source: https://easy2boot.com/add-payload-files/list-of-file-extensions-recognised-by-e2b/
" .. E2B\grub4dos automatically detects if a file has been compressed to gzip or LZMA format. The file extension is not used by E2B to determine if a file is compressed or not. For instance, a LZMA-compressed DOS floppy image can be named .ima or .imagz."

Greetings

Glad you found a solution. It is possible to run images from memory using various file extensions, but not .imgPTN files, which is what you asked about.
P.S. What form is the original source file(s) provided in? Why not just use that?

I just followed the tutorial given some posts ago, source is Openelec Installer as .img file.

KEEP IT COMING XD

Hi Steve,

USB harddisk works fine in qemu test.

I'm not sure What is wrong in real boot:
"Booting Easy2Boot vl.72 - please wait...
Using settings in /ISO/MyE2B.CFG
Using strings from /ISO/e2b/grub/ENG/STRINGS.txt
BIOS 11/24/11
Last Sector of last partition of (hd0) is 58605052 (27Gb)
Checking last sector is accessible... "
and no go!

Did you format the drive using the Make_E2B_USB_Drive.cmd script? If not, try it.

Yes I did run it as admin under win7.
It created 2 partitions: ntfs=27.94Gb and hidden/unknown=31.5Kb,
but it didnt create any cdfs-partition to boot my.iso

strange, it should be OK. The cdfs partition is only created when you run an ISO. It is cleared on the next boot to E2B.
Try grub4dos 0.4.5c

Copy the \_ISO\e2b\grub\grub_045 file to \grldr and overwrite the \grldr file.

Now it works fine just by changing to regular menu.lst.
I dont know how to fix your menu.lst, any help?

I think If you have a lot of partitions on your HDD, still you need to create a space(primary) for cdfs partition.

It is nothing to do with the cdfs partition.
The check is a simple disk read of some sectors near the end of the USB disk. This tests some BIOSes which have a bug and cannot access sectors past 137GB. You can disable the test using
set CHECKBIOS=
in your \_ISO\MyE2B.cfg file, but you may find that some payloads will not work if they are beyond 137GB on some systems due to a bad BIOS.

Thank you for remind me about 137GB BIOS-limit, but my HDD is only 30 GB.
I am curious why E2B created 2 partitions: ntfs=27.94Gb and hidden/unknown=31.5Kb. Is unknown partition necessary or what is the purpose? or may something wrong with rmpartusb?
I hope you have explanation of my questions.

Finally Easy2boot works fine after shrinking the partition, just the problem I have do it manually.

Thanks Steve

The small partition is to try to fix a BIOS bug which is found on some systems, see FAQ page
After partitioning and formatting a USB drive using the Make_E2B_USB_Drive.cmd script or RMPrepUSB, there is a small hidden partition at the end of the USB drive - what is this used for?
Read more: https://easy2boot.com/faq-/

Do you have any more details on what system you are using and what size partitions work and do not work? It would help to make future versions more 'bootable'. How much did you reduce the partition sizes by and which parititions did you change, etc.?

Fujitsu MHS2030AT 30GB.
E2B (NTFS or FAT32) is not working on some computers:
Dell 4600/intel, Acer 5810TS/intel, Lenovo K100/intel, Toshiba A600/intel and working fine on: HP dm4/intel, Toshiba A215/AMD.

E2B works fine on all computers after shrinking the partition to any size or resize to one whole full partition.

I tested also using 80GB and 20GB HDD and everything work fine without to resize the partition.

So in the case of the MHS2030AT 30GB HDD and one of the 'bad' systems -e.g. Dell 4600 - are you saying that if you prepare the 30GB drive using MAKE_E2B_USB_DRIVE.cmd as either NTFS or FAT32 then it does not boot, but if you reduce the size of a partition (which partition? there should be two, and using what tool?) then it works?
If so, could you prepare the 30GB drive using MAKE_E2B_USB_DRIVE.cmd as NTFS and check it fails, then send me a 'Drive Info - 0' email of the LBA0. Then 'fix' the problem by reducing the partition size and send me another 'Drive Info - 0' printout please? You can use the 'Contact Me' form or directly email me.

how to use hiren or any MBR related tools to boot from cd or usb on system with only uefi support no csm /mbr support using easyboot or any other method. Thanks

See https://easy2boot.com/useful-things-to-know/
last item.

Thanks 4 ur quick reply :)

I put a Windows 10 ISO on my E2B USB key. But when I tried to boot it, it appears to have booted into BIOS mode. As a result, Windows refused to install to a GPT drive.

Is that the correct diagnosis? If so, can I force UEFI?

You need to boot in UEFI mode.
Convert the .ISO file to a FAT32 .imgPTN file using MakePartImage (MPI Tool Kit) and copy the .imgPTN file to the E2B USB drive \_ISO\WIN folder or \_ISO\MAINMENU folder.
Then you boot to E2B and select the Win10.imgPTN file and switch to the CSM Menu.
You can now either boot using the Clover menu or UEFI-boot using your UEFI BIOS selection menu. Watch the videos for more help.

Hi there,

I have a WD Passport Enterprise, a 500 GB USB Disk Drive with support for BitLocker drive encryption. I have installed Windows To Go (Windows 10 Enterprise) on it; with BitLocker encryption enabled.

I want to be able to use disk for all kinds of situations, so besides Windows To Go (WTG), I also want to install Linux LiveCDs.

Is it possible to install E2B on a USB Disk Drive with WTG on it, and to boot into either Windows or E2B?

I am not sure, I have not tried that. I would
1. Make a 2nd primary partition
#1 - E2B NTFS (first 137GB or less)
#2 - WinToGo (rest of disk)
Check WinToGo still boots OK or use EasyBCD or BootIce to fix BCD.
2. backup the first 2048 sectors of the disk to a file using RMPrepUSB - Disk>File for safe keeping.
3. Install grub4dos to MBR and PBR of first (E2B) partition using RMPrepUSB - Install grub4dos
4. Add E2B files to #1 partition
5. Add a bootmgr .mnu file to \_ISO\MAINMENU for partition #2

Try it! If it doesn't work you can restore MBR+first sectors saved in step 2.

Hi Steve, this is the first .ISO I'm having trouble with to boot. I copy the .ISO as downloaded(dl.acronis.com/s/AcronisTrueImage2016.iso) to \_ISO\BACKUP. It then boots to lang+arch selection menu. After selecting x64 option (english default is ok for me), linux seems to start booting, but then my display blanks, no further activity. Since 2013 and 2014 versions were tested working, maybe the booting method in the new version has something to offer to improve E2B.
Thanks in advance.

I tested the Acronis ISO under VBox with no problems. Usually a blank screen issue is due to the version of linux that is used does not support your graphics adapter.
Try converting the .ISO file to a .imgPTN file and then using the 2nd Acronis Recovery option. This will prompt you to choose a VGA mode - try different modes and see if that works.
I would also check the Acronis forums as probably others have found the same issue if they have the same graphics adapter.

You are right Steve. While I can not be sure about my physical graphics card being the problem (GTX 770, nothing new as of today for a "2016" product), exactly same E2B drive tested on VBox 5.04, and the x64 TI boots just fine. Definitely some hw incompatibility. Well, everything elese boots just fine, so no TI for me then (I'm not interested in the WinPE-based option).

Hi,

I've created the USB key and am testing booting with Virtual Box 5.0.4 (nothing added as yet). Boots OK but when it gets to "Adding menu entries from files in /_ISO/MAINMENU..." it just stops there, can't tell if it has hung completely or is trying to do something. Anyone else come across this before ?

Thanks.

Not seen that before.
How did you make VBox boot from USB?
Did you use VMUB?
What happens if you boot using QEMU?
https://easy2boot.com/testing-e2b/using-qemu-or-virtual-box/

Increase the memory size of the emulated system, it gets stuck with 64MB. Increased to 512MB and booted successfully.

Hello. How integrate DPMS for Vista/7 x86 and x64 into easy2boot?

Here is this driverpacks:
http://driverpacks.net/driverpacks/windows/7/x64/mass-storage/12.12.1
http://driverpacks.net/driverpacks/windows/7/x86/mass-storage/12.12.1-0

but this driverpacks without ini files. Any solution? Thank you so much

I used a thing called 'Google Search' and found this
http://www.win-raid.com/t750f25-Guide-Integration-of-drivers-into-a-Win-image.html

I know about that perfect thing 'Google Search', but i need full driver pack on my E2B usb-flash, instead of instructions about how to embed a particular driver in a particular system image

Why not just copy the driver pack files onto the USB drive? Once you have booted to PE, you could try loading the INF file using drvinst or drvload maybe?
What driver did you need to add?

That's right, it can be used as one of methods, but on different hardware need different driver. It is mainly server hardware. Each time a different driver needs. So I'm looking for a way to integrate these drivers to E2B's DPMS

Can I create on some way bootable dvd with this app? Thanks!

https://easy2boot.com/make-an-easy2boot-usb-drive/make-and-burn-an-e2b-dvd/

hi,
i have been using e2b from longtime. the only thing i want to know, why usb harddisk cant be used as winhelper usb drive or what that usb flash drive does at the point of mounting iso that usb hard disk can not do??
can u explain me the trigger function of menu.lst present on usb flash drive that leads to work installing windows iso??

https://easy2boot.com/faq-/how-e2b-works/

so thats the Microsoft's way of installing an iso,
solution for this problem is either connect winhelper USB or modify iso to use firadisk
i will go for Winhelper USB
thanks for ur support!!

Best solution is to convert the ISO to an image partition (.imgPTN) file. Then you can UEFI and MBR boot.
Conversion does not add firadisk or any other driver.

so i have to keep both file,
an iso and an imgptn file??
right??

No, only the .imgPTN file is required.
Watch the YouTube videos for more info.

always there's something wrong in newer versions of e2b like win7.imgptn it list AGAIN usb dribe as drive0. Can we not have a bugfree e2b

srx, nm installs just fine, only sometimes in expanding windows files it misreads some files,
made a new vm with default settings. OK now

Sorry, don't understand, "srx nm"??
Do you mean that E2B is OK and something was wrong with your .imgPTN file?
P.S. I release Beta versions for feedback from users. If no one reports a problem, I can only assume it is OK. I cannot test every conceivable function of E2B - there are thousands of configurations and hundreds of payloads to test!

Dear sir, I convert Win 7 AIO imagePTN and booted
it ask me win7 activation key to in put manually so please help me

Win7 normally requires activation.
Buy a licence!

Anyone else having issues having Kali Linux 2.0 boot up, or is it just me?

Kali is in the list of tested ISOs.
It works fine for me.
If you have problems please give details.
First thing to do is check the MD5/CRC32 hash value of the ISO file on the USB drive to check for file corruption.

Same, when I choose Install or Graphical Install it doesn't boot. Live works fine.

Kali2 *boots* fine for me.
The only problem is that it cannot find the 'Install CD' - but this is easily solved by specifying \dev\sdb4 as the CD-ROM drive (or use \dev\sdc4 or \dev\sdd4, etc. depending on what the USB drive letter is).
This is detailed in the 'List of tested ISOs' page which you should ALWAYS look at if you have problems (or even before you have problems!)
P.S. See "\_ISO\docs\Sample mnu files\Linux\kali-linux-1.0.5-amd64.txt" for a .txt file which will remind you what to do.

Hi,

I have Windows 7 AIO, 8 and 10 and am trying to get them automated. Just trying to work on the Windows 7 first as I imagine once I get that it will be simple for the others. I have the latest version 1.71. My Windows 7 AIO is about 5GB. I converted it to a imgPTN (NTFS) and deleted that file it prompts you when following the bouncing ball. I forget exactly what it is called. I am doing method three "http://m.easy2boot.com/add-payload-files/automating-windows-install-from-imgptn-files/" and have done everything however it boots up, runs that mysetup.cmd (looks like it does anyway) then the computer just reboots. Is there anything I have missed or need do something? Any help would be greatly appreciated. Thank You.

There are no official Windows AIO ISOs - different people make different AIOs in different ways.
You need to look inside the boot.wim at the \windows\system32 files winpeshl.ini, startnet.cmd, mysetup.cmd and other files of a similar date to see how it has been modified.
Since you are using a USB drive and not a DVD, you have plenty of room, so why use a AIO ISO - why not just use the official MS ISOs?

I copied the files in there and I followed this thread http://m.easy2boot.com/add-payload-files/automating-windows-install-from-imgptn-files/. I haven't touched the startnet.cmd. Do I need to look at that? My reason for using AIO is they are smaller then having all the individual ISO's. My USB is only 64GB and I have a fair bit of stuff on there already. Not really sure why it wouldn't be working. They didn't mention that startnet.cmd on that link.

You have not told me anything about your AIO ISOs, as I said they are all different - what are they, where did you get them from, how were they made, how do they work? I don't have super-powers - do you expect me to guess!
The Easy2Boot instructions are for standard MS ISOs, not heavily modified AIO ISOs by some unknown author and modified in some unknown way!
It is also important to know if your E2B drive is a Removable type or fixed disk type.

Sorry mate. I got the Windows AIO from iptorrents.com. Here is another link http://torrent-release.com/software/14632-windows-7-sp1-5in1-x86-x64-en-us-aug2015.html. It has 5 different versions in there. As you can see nothing has been modified or changed from that link. What I have done is converted that ISO x64 into a imgPTN. Then I have followed those steps in that link provided before method three. I am assuming method three is referring to AIO as it talks about selecting different windows installation images. There is also another thread on rmprep that suggests the same thing how to suppress the OS Image http://rmprepusb.blogspot.co.uk/2015/05/easy2boot-and-automating-windows-78.html. So I thought both those links are referring to AIO. But basically after i converted the image into imgptn I mounted the image picking image 2 from the boot.wim and copied those two files in \windows\system32 committed the changes and copied that other .cmd to the root of the imgptn. It boots up fine from CSM loads the files get the little windows 7 install thing and then it is as if its running the cmd but then the computer just restarts. Sorry for providing less information before. I hope that helps more. my E2B drive is removable as well.

Hi
I used Win7SP1_5in1-x86-Aug2015-en-US.iso.
I followed Method 3 (boot.wim image #2) and used the modified Auto.cmd with the menu.
I added a AutoUnattend7.xml file which was the same as \_ISO\WINDOWS\WIN7\Sample.xml but had a Win7 Pro product key







true

HYF8J-CVRMY-CM74G-RPHKF-PW487






true

HYF8J-CVRMY-CM74G-RPHKF-PW487







This worked as expected just fine.
Either you corrupted the boot.wim or your xml file is causing the problem.
P.S. I used the MPI_FAT32 shortcut.

Got it working mate. I noticed before when I copied in winpeshl.ini it already existed. On those steps on method three it just tells you to copy it in. What I did was edit the winpeshl.ini to look like this

[LaunchApps]
%windir%\system32\wpeinit.exe
%windir%\system32\netstart.exe
%windir%\system32\mysetup.cmd

After I did this I was able to get the custom menu to select what Image I want. Did you have to do something similar. Is it worth updating that page? Incase similar users run into the same problem.

That was for the x64 AIO did NTFS as well for the .imgPTN

I just followed the Method 3 and copied the two files to windows\system32 and it worked.
wpeinit and netstart should not be needed unless you want the network and PnP devices initialised.
If you just wanted to see all OS choices, there is no need to modify the boot.wim.

After trying all possible methods offered by amazing E2B for Windows OSes installation my recommendations are:

1. Get a light PE image with ImDisk installed or allowing you to install it. Even a spartan boot.wim from one of those AIOs from m78 will work, though youll need to install ImDisk .inf manually. I use a .cmd for that. Boot to that .wim using E2B and install ImDisk.
2. Setup your target drive using diskpart (manually or by script of choice).
3. Use WinNTSetup to deploy your OS. You can mount your untouched AIO ISOs (though I convert them to imgPTN because I previously tweak them, and you can mount a imgPTN with ImDisk like you do with an ISO).
Optional: select the autounattend.xml file to use ( no need to modify the ISO)
Optional: Choose a folder containing your drivers (INFs, can be arranged in subfolders).
4. Deploy. Shutdown. Remove your USB. Boot to your target drive and let the install finish.

This message is caused by specifying the wrong product key (e.g. a Retail product key for Enterprise Win8 or 10).
Even if an ISO does not require a Product Key to be entered, when using E2B with a XML file, you need to specify a key (or modify the ISO).
An alternative is to convert the ISO to a .imgPTN file so that an XML file is not used.

Hi, i get a really weird issue when i try to boot from windows iso. when i choose a windows installation folder i get Usage:/_iso/e2b/grub/pickafile.g4b returns : %chosen% Aborting...

i try to replace a lot of file with original file from the download selection but it always do that

Need more details. What ISOs? What menu entry are you using? How can I reproduce? What version of E2B? Did you try fresh install of E2B? etc.

I tried with a lot of iso. all windows iso. it was withe e2b 1.7 my iso is in _isos/WINDOWS/XXXXX I try to replace all the e2b file i try to update e2b but i didn't try to format. Also I notice that after i tried to boot on windows iso my /Unattended.xml was modified. The file is juste anymore

Check the version of \grldr. It may be old version? Use same version that is in the download 7zip file.
XML files go in \_ISO\WINDOWS\xxxxx folders. \AutoUnattend.xml and \Unattend.xml are updated by E2B.

I try to get an .imgPTN - image of an USB-Stick.
This stick is made by a tool of the manufacture I repair computers for. Lets call this USB-Key just 'A'.
As I understand now, the usb-key('A') is based on FreeDos and I want to migrate it into my Tools-HDD / Stick based on E2B ( I tried yumi before, worked well, but then changed to use ISO's instead and E2B works like charm, love it! ).
Before, i just used another tool to get an img-Image of 'A' but since never version of the manufacture-tools it doesn't work any more this way. Don't know why.
My Idea so was to get an imgPTN - file of 'A', but whenever I use the tool "MakePartImage" (no matter if iso or anything else), I get later in process the Message:
"ERROR: T:\menu.lst does not contain any code to restore the E2B partitions"
As I saw in tutorials it looked easy, but I don't get any Idea what and when I shall give more information to the command.
Maybe someone can help me how to get to next step to get the Tool-Stick finally again inside my beloved E2B!
Thanks and Greetings!

Can you describe exactly how you are converting the ISO or USB drive to a .imgPTN file?
i.e. Are you dragging-and-dropping onto MPI_FAT32 Desktop shortcut? Are you prompted with any questions and how do you answer?
Actually, for DOS, you should just make a .img or .imghd file or for a DOS iso just use .isodos or .isodos01. Did you try other file extensions?

I use only the MakePartImage.bat with administrative permission rights.
1. Source ISO or Folder
e:\ (my usb-drive)
2. Use Fat32 for new image?
Y
3. Size for Image file
*just enter*
4. OUtput Filename for new Image
c:\tmp\key.imgPTN
5. Volume Name for partition image
DIFS
6. Enter a name for the title of the CSM menu:
DIFS
Then i could have a look into drive T and continue with enter
(don't need to have a look into it)
Then comes the mentioned error message.
I also tried your mentioned file extensions, but the error-message still exists and is the same.
Before I tried the simpliest way by RMPrepUSB to get an Image of the USB-Key, or otherwise with the tool called "USB Image Tool", also tried several as well. But the result with these is finally it won't boot entirely any more. So I am looking for new and other solutions. So my hope is now on tips and hints from here :)

It sounds like something is wrong with the MPI download.
Can you redownload it and try again?
If still no joy, use the Contact Me form.

You are correct, there really was something wrong.

So i redownload and tried again the same steps,
and it works fine now!
Thanks a lot! :)

how to run Easy2Boot in grub2 as grub2 can not load file *.lis. He loading only *.cfg files? Is there any sw2 file to indicate the program and boot from it?