This page has a different format from the other site pages and has hardly any adverts. You can view all pages on the entire site like this when you donate £5/$8 (English GBP/US Dollars) or more (on both www.easy2boot.com and www.rmprepusb.com sites). You can read and subscribe to my blog here.
 
 

E2B Users Forum

New! E2B eBooks are now available (eBook #1 contains instructions on how to remove the blue-screen startup banner).
 
If you would like help from me (Steve Si) or other E2B users, or would like to offer help and advice to others, please post here.
 
You will need to check this page regularly for replies or add this page's URL to a page change ch ecker.
 
Alternatively, post on the Easy2Boot discussion page on reboot.pro here - register and subscribe to any threads that interest you or post a new topic.
 
You can use the Chat\Live Help facility - if I am online, I will respond within a minute or so (if I am away from my desk, leave your email address and I will email you). For 1-to-1 email communication, use the Contact Me form and I will reply via email.
 
To post to this Forum, scroll to the bottom of the page and click on 'New comment' (use English please).
 
Also, you can read and subscribe to my blog here.

Topic: Easy2Boot

Date 25/07/2019

By cdecde57

Subject Installing winXP onto sata drive (I got drivers but still wont work)

Reply

As you can tell by the title I am trying to install windows XP onto a computer.
The computer is simple with a SATA hard drive. I have gotten a windows XP iso and have done everything required to start trying to install it. It works but when I start the installing after I choose on the easy2boot to do the first step I go and make sure to add the SATA drivers so it won't give me a BSOD. I add the following. WinVBlock 32-bit FiraDisk 32-bit as well as for my AHCI driver Intel(R) ICH9M-E/M SATA AHCI Controller. This is the driver that everyone on google seems to use to install Windows XP. Than says starting the setup and at the bottom left says "Examining 305243 MB Disk 0 at Id 0 on bus 0 on ahcix80x. . ." then the computer turns off and well nothing happens. I can't disable SATA in the bios because it won't let me. I don't know what to do because it seems whatever I do it crashes because of my SATA hard drive. :(

Date 25/07/2019

By cdecde57

Subject Re: Installing winXP onto sata drive (I got drivers but still wont work)

Reply

edit: And yes I have tried the DPMS. I load and I choose the second option which is like the firaDisk and winVBlock and the driver than I press enter and things and the same thing happens.

Date 27/07/2019

By cdecde57

Subject Re: Re: Installing winXP onto sata drive (I got drivers but still wont work)

Reply

Thank you, Steve, for the fix! It worked and all is working now :D
[Edit by SSi] Fix was to press F5 at point where it prompted to press F6 and choose an alternative PC type[/Edit]

Date 13/07/2019

By Xuo

Subject How to add a Mageia7 iso bigger than 4Gb under the _ISO/LINUX directory ?

Reply

Hi,
I use easy2boot to boot from a Linux or Windows PC to launch either Clonezilla or gParted or the Mageia installation.
I have under _ISO/LINUX the Mageia6.iso file which is about 3.9Gb. But the new Mageia7.iso is about 4.5 Gb big.
How can I add this greater than 4Gb iso file in the _ISO/LINUX directory ?
Thank you for your help.

Date 13/07/2019

By SteveSi

Subject Re: How to add a Mageia7 iso bigger than 4Gb under the _ISO/LINUX directory ?

Reply

Just copy the file! What is the problem?

Date 13/07/2019

By Xuo

Subject Re: Re: How to add a Mageia7 iso bigger than 4Gb under the _ISO/LINUX directory ?

Reply

I can't as it is bigger than 4Gb and the FAT32 partition where is the _ISO/LINUX directory does not accept such big files.

Date 13/07/2019

By SteveSi

Subject Re: Re: Re: How to add a Mageia7 iso bigger than 4Gb under the _ISO/LINUX directory ?

Reply

Easy2Boot uses an NTFS partition by default.

Date 13/07/2019

By Xuo

Subject Re: Re: Re: Re: How to add a Mageia7 iso bigger than 4Gb under the _ISO/LINUX directory ?

Reply

If I remember correctly, I have run a script to create the easy2boot partitions : fmt.sh.
It is possible to ask for NTFS partitions instead of a FAT32 ones ?

Date 13/07/2019

By SteveSi

Subject Re: Re: Re: Re: Re: How to add a Mageia7 iso bigger than 4Gb under the _ISO/LINUX directory ?

Reply

Why not use the NTFS script that is provided! fmt_ntfs.sh

Date 14/07/2019

By Xuo

Subject Re: Re: Re: Re: Re: Re: How to add a Mageia7 iso bigger than 4Gb under the _ISO/LINUX directory ?

Reply

I didn't know it was available. It might solve my issue.
Thank you for your help.

Date 14/07/2019

By Xuo

Subject Re: Re: Re: Re: Re: Re: Re: How to add a Mageia7 iso bigger than 4Gb under the _ISO/LINUX directory ?

Reply

It worked and I could write the 4.5Gb file on the ntfs partition. Thanks.

Date 13/07/2019

By Krauter_German

Subject Subfolders

Reply

Hello,
I would like to create two subfolders for e.g. Acronis and EASEUS or AOMEI under Backup in the main menu. Can you help me how to proceed?

Date 13/07/2019

By SteveSi

Subject Re: Subfolders

Reply

Use the Site Map
http://www.easy2boot.com/configuring-e2b/add-a-new-menu-folder/
For a sub-sub-menu see the example for Linux_Ubuntu.

Date 04/07/2019

By Long Vu

Subject Why E2B drive created on Windows do not need to make contiguous?

Reply

I just tried the currently most recent Easy2Boot_v1.B2 both on Windows and Linux.
On Windows 7, use the installer then copy iso using Windows Explorer.
On Linux (Ubuntu 18.04) use the fmt_ntfs.sh then copy iso using rsync.
I was completely stumped by the fact that the usb drive created by Windows did not complain that the iso was not contiguous but the Linux one did complain about the iso was not contiguous !!!
What's the magic on Windows?

Date 04/07/2019

By SteveSi

Subject Re: Why E2B drive created on Windows do not need to make contiguous?

Reply

My guess is that rsync opens several 'streams' and always makes fragmented files. e.g. a file will often be fragmented if you download it from the internet directly onto the USB drive using Windows because that also opens several streams.
Try to avoid rsync for copying files onto the USB drive or maybe try the -W option with rsync to copy whole files.
-W, --whole-file copy files whole (w/o delta-xfer algorithm)
or try the --preallocate switch which may also be faster when copying to a USB drive as well as making non-contiguous files. Let me know if this works...

Date 27/06/2019

By max

Subject make contiguous

Reply

hello, is the script "make contiguous" mandatory? I have never launched it and my key works perfectly ... What is it exactly for?

Date 27/06/2019

By SteveSi

Subject Re: make contiguous

Reply

Please use the site map first before asking questions on this Forum! There is also a search box you can use. This is explained on many pages, many times! The NTFS file system will always use 'virgin' free space first before it overwrites 'dirty' space from deleted files. When you copy a file to a volume which has been recently formatted the file will usually be contiguous. Once the drive has been 'filled' with files (i.e. a 32GB volume has had 32GB of files copied to it since it was last formatted), then there will be no large contiguous free spaces left and any newly copied files will be spread out over several blocks of free space and thus be non-contiguous.

Date 25/06/2019

By max

Subject legacy and uefi

Reply

Hello,
To boot easy2boot in uefi, I have to start a first time in legacy. I wanted to know if it's normal? If so, are future releases planned to work around this problem? I read that Intel could forget the legacy mode to have only bios 100% UEFI. Thanks!

Date 25/06/2019

By SteveSi

Subject Re: legacy and uefi

Reply

The new Intel UEFI-only BIOSes actually only restrict the INTERNAL disk to UEFI-only booting - they will still allow MBR-boot from external USB media (so they can boot to a DOS BIOS Flash program, for instance).
You can use SWITCH_E2B.exe first to switch in any .imgPTN file.
It is possible to UEFI-boot from an E2B drive BUT many BIOSes have bugs which means that a BIOS will always UEFI-boot from the E2B drive and will NEVER MBR-boot to the Legacy E2B menu even if you enable CSM in the BIOS Settings.
I recommend you look at http://www.easy2boot.com/add-payload-files/refind/ and eBook #3.

Date 24/06/2019

By max

Subject 128Go

Reply

Hello, is it problematic to use a hard drive with a partition greater than 128GB as recommended? Thanks

Date 24/06/2019

By SteveSi

Subject Re: 128Go

Reply

I recommend that the first partition does not exceed 128GiB because some BIOSes have a USB driver bug and cannot access sectors past 128GiB. If you use a BIOS which does not have this bug then you will be OK - if you use E2B on a wide range of systems then you are bound to find systems with this common bug and then you may not be able to boot to E2B or to boot certain ISOs\.imgPTN files, etc.

Date 26/06/2019

By max

Subject Re: Re: 128Go

Reply

ok, I understand. But with a 1TB hard drive for example, can I use the rest of the disk space to boot systems with easy2boot? Or can we really only use the 128GB? Thanks!

Date 26/06/2019

By SteveSi

Subject Re: Re: Re: 128Go

Reply

If you use the Easy2Boot install GUI download, it will make a 128GB NTFS partition for E2B and another NTFS partition to use the rest of the 1TB disk. You can store any files you like on the second partition.

Date 17/06/2019

By Carlos

Subject alphabetical

Reply

some page in alphabetical order, name application with extension and indicate if it is necessary to change extension to another one. But applications in alphabetical order

Date 17/06/2019

By SteveSi

Subject Re: alphabetical

Reply

QEMU can be used for menu testing and booting some 32-bit ISOs.

To change order use _nnn_ prefix, e.g.
_100_Ubuntu 64-bit.isodef
_200_Linux Mint 64-bit.isodef
_250_Blank_Entry.mnu
_300_Parrot.isodef

Date 14/06/2019

By Krauter_German

Subject Acronis Backup

Reply

Hello,
I need your help with a question:
I use Zalman ZM-VE500 and IODD-2541 to install Sysprep pre-installations via Acronis. This works on almost all systems.
Alternatively with E2B on Sandisk Extreme 256GB USB Stick ???
I thought I naiv a Acronis img.PTN with 10 GB to create and paste the split backup in the img.PTN as a folder. Can this generally work before I test, or is my idea stupid?

Date 14/06/2019

By SteveSi

Subject Re: Acronis Backup

Reply

Most people use a large E2B USB hard drive with two partitions:
Ptn1: E2B NTFS (16-128GB)
Ptn2: for images NTFS (rest of drive).
Then convert the Acronis ISO to a .imgPTN23AUTO file.
Put all your backup images on partition 2.
Not sure if this will work with Acronis and a Removable USB drive because it depends on what version of Windows they use, but as long as it is not older than 2 years, it should detect the 2nd partition OK.

Date 15/06/2019

By Krauter_German

Subject Re: Re: Acronis Backup

Reply

Hi,
Ptn1: E2B NTFS (16-128GB)
Ptn2: for images NTFS (rest of drive).
Then convert the Acronis ISO to a .imgPTN23AUTO file.
Put all your backup images on partition 2.
It also works with a Removable USB drive.
Tested on 3 PC, on 1 PC the images are not recognized.
In the alternative, I have inserted the images in the .imgPTNAUTO, they are recognized on all 3 PC. I will test if it is installed correctly in this variant. Then I think this is the more compatible option. Unfortunately a little more complicated.
Maybe it would be possible in the MPI Tool Pack to include an option to integrate additional folders.

Date 15/06/2019

By SteveSi

Subject Re: Re: Re: Acronis Backup

Reply

I am interested in the one that didn't work.
Was this UEFI booting or MBR booting?
You can copy images to the .\CUSTOM folder in the MPI folder and whenever you make a .imgPTN file, they will also be copied over. But they must be under 32GB because of the FAT32 partition size limitation imposed by Windows. If you use MPI_NTFS then they won't UEFI-boot.
Also, the E2B first partition must be under 128GB in size if you want to MBR-boot from the .imgPTN file.

Date 16/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Acronis Backup

Reply

Hi,
it was MBR booting.
But the PC on which the backup images were not found: it was the data partition that was visible to Windows. That is, on all three PCs, the E2B partition for Windows must be visible, otherwise it will not work on all 3 PC, which can be accessed in Acronis on the data partition.
With Windows 10 it is no problem if the EB2 partition is visible, because I still have access to the data partition.
With Windows 7 I want to access the data partition and boot E2B. Therefore, for me the solution of a .imgPTNAUTO file with integrated image of a pre-installation would be the max. 15GB is supported and UEFI (FAT32), the better choice.
For permanent backups, a USB Hard Drive is the better choice.

Date 16/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Acronis Backup

Reply

You can access the Data partition under Windows 7 using SWITCH_E2B.exe - 'Access partition 2 on Removable drive' button.
Copy SWITCH_E2B.exe to your Win7 system from the E2B drive and run it. You can then add/delete files from the DATA partition. You can then use the same button in SWITCH_E2B to switch back to view the E2B partition.

Date 13/06/2019

By SemperCoitus

Subject Windows Install Menu Not Showing Up

Reply

I noticed on v1.B1 and newer that when I built the drive and booted, when counting the windows install ISOs (before the main menu) it would get to XP (0) and then just jump to the main menu. Once in the main menu, I noticed that the "windows install" menu was missing entirely. After many hours of trying to fix this, I was able to fix it by replacing the file at _iso\e2b\grup\countfiles.g4b with a version from my old flash drive. My old file was dated 3/7/2016. I'm not sure if anyone else has had this issue, but just in case.

Date 13/06/2019

By SteveSi

Subject Re: Windows Install Menu Not Showing Up

Reply

Thanks for the report, I will look into it. Are there any ISOs present in any of the \_ISO\WINDOWS subfolders? If so, which ones and how many?
No one else has reported an issue and presumably they would not see any menu for any of the other windows folders. Can you think of why your E2B drive may be different? Any special files in the XP or VISTA folders or special extensions on the ISO files? Maybe you deleted the VISTA folder? Try E2B v1.B2e1 Beta.

Date 13/06/2019

By SemperCoitus

Subject Re: Re: Windows Install Menu Not Showing Up

Reply

I am using a SanDisk 256gb extreme 3.1 drive with a single NTFS partition. I have deleted all of the folders that I do not put ISOs in. The only folders left in the "Windows" directory are:
SVR2012 with 1 ISO
SVR2016 with 1 ISO
SVR2019 with 0 ISOs because I deleted it while testing.
Win7 with 2 ISOs
Win10 With 3 ISOs

I see where you're going with the deleted folders, but I also deleted the XP folder and it was showing up when counting ISOs. I tried v1b1 - 1b2d_beta with no luck. I'll try 1b2e1 and let you know. Also, is there a way to either remove the box around the menu, or make it clear?
Thank you
Jeremy

Date 13/06/2019

By SteveSi

Subject Re: Re: Re: Windows Install Menu Not Showing Up

Reply

OK - so that explains why no one else has reported a problem! It should be fixed in new beta.
Use the \_ISO\E2B_Editor.exe to configure the menu including the menu border width (0 for none).

Date 13/06/2019

By SemperCoitus

Subject Re: Re: Re: Re: Windows Install Menu Not Showing Up

Reply

Right again, sir! Everything works perfectly now. Next time I'm in the UK, I owe you many beers!

Date 12/06/2019

By Steffen

Subject PfSense Payloads

Reply

Hello Steve,
I tried to add a PfSense Memstick image (VGA - 2.4.4-RELEASE-p3) to my E2B following the following Guide:
http://www.easy2boot.com/add-payload-files/freebsd/
I created a .imgPTNA5 File with an empty folder and extracted and renamed the .img file matching the .imgPTN without any dots and file extension.
Afterwards I made the drive contigous and switched it in using the E2B menu. But I get only "Boot Error" when trying to boot. I looked at Switch_E2B and the images are recognized properly.
Did you have this Problem on your own or do you have any idea?
Thank you very much :)

Date 12/06/2019

By SteveSi

Subject Re: PfSense Payloads

Reply

Using pfSense-CE-2.4.4-RELEASE-p3-amd64.isoBSD (non-memstick ISO) MBR-boots OK. I will try the .imgPTN memstick image soon.
Do you want to UEFI boot or MBR boot?

Date 12/06/2019

By Steffen

Subject Re: Re: PfSense Payloads

Reply

I wanted to MBR Boot generally. I'm not sure if pfSense is generally bootable via UEFI. It would be interesting for future use cases but at the moment servers still support MBR Boot.

Date 12/06/2019

By SteveSi

Subject Re: Re: Re: PfSense Payloads

Reply

OK, well use the ISO file and a .isoBSD file extension.
For UEFI booting, use the memstick image and create some partition images as detailed in a blog article https://rmprepusb.blogspot.com/2015/03/adding-freebsd-freenas-pcbsdtrueos-to.html

Date 12/06/2019

By Steffen

Subject Re: Re: Re: Re: PfSense Payloads

Reply

I would need to MBR boot from the memstick-serial image because i have some appliances with only a serial port.
I will have a look for a workaround.
Thanks for your help :)

Date 13/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: PfSense Payloads

Reply

You did not say you needed to boot the Serial version!
I have added an extra menu to the blog instructions so you can MBR-boot from a memstick image as well. :-)

Date 14/06/2019

By Steffen

Subject Re: Re: Re: Re: Re: Re: PfSense Payloads

Reply

I just tested to boot to the memstick image. Works perfectly as described. Thank you for that :)

Date 10/06/2019

By Steffen

Subject Dualboot with PE Files on E2B_PTN2

Reply

Hello Steve,
My setup at the Moment is the normal E2B Partition with the E2B files and a second FAT32 Partition with the UEFI Bootfiles for WINPE. I have an aditional folder for tools and data on ptn2 so i would like to format ptn2 to NTFS to store files larger than 4 GB. The first option is to add refind into the payload files. And the other is to use the.imgPTNSWPEFAT32 file extension.
Could you explain me how that works? I haven't found a detailed description yet.
Thank you very much.
Greetings
Steffen

Date 10/06/2019

By SteveSi

Subject Re: Dualboot with PE Files on E2B_PTN2

Reply

Well if the 2nd partition is NTFS then you wont be able to UEFI-boot to WinPE immediately. Also, if you add refind to the images you wont be able to secure boot. If you use .imgPTNSWPEFAT32 file then you can UEFI secure boot but you will have to switch it in.
Another solution is to have 3 ptns. NTFS,FAT32,NTFS. With FAT32 holding WinPE files. The problem with this is that you cant use Legacy booting of Linux ISOs with persistence because the 3rd partition is in use (but you could convert the linux to a .imgPTN file and use a 2nd image file as the persistence partition).
This is all explained in my eBook #3 - Chapter 9 ;-)

Date 10/06/2019

By Steffen

Subject Re: Re: Dualboot with PE Files on E2B_PTN2

Reply

Hey Steve,
thank you for your quick answer. I knew about the problems with the third partition and Linux with persistence thats the reason i wanted to avoid it. Thats the reason i asked about the imgPTNSWPEFAT23 file extension because i didn't know how it works.
I think I will try the linux distro as .imgPTN and add a second image File for persistence.
Thanks for your help :)

Date 10/06/2019

By SteveSi

Subject Re: Re: Re: Dualboot with PE Files on E2B_PTN2

Reply

Not quite sure what you mean (do you mean .imgPTNX4 file extension?), but you can always contact me using live chat.
e.g. FRED.imgPTNX4DORIS will replace ptn 1 with this file and will also add in Partition 4 using another file \_ISO\DORIS which is also a partition image. So DORIS could contain a FAT32 partition with WinPE files and FRED.imgPTNX4DORIS could contain FAT32 UEFI files for linux or whatever payload you wish to boot to.

Date 12/06/2019

By Steffen

Subject Re: Re: Re: Re: Dualboot with PE Files on E2B_PTN2

Reply

Ahh okay now I understand what this extension is for. Thank you :)

Date 06/06/2019

By ocean55

Subject RAID controller

Reply

Hello All,
I am working on a specific project that I am having trouble with and was wondering if I could obtain some advice.
I have a system that contains a SIL3114 Raid controller. This controller has 2 Samsung 1Tb SSDs that are striped.
The system has ESXi installed on a 1Tb drive and has one VM (so far) that is Windows 10.
The SIL3114 controller is PCI-Passthrough’d to the Win10 machine.
I then cloned the Win10 virtual disk to the stripe and want to be able to boot to it.
The problem is that in ESXi‘s virtual BIOS, the raid controller is not seen because the passthrough doesn’t happen until after the virtual machine has booted, so I cannot set it in the boot order.
A trick for this is to create another virtual hard drive, and install either E2B or Clover or AIOBOOT and have it automatically then boot the VM to the stripe.
The problem is that I cannot seem to figure out how to get any of these boot loaders to contain the right driver for the SIL3114 so it can be seen and then have it as the bootable drive.
Any advice would be much appreciated!

Thank you!!
-=oCeAN=-

Date 06/06/2019

By SteveSi

Subject Re: RAID controller

Reply

Why not install win10 boot files on another virtual disk. Then configure it to load bootmgr and configure the BCD to load the Win10 on the striped disks?
You should be able to boot from a Win10 install ISO as a virtual DVD and then use repair\troubleshooting or BCDBOOT to add in the boot files.

Date 04/06/2019

By Dick

Subject New Version 1.b1 and Acronis

Reply

I created a new USB drive with v1.b1 and added all my ISO's that have worked perfectly under v1.a6 and V1.a9.
I booted the new USB fine, but when I try to start Acronis TI it just says "Starting Acronis Loader" and never completes. Assistance please.

Date 04/06/2019

By SteveSi

Subject Re: New Version 1.b1 and Acronis

Reply

Try it on a different system or under a VM.
You can downgrade to one of the previous E2B versions (just click on 'update button' in the GUI of a previous version) and see if the problem goes away.
If the USB drive is brand new, I would test it with FakeFlashTest.

Date 04/06/2019

By Dick

Subject Re: Re: New Version 1.b1 and Acronis

Reply

I have tried it on 2 different systems and it fails on both. I created another USB with V1.a9 and same Acronis ISO and that works fine. The Acronis version is 2016. If I can find a 2019 Acronis iso, I will try that on V1.b1

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: New Version 1.b1 and Acronis

Reply

OK, so it is not the target system at fault.
Could it be the flash drive is bad? Is it new? Did you test it? Is the ISO checksum correct?

Date 04/06/2019

By Dick

Subject Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

I used both a new flash and updated an old flash from 1.a9 to 1.b1. Both fail the same. I will download and run fakeflashtest on the new flash and then recreate it. Since 1.a9 still works I will keep that flash drive around till the issue with 1.b1 is resolved. I will also test my other payload files to insure they all still work under 1.b1. I will update this thread as I test.

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

2016 and 2019 both work fine for me with E2B v1.B2b. No one else has yet reported an issue.
Maybe it is a strange issue with the new grub4dos (\grldr)?

Date 04/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

As stated earlier, I had an older flash drive using v1.a9 that up updated to 1.b1 and that drive fails also. That particular drive has been in use for over a year with no issues. To me, the only thing that has changed is the new 1.b1 version.

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

well, you would need to test the same flash drive on the same system. Try an earlier version and then update to 1.B1 and then downgrade to the earlier version again so nothing changes except E2B and the position of the files on the USB drive.
QEMU MENU TEST will boot TI 2016 OK so you can try that too to remove any target system issues.
v1.B1 works OK for me.

Date 04/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

I ran QEMU menu test and it fails there using v1.b1. I have a v1.A9 version flash that works. I will update that to 1.b1, test, and then downgrade again to 1.A9 and test again. Heading to work. Will be back in about 6 hours.

Date 04/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Booted new flash drive created with V1.A9. Boots ok.
Ran Qemu and Acronis loads.
Rebooted 1.A9 flash drive again and selected Acronis to load - loads ok.
Used 1.B1 to update same flash drive.
Booted 1.B1 flash - boots ok.
Tried to load Acronis - just hangs.
Rebooted 1.B1 flash and loaded Kyhi Rescure with no issues - loads ok.
Downgraded same flash drive to 1.A1.
Booted 1.A1 flash - boots ok.
Loaded Acronis - loads ok.
Did not run FakeFlashTest as drive appears ok.

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Thats really odd.
Can you update to 1.b1
check it fails to boot TI
Then change the \grldr file to the one used in 1.A1.
If that still fails, change the \_ISO\e2b\grub\QRUN.g4b file to the 1.A1 version too. Thanks.

Date 05/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Progress!!
Booted 1b1 and tried TI - fails.
renamed grldr on flash to 1b1gldr.
copied grldr from 1a9 to flash.
Booted 1b1 flash with 1a9 grldr and loaded Ti with success.

Date 05/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Could you update to E2B v1.B2c and try it please?
If it doesn't work, can you try various versions of 0.4.6a working back from the latest version. Just extract the grldr file from the zip file and replace the one on the E2B root folder.
http://grub4dos.chenall.net/
I will report to the developers if we can narrow it down to a version change.

Date 05/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Updated to 1.B2c
Ran Qemu to attempt TI load - fail.
Downgraded grldr to 190325
Tested again - Success.
All after 190325 (190507 and 190512) fail

Date 05/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

That's great! Good work!
The only thing now is that I cannot reproduce the problem. So could you tell me the checksum (MD5\CRC32,SHA1 or whatever) of your ISO and where I can obtain it (so I can download it - you can email me if you prefer at [email protected]).
I will then reproduce the issue using QEMU and raise an issue report for it.
P.S. In E2B - have you selected a different keyboard translation file (not QWERTY USA)? If so, which one are you using (see \_ISO\MyE2B.cfg KBD setting and try removing that line so USA kbd is used).
I have tried 5 different versions of 2016 ISOs and they all work.

Date 05/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

I don't have a checksum for the ISO, but if you mean I should create one, I can do that. I am uploading the ISO to Mega at the moment. Once upload, I will send you a link to the file. On the way to work, will send link on return.

Date 09/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Please try latest grldr file - it seems to work
http://grub4dos.chenall.net/downloads/grub4dos-0.4.6a-2019-06-09/
Should be fixed now in E2B v1.B2e Beta or later.

Date 22/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

The date of your posts is incorrect. Where is the latest beta (v1.B2e) so that I can download and test. Thanks

Date 22/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

v1.B2 is the latest version.
(v1.B2e was a previous Beta.)

Date 23/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

I downloaded and tested the latest v1.B2 and all is good now. TI loads correctly. Thank you for your quick and excellent help to resolve this.

Date 02/06/2019

By Krauter_German

Subject 137GB BAD BIOS BUG

Reply

Hello,
I use a Sandisk Extreme Pro 256GB. The first partition NTFS 114Gb for E2B_v1.B2b and a second primary partition NTFS 123GB for data.
1. Dell Workstation T3500 with Windows 7. Data partition visible to Windows 7. Boots from E2B without problems.
2. PC with Asus P6T SE socket 1366 and Windows 7. Data partition visible for Windows 7. Booting E2B with Note: e2b.cfg is corrupt or missing, enter. Note: BIOS Bad (possible 137GB BIOS limt?). Warning: THIS BIOS MAY HAVE PROBLEMS ACCESSING SOME FILES ON THIS DRIVE!
Then the option click U and load USB 2 driver (something like that), then the E2B menu appears.
The first partition for E2B has significantly less than 137GB and still this error appears. Can one ignore this message or do some files not work?
Before I had E2B partition 100GB and data partition 137GB.
RMPrep CTRL-O-2 makes data partition visible but under Windows 7 E2B partition was still visible.

Date 02/06/2019

By SteveSi

Subject Re: 137GB BAD BIOS BUG

Reply

If you load the USB driver (U) OK, then there will be no problem.
If no USB driver, then you will not be able to access files past 128GB on the drive. So E2B\grub4dos will not be able to access some files on the 2nd partition using the BIOS (no problem once booted to Windows). So in your case you can ignore the message.
E2B does not know if you have ISOs etc. on 2nd partition.
But the e2b.cfg file is corrupt or missing message is a bit worrying... not sure why you see that!
Can you use RMPrepUSB - Drive Info - 0 to view partition table - maybe you have accidentally installed E2B to the last partition?

Date 04/06/2019

By Krauter_German

Subject Re: Re: 137GB BAD BIOS BUG

Reply

Hello,
I've tested even further: first partition 99GB E2B, second partition 99GB DATA, the remaining capacity unallocated. DATA partition for Windows 7 made visible and booted. e2b.cfg is corrupt or missing does not appear. Note: BIOS Bad (possible 137GB BIOS limt?). Warning: THIS BIOS MAY HAVE PROBLEMS ... will continue to appear. Then I installed with Easy2Boot_v1.B1.exe, EB on the USB stick, deleted the second small partition with EASEUS and a second primary data partition with the remaining capacity erstellet, created PBR and MBR. DATA partition for Windows 7 made visible and booted. e2b.cfg is corrupt or missing appears, Enter, Note: BIOS Bad (possible 137GB BIOS limt?). Warning: THIS BIOS MAY HAVE PROBLEMS ... will continue to appear. E2B partition for Windows 7 made visible and booted: e2b.cfg is corrupt or missing does not appear. Message:
Booting Easy2Boot v1.A9-please wait ...
Using settings in /-ISO/MyE2B.cfg
Using settings from / _ISO / e2b / grub / German / Strings.txt file
BIOS 09/21/10
Last Sector of last partition of (hd0) is 500170748 (238GB)
Checking (HD0) sector 500170494 is accessible ...
BIOS BAD (possible 137GB BIOS limit?)
Warning: This BIOS MAY HAVE PROBLEMS ...
On an AM4 board with Ryzen and Windows 10, there are no problems. On Dell Workstation with Socket 1366, XEON and Data Partition visible for Windows 7, there is also no problem booting E2B. On ASUS Board, Socket 1366, I7 960 witerhin the symptoms described above. Maybe you think of something else.
Incidentally, yesterday I received the download link for the purchased eBooks, a big compliment for a great job.

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: 137GB BAD BIOS BUG

Reply

So to sum up:
ASUS P6T
1.A9 99GB+99GB SWAP >> BIOS BAD
1.B1 99GB+400GB NO SWAP >> BIOS BAD
1.B1 99GB+400GB SWAP >> BIOS BAD + e2b.cfg is corrupt
1.B2b 114GB+123GB SWAP >> BIOS BAD + e2b.cfg is corrupt

I think the e2b.cfg message is caused by a change I made in v1.B1 and 1.B2b. E2B v1.B2c should fix this - please try it.

Since the last partition is always past 137GB, you will always see the BIOS BAD message on the P6T because it has a bad BIOS!

Date 05/06/2019

By Krauter_German

Subject Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Hello,
I have E2B 1.B2c installed but unfortunately no change:
1.B2c 125GB + 113GB SWAP >> BIOS BAD + e2b.cfg is corrupt.
I think it's very difficult to make all bios (especially older ones) compatible with E2B. For these cases, it is probably advisable to use a USB stick with max. 128GB to use.

Date 05/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

But according to your report, the behavior of the two E2B versions is different:
1.A9 99GB+99GB SWAP >> BIOS BAD
1.B1 99GB+400GB SWAP >> BIOS BAD + e2b.cfg is corrupt
??? I don't understand why you see the e2b.cfg error message ???

Date 05/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

1.B2b 114GB+123GB SWAP >> BIOS BAD + e2b.cfg is corrupt
1.B2B 99GB+99GB remaining capacity unallocated SWAP >> BIOS BAD

v1.B1.exe 127GB+111GB SWAP >> BIOS BAD + e2b.cfg is corrupt,
If e2b is visible for Windows 7, the message Bios Bad appears.

Date 08/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Hello,
I came to a conclusion.
I have tested with v1.89, v1.A9, v1.B1 and v1.B2c.
The E2B partition must not be larger than max. 99GB.
Then no version will show e2b.cfg is missing or corrupt.
V1.89, v1.A9, v1.B1, v1.B2c 99GB + 138GB SWAP >> BIOS BAD
Interested for you? : If E2B partition in v1.89 greater than 99GB,
I get more information.
Message: Fatal! Inconsistent data read from (0x80) 354345113 + 127
Fatal! Inconsistent data read from (0x80) 354345232 + 2
Error: No such command: ... progamming code? ...
e2b.cfg is missing

Date 08/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

So it will depend on the size of both the first and second partition and where each partition starts. What are the sizes and start positions of the two partitions?
The limit should be 128GiB (or 137GB).
So are you saying a 110GB first partition behaves differently from a 99GiB partition? The start sector of the partition is important not just their size. Even if your 2nd partition is only 3GB but starts at the end of the drive, it will fail.
What folders/files are on the 2nd data partition?

Date 08/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

EaseUS shows for E2B partition:
First Physical Sector: 2048 (Cyl: 0, HD: 32; Sect: 33)
Last Physical Sector: 206551039 (Cyl: 12857, HD: 52, Sect: 59)
All physical sectors: 206548992 (98,49GB)
DATA partition:
First Physical Sector: 206551040 (Cyl: 12857, HD: 52; Sect: 60)
Last Physical Sector: 500170751 (Cyl: 31134, HD: 48, Sect: 18)
All physical sectors: 293619712 (140,01GB)
For testing, the second data partition was empty

Date 08/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Is the Last Physical Sector: 500170751 (Cyl: 31134, HD: 48, Sect: 18)
the very end of your drive (check with RMPrepUSB - Drive Info - 0)? If so you may get errors. You should always leave the last 1MB of a drive unused for best BIOS compatibility. EaseUS Partition Master has a bad habit of using right up to the very last sector of a disk which can cause problems (grub4dos nnn + 127 error messages).
I cannot reproduce the '/_ISO/e2b/grub/E2B.cfg is MISSING or CORRUPT! Press ENTER to continue...' message. I used a 119GB E2B partition and a 119GB DATA partition and swapped them over using RMPrepUSB Crtrl-O and then tested it on an EeePC which has the 128GB USB BIOS bug. I got the BAD BIOS message but not the E2B.cfg message. Strange.. I don't know why you get this message...

Date 10/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Hello,
I have recreated the USB stick:
First partition E2B 119GB, second partition DATA 119GB.
DATA partition created with AOMEI Partition Assistant:

First Physical Sector: 2048 (Cyl: 0, HD: 32; Sect: 33)
Last Physical Sector: 250591231 (Cyl: 15598, HD: 148, Sect: 38)
All physical sectors: 250589184 (119.49GB)
DATA partition:
First Physical Sector: 250597935 (Cyl: 15599, HD: 0, Sect: 1)
Last Physical Sector: 500166655 (Cyl: 31133, HD: 238, Sect: 17)
All physical sectors: 249568721 (119,00GB)

RMPrepUSB_Drive Info:
Disk Signature bytes (1B8h-1BBh) = 21 E0 A7 AC

Partition 1 SIZE = 121859,727MB Type: 07 NTFS
START POS = CYL: 1023 HD: 254 SEC: 63 END POS = CYL: 1023 HD: 254 SEC: 63
START (LBA) = 250,597,935 (0EEFD22F) SIZE (LBA) = 249,568,721 (0EE01DD1) [End = 500,166,655]

Partition 2 SIZE = 122358MIB Type: 07 NTFS * ACTIVE *
START POS = CYL: 0 HD: 32 SEC: 33 END POS = CYL: 1023 HD: 254 SEC: 63
START (LBA) = 2.048 (00000800) SIZE (LBA) = 250,589,184 (0EEFB000) [End = 250,591,231]

P1 start = 250,597,935 (128,306,142,720 bytes) end = 500,166,655 (256,085,327,360 bytes)
P2 start = 2,048 (1,048,576 bytes) end = 250,591,231 (128,302,710,272 bytes)

Drive 6 SanDisk Extreme Pro F / W Rev. = 0 Serial No. = [bytes = 00 00 00 00 00 00 00 00]
Reported size 256,087,425,024 bytes (238.5GiB) Last LBA 500,170,751
RMPrepUSB Max 256,077,642,240 bytes (238,4908GiB) Last LBA 500,151,644
Is that how it should be?

I got the BAD BIOS message but not the E2B.cfg message :-)
This ASUS P6T board has another peculiarity.
On the USB port of the rear panel:
When I click USB Driver U I briefly see the message:
Error 81 No USB Drive found, USB Drive enumeration failed.
On the front panel: USB found.
Tested with 2 SanDisk Extreme Pro 256GB.
It is crazy but the e2b.cfg message does not appear anymore.

Date 10/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Thanks for re-testing. That is what I expected and yes, the unused sectors at the end of the drive is prudent.
The P6T has two USB controllers (6+6 USB 2.0), so I guess one is compatible with the grub4dos USB driver code and the other controller is not.

Date 10/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Thanks for your help and great respect for your tremendous knowledge.

Date 28/05/2019

By Batfink

Subject UEFI

Reply

Wow, Ok, So i had visions of sugar plums dancing in my UEFI menu, Launching Windows10 Pe's of my making, Modified Pe's, UEFI friendy password changers, UEFI friendly cloning software etc.
Not so Huh ;)
It's very picky, I've even tried cheating and extracting ISO's, renaming the UEFI payloads and booting them extracted and compressed and it's given me no love.
You're almost better off making a huge UEFI capable windows 10PE with every portable tool you can think of (Which I've done on the MBR one and can just burn as UEFI).
Not a criticism, just sharing what I've discovered, I definitely appreciate what you've built here.
I think the only thing I'll miss in a Windows 10PE is MEMtestX86, I know it can be booted as UEFI, but having it as a boot option prior to the Windows 10PE UEFI booting is still eluding me (Not a question, just a ponder) hmmm

Date 28/05/2019

By SteveSi

Subject Re: UEFI

Reply

There is no multiboot UEFI menu unless you use the E2B grub2 menu system which is limited.
Except for grub2 and syslinux-EFI with some linux ISOs (which are limited in what they can do), EFI booting requires the files to be in a 'flat-file' structure. This means you cannot have two OS's with the same files/directories on the same partition.
The E2B grub2 menu will let you have multiple PEs and linux's in a large menu, but you basically have to hand-craft each menu entry. There is no simple automatic or even semi-automatic way.
WinSetupFromUSB may be a better option for UEFI for you (mainly Windows-based source files) but it is limited too.
The MBR CSM menu can be customized and have animations, etc. using grub4dos commands and you can put the mods in the CUSTOM folder so that any new .imgPTN file you make will look the same.
The latest UEFI eBook #3 describes how you can add MemTest86 (or most other EFI small payloads) into your main UEFI .imgPTN file and includes URLs to ready-made UEFI files.
The .imgPTN solution allows you to Secure Boot from any signed UEFI payload or from a very wide range of other UEFI payloads (just not all from the same menu at the same time).
By adding a 2nd FAT32 partition containing a UEFI-bootable WinPE (see UEFI eBook #3 which includes download URLs for required WinPE files) you can boot on a pure UEFI system and choose any .imgPTN file that you want to boot to.
P.S. Latest BETA files in Alternate Download Area have improved E2B_Editor and MakePartImage CSM menu functions (see Change History for details).

Date 28/05/2019

By Batfink

Subject Re: Re: UEFI

Reply

That's actually what I've done as an experiment .. The dual partition usb stick.. *sigh*, I suppose I could use it primarily for mbr like the pictures I've shown you, replicating that to a new dual partition stick isn't a problem and then keep MEMTESTX86 and a few other maybe useful apps that are on the excel list in the efi partition... But ultimately as you said the items on the Excel list have limited functionality depending on your needs... Looking at the list there's almost nothing there I can't do on a UEFI secure boot enabled Windows 10pe.
Ultimately I was going to use two usb sticks anyway, even though your dual partition supports mbr grub I was going to ignore it and have one for mbr and one for uefi.
I know I can do the whole change a single file to imgptn, boot from it and then change it back, but by then I could have booted a winpe environment in the same length of time it takes to change it to imgptn and back again.
Just out of curiosity, which of the Linux uefi payloads on the list contains a MEMTESTX86 option in its menu before it boots the Linux.

Date 28/05/2019

By Batfink

Subject Re: Re: Re: UEFI

Reply

Sorry, I was just rereading the last bit of your message, so I can have the GRUB mbr menu on the first partition and a UEFI WINPE System and boot any imgptn file... Does it have a menu system or does it boot to a Windows desktop?

Date 28/05/2019

By Batfink

Subject Re: Re: Re: Re: UEFI

Reply

If it boots to a WINPE quick select sort of menu then I'll look at the books, I presume I need books 1&3, if it boots to a windows desktop and uses that as a launcher, I've got win pe environments that can already do everything I need, really I wanted a nice easy to select menu that comes up very fast (obviously not as fast as grub since it's a PE) but something with some kind of selectable menu.. Is there a place I can look at what it looks like or see it working.
Haha I'll stop bothering you now... I appreciate all your help.

Date 28/05/2019

By SteveSi

Subject Re: Re: Re: Re: Re: UEFI

Reply

The E2B grub2 menu system uses two partitions, the first is a .imgPTN file with grub2. The second is your existing 2nd partition which can contain linux ISOs, etc. (as well as your WinPE boot files, etc.)
http://www.easy2boot.com/uefi-grub2-ptn2/
The WinPE UEFI 2nd ptn just allows you to run SWITCH_E2B to choose a .imgPTN - you then need to reboot. Use the SITE MAP!
http://www.easy2boot.com/add-payload-files/refind/

Date 26/05/2019

By Batfink

Subject Fastload Caching menu spacing

Reply

Hahaha I hate asking for your help, I feel i should be able to work it out myself but out of all the things I've built this USB stick to do, Your menu is always the hardest thing for me :) .
Is there a way when you enable FASTLOAD.YES to not be directly under the bottom menu option.
https://imgur.com/6tPp528
This link shows the top one as it looks by default, and the bottom one is a photoshop i made to ask if it can be done to look like that or something along those lines.
As soon as I find out if this is written in stone or can be spaced out a bit I've finished my legacy stick, Then I'll be moving on to the UEFI...SMH hahaha I don't even know where to start.

Date 26/05/2019

By Batfink

Subject Re: Fastload Caching menu spacing

Reply

Oooops sorry, I thought the two pictures would appear in the same link.
https://imgur.com/u0mmtaB
This is the photoshop one.

Date 26/05/2019

By SteveSi

Subject Re: Re: Fastload Caching menu spacing

Reply

Hi
FASTLOAD is controlled by \_ISO\MAINMENU\ZZSubMenuAll.mnu
If you look at the start it has
# --- FASTLOAD ---

iftitle [if not exist CD && if not exist NOFLDMNU && cat --locate=NO ()/FASTLOAD.YES > nul] $$STRhMFE
# use current menu
echo YES > /FASTLOAD.YES && set MFOLDER=/_ISO/MAINMENU
# update cached menu file
cat (md)0xa000+0xA0 > /_ISO/e2b/grub/FASTLOAD.MNU
configfile (md)0xa000+0xA0

iftitle [if not exist CD && if not exist NOFLDMNU && cat --locate=YES ()/FASTLOAD.YES > nul] $$STRhMFD
# Disable fastload
echo NO > /FASTLOAD.YES && set MFOLDER=/_ISO/MAINMENU
configfile /_ISO/e2b/grub/menu.lst

# --- FASTLOAD STATUS INDICATOR

iftitle [if not exist NOFLDST if exist STALE && cat --locate=YES ()/FASTLOAD.YES > nul] $$STRmFS1
if not "%GFX%"=="" configfile (md)0xa000+0xA0
root ()

So NOFLDMNU will stop the menu entries from appearing
However the Status indicator line is suppressed by NOFLDST.
So if you use
set NOFLDMNU=1
set NOFLDST=1
in your MyE2B.cfg file, then it should suppress them.
Now if you want to add your own .mnu file for Fastload, then copy these lines and change them as you wish.
Obviously, you will need to remove the 'if not exist NOxxxxxx' bit or they won't display!
http://www.easy2boot.com/speeding-up-e2b/
(Tip: Use the Search box and search for FASTLOAD if you want to find out about FASTLOAD - or - look in Sample_MyE2B.cfg for all possible settings ;-)

Date 26/05/2019

By Batfink

Subject Re: Re: Re: Fastload Caching menu spacing

Reply

Thank you Sir, You are a gentleman and a scholar, That worked perfectly.
The problem is I'm a computer technician, not a programmer.

Date 25/05/2019

By Krauter_German

Subject Multiple partitions

Reply

Hello, I still have a USB stick with Easy2Boot v1.89 and a second primary partition for data. If I make the data partition visible in Windows 7 with RMPrep Ctrl-O-2 I can still boot from e2b. This no longer works with the newer Easy2boot versions and ends with an error. Only after restart can then be booted from the E2B partition.
With Windows 10, it does not matter because both partitons are recognized.
Since Windows 7 is still very common it makes sense to use the data partition but to boot from e2b. Can this feature be integrated into the new e2b version?

Date 25/05/2019

By SteveSi

Subject Re: Multiple partitions

Reply

I don't see how it can have worked? When you boot to Windows 7 Setup, the Win7 ISO will be on the 2nd partition which is inaccessible to Windows 7 PE and so it will not be able to find the ISO.
1. Can you retest with v1.89 and confirm you can fully install from a Win 7 ISO.
2. What is the exact error message that you get with E2B v1.B1?
3. You say after running RMPrepUSB Ctrl-O you must do a reboot before it will boot to the E2B menu. So how are you managing to run RMPrepUSB and then boot to E2B without rebooting the PC?

Date 25/05/2019

By Krauter_German

Subject Re: Re: Multiple partitions

Reply

Hello, Maybe I have expressed myself inaccurately by the bad English. I have 2 Windows 10 PC and a Windows 7 PC. The USB stick with Easy2boot v 1.89 and visible data partition can boot on the Windows 7 PC, Easy2boot and I can use Acronis, Aomei, Easeus or other software, all imgPTNAUTO files.
The Windows 7 install imgPTNAUTO will start to select the partition selection for the installation, then I canceled.
I can later gladly install for testing on other SSD completely.
If I use another USB stick with Easy2boot v 1.B0A on the Windows 7 PC with visible data partition, Acronis, Aomei ... imgPTNAUTO in the main menu can not be executed.
(hd0,0) EASEUS_PART_ASSIST__13.5_PE.imgPTNAUTO
root ()> nul
ERROR 22: (http://grub4dos.chenall.net/e/22) No such partition
Press any key to continue ...

Date 25/05/2019

By SteveSi

Subject Re: Re: Re: Multiple partitions

Reply

ah, OK. So you are saying that switching to a .imgPTNauto file when the two partitions are switched produces an error.
I think this is now fixed in todays version of E2B v1.B2b in the Alternate Download Area. Please update your E2B drive to it and try again.

Date 25/05/2019

By Krauter_German

Subject Re: Re: Re: Re: Multiple partitions

Reply

Yeah, it's working perfectly.
Many thanks and best regards

Date 19/05/2019

By Batfink

Subject Space after Subdirectories

Reply

I've been beavering away at this for ages, modding PE Windows, 7Zip compressing executables etc and I'm finally close to finishing the Legacy version (haha haven't even started the UEFI version), But for the life of me I can't figure out if there is a way to put a space after a Sub Dir, especially between the F8 to rebuild the main menu...I know I can turn it off, but i actually want to keep it.
Menu's 23,24,25 & 26 are sub menu's, is there a way to put a space between Menu 26 and the F8 menu below it.
https://imgur.com/acOYAYi
Many Thanks for making such a great menu system, I've been able to get things to work that I've never had working before.

New comment

There is a LOT of information on this site which should cover all common questions and problems - please use the Site Map to find the page you need.

For specific problems, it is much easier for 1-to-1 communication to use the Contact Me form and I will reply via email.