Please wait...
This page has a different format from the other site pages and has hardly any adverts!
Support my work and donate £5/$8 (English GBP/US Dollars) or more (bitcoins also accepted) to see all pages on www.easy2boot.com and www.rmprepusb.com in a similar format.
Support my work and donate £5/$8 (English GBP/US Dollars) or more (bitcoins also accepted) to see all pages on www.easy2boot.com and www.rmprepusb.com in a similar format.
Please don't block ads on this site!
Blog 
This Site has over 150 pages!E2B Users Forum
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 (in English please).
Topic: Easy2Boot
Cannot boot Linux ISOs with persistence.
Hello! I've been trying to boot Linux ISOs (Xubuntu 16.04.3 i386 and KDE Neon amd64 in particular) with persistence, but i get an error message that says the the persistence file was not found.
I'm running the latest E2B release, 1.A9 and using an edited ubuntu-13.04-desktop-i386_Persistent.mnu file from the sample mnu files folder where i changed the ISO and persistence file paths accordingly.
I created a 1024 MB persistence file using Make_Ext.exe at the root of my flash drive, named it "neon-rw" for KDE Neon but while trying to boot it says the neon-rw persistence file was not found. I even tryed moving the neon-rw file inside the MNU folder and changing the set PF line to set PF=$HOME$/neon-rw, but it still said persistence file was not found.
The ISO files are detected fine, before showing the error message, it says the file system is joliet. Also, both ISO files boot fine without persistence. My flash drive is formatted NTFS.
I'm running the latest E2B release, 1.A9 and using an edited ubuntu-13.04-desktop-i386_Persistent.mnu file from the sample mnu files folder where i changed the ISO and persistence file paths accordingly.
I created a 1024 MB persistence file using Make_Ext.exe at the root of my flash drive, named it "neon-rw" for KDE Neon but while trying to boot it says the neon-rw persistence file was not found. I even tryed moving the neon-rw file inside the MNU folder and changing the set PF line to set PF=$HOME$/neon-rw, but it still said persistence file was not found.
The ISO files are detected fine, before showing the error message, it says the file system is joliet. Also, both ISO files boot fine without persistence. My flash drive is formatted NTFS.
Carlos
20/03/2019
Re: Cannot boot Linux ISOs with persistence.
Can you post here the exact line that you used for the PER line in the menu?
Also check that the file exists by booting from the E2B drive and use the utilities menu to list the root directory files.
Also test the menu using the test_using_qemu CMD file under Windows.
Also check that the file exists by booting from the E2B drive and use the utilities menu to list the root directory files.
Also test the menu using the test_using_qemu CMD file under Windows.
Stevesi
20/03/2019
Re: Re: Cannot boot Linux ISOs with persistence.
I've put the KDE Neon ISO, edited MNU file and neon-rw file inside /Linux/MNU folder. Using the ls dir command from the utilities menu lists the 3 files correctly.
The lines i used for the MNU files are the following:
"set ISO=$HOME$/xubuntu-16.04.3-i386.iso"
and
"set PF=$HOME$/neon-rw"
Both without quotation marks.
The lines i used for the MNU files are the following:
"set ISO=$HOME$/xubuntu-16.04.3-i386.iso"
and
"set PF=$HOME$/neon-rw"
Both without quotation marks.
Carlos
20/03/2019
Re: Re: Re: Cannot boot Linux ISOs with persistence.
see below...
SteveSi
20/03/2019
Re: Re: Re: Re: Cannot boot Linux ISOs with persistence.
P.S. You said that you were using ubuntu-13.04-desktop-i386_Persistent.mnu
Well that mnu file uses PER not PF!!!
...
set ISO=$HOME$/ubuntu-13.04-desktop-i386.iso
set PER=/ubuntu1304-rw
Well that mnu file uses PER not PF!!!
...
set ISO=$HOME$/ubuntu-13.04-desktop-i386.iso
set PER=/ubuntu1304-rw
SteveSi
20/03/2019
How do I install W7 & W10, as Dual-Boot OS's?
I've built a new PC.
I want to be able to Dual-Boot by installing W7 & W10,
preferably by installing each of them into their own GPT partition on one HDD.
So can I install each of these OS from their original install DVD's ?
And what should my BIOS settings be ?
I seem to getting issues, so could you provide a detailed guide as to how to do this?
Hoping you can help,
Many thanks.
I want to be able to Dual-Boot by installing W7 & W10,
preferably by installing each of them into their own GPT partition on one HDD.
So can I install each of these OS from their original install DVD's ?
And what should my BIOS settings be ?
I seem to getting issues, so could you provide a detailed guide as to how to do this?
Hoping you can help,
Many thanks.
mac
08/03/2019
Re: How do I install W7 & W10, as Dual-Boot OS's?
Hi
First convert each ISO to a .imgPTN file and add the two files to the E2B drive.
Then UEFI-boot from the Win7 x64 .imgPTN file (after switching it in) and install Win7.
Then reduce the OS partition to make room for the Win10 OS.
Then boot to the Win10 .imgPTN file (after switching it in) and install Win10.
Note that to make the Win7 imgPTN bootable you will need to add the bootx64.efi file - see http://www.easy2boot.com/add-payload-files/win7-uefi/
Also note that Win7 is very old and does not contain drivers for USB 3 - so you may have problems installing Win7 from a USB drive!
or you could always read my eBook... ;-)
First convert each ISO to a .imgPTN file and add the two files to the E2B drive.
Then UEFI-boot from the Win7 x64 .imgPTN file (after switching it in) and install Win7.
Then reduce the OS partition to make room for the Win10 OS.
Then boot to the Win10 .imgPTN file (after switching it in) and install Win10.
Note that to make the Win7 imgPTN bootable you will need to add the bootx64.efi file - see http://www.easy2boot.com/add-payload-files/win7-uefi/
Also note that Win7 is very old and does not contain drivers for USB 3 - so you may have problems installing Win7 from a USB drive!
or you could always read my eBook... ;-)
SteveSi
08/03/2019
Re: Re: How do I install W7 & W10, as Dual-Boot OS's?
Hi Steve,
Many thanks for your reply, seems like a great website!
I'm new to these problems, so I have a few queries & questions:
Q1: Firstly, I was told that installing W7 & W10 with UEFI enabled in my BIOS
would 'Cause Problems' because W7 was developed B4 UEFI ?
Q2: Also, Do I need UEFI enabled in my BIOS ?
Q3: What exactly do I need to 'SET' in my BIOS ?
And in your reply you said...
First convert each ISO to a .imgPTN file
(Q4: How do I do that? *)
...and add the two files to the E2B drive.
Then UEFI-boot from the Win7 x64 .imgPTN file (after switching it in)
(Q5: * after switching it in * So how do I do that ?)
...and install Win7.
...Also note that Win7 is very old and does not contain drivers for USB 3 -
so you may have problems installing Win7 from a USB drive!
(Q6: * Win7 does not contain USB 3 drivers * So can I use USB2 ?)
...or you could always read my eBook... ;-)
(Q7: Does that explain everything in more detail ? If so where's the link ? )
Many thanks
Many thanks for your reply, seems like a great website!
I'm new to these problems, so I have a few queries & questions:
Q1: Firstly, I was told that installing W7 & W10 with UEFI enabled in my BIOS
would 'Cause Problems' because W7 was developed B4 UEFI ?
Q2: Also, Do I need UEFI enabled in my BIOS ?
Q3: What exactly do I need to 'SET' in my BIOS ?
And in your reply you said...
First convert each ISO to a .imgPTN file
(Q4: How do I do that? *)
...and add the two files to the E2B drive.
Then UEFI-boot from the Win7 x64 .imgPTN file (after switching it in)
(Q5: * after switching it in * So how do I do that ?)
...and install Win7.
...Also note that Win7 is very old and does not contain drivers for USB 3 -
so you may have problems installing Win7 from a USB drive!
(Q6: * Win7 does not contain USB 3 drivers * So can I use USB2 ?)
...or you could always read my eBook... ;-)
(Q7: Does that explain everything in more detail ? If so where's the link ? )
Many thanks
mac
08/03/2019
Re: Re: Re: How do I install W7 & W10, as Dual-Boot OS's?
I also forgot to ask:
Q8: What preparation do I need to make to my HDD before I use easy"boot to install the Os's ?
Q9: Eg BIOS settings / Formatting HDD to GPT etc ?
Thanks
Q8: What preparation do I need to make to my HDD before I use easy"boot to install the Os's ?
Q9: Eg BIOS settings / Formatting HDD to GPT etc ?
Thanks
mac
08/03/2019
Re: Re: Re: Re: How do I install W7 & W10, as Dual-Boot OS's?
Q1. If you have 2TB or larger disks, then you need GPT partitions. If you need GPT partitions then you need UEFI. If your disk is smaller than 2TB there is no need for GPT and no need for UEFI. Win7 64-bit works OK with UEFI+GPT.
Q2. See Q1 above.
Q3. For BIOS - just do not disable UEFI. preferably also enable CSM.
Q4. - Q9. Please use the Site Map or Google for your answers. This is an E2B forum, not a 'How do I install Windows' forum.
Read http://www.easy2boot.com/useful-things-to-know/
Q2. See Q1 above.
Q3. For BIOS - just do not disable UEFI. preferably also enable CSM.
Q4. - Q9. Please use the Site Map or Google for your answers. This is an E2B forum, not a 'How do I install Windows' forum.
Read http://www.easy2boot.com/useful-things-to-know/
SteveSi
08/03/2019
XP wiping out boot record on E2B flash drive
I am trying to install XP on a MSI MS-6570 XP wipes out the boot record of the E2B flash. I am using the boot menu (F8) with the same issue. I am using a SIL3114 SATA card and a Kingston 240GB SSD.
Harold Robinson
03/03/2019
Re: XP wiping out boot record on E2B flash drive
I can tell this because after the initial dos screen where XP copies the basic files and reboots, this error comes up "Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware.
Please check the windows documentation about hardware disk configuration and your hardware reference manuals for additional information.
When I remove all disks except the E2B flash this error comes up. anyway else and I get the standard "No boot disk found" error. "BOOT DISK FAILURE, INSERT SYSTEM DISK AND PRESS ENTER"
Could not read from the selected boot disk. Check boot path and disk hardware.
Please check the windows documentation about hardware disk configuration and your hardware reference manuals for additional information.
When I remove all disks except the E2B flash this error comes up. anyway else and I get the standard "No boot disk found" error. "BOOT DISK FAILURE, INSERT SYSTEM DISK AND PRESS ENTER"
Harold Robinson
03/03/2019
Re: XP wiping out boot record on E2B flash drive
When I remove the E2B USB drive and insert it into the PC that I built the drive with, and press with "TEST with QEMU I see the same "Windows could not start" error
Harold Robinson
03/03/2019
Re: XP wiping out boot record on E2B flash drive
After removing all drives from BIOS, i have stopped XP from wiping out the boot record on the flash drive but the second step for the xp install only copies the image to ram disk and then reboots to the E2B menu.
Harold Robinson
03/03/2019
Re: Re: XP wiping out boot record on E2B flash drive
It sounds like the first hard disk in the system is not the disk you are installing XP onto? It needs to be the first hard disk (if you boot to E2B - Utilities and use List BIOS Disks - it should list hd1 as the SSD drive).
Do you have both an internal IDE controller enabled in the BIOS and the SATA card? If so disable all controllers and disks except for the SATA card and SSD.
Step 2 assumes that you have installed the boot code to Disk 0.
When you run Step 2 - you should see a message like
'Mapping (hd0) to (hd1) and (hd1) to (hd0)
SPACEBAR=Pause, ENTER=Start now - STARTING IN 5 SECONDS...'
When you see the last message - quickly press the C key and then press ENTER key to get to the command line. Then type
find
ls (hd0,0)/
ls (hd1,0)/
ls (hd2,0)/
now if one of these lists the file /ntldr on the XP hard disk, type the following (assuming that (hd1,0) has the XP files...
root (hd1,0)
chainloader +1
boot
Do you have both an internal IDE controller enabled in the BIOS and the SATA card? If so disable all controllers and disks except for the SATA card and SSD.
Step 2 assumes that you have installed the boot code to Disk 0.
When you run Step 2 - you should see a message like
'Mapping (hd0) to (hd1) and (hd1) to (hd0)
SPACEBAR=Pause, ENTER=Start now - STARTING IN 5 SECONDS...'
When you see the last message - quickly press the C key and then press ENTER key to get to the command line. Then type
find
ls (hd0,0)/
ls (hd1,0)/
ls (hd2,0)/
now if one of these lists the file /ntldr on the XP hard disk, type the following (assuming that (hd1,0) has the XP files...
root (hd1,0)
chainloader +1
boot
SteveSi
03/03/2019
Re: Re: Re: XP wiping out boot record on E2B flash drive
Hi Steve, Yes I do have an IDE controller enabled. It has a optical drive attached. I will do as you suggested and get back to you. I saw your response after giving up. The file copy takes such a LOOOOOOONNNNNGGGG time. Its easily 40 minutes for each try.
Harold Robinson
03/03/2019
Re: Re: Re: XP wiping out boot record on E2B flash drive
Steve: >It sounds like the first hard disk in the system is not the disk you are installing XP onto? It needs to be the first hard disk (if you boot to E2B - Utilities and use List BIOS Disks - it should list hd1 as the SSD drive).
Do you have both an internal IDE controller enabled in the BIOS and the SATA card? If so disable all controllers and disks except for the SATA card and SSD."
Yes I did have the IDE controller enabled. As of this posting it is Disabled (both controllers)
I ran List Bios disks and here is what came out:
(fd3): Volume name is "(unsupported)".
Filesstem type is fat12, using whole disk
(hd0,0): Volume name is "E2B"
File System type is ntfs, partition type 0x07
(hd0,1): Volume name is "PTN2"
file system type is fat12 partition type is 0x21
=================hd0===============
drive 0x80(LBA): C/H/S=1885/255/63. sector count/size=30282525/512
Partition num: 0, active, filesystem type is ntfs, partition type 0x07
Partition num: 1, filesystem type is fat12, partition type 0x21
Contents of (hd0,0) E2B
{looks like it lists some files}
Contents of (hd0,1) PTN2
System\ Volume\ Information
==========
Press a key for current drive map...
floppies_orig=1, Harddrives_orig=2, floppies_curr=0, harddrives_curr=2
Number of atapi CD-ROMs: 0
ram_drive=0x7f, rd_base=0x3FFAF000, rd_size=0x13000
Fr To Hm Sm To_c _H _S Start_Sector Sector _Count DHR
03 ff 00 88 8882 FE 3F 00000000001FFE40 0000000000000140 M=R
After waiting for 10 minutes, I pressed a key and it returned to the utilities menu.
Do you have both an internal IDE controller enabled in the BIOS and the SATA card? If so disable all controllers and disks except for the SATA card and SSD."
Yes I did have the IDE controller enabled. As of this posting it is Disabled (both controllers)
I ran List Bios disks and here is what came out:
(fd3): Volume name is "(unsupported)".
Filesstem type is fat12, using whole disk
(hd0,0): Volume name is "E2B"
File System type is ntfs, partition type 0x07
(hd0,1): Volume name is "PTN2"
file system type is fat12 partition type is 0x21
=================hd0===============
drive 0x80(LBA): C/H/S=1885/255/63. sector count/size=30282525/512
Partition num: 0, active, filesystem type is ntfs, partition type 0x07
Partition num: 1, filesystem type is fat12, partition type 0x21
Contents of (hd0,0) E2B
{looks like it lists some files}
Contents of (hd0,1) PTN2
System\ Volume\ Information
==========
Press a key for current drive map...
floppies_orig=1, Harddrives_orig=2, floppies_curr=0, harddrives_curr=2
Number of atapi CD-ROMs: 0
ram_drive=0x7f, rd_base=0x3FFAF000, rd_size=0x13000
Fr To Hm Sm To_c _H _S Start_Sector Sector _Count DHR
03 ff 00 88 8882 FE 3F 00000000001FFE40 0000000000000140 M=R
After waiting for 10 minutes, I pressed a key and it returned to the utilities menu.
Harold Robinson
03/03/2019
Re: Re: Re: XP wiping out boot record on E2B flash drive
ok. After running the find command it returned the following:
(0xff)
(hd0,0)
(hd0,1)
(fd0)
(fd1)
ls (hd0,0)/ returned files that appeared to be on the e2b flash drive. I see "MAKE_E2B_USB_DRIVE (run\ as\ admin).cmd etc
ls (hd1,0)/ returned the same files. (yes I don't understand it but there it is.)
ls (hd2,0)/ returned Error 21: (http://grup4dos.chenall.net/e/21) The selected disk does not exist.
It seems your environment is not seeing the SSD drive.
I will hold off installing the XP OS from CD rom (as I know this does work) and work with you on this. If you want to take this to email let me know.
Sincerely,
Harold Robinson
(0xff)
(hd0,0)
(hd0,1)
(fd0)
(fd1)
ls (hd0,0)/ returned files that appeared to be on the e2b flash drive. I see "MAKE_E2B_USB_DRIVE (run\ as\ admin).cmd etc
ls (hd1,0)/ returned the same files. (yes I don't understand it but there it is.)
ls (hd2,0)/ returned Error 21: (http://grup4dos.chenall.net/e/21) The selected disk does not exist.
It seems your environment is not seeing the SSD drive.
I will hold off installing the XP OS from CD rom (as I know this does work) and work with you on this. If you want to take this to email let me know.
Sincerely,
Harold Robinson
Harold Robinson
03/03/2019
Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
Hi
You obviously need to enable the external SATA controller in the BIOS so the SSD can be seen by the BIOS (and XP).
If E2B warns you that no HDD was detected, then it is never going to boot from the SSD.
Ensure the first boot device in the BIOS settings is set to the SSD drive.
If the SSD is not visible in the BIOS settings, then it obviously can't boot from the SSD.
If XP Setup is trying to write the boot code to the USB drive, then there will be no boot code on the SSD so it will not boot in Step 2. You must configure the BIOS so the SSD is the first drive in the system and keep the E2B drive connected so that you can tell if it has corrupted it or not after Step 1. If the boot code has been written to the USB drive, then there is no point trying Step 2.
If any more problems - use the online Chat facility on this website (enable pop-ups if using FireFox) or Contact Me page.
You obviously need to enable the external SATA controller in the BIOS so the SSD can be seen by the BIOS (and XP).
If E2B warns you that no HDD was detected, then it is never going to boot from the SSD.
Ensure the first boot device in the BIOS settings is set to the SSD drive.
If the SSD is not visible in the BIOS settings, then it obviously can't boot from the SSD.
If XP Setup is trying to write the boot code to the USB drive, then there will be no boot code on the SSD so it will not boot in Step 2. You must configure the BIOS so the SSD is the first drive in the system and keep the E2B drive connected so that you can tell if it has corrupted it or not after Step 1. If the boot code has been written to the USB drive, then there is no point trying Step 2.
If any more problems - use the online Chat facility on this website (enable pop-ups if using FireFox) or Contact Me page.
SteveSi
03/03/2019
Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
There is no BIOS setting to make the external SATA visable. I went into the SATA cards bios and there is no option in there either only menu selections dealing with creating a array, deleting an array, repairing an array, and an exit option. I am not seeing an error that tells me that there is no drive or hard disk present. I do see that when I run under QEMU when testing to make sure it will boot. The computers BIOS is set as follows:
Advanced BIOS Features
1st boot device [HDD-0]
2nd boot device [Disabled]
3rd boot device [Disabled]
Boot Other Device [Disabled]
I can list other BIOS settings if you wish.
Advanced BIOS Features
1st boot device [HDD-0]
2nd boot device [Disabled]
3rd boot device [Disabled]
Boot Other Device [Disabled]
I can list other BIOS settings if you wish.
Harold Robinson
03/03/2019
Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
Ignore QEMU - it is a virtual system and has nothing to do with your real system.
If the 1st boot device [HDD-0] is set - then what exactly is that HDD-0 device (with no USB drive or other storage device connected). Surely it must be the SSD if that is the only device connected?
If E2B does not give you a warning on boot, then it must see an internal BIOS HDD in the system.
Can you boot to E2B and go to the Utilities Menu and run the List BIOS devices option? hd0 should be the USB drive and hd1 should be the SSD.
If the 1st boot device [HDD-0] is set - then what exactly is that HDD-0 device (with no USB drive or other storage device connected). Surely it must be the SSD if that is the only device connected?
If E2B does not give you a warning on boot, then it must see an internal BIOS HDD in the system.
Can you boot to E2B and go to the Utilities Menu and run the List BIOS devices option? hd0 should be the USB drive and hd1 should be the SSD.
SteveSi
03/03/2019
Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
I can confirm that if I slipstream the SIL drivers into my ISO and burn that to a CD, XP will install successfully. So Your Easy2Boot drive is selecting the correct drivers. during XP's first stage installer (the text part) It does see the drive, it formats it and (that is when the USB key boot record is wiped out). the USB key is listed as Drive 0 and the SSD is listed as Drive 1, which is were we are having our problem.
Harold Robinson
03/03/2019
Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
So does the E2B Utilities - List BIOS disks menu option list hd0 as the USB drive and hd1 as the SSD?
The issue here is that the BIOS must see the SSD.
Of course XP Setup can see the SSD because it loads the driver for it. But in order to boot from the SSD, the BIOS must be able to see it.
The boot code is transferred to the internal hard disk at the end of the copy files stage. So pulling out the USB drive just means that it cannot write the boot code and files to the USB drive (if it was going to). XP Setup will want to update the boot code on the 'boot' drive and E2B takes steps to ensure this happens by changing hdd0 to be the internal hdd instead of hd1.
For instance, if you run Step 1 and then allow it to reboot from the SSD, it should boot OK (it will fail later with an 'asms not found' error - but at least it will boot).
So your 'objective' is to run Step 1, when it starts the 10 second timer to reboot at the end - pull out the USB drive and allow it to boot to the SSD. If it does not boot - then Setup has gone wrong.
Once it does boot from the SSD, you can reboot and run Step 2 (which should then also work) and complete the install.
P.S. Make sure you use the F8 boot selection pop-up menu when booting to E2B - do NOT set the USB drive as the first boot device in the BIOS Settings menu.
If you do spoil your E2B drive, you should be able to fix it by running RMPrepUSB - Install grub4dos twice, once for MBR and once for PBR.
The issue here is that the BIOS must see the SSD.
Of course XP Setup can see the SSD because it loads the driver for it. But in order to boot from the SSD, the BIOS must be able to see it.
The boot code is transferred to the internal hard disk at the end of the copy files stage. So pulling out the USB drive just means that it cannot write the boot code and files to the USB drive (if it was going to). XP Setup will want to update the boot code on the 'boot' drive and E2B takes steps to ensure this happens by changing hdd0 to be the internal hdd instead of hd1.
For instance, if you run Step 1 and then allow it to reboot from the SSD, it should boot OK (it will fail later with an 'asms not found' error - but at least it will boot).
So your 'objective' is to run Step 1, when it starts the 10 second timer to reboot at the end - pull out the USB drive and allow it to boot to the SSD. If it does not boot - then Setup has gone wrong.
Once it does boot from the SSD, you can reboot and run Step 2 (which should then also work) and complete the install.
P.S. Make sure you use the F8 boot selection pop-up menu when booting to E2B - do NOT set the USB drive as the first boot device in the BIOS Settings menu.
If you do spoil your E2B drive, you should be able to fix it by running RMPrepUSB - Install grub4dos twice, once for MBR and once for PBR.
SteveSi
04/03/2019
Re: Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
Steve:> "So does the E2B Utilities - List BIOS disks menu option list hd0 as the USB drive and hd1 as the SSD?"
Harold: No I just checked again and it only lists the USB drive as HDD0
Steve:>"The issue here is that the BIOS must see the SSD. Of course XP Setup can see the SSD because it loads the driver for it. But in order to boot from the SSD, the BIOS must be able to see it."
Harold: "After the computer BIOS has completed its post stage, I then see:
Sil 3114 SataRaid BIOS Version 5.4.03
Copyright (C) 1997-2006 Silicon Image, Inc.
Press <Ctrl+S> or F4 to enter RAID utility
0 KINGSTON SV300S37A24 223 GB"
My BIOS does not support SATA drives, hence I am using the SATA card. I don't even have an option in BIOS (I don't think) to see the drive because the BIOS of the SATA card had not been initialized yet.
If you want I can run freedos to see if I can see the drive. but under grub4dos (E2B) I am not seeing it. I am guessing you are using grub4dos.
Harold: No I just checked again and it only lists the USB drive as HDD0
Steve:>"The issue here is that the BIOS must see the SSD. Of course XP Setup can see the SSD because it loads the driver for it. But in order to boot from the SSD, the BIOS must be able to see it."
Harold: "After the computer BIOS has completed its post stage, I then see:
Sil 3114 SataRaid BIOS Version 5.4.03
Copyright (C) 1997-2006 Silicon Image, Inc.
Press <Ctrl+S> or F4 to enter RAID utility
0 KINGSTON SV300S37A24 223 GB"
My BIOS does not support SATA drives, hence I am using the SATA card. I don't even have an option in BIOS (I don't think) to see the drive because the BIOS of the SATA card had not been initialized yet.
If you want I can run freedos to see if I can see the drive. but under grub4dos (E2B) I am not seeing it. I am guessing you are using grub4dos.
Harold Robinson
04/03/2019
Re: Re: Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
Thanks for the clarification. So if E2B does not list the SSD SATA drive as a BIOS drive then installing XP from the E2B drive is not going to work.
BUT I don't understand why E2B does not warn you that it cannot see an internal hard disk when you boot to E2B??? If E2B does not detect an hd1 (the first internal hard disk) you should see that coloured warning text???
What should happen is that after switch-on, POST should run, it should add its Option ROM code into the BIOS and detect SATA drive, then it should allow you to boot from USB or from the SATA drive or go into the BIOS and see the SATA drive listed.
According to the SIL website, if you are not using RAID, you should update the firmware on the SIL card to use the 'IDE' base 'b' version of the firmware. Maybe this will help? http://www.latticesemi.com/en/Support/AnswerDatabase/4/7/8/4784
Do you still say that you can install XP from CD (with the only drive being the SSD drive) and it boots to XP OK? I am not quite sure how it could do that!
P.S. Update firmware+manual is here https://1drv.ms/u/s!AqlrQcdsFA-KsQhnt96X0lkfYfFs
Extract the files to the root of your E2B drive, boot to E2B and run DOS menu - boot to FreeDOS - choose default NTFS option to get to C: prompt. Now you can type UpdFlash and load the b5403.bin file (r is for RAID version).
Here is an excellent post from someone who seems to know where his towel is...
https://www.vogons.org/viewtopic.php?f=46&t=49471#p734172
BUT I don't understand why E2B does not warn you that it cannot see an internal hard disk when you boot to E2B??? If E2B does not detect an hd1 (the first internal hard disk) you should see that coloured warning text???
What should happen is that after switch-on, POST should run, it should add its Option ROM code into the BIOS and detect SATA drive, then it should allow you to boot from USB or from the SATA drive or go into the BIOS and see the SATA drive listed.
According to the SIL website, if you are not using RAID, you should update the firmware on the SIL card to use the 'IDE' base 'b' version of the firmware. Maybe this will help? http://www.latticesemi.com/en/Support/AnswerDatabase/4/7/8/4784
Do you still say that you can install XP from CD (with the only drive being the SSD drive) and it boots to XP OK? I am not quite sure how it could do that!
P.S. Update firmware+manual is here https://1drv.ms/u/s!AqlrQcdsFA-KsQhnt96X0lkfYfFs
Extract the files to the root of your E2B drive, boot to E2B and run DOS menu - boot to FreeDOS - choose default NTFS option to get to C: prompt. Now you can type UpdFlash and load the b5403.bin file (r is for RAID version).
Here is an excellent post from someone who seems to know where his towel is...
https://www.vogons.org/viewtopic.php?f=46&t=49471#p734172
SteveSi
04/03/2019
Re: Re: Re: Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
Please try v1.B0c Beta
http://tiny.cc/i4nr3y
If you try it before you update the SIL3114 firmware, it should give you plenty of warnings.
If you try it after updating the SIL3114 firmware, hopefully it will work :-). I have not changed E2B XP install functions though - it won't fix your issue (unless you update the SIL3114 firmware).
http://tiny.cc/i4nr3y
If you try it before you update the SIL3114 firmware, it should give you plenty of warnings.
If you try it after updating the SIL3114 firmware, hopefully it will work :-). I have not changed E2B XP install functions though - it won't fix your issue (unless you update the SIL3114 firmware).
SteveSi
04/03/2019
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive
I just found this buried in the manual. It seems you can use the RAID firmware!
Creating a JBOD Configuration
The BIOS RAID utility does not report non-RAID drives to the system BIOS. If a non-RAID boot drive or data drive is desired, create a JBOD so the BIOS RAID utility will report the drive to the system BIOS.
1. Select 'Create RAID set' from the Main Menu section of the RAID Configuration Utility screen.
2. Select 'JBOD' and press Enter.
3. Select 'JBOD drive' from the Physical Drive list and press Enter.
4. Select the size of the JBOD drive with the ↑ and ↓ keys and press Enter.
5. When the 'Are You Sure?' confirmation prompt appears, respond 'Y' to complete the JBOD configuration.
The hard disk should now be listed in the BIOS menu as a 'JBOD' device.
Obvious, isn't it! To add a non-RAID single disk, you use the Create RAID set option!!!
Creating a JBOD Configuration
The BIOS RAID utility does not report non-RAID drives to the system BIOS. If a non-RAID boot drive or data drive is desired, create a JBOD so the BIOS RAID utility will report the drive to the system BIOS.
1. Select 'Create RAID set' from the Main Menu section of the RAID Configuration Utility screen.
2. Select 'JBOD' and press Enter.
3. Select 'JBOD drive' from the Physical Drive list and press Enter.
4. Select the size of the JBOD drive with the ↑ and ↓ keys and press Enter.
5. When the 'Are You Sure?' confirmation prompt appears, respond 'Y' to complete the JBOD configuration.
The hard disk should now be listed in the BIOS menu as a 'JBOD' device.
Obvious, isn't it! To add a non-RAID single disk, you use the Create RAID set option!!!
SteveSi
04/03/2019
Re: XP wiping out boot record on E2B flash drive
I have given up on this for now. I have been at this for 12 hours. I can not get the second stage of XP to start. In order to get the first stage to successfully run. I would wait until the XP files were copied to RAM disk. then before the XP install started, pull the USB drive to prevent XP from overwriting the boot record.
the first stage install would run successfully and reboot. After the 2nd stage completed its copy it was suppose to boot off the hard disk, and this would not happen. I could not get the second stage of XP to work properly. I am going to use old school, stream line a set of drivers and do it this way. I will continue to monitor this thread for possible solutions.
the first stage install would run successfully and reboot. After the 2nd stage completed its copy it was suppose to boot off the hard disk, and this would not happen. I could not get the second stage of XP to work properly. I am going to use old school, stream line a set of drivers and do it this way. I will continue to monitor this thread for possible solutions.
Harold Robinson
03/03/2019
Passcape
Hi. How to Proper Boot Passcape?. I tried once boot it but my keyboard and mouse did not work. tnx, easy 2 boot :)
Robb
02/03/2019
Re: Passcape
Passcape Reset Password is based on WinPE. It may not have the drivers required for your (modern?) PC. Try using a USB 2 port for the kbd and mouse. Since it is a commercial program, contact Passcape. The latest trial version seems to have drivers which were added on Jan 2019 - so it seems up to date and should work. Is your ISO too old?
Also, try converting the ISO to a FAT32 .imgPTN file and see if UEFI-booting works?
Also, try converting the ISO to a FAT32 .imgPTN file and see if UEFI-booting works?
SteveSi
02/03/2019
Neater Menu
I've been using Grub4dos for a long time and I've set up my menu with all the things i use the most at the top of the screen (HDSentinel for dos and then a space) and then after the space i have Cloning Software clumped together like Acronis,Paragon etc..These arent in sub menu's, they are launched directly from the main menu.
Then I have another space and after that i have partitioning tools, once again Acronis,Paragon etc.
Then another space and after that portable OS's , Hirens Windows 7,Gandalfs Windows 8 & 10 etc.
Then another space and finally under that i have submenus of the things i don't use as often.
Its just there is sooooo much information I'm having trouble coming to grips if i can move out the default menu's completely, Insert my top options and add a line in between the different genres of programs.
I took some quick pictures of what I'm trying to achieve but there's nowhere to post them unfortunately.
Is there anywhere i can download peoples e2b config files or even whole iso images of usb sticks that i can go through and see how they've done it...Thats originally how i learnt on grub4dos...pulling apart somebody else's work, making changes and seeing what it did, seeing what changed.
Is there a place you use to host a couple of pictures to show you what i mean ?
Then I have another space and after that i have partitioning tools, once again Acronis,Paragon etc.
Then another space and after that portable OS's , Hirens Windows 7,Gandalfs Windows 8 & 10 etc.
Then another space and finally under that i have submenus of the things i don't use as often.
Its just there is sooooo much information I'm having trouble coming to grips if i can move out the default menu's completely, Insert my top options and add a line in between the different genres of programs.
I took some quick pictures of what I'm trying to achieve but there's nowhere to post them unfortunately.
Is there anywhere i can download peoples e2b config files or even whole iso images of usb sticks that i can go through and see how they've done it...Thats originally how i learnt on grub4dos...pulling apart somebody else's work, making changes and seeing what it did, seeing what changed.
Is there a place you use to host a couple of pictures to show you what i mean ?
Batfink
10/02/2019
Re: Neater Menu
I added a couple of pictures to Imgur
https://imgur.com/a/1mPXU6b
https://imgur.com/a/1mPXU6b
Batfink
10/02/2019
Re: Re: Neater Menu
Hi
The first entry you have is Hard Disk Sentinel for DOS. So copy the ISO to the \_ISO\MAINMENU and boot to E2B and try it. It will appear in the Main Menu is 'hdsdos' but you can change the file name to 'Hard Disk Sentinel (DOS).iso if you like. If you want it in the Utilities menu, then just copy the ISO to \_ISO\UTILITIES.
If you want it to be listed as the first entry, name it aaa_hdsdos.iso. Entries are listed alphabetically by file name.
Now to change the entry text and also add the lines of help text under the menu when you select it, create a aaa_hdsdos.txt file using \_ISO\Txt_Maker.exe.
The next item you have is a blank line, so copy "\_ISO\docs\Sample mnu files\E2B Menus\A_BlankMenuEntry.mnu"
to \_ISO\MAINMENU folder and rename it as aab_blank.mnu.
The next item you have is Acronis True Image 2018. So copy the .ISO file to \_ISO\MAINMENU and name it aba_Acronis2018.iso. Then make a aba_Acronis2018.txt file for it.
Rinse and repeat...
For some of the other items, e.g. Antivirus, backup, Windows Install, just copy the ISOs to the correct E2B menu folders.
The other alternative is to simply use your current menu.lst file. Copy your menu to \_ISO\MAINMENU and name it 'Batfink Menu.mnu'. Edit it to remove the initial grub4dos lines so it starts with 'title xxxx' and all the following entries. Copy your ISOs to the correct folders on the E2B drive as expected by your menu.
You can always start a chat session with me if you have any problems. There should be a chat icon pop-up on this page.
The first entry you have is Hard Disk Sentinel for DOS. So copy the ISO to the \_ISO\MAINMENU and boot to E2B and try it. It will appear in the Main Menu is 'hdsdos' but you can change the file name to 'Hard Disk Sentinel (DOS).iso if you like. If you want it in the Utilities menu, then just copy the ISO to \_ISO\UTILITIES.
If you want it to be listed as the first entry, name it aaa_hdsdos.iso. Entries are listed alphabetically by file name.
Now to change the entry text and also add the lines of help text under the menu when you select it, create a aaa_hdsdos.txt file using \_ISO\Txt_Maker.exe.
The next item you have is a blank line, so copy "\_ISO\docs\Sample mnu files\E2B Menus\A_BlankMenuEntry.mnu"
to \_ISO\MAINMENU folder and rename it as aab_blank.mnu.
The next item you have is Acronis True Image 2018. So copy the .ISO file to \_ISO\MAINMENU and name it aba_Acronis2018.iso. Then make a aba_Acronis2018.txt file for it.
Rinse and repeat...
For some of the other items, e.g. Antivirus, backup, Windows Install, just copy the ISOs to the correct E2B menu folders.
The other alternative is to simply use your current menu.lst file. Copy your menu to \_ISO\MAINMENU and name it 'Batfink Menu.mnu'. Edit it to remove the initial grub4dos lines so it starts with 'title xxxx' and all the following entries. Copy your ISOs to the correct folders on the E2B drive as expected by your menu.
You can always start a chat session with me if you have any problems. There should be a chat icon pop-up on this page.
SteveSi
10/02/2019
Re: Re: Re: Neater Menu
Thank you so much for your reply, it put me on the right path so to speak.
Hahaha however I think this menu is going to drive me to drink.
Is the sorting Alphanumeric, When i first started with just HDsentinel and the cloning software i could have sworn they were in the correct order.
Then I added a space and added partitioning software, Removed the backdrop,set it to 1024..I know it looks like a dogs breakfast, I was going to ask and read a bit more about removing help menu's and highlighting menu items etc..eventually.
However, This is driving me bonkers ..as you can see from the explorer picture all my files are in perfect alphanumeric order and yet in the second picture you can actually see them detecting in the wrong order as the USB stick boots, and finally in the last picture you can see them in the wrong order (or the same order they detected in)
https://imgur.com/a/7g5agy5
Am i insane, is it my numbering system, is it something to do with me not having a backdrop or turning off the extra menu's.
Hahaha however I think this menu is going to drive me to drink.
Is the sorting Alphanumeric, When i first started with just HDsentinel and the cloning software i could have sworn they were in the correct order.
Then I added a space and added partitioning software, Removed the backdrop,set it to 1024..I know it looks like a dogs breakfast, I was going to ask and read a bit more about removing help menu's and highlighting menu items etc..eventually.
However, This is driving me bonkers ..as you can see from the explorer picture all my files are in perfect alphanumeric order and yet in the second picture you can actually see them detecting in the wrong order as the USB stick boots, and finally in the last picture you can see them in the wrong order (or the same order they detected in)
https://imgur.com/a/7g5agy5
Am i insane, is it my numbering system, is it something to do with me not having a backdrop or turning off the extra menu's.
Batfink
13/02/2019
Re: Re: Re: Re: Neater Menu
Whoops! You have found a bug! Though I did tell you to use aaa not 000 ;-)
It is because grub4dos is treating 002f as a number and is discarding the non-numbers, so 002a is smaller than 002g (g=GB so 002g=2GB whereas 003d = 3 and 002f=2). grub4dos treats k,m,g and t as multipliers and so the list is not sorted correctly. You can use a non-number as the first character and it should work correctly - e.g. @002f-
or download the latest E2B v1.A9j Beta from the Alternate Download Areas on GDrive or OneDrive.
http://www.easy2boot.com/download/alternate-download-sites/
if you try the latest version, please let me know if it works or not.
See also
http://www.easy2boot.com/configuring-e2b/mainmenuonly/
and use the E2B_Editor.exe to make your menu (load a 1024x768 bitmap so the editor switches to 1024 mode - you can remove the bitmap later if you wish).
It is because grub4dos is treating 002f as a number and is discarding the non-numbers, so 002a is smaller than 002g (g=GB so 002g=2GB whereas 003d = 3 and 002f=2). grub4dos treats k,m,g and t as multipliers and so the list is not sorted correctly. You can use a non-number as the first character and it should work correctly - e.g. @002f-
or download the latest E2B v1.A9j Beta from the Alternate Download Areas on GDrive or OneDrive.
http://www.easy2boot.com/download/alternate-download-sites/
if you try the latest version, please let me know if it works or not.
See also
http://www.easy2boot.com/configuring-e2b/mainmenuonly/
and use the E2B_Editor.exe to make your menu (load a 1024x768 bitmap so the editor switches to 1024 mode - you can remove the bitmap later if you wish).
SteveSi
13/02/2019
Re: Re: Re: Re: Re: Neater Menu
Hahaha I found a bug.
Goddammit, yes you did say to use aaa but I thought I'd be a smarty-pants and use numbers to give myself more options to expand if needed be.. Lots more numbers than letters in the alphabet etc etc.
I'll try the beta first before I do anything else because now I'm curious to see what happens.
Ah OK, I thought the editor only supported up to 800..I'll give that a try. At least I know I'm not freaking insane.
Goddammit, yes you did say to use aaa but I thought I'd be a smarty-pants and use numbers to give myself more options to expand if needed be.. Lots more numbers than letters in the alphabet etc etc.
I'll try the beta first before I do anything else because now I'm curious to see what happens.
Ah OK, I thought the editor only supported up to 800..I'll give that a try. At least I know I'm not freaking insane.
Batfink
13/02/2019
Re: Re: Re: Re: Re: Re: Neater Menu
Actually there are more letters! a-z is 26 whereas 0-9 is 10. so aaa-zzz gives far wider scope than 000-999 ;-)
SteveSi
13/02/2019
Re: Re: Re: Re: Re: Re: Re: Neater Menu
You're hurting my brain ;)
Your beta worked perfectly, I upgraded it directly over the USB stick.
I'm actually pretty bland when it comes to this stuff, I don't need a backdrop at all, or a logo..just a surrounding box is good enough...It's a tool, not a Picasso :)
I don't even need a help menu, Its for me, I know what everything does since I made it, The more i can fit on the screen the better.
That being said, I do like a menu thats easy to see, Easy to tell whats selected so i have a couple of questions.
1. In the Imgur pictures i posted you'll notice the text is white unless selected and then a large white selection over it highlites it and makes the text under it black..nice and easy to see...Can that be done ?
2. Also the RETURN TO PREVIOUS MENU (F8), is that location set in stone, can it be moved to the top of the sub menu's and be the default item selected and set apart with a space so if you're looking for something and went to the wrong menu you can just press enter to go back.
3.Is there a way to actually completely remove the help ...I did move it down totally off the screen but for the built in items (MENU REFRESH) like shown in the picture it still shows up in the default place.
4.Can i move the wwww.easy2boot.com to maybe the top of the main menu where it shows the version number.
Hahaha, So many questions, so little time..I'm appreciative of all the help you've given me so far.
After this I'm going to used my applied knowledge to try and make a UEFI one, I'm sorely in need of one of those. https://imgur.com/a/MqcQ5uu
Your beta worked perfectly, I upgraded it directly over the USB stick.
I'm actually pretty bland when it comes to this stuff, I don't need a backdrop at all, or a logo..just a surrounding box is good enough...It's a tool, not a Picasso :)
I don't even need a help menu, Its for me, I know what everything does since I made it, The more i can fit on the screen the better.
That being said, I do like a menu thats easy to see, Easy to tell whats selected so i have a couple of questions.
1. In the Imgur pictures i posted you'll notice the text is white unless selected and then a large white selection over it highlites it and makes the text under it black..nice and easy to see...Can that be done ?
2. Also the RETURN TO PREVIOUS MENU (F8), is that location set in stone, can it be moved to the top of the sub menu's and be the default item selected and set apart with a space so if you're looking for something and went to the wrong menu you can just press enter to go back.
3.Is there a way to actually completely remove the help ...I did move it down totally off the screen but for the built in items (MENU REFRESH) like shown in the picture it still shows up in the default place.
4.Can i move the wwww.easy2boot.com to maybe the top of the main menu where it shows the version number.
Hahaha, So many questions, so little time..I'm appreciative of all the help you've given me so far.
After this I'm going to used my applied knowledge to try and make a UEFI one, I'm sorely in need of one of those. https://imgur.com/a/MqcQ5uu
Batfink
16/02/2019
Re: Re: Re: Re: Re: Re: Re: Re: Neater Menu
1. As in the Sample_MyE2B.cfg and on the http://www.easy2boot.com/configuring-e2b/ page,
the selection text can be highlighted by defining a highlight colour - e.g. color highlight=0xFFFFFF00000000
2. Any menu can be removed using one of the NOFxxx variables in your MyE2B.cfg file. Any new menu can be added by adding in a .mnu file (see v1.A9k Sample mnu Files\E2B Menus for example .mnu files). A menu space can be added as already explained by adding a .mnu file. http://www.easy2boot.com/configuring-e2b/mainmenuonly/
3. Help can be removed using set NOF1=1 in your MyE2B.cfg file - http://www.easy2boot.com/configuring-e2b/f1-help-menu/
4. The FOOTER help text can be removed by setting its position to just after the last line of the menu - or moved - using HBTM. The Main Menu heading is determined by the HEADING variable. As already explained, the E2B_Editor.exe GUI will help you and it already has an Options list for suppressing F1 and F8, etc.
You may find it useful to define Global Hotkeys - http://www.easy2boot.com/configuring-e2b/global-hotkeys/
and look at the Sample_MyE2B.cfg file which contains a load of example settings. Use the SITE MAP!
P.S. grub4dos does not UEFI-boot. You will need to use grub (grub2) for a UEFI menu system or the new syslinux for UEFI.
the selection text can be highlighted by defining a highlight colour - e.g. color highlight=0xFFFFFF00000000
2. Any menu can be removed using one of the NOFxxx variables in your MyE2B.cfg file. Any new menu can be added by adding in a .mnu file (see v1.A9k Sample mnu Files\E2B Menus for example .mnu files). A menu space can be added as already explained by adding a .mnu file. http://www.easy2boot.com/configuring-e2b/mainmenuonly/
3. Help can be removed using set NOF1=1 in your MyE2B.cfg file - http://www.easy2boot.com/configuring-e2b/f1-help-menu/
4. The FOOTER help text can be removed by setting its position to just after the last line of the menu - or moved - using HBTM. The Main Menu heading is determined by the HEADING variable. As already explained, the E2B_Editor.exe GUI will help you and it already has an Options list for suppressing F1 and F8, etc.
You may find it useful to define Global Hotkeys - http://www.easy2boot.com/configuring-e2b/global-hotkeys/
and look at the Sample_MyE2B.cfg file which contains a load of example settings. Use the SITE MAP!
P.S. grub4dos does not UEFI-boot. You will need to use grub (grub2) for a UEFI menu system or the new syslinux for UEFI.
SteveSi
16/02/2019
Support
I am very impressed with this product, but also the support is amazing. I had an issue (turned out was my windows 10 machine) but the help was far better than any other support forum.
I wish there were more products like this out there and more companies that run with this service level.
I wish there were more products like this out there and more companies that run with this service level.
Ryan
24/01/2019
Re: Support
I can totally agree with this. Seriously, look at my question right below this. I couldn't tell one company I BOUGHT something from that has such a fast + straight forward support.
C.F.
25/01/2019
Re: Support
Hello, I'm trying to boot a 7GB windows 7 based WIM file. I get the following error: There isn't enough memory to create a ramdisk device
Any idea what i'm doing wrong?
Any idea what i'm doing wrong?
Nicolai
29/01/2019
Re: Re: Support
wim files are loaded into RAM. So does your system have at least 8GB of RAM?
Why didn't you use a VHD instead?
Why didn't you use a VHD instead?
SteveSi
29/01/2019
Re: Re: Re: Support
Hi Steve, Thanks for your answer.
I'll check that asap. It's a weird customer request and we don't have people with experience to set it up, im left with google. Is that always the case for wim files from USB? Would that problem be solved with a server or using MDT to make a bootable USB?
I'll check that asap. It's a weird customer request and we don't have people with experience to set it up, im left with google. Is that always the case for wim files from USB? Would that problem be solved with a server or using MDT to make a bootable USB?
Nicolai
30/01/2019
Re: Re: Re: Re: Support
boot.wim files (the WinPE that is initially booted to from an ISO or MDT, etc. when deploying an image) are typically 300-800MB in size. They typically run Setup.exe which is used to deploy a second much larger install.wim file to a target system.
The large install.wim is not usually bootable and contains a copy of the OS files that you want to install onto the target device.
All bootable .wim files are always loaded into memory as the X: drive. You cannot boot the install.wim type of file with E2B or MDT or Microsoft bootmgr+BCD because it is not intended to be bootable.
The large install.wim is not usually bootable and contains a copy of the OS files that you want to install onto the target device.
All bootable .wim files are always loaded into memory as the X: drive. You cannot boot the install.wim type of file with E2B or MDT or Microsoft bootmgr+BCD because it is not intended to be bootable.
SteveSi
30/01/2019
How to restore E2B partition after switching to .imgPTN file
So far the only thing I didn't accomplish, using E2B is, to switch back to the regular Legacy Boot menu after booting a payload via an imgPTN file. (I know, this is not the right place for support, but as I hope I am only to stupid / blind to find the hint and you can help me with one link I didnt find so far, I ask it here:
I boot a payload via ImgPTN, but not in UEFI but in CSM Mode.
1. I boot in the regular E2B menu, chose the .imgPTN payload and the MBR gets overwritten (-> the partitions switched)
2. I boot the payload (also in CSM Mode) and use it, so far it works like you describe in the corresponding instruction.
3. How do I flip the partitions back now (to get back to the regular E2B menu) without the need to boot a windows and use the .exe ? In your article about the use of imgPTN files you write, that after I booted the stick in UEFI-Mode to boot the payload I will get an simple menu with the option to switch back the partitions if I boot the stick in legacy / csm mode again. This doesn't work for me since I boot the payload again immediately when I boot the stick in csm / legacy mode. That is logically because the Bios / UEFI only sees this one partition after the partition swap. Does this mean, its impossible to switch back the partition table without a working windows-pc or am I just to stupid to understand, how it works ?
However, I can totally live with this limitation since I mostly use payloads that doesn't need the imgPTN trick to work, I just wondered if I've missed the trick of switching back.
I boot a payload via ImgPTN, but not in UEFI but in CSM Mode.
1. I boot in the regular E2B menu, chose the .imgPTN payload and the MBR gets overwritten (-> the partitions switched)
2. I boot the payload (also in CSM Mode) and use it, so far it works like you describe in the corresponding instruction.
3. How do I flip the partitions back now (to get back to the regular E2B menu) without the need to boot a windows and use the .exe ? In your article about the use of imgPTN files you write, that after I booted the stick in UEFI-Mode to boot the payload I will get an simple menu with the option to switch back the partitions if I boot the stick in legacy / csm mode again. This doesn't work for me since I boot the payload again immediately when I boot the stick in csm / legacy mode. That is logically because the Bios / UEFI only sees this one partition after the partition swap. Does this mean, its impossible to switch back the partition table without a working windows-pc or am I just to stupid to understand, how it works ?
However, I can totally live with this limitation since I mostly use payloads that doesn't need the imgPTN trick to work, I just wondered if I've missed the trick of switching back.
C.F.
19/01/2019
Re: How to restore E2B partition after switching to .imgPTN file
If you UEFI-boot to Windows\WinPE then you can use one of the utilities in the \e2b folder to restore the E2B partition.
If you UEFI-boot to linux, then you can use the \e2b\Restore_E2B.sh bash script to restore the E2B partition (it will be in MPI v0.090 and later versions).
Otherwise you must find some other way to MBR-boot or boot to a linux or Windows\WinPE system in order to switch back in the E2B partition.
If you want to try a variety of linux payloads from a single UEFI menu, try the E2B grub2 menu system - see Site Index for the page (but it has it's own set of drawbacks).
If you UEFI-boot to linux, then you can use the \e2b\Restore_E2B.sh bash script to restore the E2B partition (it will be in MPI v0.090 and later versions).
Otherwise you must find some other way to MBR-boot or boot to a linux or Windows\WinPE system in order to switch back in the E2B partition.
If you want to try a variety of linux payloads from a single UEFI menu, try the E2B grub2 menu system - see Site Index for the page (but it has it's own set of drawbacks).
SteveSi
19/01/2019
Re: Re: How to restore E2B partition after switching to .imgPTN file
In fact the only tool I would want to use on daily basis would be rescatux (by the creator[s]) of the SuperGrubDisk. Since that is based on a linux live system, the bash file should work. I will try that.
I've read the page about using grub2 instead of grub4dos, but because of the drawbacks (and because of the fact that I wouldnt consider myself as an "expert" in terms of booting) I didnt try it so far.
Thank you for the fast response.
Also I tried to boot the switch-back-menu again on a much older laptop - and it works. It seems to be a problem with my current device (Acer Travelmate x349). Do you have any other advice considering the UEFI-Settings except Secure-Boot=Off, Fastboot=Off, Legacy-Boot/CSM=On that might help me to use the switch-back-menu on my laptop ?
I've read the page about using grub2 instead of grub4dos, but because of the drawbacks (and because of the fact that I wouldnt consider myself as an "expert" in terms of booting) I didnt try it so far.
Thank you for the fast response.
Also I tried to boot the switch-back-menu again on a much older laptop - and it works. It seems to be a problem with my current device (Acer Travelmate x349). Do you have any other advice considering the UEFI-Settings except Secure-Boot=Off, Fastboot=Off, Legacy-Boot/CSM=On that might help me to use the switch-back-menu on my laptop ?
C.F.
19/01/2019
Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
You have found the exact reason why E2B uses the .imgPTN scheme! Some BIOSes will ONLY UEFI boot from a UEFI-enabled USB drive even though you have enabled CSM mode. Many BIOSes have this bug. It means such solutions as SARDU or WinSetupFromUSB or YUMI will only be able to UEFI-boot on your system and it will never boot to the MBR menu so you cannot run any MBR payloads on those systems (unless you delete\rename the \EFI folder).
SteveSi
19/01/2019
Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
I see. Thank you. I thought of E2B being the problem because it does neither work on my current laptop nor on my tower-pc, but as it looks, both seem to have this bios / UEFI-bug, as it does work on my old laptop.
BTW I recommend your tool to everyone I think it would be usefull for and I know that min. 3 people also started using it. I realy dont know how I missed this for long.
BTW I recommend your tool to everyone I think it would be usefull for and I know that min. 3 people also started using it. I realy dont know how I missed this for long.
C.F.
19/01/2019
Re: Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
Either you have not set the BIOS options correctly OR your systems have this BIOS bug.
To check, select one of the .imgPTN images which show the problem and confirm that it will not boot to the CSM MBR menu. Then rename the \EFI folder to \EFIxx and try again. If it now boots to the CSM menu then your BIOS has a bug or it is set to boot from UEFI first. If it still does not boot to the CSM menu then you have not set up the BIOS settings correctly.
Always use the F8/F12 or whatever function key to get the BIOS Boot Selection Menu pop-up - do NOT set the boot order in the BIOS Settings menu to boot from USB first.
To check, select one of the .imgPTN images which show the problem and confirm that it will not boot to the CSM MBR menu. Then rename the \EFI folder to \EFIxx and try again. If it now boots to the CSM menu then your BIOS has a bug or it is set to boot from UEFI first. If it still does not boot to the CSM menu then you have not set up the BIOS settings correctly.
Always use the F8/F12 or whatever function key to get the BIOS Boot Selection Menu pop-up - do NOT set the boot order in the BIOS Settings menu to boot from USB first.
SteveSi
23/01/2019
Re: Re: Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
I checked my BIOS settings again. My Bios has only 2 options (concerning boot style): Legacy (only) and UEFI (only). So I dont have any option on how to boot the stick in the boot menu (like UEFI USB Stick: SanDisk... / USB Stick: SanDisk...) And since my local OS is MBR-installed, Legacy (only) is the choosen setting.
If I switch to an imgPTN Partition, the first time I boot I get the CSM menu. After I have booted the imgPTN-Payload once (Legacy-Mode, ofc.), my Notebook boots the payload immediately. This doesn't happen if I rename or delete the EFI folder. If I do that, it always boots to the CSM menu. I guess that means: buggy bios confirmed.
So I can't use the imgPTN-trick for uefi-booting (and switching back easily) with my notebook, but that's not realy a problem since I can totally live with Legacy-only booting. The only payload I wanna use on a daily basis that isn't bootable as a simple ISO is also fully functional when booted in Legacy-mode, so I will just delete its EFI-folder and use it this way.
Thanks again for the really fast and qualified help.
I still have one question: You wrote that I shouldn't set USB boot as the default option, but use the boot-menu-hotkey instead. Is there any technical difference between this two options ? If yes, what exactly ?
If I switch to an imgPTN Partition, the first time I boot I get the CSM menu. After I have booted the imgPTN-Payload once (Legacy-Mode, ofc.), my Notebook boots the payload immediately. This doesn't happen if I rename or delete the EFI folder. If I do that, it always boots to the CSM menu. I guess that means: buggy bios confirmed.
So I can't use the imgPTN-trick for uefi-booting (and switching back easily) with my notebook, but that's not realy a problem since I can totally live with Legacy-only booting. The only payload I wanna use on a daily basis that isn't bootable as a simple ISO is also fully functional when booted in Legacy-mode, so I will just delete its EFI-folder and use it this way.
Thanks again for the really fast and qualified help.
I still have one question: You wrote that I shouldn't set USB boot as the default option, but use the boot-menu-hotkey instead. Is there any technical difference between this two options ? If yes, what exactly ?
C.F.
25/01/2019
Re: Re: Re: Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
So what options do you actually see in the BIOS Boot selection pop-up menu? Does the BIOS Settings menu system show anything in 'Boot devices' or anything under + Hard disk?
You should not set the USB device as the first boot device in the BIOS settings because many BIOSes have a bug and they can tell an OS that the USB is the 'boot device' of your system. The result is if you then install an OS to your internal hard disk (XP, linux, etc.) you may find that the boot code and files have been installed onto your USB drive because that is the system 'boot device'.
Now the boot code on the USB drive is trashed and you can only boot to the internal hard disk if you first boot to your USB drive! This can often happen when using a USB HDD to install an OS from.
This issue can still happen when booting from the pop-up menu too, but E2B tries to fix it by swapping over the BIOS hd0 (USB drive) with hd1 (first internal HDD).
You should not set the USB device as the first boot device in the BIOS settings because many BIOSes have a bug and they can tell an OS that the USB is the 'boot device' of your system. The result is if you then install an OS to your internal hard disk (XP, linux, etc.) you may find that the boot code and files have been installed onto your USB drive because that is the system 'boot device'.
Now the boot code on the USB drive is trashed and you can only boot to the internal hard disk if you first boot to your USB drive! This can often happen when using a USB HDD to install an OS from.
This issue can still happen when booting from the pop-up menu too, but E2B tries to fix it by swapping over the BIOS hd0 (USB drive) with hd1 (first internal HDD).
SteveSi
25/01/2019
Re: Re: Re: Re: Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
Okay, possibly I was describing it a little bit misunderstandable.
If I choose the way to boot in the BIOS / UEFI, I have only two options:
1. Legacy
2. UEFI
https://ibb.co/wdnPgyd
(Screenshot of my BIOS settings)
I know about other PCs (at my workplace, for example) which have a third option, like "UEFI and Legacy" (or with a similar name). Take the following BIOS-Screenshot for example (not my BIOS):
https://browse.startpage.com/do/show_picture.pl?l=english&rais=1&oiu=https%3A%2F%2Fi1.wp.com%2Fneosmart.net%2Fwiki%2Fwp-content%2Fuploads%2Fsites%2F5%2F2014%2F05%2FASUS-Boot-Device-Control.jpg%3Fssl%3D1&sp=93d3a0226b9295113b636263aaf675d2&rl=to&t=default
At that place I can only choose between UEFI or Legacy. At the PCs with the "both" option, I can choose at the boot menu wether I want to boot the device in UEFI or in Legacy mode, it looks like at this screenshot:
https://browse.startpage.com/do/show_picture.pl?l=english&rais=1&oiu=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMHOP3VY4qZM%2Fmaxresdefault.jpg&sp=046dea4b255f12c3c9fb7bd8eba93bee&rl=to&t=default
And Since I can not choose the "both" option, I have no choise in the pop-up-boot-menu.
https://ibb.co/9b59NC0
<- My boot menu in legacy-mode) Thats all I wanted to clarify with my last post.
Thanks for the information about the default boot option. Luckily didn't encounter this problem so far, but good to know for the future.
If I choose the way to boot in the BIOS / UEFI, I have only two options:
1. Legacy
2. UEFI
https://ibb.co/wdnPgyd
(Screenshot of my BIOS settings)
I know about other PCs (at my workplace, for example) which have a third option, like "UEFI and Legacy" (or with a similar name). Take the following BIOS-Screenshot for example (not my BIOS):
https://browse.startpage.com/do/show_picture.pl?l=english&rais=1&oiu=https%3A%2F%2Fi1.wp.com%2Fneosmart.net%2Fwiki%2Fwp-content%2Fuploads%2Fsites%2F5%2F2014%2F05%2FASUS-Boot-Device-Control.jpg%3Fssl%3D1&sp=93d3a0226b9295113b636263aaf675d2&rl=to&t=default
At that place I can only choose between UEFI or Legacy. At the PCs with the "both" option, I can choose at the boot menu wether I want to boot the device in UEFI or in Legacy mode, it looks like at this screenshot:
https://browse.startpage.com/do/show_picture.pl?l=english&rais=1&oiu=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMHOP3VY4qZM%2Fmaxresdefault.jpg&sp=046dea4b255f12c3c9fb7bd8eba93bee&rl=to&t=default
And Since I can not choose the "both" option, I have no choise in the pop-up-boot-menu.
https://ibb.co/9b59NC0
<- My boot menu in legacy-mode) Thats all I wanted to clarify with my last post.
Thanks for the information about the default boot option. Luckily didn't encounter this problem so far, but good to know for the future.
C.F.
25/01/2019
Re: Re: Re: Re: Re: Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
OK, thanks. So your BIOS is like this one:
https://youtu.be/BA4Zhh2zU4c
Just a thought... did you try setting a BIOS Supervisor password? Sometimes you get more options when you do this.
https://youtu.be/BA4Zhh2zU4c
Just a thought... did you try setting a BIOS Supervisor password? Sometimes you get more options when you do this.
SteveSi
25/01/2019
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
Yes, my BIOS is 90 to 95% like the one in the YT Video. Not really surprising since it is an Acer, too.
About the Supervisor PW: Yes. I knew it so I did it, but the only additional setting which was availible after that, was a toggle for Secure Boot (and the corresponding settings at the security tab).
About the Supervisor PW: Yes. I knew it so I did it, but the only additional setting which was availible after that, was a toggle for Secure Boot (and the corresponding settings at the security tab).
C.F.
25/01/2019
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
OK - if the BIOS allows it, you can try setting Secure Boot = enabled + Legacy boot. Then if the EFI boot files are not signed (secure) it may boot in Legacy mode. Some payloads may have signed EFI boot files however, in which case this trick won't work!
SteveSi
26/01/2019
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: How to restore E2B partition after switching to .imgPTN file
Good Idea. I tried that. When I switch back to legacy-boot, the secure-boot switch gets hidden. It also makes no difference, if secure boot is on or off before I switch back to legacy.
Thank you very much for supporting me at this question.
Thank you very much for supporting me at this question.
C.F.
27/01/2019
Wrong year in version history page
In the version history page it say "v1.A8 2018-01-15" should that not be "v1.A8 2019-01-15"
[SS]It is called a typo!
[SS]It is called a typo!
Puzzled
18/01/2019
Virtual Machine USB Boot 1.72 doesn't work on VirtualBox 6.0
Hello,
I would like to ask if it is known that there is a problem with the Virtual Machine USB Boot 1.72 x64 and VirtualBox 6.0. If I want to start my USB-Stick I get an error message:
"--startvm ist eine Option für die VirtualBox VM-Ausführungs-Anwendung (VirtualBoxVM), nicht den VirtualBox Manager". Buttons under the error message: <OK> or <Kopieren>.
The error message ist from a German VBox Installation.
Maybe there is a fix around for this.
I would like to ask if it is known that there is a problem with the Virtual Machine USB Boot 1.72 x64 and VirtualBox 6.0. If I want to start my USB-Stick I get an error message:
"--startvm ist eine Option für die VirtualBox VM-Ausführungs-Anwendung (VirtualBoxVM), nicht den VirtualBox Manager". Buttons under the error message: <OK> or <Kopieren>.
The error message ist from a German VBox Installation.
Maybe there is a fix around for this.
Peter Kalauer
14/01/2019
Re: Virtual Machine USB Boot 1.72 doesn't work on VirtualBox 6.0
https://github.com/DavidBrenner3/VMUB/issues
SteveSi
14/01/2019
Re: Virtual Machine USB Boot 1.72 doesn't work on VirtualBox 6.0
Workaround for VBox v6:
VMUB - Options - VirtualBox - Exe Path = C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
VMUB - Options - VirtualBox - Exe Path = C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
SteveSi
14/01/2019
Re: Re: Virtual Machine USB Boot 1.72 doesn't work on VirtualBox 6.0
Thanks SteveSi, works like a charm. Thank you for all of the great work. Excellent support.
Peter Kalauer
15/01/2019
Re: Re: Re: Virtual Machine USB Boot 1.72 doesn't work on VirtualBox 6.0
http://rmprepusb.blogspot.com/2019/01/fix-issues-with-virtualbox-v6-and-vmub.html
Basically, it is best to use VBox v5 until DavidB releases a fix or someone else can fix.
Basically, it is best to use VBox v5 until DavidB releases a fix or someone else can fix.
SteveSi
16/01/2019
ISO contiguous issues
Hello again. I've set up another E2B stick. No background image issues this time!
But what is giving me a hard time is the ISO contiguous thing. For testing and demonstrations I made a 16GB Lexar USB3 stick with several flavors of Linux, like Fedora, Xubuntu, Manjaro etc.
After I loaded the ISOs I ran the make contiguous file and got an error there was not enough free space to make several files discontiguous. At this point there was about 2GB free. I started deleting some ISOs but the error would persist.
Finally, I removed all but one ISO, then could make that contiguous. Then I added ISOs one by one, each time running the make contiguous process.
I have about 5GB left and thinking about what would fit the idea of the stick I downloaded openSuse first to a harddisk. This image is 3.9GB large and I fear it can not be made contiguous if I copy it to the stick, and I would have wasted 4GB of the lifetime of the stick.
I do not exactly understand the purpose of the making contiguous process. I learned, fragmentation is no issue on flash memory, and even to be avoided.
When I write a single ISO to a single stick, there is never a problem with dis-contiguousness.
But what is giving me a hard time is the ISO contiguous thing. For testing and demonstrations I made a 16GB Lexar USB3 stick with several flavors of Linux, like Fedora, Xubuntu, Manjaro etc.
After I loaded the ISOs I ran the make contiguous file and got an error there was not enough free space to make several files discontiguous. At this point there was about 2GB free. I started deleting some ISOs but the error would persist.
Finally, I removed all but one ISO, then could make that contiguous. Then I added ISOs one by one, each time running the make contiguous process.
I have about 5GB left and thinking about what would fit the idea of the stick I downloaded openSuse first to a harddisk. This image is 3.9GB large and I fear it can not be made contiguous if I copy it to the stick, and I would have wasted 4GB of the lifetime of the stick.
I do not exactly understand the purpose of the making contiguous process. I learned, fragmentation is no issue on flash memory, and even to be avoided.
When I write a single ISO to a single stick, there is never a problem with dis-contiguousness.
Rick Vansloneker
19/12/2018
Re: ISO contiguous issues
The file is required to be contiguous because E2B uses it as a partition and actually writes the start address of the file to the USB stick's partition table. Linux will then see the ISO as a partition and so can easily access the files inside the ISO. Partitions cannot be fragmented - they start at sector X and finish at sector Y in one contiguous block. So the ISO must be contiguous.
See http://www.easy2boot.com/not-contiguous-error/ for more info.
You need to realise that WinContig needs a contiguous block of free space in order to move the ISO and make it contiguous. I use Defraggler to consolidate the free space on the drive if the free space starts to get fragmented.
P.S. As I say on this site, 16GB is really the minimum size for a multiboot drive - because you need at least 4GB of consolidated free space to make a 4GB file contiguous. So Use the Action - Advanced - Defrag Freespace option in Defraggler and then copy on your last file.
P.S. NEVER download files DIRECTLY to your USB drive from your browser - it usually makes the file fragmented, even if there was enough contiguous free space on the USB drive, because it opens up several 'streams' when downloading the file.
See http://www.easy2boot.com/not-contiguous-error/ for more info.
You need to realise that WinContig needs a contiguous block of free space in order to move the ISO and make it contiguous. I use Defraggler to consolidate the free space on the drive if the free space starts to get fragmented.
P.S. As I say on this site, 16GB is really the minimum size for a multiboot drive - because you need at least 4GB of consolidated free space to make a 4GB file contiguous. So Use the Action - Advanced - Defrag Freespace option in Defraggler and then copy on your last file.
P.S. NEVER download files DIRECTLY to your USB drive from your browser - it usually makes the file fragmented, even if there was enough contiguous free space on the USB drive, because it opens up several 'streams' when downloading the file.
SteveSi
19/12/2018
Re: Re: ISO contiguous issues
Thanks for explaining and thanks for the recommendations!
Rick Vansloneker
19/12/2018
Re: Re: ISO contiguous issues
After defraggling free space I copied the openSuse ISO and booted the E2B stick. A message appeared that Suse was discontiguous. I tried it anyway. I had to walk away for a minute and when I returned an installer had started: the Suse ISO wasn't a liveCD as I had intended! I'll remove it from the stick and find something else.
Rick Vansloneker
19/12/2018
Remastered Lubuntu doesn't boot
Hello, and thanks for this great tool!
What I want to do is this: add three or four Linux ISOs and make an Easy2Boot USB drive, make an ISO of the whole thing using RMPrepUsb, and then burn it to DVD. I have added two regular downloaded-from-the-website *buntu ISOs, and a Remastered version of Lubuntu (made using Pinguy Builder) in which I have added LibreOffice. This Remastered Lubuntu ISO alone boots in VirtualBox and directly on the computer, but when I add it to E2B and make an ISO of the E2B USB (to burn to DVD) and try to boot the Remastered Lubuntu by testing it in VirtualBox, I get a Kernel Panic.
E2B first tries to ISOBOOT the Remastered Lubuntu using ISO Cheat Codes, fails saying "Error: No initrd file found!", asks to "Press a key to boot..." to which I press the down arrow, a whole lot of text goes by as it tries to boot and then finally stops with the message: "---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)". This same Remastered Lubuntu boots otherwise, only not in E2B.
Please help. I'm a noob in such matters.
What I want to do is this: add three or four Linux ISOs and make an Easy2Boot USB drive, make an ISO of the whole thing using RMPrepUsb, and then burn it to DVD. I have added two regular downloaded-from-the-website *buntu ISOs, and a Remastered version of Lubuntu (made using Pinguy Builder) in which I have added LibreOffice. This Remastered Lubuntu ISO alone boots in VirtualBox and directly on the computer, but when I add it to E2B and make an ISO of the E2B USB (to burn to DVD) and try to boot the Remastered Lubuntu by testing it in VirtualBox, I get a Kernel Panic.
E2B first tries to ISOBOOT the Remastered Lubuntu using ISO Cheat Codes, fails saying "Error: No initrd file found!", asks to "Press a key to boot..." to which I press the down arrow, a whole lot of text goes by as it tries to boot and then finally stops with the message: "---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)". This same Remastered Lubuntu boots otherwise, only not in E2B.
Please help. I'm a noob in such matters.
FL99
13/11/2018
Re: Remastered Lubuntu doesn't boot
Hi
So your only problem is the remastered ISO - the other two ISOs work fine?
You can test ISOBOOT from an E2B drive by holding down the SHIFT key before you press ENTER to run the ISO from the menu.
It is probably easier to start a Chat session with me on the website if the ISOBOOT web page does not help you.
http://www.easy2boot.com/faq-/isoboot/
If the ISO contains a casper-rw file, you will probably need to extract it to the root of the E2B USB drive.
If the initrd file cannot be found, then ISOBOOT is probably looking for the wrong file. Look at the isolinux.cfg or grub.cfg file inside your remastered ISO file to see what cheat code parameters it is using. Then make a new ISOBOOT.g4b file as described on the isoboot web page above. If the iso is using initrd.gz then you will need to add the 'try' lines into the :.isoubu code section.
So your only problem is the remastered ISO - the other two ISOs work fine?
You can test ISOBOOT from an E2B drive by holding down the SHIFT key before you press ENTER to run the ISO from the menu.
It is probably easier to start a Chat session with me on the website if the ISOBOOT web page does not help you.
http://www.easy2boot.com/faq-/isoboot/
If the ISO contains a casper-rw file, you will probably need to extract it to the root of the E2B USB drive.
If the initrd file cannot be found, then ISOBOOT is probably looking for the wrong file. Look at the isolinux.cfg or grub.cfg file inside your remastered ISO file to see what cheat code parameters it is using. Then make a new ISOBOOT.g4b file as described on the isoboot web page above. If the iso is using initrd.gz then you will need to add the 'try' lines into the :.isoubu code section.
SteveSi
13/11/2018
Re: Re: Remastered Lubuntu doesn't boot
I have been looking at an ISO built with PinguyBuilder and it does not seem to support any cheat code parameter to specify the name of the ISO file. This means that the only way to boot it as you want to do from an E2B DVD is to extract the contents of the ISO to root of the E2B drive. If it works, you could then remove those folders from the remastered ISO.
However, if you are booting other ubuntu-based ISOs, they may find the \casper folder on the root of the DVD instead of the \casper folder inside the mounted ubuntu ISO, and so they would all boot to your remastered files instead of the files inside the ISO.
I suggest making a special .mnu file, extracting all the files from the remastered ISO (so the .iso file is not needed):
title Start PinguyOS 18.04.1 Full LTS
kernel /casper/vmlinuz file=/preseed/custom.seed boot=casper quiet splash --
initrd /casper/initrd.gz
boot
This works, but if the \casper folder is renamed and the menu adjusted, it no longer boots and so the other ubuntu ISOs may get 'confused' still! See https://forums.linuxmint.com/viewtopic.php?t=35567 for how to modify it to boot from a different folder.
However, if you are booting other ubuntu-based ISOs, they may find the \casper folder on the root of the DVD instead of the \casper folder inside the mounted ubuntu ISO, and so they would all boot to your remastered files instead of the files inside the ISO.
I suggest making a special .mnu file, extracting all the files from the remastered ISO (so the .iso file is not needed):
title Start PinguyOS 18.04.1 Full LTS
kernel /casper/vmlinuz file=/preseed/custom.seed boot=casper quiet splash --
initrd /casper/initrd.gz
boot
This works, but if the \casper folder is renamed and the menu adjusted, it no longer boots and so the other ubuntu ISOs may get 'confused' still! See https://forums.linuxmint.com/viewtopic.php?t=35567 for how to modify it to boot from a different folder.
SteveSi
13/11/2018
Re: Re: Re: Remastered Lubuntu doesn't boot
Thanks for the reply. Yes, only the Remastered Lubuntu doesn't boot, the other ISOs work fine.
Actually I don't understand all this stuff about casper and initrd and stuff, I'm a noob, and I am still learning. So I'll keep learning and tinkering, and maybe after I've gained some amount of knowledge about how the Linux booting works, and still have a doubt, I'll ask you again then. Thanks again!
Actually I don't understand all this stuff about casper and initrd and stuff, I'm a noob, and I am still learning. So I'll keep learning and tinkering, and maybe after I've gained some amount of knowledge about how the Linux booting works, and still have a doubt, I'll ask you again then. Thanks again!
FL99
14/11/2018
Re: Re: Re: Re: Remastered Lubuntu doesn't boot
Sorry to bug you again, and maybe I am just typing what I typed earlier, but the problem I face is that the Remastered ISO only boots if the media is not write-protected. If I add the Remastered Lubuntu to a USB drive, reboot, and try to boot the Remastered Lubuntu normally, the regular way Easy2Boot boots it, it works fine. If however, I press the Shift key when selecting the ISO, it is not able to boot it.
If I try to boot it with the Shift key, first E2B asks whether to change the extension, then gives a screen with a huge list of options one of which has to be typed, and if I select the first option to just boot it, a lot of text goes by and finally it ends in kernel panic - "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)". But if at the E2B options screen where it asks how to boot the ISO, I select the option to load the entire ISO to RAM, then it loads the ISO to RAM and boots fine.
The problem I think is because of the media being write-protected. Is there any simple workaround for this?
FL99
20/11/2018
Re: Re: Re: Re: Re: Remastered Lubuntu doesn't boot
If it works when you load the ISO into memory, then simply change the file extension to the one that works (e.g. .isomem).
But I already told you how to get it to work.
1. Extract all the files from the ISO onto the root of the E2B USB drive.
2. Add a .mnu file (as detailed earlier) to the \_ISO\MAINMENU folder.
Or just convert the ISO to a FAT32 .imgPTN file.
But I already told you how to get it to work.
1. Extract all the files from the ISO onto the root of the E2B USB drive.
2. Add a .mnu file (as detailed earlier) to the \_ISO\MAINMENU folder.
Or just convert the ISO to a FAT32 .imgPTN file.
SteveSi
20/11/2018
partition restrictions
Hello again steve, i have a question about the partition restrictions when using e2b scripts to build a menu and load images. I know you stated we can have either ONLY 2 primary partitions or ONE primary and any number of logical partitions. I am using fbinst hidden partition to boot e2b, is that hidden fbinst partition counted as a primary partition? If so would e2b still run fine if i changed the partition it resides on to a logical partition?
JJ
26/10/2018
Re: partition restrictions
Use RMPrepUSB - Drive Info - 0
to examine the partition table.
It will show you the four table entries and how they are used.
to examine the partition table.
It will show you the four table entries and how they are used.
SteveSi
26/10/2018
Language for CSM
The file MyCSM.cfg says:
"#set the language (uses \e2b\LANG\%LANG%.txt file)"
But there is no such folder. And according to the file too.
PS. How to set the Russian language for the CSM menu (NOT FOR MAINMENU)
"#set the language (uses \e2b\LANG\%LANG%.txt file)"
But there is no such folder. And according to the file too.
PS. How to set the Russian language for the CSM menu (NOT FOR MAINMENU)
БлагоЯр Тишина
20/10/2018
Re: Language for CSM
Sorry, only English and German are currently available. All details are on this website, use the Site Map. You must have latest version of MPI.
http://www.easy2boot.com/configuring-e2b/csm-menu-changes/
http://www.easy2boot.com/configuring-e2b/csm-menu-changes/
SteveSi
20/10/2018
Re: Re: Language for CSM
I always have the latest version
PS. Is it possible to translate (I can do it)?
PS. Is it possible to translate (I can do it)?
БлагоЯр Тишина
20/10/2018
Re: Re: Re: Language for CSM
Yes, please send me a translated ENG.txt file when you have it working. Save in UTF-8 format using Notepad.
SteveSi
20/10/2018
Fbinst & Easy2Boot
Hello everybody, today i was messing around with a few bootable usb's i had laying around. I decided to create a FBINST usb drive and attempt to load e2b from it....im not having much luck. Is e2b compatible with fbinst boot partition (ud)? I got it to boot up by using the --set-root command but i noticed a few errors pop up with e2b, likely due to fbinst being mapped to (bd)
JJ
11/10/2018
Re: Fbinst & Easy2Boot
https://www.rmprepusb.com/tutorials/usbutils
You put grldr in the hidden Primary area but all other files in the 'normal' area using Windows Explorer.
You can format the normal area first to NTFS using Windows Format.
It is not really suitable for E2B because it is not compatible with .imgPTN files.
You put grldr in the hidden Primary area but all other files in the 'normal' area using Windows Explorer.
You can format the normal area first to NTFS using Windows Format.
It is not really suitable for E2B because it is not compatible with .imgPTN files.
SteveSi
12/10/2018
Re: Re: Fbinst & Easy2Boot
Thanks steve, i'll give it another try.
JJ
12/10/2018
SUB_MENU_MAKER
Hello everybody
I came across the Easy2Boot a few days ago and I am very excited about it. First a great praise to the developers.
Now to my question:
It is indeed the file "SUB_MENU_MAKER" to create menu items. How can I do it that I get menu sub items? As an example: There is indeed the Linux folder. I would now like to create subfolders in this folder, such as "Ubuntu" or Debian. "This is how it should be visible in the menu, first as" Linux "and then follow the subfolders, but always with the" SUB_MENU_MAKER " only menu items in the main menu.
Can you tell me how I have to implement that, because I seem to be really stupid for it.
Greetings Marcel
I came across the Easy2Boot a few days ago and I am very excited about it. First a great praise to the developers.
Now to my question:
It is indeed the file "SUB_MENU_MAKER" to create menu items. How can I do it that I get menu sub items? As an example: There is indeed the Linux folder. I would now like to create subfolders in this folder, such as "Ubuntu" or Debian. "This is how it should be visible in the menu, first as" Linux "and then follow the subfolders, but always with the" SUB_MENU_MAKER " only menu items in the main menu.
Can you tell me how I have to implement that, because I seem to be really stupid for it.
Greetings Marcel
Marcel
11/10/2018
Re: SUB_MENU_MAKER
All menu folders must be directly under \_ISO.
To do what you want, just make a new folder called \_ISO\LINUX_Ubuntu and drag-and-drop this folder onto the Sub_Menu_Maker.cmd file. This will make a .mnu file in \_ISO\MAINMENU folder.
Then simply move the new .mnu file to \_ISO\LINUX folder. see
http://www.easy2boot.com/configuring-e2b/add-a-new-menu-folder/
'Example for Linux - Ubuntu sub-sub-menu'
To do what you want, just make a new folder called \_ISO\LINUX_Ubuntu and drag-and-drop this folder onto the Sub_Menu_Maker.cmd file. This will make a .mnu file in \_ISO\MAINMENU folder.
Then simply move the new .mnu file to \_ISO\LINUX folder. see
http://www.easy2boot.com/configuring-e2b/add-a-new-menu-folder/
'Example for Linux - Ubuntu sub-sub-menu'
SteveSi
11/10/2018
Results from ISO conversion to imgPTN
When I drop an iso onto the MPI_xx desktop icons, everything goes just fine, but just before it all wraps up I see a series of comments regarding the imgPTN file (below) is this anything I should follow up on? Do I need to make these changes within the resulting image file?
INFORMATION: LABEL occurs in .LST files
INFORMATION: 'boot=' occurs in .CFG files
UUID should use 74AAC0F4AAC0B3C0
CDLABEL should be LABEL
LABEL should use EASY2BOOT
'media=cdrom' should be 'media=usb'
If it matters, the ISO is Kaspersky Rescue Disk 2018.
Thank you by the way, the software is great, but your support is amazing.
-James
INFORMATION: LABEL occurs in .LST files
INFORMATION: 'boot=' occurs in .CFG files
UUID should use 74AAC0F4AAC0B3C0
CDLABEL should be LABEL
LABEL should use EASY2BOOT
'media=cdrom' should be 'media=usb'
If it matters, the ISO is Kaspersky Rescue Disk 2018.
Thank you by the way, the software is great, but your support is amazing.
-James
James Pelt
24/09/2018
Re: Results from ISO conversion to imgPTN
It is for information only, no action is needed. MPI will adjust these for you.
SteveSi
24/09/2018
Booting on GPT systems
Good morning, I am able to install the framework on empty pen drive, fill in desired ISOs and multiboot on MBR computer, but the drive is ignored on GPT computer even though it takes highest priority in boot sequence order, so I suppose it's not compatible.
Is there a trick or workaround that would make the E2B bootloader compatible with both MBR and GPT BIOSes?
Is there a trick or workaround that would make the E2B bootloader compatible with both MBR and GPT BIOSes?
Hurvajz
23/09/2018
Re: Booting on GPT systems
You cannot UEFI-boot to the E2B menu system.
If you want to UEFI-boot from the E2B USB drive, you must make a UEFI-compatible .imgPTN file using the MPI Tool Kit and then select the .imgPTN file from the E2B menu system (MBR-boot) or use \_ISO\SWITCH_E2B.exe to select the .imgPTN file.
Once the .imgPTN file has been 'switched in', you can then UEFI-boot or MBR-boot from the E2B drive.
See http://www.easy2boot.com/add-payload-files/e2b-uefi/
If you want to UEFI-boot from the E2B USB drive, you must make a UEFI-compatible .imgPTN file using the MPI Tool Kit and then select the .imgPTN file from the E2B menu system (MBR-boot) or use \_ISO\SWITCH_E2B.exe to select the .imgPTN file.
Once the .imgPTN file has been 'switched in', you can then UEFI-boot or MBR-boot from the E2B drive.
See http://www.easy2boot.com/add-payload-files/e2b-uefi/
SteveSi
23/09/2018
Re: Re: Booting on GPT systems
OK, is there a different known multiboot framework that once installed out of the box will boot as with UEFI as with MBR BIOSes?
I understand it as that I need different image for MBR and different for UEFI? I'd prefer rather to share one image for all platforms.
I understand it as that I need different image for MBR and different for UEFI? I'd prefer rather to share one image for all platforms.
Hurvajz
26/09/2018
Re: Re: Re: Booting on GPT systems
You can MBR or UEFI boot from the same .imgPTN file - the ISO is not required if you use .imgPTN files.
The problem with other multiboot solutions is that some systems (Fujitsu LifeBook, Samsung, Acer and probably others too) refuse to MBR boot if an EFI boot file is present on a FAT partition. This means, that on these systems, they will not boot via MBR to MBR payloads such as Hirens, many linux OS's, DOS, Mini XP, etc. because they will *always* UEFI boot instead.
UEFI requires a FAT partition to be on the drive and many other products just use a FAT32 USB drive which limits the file size to 4GB per file.
You can try the E2B grub2 menu system, or other products such as YUMI UEFI Beta version, SARDU, WinSetupFromUSB (for Windows UEFI) or multisystem. http://www.easy2boot.com/uefi-grub2-ptn2/
I am afraid there is no good universal solution because of these 'buggy' BIOSes.
That is why E2B uses the .imgPTN scheme - so that you can boot on 99% of all systems including those with this annoying bug.
Also, the E2B .imgPTN scheme means you can Secure Boot and boot from a wide variety of payloads (linux, Windows, KonBoot, memtest, etc.) all from the one USB drive.
If you want to spend some money, try the IODD USB HDD enclosure https://rmprepusb.blogspot.com/2016/09/using-e2b-with-zalmaniodd-disk-drive.html
The problem with other multiboot solutions is that some systems (Fujitsu LifeBook, Samsung, Acer and probably others too) refuse to MBR boot if an EFI boot file is present on a FAT partition. This means, that on these systems, they will not boot via MBR to MBR payloads such as Hirens, many linux OS's, DOS, Mini XP, etc. because they will *always* UEFI boot instead.
UEFI requires a FAT partition to be on the drive and many other products just use a FAT32 USB drive which limits the file size to 4GB per file.
You can try the E2B grub2 menu system, or other products such as YUMI UEFI Beta version, SARDU, WinSetupFromUSB (for Windows UEFI) or multisystem. http://www.easy2boot.com/uefi-grub2-ptn2/
I am afraid there is no good universal solution because of these 'buggy' BIOSes.
That is why E2B uses the .imgPTN scheme - so that you can boot on 99% of all systems including those with this annoying bug.
Also, the E2B .imgPTN scheme means you can Secure Boot and boot from a wide variety of payloads (linux, Windows, KonBoot, memtest, etc.) all from the one USB drive.
If you want to spend some money, try the IODD USB HDD enclosure https://rmprepusb.blogspot.com/2016/09/using-e2b-with-zalmaniodd-disk-drive.html
SteveSi
26/09/2018
Multiple backgrounds and/or Stamps (v1.A1+)
Hi.
It seems that this manual don´t work with new submenu folders created with SUB_MENU_Maker.cmd.
I can´t set a personal background to this folders. I copy it to _ISO folder with the same name that the folder and don´t work. It seems that .g4b files don´t work too.
The normal folders works OK, but created don´t.
It seems that this manual don´t work with new submenu folders created with SUB_MENU_Maker.cmd.
I can´t set a personal background to this folders. I copy it to _ISO folder with the same name that the folder and don´t work. It seems that .g4b files don´t work too.
The normal folders works OK, but created don´t.
Visolo
07/09/2018
Re: Multiple backgrounds and/or Stamps (v1.A1+)
Sorry, it's a bug in the SubMenu Maker script.
Ensure that there is no space character at the end of the set MFOLDER= line in the .mnu file.
I will fix in 1.A2 v. soon!
Ensure that there is no space character at the end of the set MFOLDER= line in the .mnu file.
I will fix in 1.A2 v. soon!
SteveSi
07/09/2018
Re: Re: Multiple backgrounds and/or Stamps (v1.A1+)
Working great in E2B v1.A2a Beta. Thanks for your work.
Visolo
07/09/2018
Grub2 menu system - no ISOs listed?
If you have tried the grub2 menu system, and could not get any ISOs to be listed in the menu, this issue should now be fixed with the new Beta9 version.
SteveSi
27/08/2018
NO FUNCIONA EN SSD 120GB EN USB PERFECTO
Buenas noches, he probado E2B en USB 32Gb y funciona de lo mejor,sin embargo trate de hacer lo mismo en SSD 120Gb pero no funciona correctamente, por ejemplo cuando voy a formatear win7 no encuentra los controladores del HDD que se va a formatear, o cuando booting HirenBoot15CD no funciona todas las opciones, espero puedan ayudarme, Gracias!
Good evening, I tested E2B on USB 32Gb and it works best, however try to do the same in SSD 120Gb but it does not work properly, for example when I go to format win7 it does not find the drivers of the HDD that is going to be formatted, or when booting HirenBoot15CD does not work all the options, I hope you can help me, Thanks!
Good evening, I tested E2B on USB 32Gb and it works best, however try to do the same in SSD 120Gb but it does not work properly, for example when I go to format win7 it does not find the drivers of the HDD that is going to be formatted, or when booting HirenBoot15CD does not work all the options, I hope you can help me, Thanks!
Eduardo H. Mertz
19/08/2018
Re: NO FUNCIONA EN SSD 120GB EN USB PERFECTO
http://www.easy2boot.com/make-an-easy2boot-usb-drive/how-to-make-a-helper-usb-flash-drive/
http://www.easy2boot.com/add-payload-files/hirens-isos/
http://www.easy2boot.com/add-payload-files/hirens-isos/
SteveSi
19/08/2018
Grub menu password
The default password of "easy2boot" does not work. I have tried adding "set psw=" to my MyE2B.cfg. Problem is if I set the password to whatever, it doesn't work...same for an md5 hash. Simply states Failed and restarts the menu. Now if I leave the "set psw=" blank to remove the password, it works and I am able to access the grub console. Any help is appreciated. Thanks
BrianB
23/04/2018
Re: Grub menu password
Hi
You should be setting pwd not psw and it is grub4dos not grub!
e.g.
set pwd=fred
Are you using a standard QWERTY keyboard?
If not, have you set the KBD type - as in Sample_MyE2B.cfg
# ---- KEYBOARD TYPE -----
#set which keyboard you are using (use one only!) - see the KBD_xxxx.g4b files in the grub folder if you want to modify the key mapping
#Note: Passwords may not work properly if the keyboard scan code mapping is not correct! Default = US keyboard
###set KBD=KBD_AZERTY.g4b
###set KBD=KBD_FRENCH.g4b
###set KBD=KBD_GERMAN.g4b
###set KBD=KBD_ITALIANO.g4b
###set KBD=KBD_JAPAN_106.g4b
###set KBD=KBD_QWERTY_UK.g4b
###set KBD=KBD_QWERTZ.g4b
###set KBD=KBD_SPANISH.G4B
You should be setting pwd not psw and it is grub4dos not grub!
e.g.
set pwd=fred
Are you using a standard QWERTY keyboard?
If not, have you set the KBD type - as in Sample_MyE2B.cfg
# ---- KEYBOARD TYPE -----
#set which keyboard you are using (use one only!) - see the KBD_xxxx.g4b files in the grub folder if you want to modify the key mapping
#Note: Passwords may not work properly if the keyboard scan code mapping is not correct! Default = US keyboard
###set KBD=KBD_AZERTY.g4b
###set KBD=KBD_FRENCH.g4b
###set KBD=KBD_GERMAN.g4b
###set KBD=KBD_ITALIANO.g4b
###set KBD=KBD_JAPAN_106.g4b
###set KBD=KBD_QWERTY_UK.g4b
###set KBD=KBD_QWERTZ.g4b
###set KBD=KBD_SPANISH.G4B
SteveSi
23/04/2018
Re: Re: Grub menu password
psw was a typing error. I am using US azerty keyboard. As I said, set pwd= works without a password but not with one...either text or md5
BrianB
23/04/2018
Re: Re: Re: Grub menu password
disregard...I thought the first choice for keyboard layout was US. My bad.
Brian
24/04/2018
Re: Re: Re: Re: Grub menu password
To make it work for both QWERTY and AZERTY do not use letter keys, a q w m or z in the password (and avoid numbers and special characters too!).
SteveSi
24/04/2018
correct sized uncompressed wallpaper not accepted
It's not the end of the world but I have tried to put in my default wallpaper to E2B. I tried both jpeg's and bitmaps, uncompressed, not progressive, 800x600 and 1024x768 and each and every file is rejected for being the wrong size, where a size is displayed that is not that of the image. Even Sample_MyBackground.jpg is rejected as being 640x480.
Version of E2B is the current download.
Version of E2B is the current download.
Rick Vansloneker
11/04/2018
Re: correct sized uncompressed wallpaper not accepted
You mean rejected by E2B_Editor or rejected by E2B?
The sample file should work. Maybe you have strange DPI setting or some other OS display setting different from normal systems.
Can you try on a different system?
Have you actually booted to E2B using one of the graphics files?
If still no luck, enter Chat session with me.
The sample file should work. Maybe you have strange DPI setting or some other OS display setting different from normal systems.
Can you try on a different system?
Have you actually booted to E2B using one of the graphics files?
If still no luck, enter Chat session with me.
SteveSi
11/04/2018
Re: Re: correct sized uncompressed wallpaper not accepted
Thanks for the reply. E2B_Editor rejects the files for being faulty dimensioned. And yes I have booted them all and none of them shows up. Will try another system but if even Sample_MyBackground.jpg is rejected I am pretty sure it has nothing to do with my OS or DPI.
Rick Vansloneker
12/04/2018
Re: Re: Re: correct sized uncompressed wallpaper not accepted
Well the sample file works for me on three different Windows systems and no one else has mentioned it (well over 500,000 downloads). So it seems that there is something different about your system? If you still have problems, give details of your system OS and display.
SteveSi
12/04/2018
Re: Re: Re: Re: correct sized uncompressed wallpaper not accepted
Thanks again for the reply. I have now tried it in Windows 10 Pro/UK/64. My preferred imaged is accepted, but still does not show up when the stick is booted. It is visible in the editor. In the MyE2B.cfg I see no reference to any background image. Yes, I did click Save cfg file.
MyE2B.cfg:
!BAT
# See \_ISO\Sample_MyE2B.cfg for many more settings
if "%LANG%"=="" set LANG=ENG
set KBD=
# ---- ADVANCED MENU SETTINGS -----
set EXTOFF=1
# This drive is the removable type - so don't look for a WINHELPER USB Flash drive
set NOHELPER=1
set ANIMFD3=/_ISO/docs/Templates/Animate/E2B_GIF.ima
set ANIMATE=0x90=3=9=615=160 (fd3)/frame_0001.bmp
set STAMP1=0x80=570=23 /_ISO/e2b/grub/E2BPlate.bmp
MyE2B.cfg:
!BAT
# See \_ISO\Sample_MyE2B.cfg for many more settings
if "%LANG%"=="" set LANG=ENG
set KBD=
# ---- ADVANCED MENU SETTINGS -----
set EXTOFF=1
# This drive is the removable type - so don't look for a WINHELPER USB Flash drive
set NOHELPER=1
set ANIMFD3=/_ISO/docs/Templates/Animate/E2B_GIF.ima
set ANIMATE=0x90=3=9=615=160 (fd3)/frame_0001.bmp
set STAMP1=0x80=570=23 /_ISO/e2b/grub/E2BPlate.bmp
Rick Vansloneker
13/04/2018
Re: Re: Re: Re: Re: correct sized uncompressed wallpaper not accepted
If it is not in the \_ISO\MyE2B.cfg file on the USB drive, then of course it wont be loaded by E2B.
Try this
1. Run \_ISO\E2B_editor.exe
2. Load the \_ISO\MyE2B.cfg
3. Load the Sample_MyBackground.jpg
4. Click on 'Save config' button
5. Click Yes so file is saved as MyE2B.cfg - click OK if warned about Advanced Menu settings
6. Notepad should run and load the MyE2B.cfg file for you to see or edit. First lines should be:
!BAT
#Generated by E2B_Editor
set GMODE=800
set MYWBMP=/_ISO/Sample_MyBackground.jpg
#MENU
Try this
1. Run \_ISO\E2B_editor.exe
2. Load the \_ISO\MyE2B.cfg
3. Load the Sample_MyBackground.jpg
4. Click on 'Save config' button
5. Click Yes so file is saved as MyE2B.cfg - click OK if warned about Advanced Menu settings
6. Notepad should run and load the MyE2B.cfg file for you to see or edit. First lines should be:
!BAT
#Generated by E2B_Editor
set GMODE=800
set MYWBMP=/_ISO/Sample_MyBackground.jpg
#MENU
SteveSi
13/04/2018
Re: Re: Re: Re: Re: Re: correct sized uncompressed wallpaper not accepted
That did the trick! Once set MYWBMP=/_ISO/Sample_MyBackground.jpg was in the config I simply changed it with the filename of my preferred background and finally it showed up.
I tested it on a system with disconnected drives, and got a rather penetrating magenta message immediately after booting about missing drives. I ticked no error messages but that didn't remove it.
And can I get rid of the spinning E2B logo? It looks nineties and cheap, and is in the wrong place covering my background. E2B deserves a better logo imho.
So far I loaded a couple of Linux ISO's in E2B and it actually works to boot them. This is the very 1st multi USB boot I ever got to work properly, well done to you!
I tested it on a system with disconnected drives, and got a rather penetrating magenta message immediately after booting about missing drives. I ticked no error messages but that didn't remove it.
And can I get rid of the spinning E2B logo? It looks nineties and cheap, and is in the wrong place covering my background. E2B deserves a better logo imho.
So far I loaded a couple of Linux ISO's in E2B and it actually works to boot them. This is the very 1st multi USB boot I ever got to work properly, well done to you!
Rick Vansloneker
13/04/2018
Re: Re: Re: Re: Re: Re: Re: correct sized uncompressed wallpaper not accepted
The warning message just warns you that there is no internal hard disk in the system. I do not recommend suppressing messages until you become experienced in E2B - the messages help you to get it to work properly!
If the system you use to boot E2B from has a hard disk, you won't see it.
The spinning logo animation is determined by the MyE2B.cfg file - see the set ANIMATE line?
Just comment it out. There is plenty of info on the E2B site - use the SITE MAP to find the relevant page.
What is the filename of your background file?
If the system you use to boot E2B from has a hard disk, you won't see it.
The spinning logo animation is determined by the MyE2B.cfg file - see the set ANIMATE line?
Just comment it out. There is plenty of info on the E2B site - use the SITE MAP to find the relevant page.
What is the filename of your background file?
SteveSi
13/04/2018
Re: Re: Re: Re: Re: Re: Re: Re: correct sized uncompressed wallpaper not accepted
Thanks again, also for pointing me to the site map. I see there is more into E2B than 1st meets the eye!
The exact image I use is here: ibb.co/ekCNbn
The exact image I use is here: ibb.co/ekCNbn
Rick Vansloneker
14/04/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: correct sized uncompressed wallpaper not accepted
I downloaded it to the \_ISO folder and it loaded fine in the E2B_Editor! Then saved the MyE2B.cfg file and it worked fine when booted. So not sure why it does not work for you???
SteveSi
14/04/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: correct sized uncompressed wallpaper not accepted
Correction: why it didn't work.
Me dunno either, but at least now it works!
Me dunno either, but at least now it works!
Rick Vansloneker
14/04/2018
RMPrepUSB: mke2fs command failed
Hi.
Here Win8.1pro 64bit, E2B usb drive (Easy2Boot v1.97A) and RMPrepUSB v2.1.741 portable ("run as administrator").
I'm trying to make a persistence drweb iso (btw, there isn't any DrWeb900_Persistent.mnu persistence file in Sample mnu Files folder).
Iso file: drweb-livedisk-900-cd.isopersist
In RMPrepUSB v2.1.741, click on "Create "Ext2/3/4 FS":
-----------------------
1- "Create Ext filesystem" window ("i:" is my e2b usb drive):
Create a file of 1000MB on volume i:
fsutil.exe file createnew "i:\drweb-livedisk-900-cd-rw" 1000000000
-----------------------
Click on "OK".
2- "Convert to Ext filesystem" window:
Convert file \drweb-livedisk-900-cd-rw to an ext3 filesystem of 1000MB on volume i:
mke2fs.exe -F -L casper-rw -t ext3 "i:\drweb-livedisk-900-cd-rw"
-----------------------
Click on "OK" but then it throws a RMPrepUSB error:
"ERROR: mke2fs command failed (see mke2fs.log for details)"
By the way, I didn't find any mke2fs.log file.
Thanks.
Here Win8.1pro 64bit, E2B usb drive (Easy2Boot v1.97A) and RMPrepUSB v2.1.741 portable ("run as administrator").
I'm trying to make a persistence drweb iso (btw, there isn't any DrWeb900_Persistent.mnu persistence file in Sample mnu Files folder).
Iso file: drweb-livedisk-900-cd.isopersist
In RMPrepUSB v2.1.741, click on "Create "Ext2/3/4 FS":
-----------------------
1- "Create Ext filesystem" window ("i:" is my e2b usb drive):
Create a file of 1000MB on volume i:
fsutil.exe file createnew "i:\drweb-livedisk-900-cd-rw" 1000000000
-----------------------
Click on "OK".
2- "Convert to Ext filesystem" window:
Convert file \drweb-livedisk-900-cd-rw to an ext3 filesystem of 1000MB on volume i:
mke2fs.exe -F -L casper-rw -t ext3 "i:\drweb-livedisk-900-cd-rw"
-----------------------
Click on "OK" but then it throws a RMPrepUSB error:
"ERROR: mke2fs command failed (see mke2fs.log for details)"
By the way, I didn't find any mke2fs.log file.
Thanks.
dexter
08/03/2018
Re: RMPrepUSB: mke2fs command failed
Works OK for me - are you using NTFS for USB drive?
Is there enough free space on your USB drive?
Press F3 to see the folder where the log file is made.
.mnu file is in E2B v1.98 and later.
Is there enough free space on your USB drive?
Press F3 to see the folder where the log file is made.
.mnu file is in E2B v1.98 and later.
SteveSi
08/03/2018
Re: Re: RMPrepUSB: mke2fs command failed
> are you using NTFS for USB drive?
No (fat32), Is it a problem?
> Is there enough free space on your USB drive?
Yes, many GB.
thanks
No (fat32), Is it a problem?
> Is there enough free space on your USB drive?
Yes, many GB.
thanks
dexter
08/03/2018
Re: Re: RMPrepUSB: mke2fs command failed
> Press F3 to see the folder where the log file is made.
It doesn't work, quickly (less than one second) It opens (F3 in RMPREPUSB) the RMPREPUSB's folder only and there's no message in RMPREPUSB's gui (only the "Error: etc." message, in red).
BUT, I FOUND THE CULPRIT: RMPREPUSB doesn't like its folder path (currently is "c:\(inLine\(LOW_LEVEL-OS_DEPLOYMENT\RMPrepUSB\").
I put It in c:\RMPrepUSB\ and all works fine!!
Sorry Steve :-(
Thanks
It doesn't work, quickly (less than one second) It opens (F3 in RMPREPUSB) the RMPREPUSB's folder only and there's no message in RMPREPUSB's gui (only the "Error: etc." message, in red).
BUT, I FOUND THE CULPRIT: RMPREPUSB doesn't like its folder path (currently is "c:\(inLine\(LOW_LEVEL-OS_DEPLOYMENT\RMPrepUSB\").
I put It in c:\RMPrepUSB\ and all works fine!!
Sorry Steve :-(
Thanks
dexter
08/03/2018
Re: Re: Re: RMPrepUSB: mke2fs command failed
Using () parentheses in paths and filenames is a bad idea! Also using other odd characters like & and ! and | is a bad idea too!
SteveSi
08/03/2018
Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
Hi Steve.
I think I've found a critical bug in latest VBox 5.2.8. It causes a *host* computer BSOD when booting a VM using a physical E2B drive attached to host computer using the raw VMDK/Virtual Machine USB Boot tool trick.
Used E2B is updated to latest v1.98 and it boots the host physical computer as well as the same VM (if previous VBox versions up to 5.2.6 are used) without issuess.
I've narrowed the problem down to triggers being 2 lines (if commented out with # then no BSOD) in \_ISO\e2b\grub\menu.lst:
line 548
dd if=(md)0x3000+0xA0 of=(md)0xa000+0xA0 > nul
and line 575
cat --locate="\ntimeout " --replace=\n# (md)0xa000+0xA0
Both lines try to access memory at 0xA000 and seem related to the FASTLOAD feature. Other 3 lines access memory at that offset previously (443, 444 and 451) but I've not tested their impact because they are not executed if FASTLOAD is not enabled by user (I don't use it). However lines 548 and 575 are unconditionally executed.
This is clearly a bug in latest VBox (current and previous E2B works like a charm on real hardware and previous VBox versions), but I would like to get bug confirmation from you if possible since opening a ticket at VBox bug tracker is going to requiere some cumbersome account creation.
Thanks in advance.
I think I've found a critical bug in latest VBox 5.2.8. It causes a *host* computer BSOD when booting a VM using a physical E2B drive attached to host computer using the raw VMDK/Virtual Machine USB Boot tool trick.
Used E2B is updated to latest v1.98 and it boots the host physical computer as well as the same VM (if previous VBox versions up to 5.2.6 are used) without issuess.
I've narrowed the problem down to triggers being 2 lines (if commented out with # then no BSOD) in \_ISO\e2b\grub\menu.lst:
line 548
dd if=(md)0x3000+0xA0 of=(md)0xa000+0xA0 > nul
and line 575
cat --locate="\ntimeout " --replace=\n# (md)0xa000+0xA0
Both lines try to access memory at 0xA000 and seem related to the FASTLOAD feature. Other 3 lines access memory at that offset previously (443, 444 and 451) but I've not tested their impact because they are not executed if FASTLOAD is not enabled by user (I don't use it). However lines 548 and 575 are unconditionally executed.
This is clearly a bug in latest VBox (current and previous E2B works like a charm on real hardware and previous VBox versions), but I would like to get bug confirmation from you if possible since opening a ticket at VBox bug tracker is going to requiere some cumbersome account creation.
Thanks in advance.
Starla
06/03/2018
Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
Hi
Well done for tracking down the lines!
I noticed the issue too and have reported the problem on the VBox forum already.
https://forums.virtualbox.org/viewtopic.php?f=6&t=86992&sid=100082440671fbaa05211550e3cceb26
P.S. 0xA000 is nothing to do with fastload, it is just where the Main Menu is stored by E2B (address 20MB) for quick reloading of the Main menu.
Well done for tracking down the lines!
I noticed the issue too and have reported the problem on the VBox forum already.
https://forums.virtualbox.org/viewtopic.php?f=6&t=86992&sid=100082440671fbaa05211550e3cceb26
P.S. 0xA000 is nothing to do with fastload, it is just where the Main Menu is stored by E2B (address 20MB) for quick reloading of the Main menu.
SteveSi
06/03/2018
Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
Very nice Steve.
Here is BSOD summary (in case you want to add it to your VBox forum post)
Bug Check String: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code: 0x000000d1
Parameter 1: 00000000`00000028
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000000
Parameter 4: fffff880`09abfe2d
Caused By Driver: VMMR0.r0
Caused By Address: VMMR0.r0+94e2d
Crash Address: ntoskrnl.exe+703c0
Extracted from report generated by NirSoft BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
Here is BSOD summary (in case you want to add it to your VBox forum post)
Bug Check String: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code: 0x000000d1
Parameter 1: 00000000`00000028
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000000
Parameter 4: fffff880`09abfe2d
Caused By Driver: VMMR0.r0
Caused By Address: VMMR0.r0+94e2d
Crash Address: ntoskrnl.exe+703c0
Extracted from report generated by NirSoft BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
Starla
06/03/2018
Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
From MS debugging tools for Windows documentation:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xd1--driver-irql-not-less-or-equal
I can generate a BSOD minidump + VBox logs as requested, but I have a suggestion instead: maybe you could create a small "BSOD trigger demo" menu.lst file for VBox devs to easily reproduce it, something that stops just before any of the trigger commands and waits for a keypress to execute. I guess they could install grub4dos to the VDI in a test VM + \grldr + \menu.lst. You can better guide them here: setup a shared folder with grub4dos installer + grldr + menu.lst, then boot VM i.e. to WinPE using a Win install iso, press SHIFT+F10 for cmd, and install and copy files to VDI root. Finally boot the VDI.
Hope the above makes sense.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xd1--driver-irql-not-less-or-equal
I can generate a BSOD minidump + VBox logs as requested, but I have a suggestion instead: maybe you could create a small "BSOD trigger demo" menu.lst file for VBox devs to easily reproduce it, something that stops just before any of the trigger commands and waits for a keypress to execute. I guess they could install grub4dos to the VDI in a test VM + \grldr + \menu.lst. You can better guide them here: setup a shared folder with grub4dos installer + grldr + menu.lst, then boot VM i.e. to WinPE using a Win install iso, press SHIFT+F10 for cmd, and install and copy files to VDI root. Finally boot the VDI.
Hope the above makes sense.
Starla
06/03/2018
Re: Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
see
https://forums.virtualbox.org/viewtopic.php?f=6&t=86992&p=415809#p415809
I tried putting pauses in menu.lst code to find the point where it BSOD's and the two lines you indicated worked fine.
I found the cause was the map command (see link to forum for details). I can repro without using VMUB or .vmdk file or E2B.
https://forums.virtualbox.org/viewtopic.php?f=6&t=86992&p=415809#p415809
I tried putting pauses in menu.lst code to find the point where it BSOD's and the two lines you indicated worked fine.
I found the cause was the map command (see link to forum for details). I can repro without using VMUB or .vmdk file or E2B.
SteveSi
07/03/2018
Re: Re: Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
Easy and to the point setup for checking the bug by devs.
However note: on my host computer I can bypass the BSOD by commenting out lines 548 (dd) and 575 (cat). Uncomment any of them (tested uncommenting one keeping the other commented) and I get the BSOD. That means line 504 (map, the ones causing BSOD for you) gets executed w/o BSOD.
My host is Win 7 x64, I think yours is 10 x64. Also, I'm assigning 4 GB RAM to my VM.
However note: on my host computer I can bypass the BSOD by commenting out lines 548 (dd) and 575 (cat). Uncomment any of them (tested uncommenting one keeping the other commented) and I get the BSOD. That means line 504 (map, the ones causing BSOD for you) gets executed w/o BSOD.
My host is Win 7 x64, I think yours is 10 x64. Also, I'm assigning 4 GB RAM to my VM.
Starla
07/03/2018
Re: Re: Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
And maybe important: PAE/NX is enable as well in my VM.
Starla
07/03/2018
Re: Re: Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
Ok Steve, nothing changed in my setup, but some minutes ago I got a BSOD even with lines 548 (dd) and 575 (cat) commented out, so they are not the only triggers.
I've uncommented them (so both execute) and just commented out line 504 (map) and NO BSOD. Never touched that line in my previous tests (always executed). So it seems to be a trigger as well. I'll keep this mnu.lst (only skipping line 504) for further tests.
I've uncommented them (so both execute) and just commented out line 504 (map) and NO BSOD. Never touched that line in my previous tests (always executed). So it seems to be a trigger as well. I'll keep this mnu.lst (only skipping line 504) for further tests.
Starla
07/03/2018
Re: Re: Re: Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
Problem reproduced by VBox devs. It doesn't just crash Windows either but other OS's. To my mind, I think they should withdraw 5.2.8 urgently, as it could cost people hours of lost work if it crashes their host system...
SteveSi
09/03/2018
Re: Re: Re: Re: Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
I have re-released E2B v1.98 and modified the map (md)0x300+0x800 code line. It should have been (md)0x300+200 but somehow got modified at some point. It was copying 1M of memory when it should have been only 100K.
The new version of E2B does not cause a BSOD on my system now with VBOX 5.2.8. Can you test too pls?
The new version of E2B does not cause a BSOD on my system now with VBOX 5.2.8. Can you test too pls?
SteveSi
09/03/2018
Re: Re: Re: Re: Re: Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst
Tested latest E2B 1.98 with revised menu.lst (20180309) on VBox 5.2.8: NO BSOD for me.
Nice job Steve. It seems that 5.2.8 introduced some kind of wrong memory handling behaviour causing the problem with old line 504 instance. According to devs it's already fixed in currrent 5.2.9? dev build.
I'll keep testing 5.2.8 with latest E2B in the meantime.
Thanks a lot for your time looking into this and the continous improvement of E2B!
Nice job Steve. It seems that 5.2.8 introduced some kind of wrong memory handling behaviour causing the problem with old line 504 instance. According to devs it's already fixed in currrent 5.2.9? dev build.
I'll keep testing 5.2.8 with latest E2B in the meantime.
Thanks a lot for your time looking into this and the continous improvement of E2B!
Starla
11/03/2018
Parted Magic's save session: doesn't work
Hi to all.
My e2b usb drive (made it with Easy2Boot v1.97A), 16GB.
The following files in "_ISO\MAINMENU\MNU\":
- pmagic_2018_01_08.mnu (properly edited from "Parted_Magic_2016_Live_Persistent.mnu").
- pmagic_2018_01_08.iso
- pmagic_2018_01_08.txt
File "pmagic_2018_01_08.SQFS" in \pmagic\pmodules\
It boots and loads, all fine.
After some working/settings inside parted magic, double clicking on "Quit" icon (on parted magic desktop), then click on "Save Session", then selected option is "Save: User settings from /root and /etc are...", click on "Ok" and here the error message:
"Save Session Notice - Unable to continue. Please verify that the Parted Magic USB is connected"
(but my usb e2b drive is connected).
Many thanks.
My e2b usb drive (made it with Easy2Boot v1.97A), 16GB.
The following files in "_ISO\MAINMENU\MNU\":
- pmagic_2018_01_08.mnu (properly edited from "Parted_Magic_2016_Live_Persistent.mnu").
- pmagic_2018_01_08.iso
- pmagic_2018_01_08.txt
File "pmagic_2018_01_08.SQFS" in \pmagic\pmodules\
It boots and loads, all fine.
After some working/settings inside parted magic, double clicking on "Quit" icon (on parted magic desktop), then click on "Save Session", then selected option is "Save: User settings from /root and /etc are...", click on "Ok" and here the error message:
"Save Session Notice - Unable to continue. Please verify that the Parted Magic USB is connected"
(but my usb e2b drive is connected).
Many thanks.
dexter
05/03/2018
Re: Parted Magic's save session: doesn't work
It sounds like it cannot find the SQFS file.
If you delete it, do you get the same symptoms?
If so, check the spelling and case of the SQFS file - in the ISO it is all uppercase...?
If you delete it, do you get the same symptoms?
If so, check the spelling and case of the SQFS file - in the ISO it is all uppercase...?
SteveSi
05/03/2018
Re: Re: Parted Magic's save session: doesn't work
Just tested it using VBOX and no problems. Upper or lower case for the SQFS both work on detection/booting.
Can you see and access the USB drive when under pmagic linux?
P.S. I tested it on a real system and now I get the same error on save! It picks up the Save file OK on boot, and if I choose 'delete Save file' then it deletes it OK, but it does not want to save it! Not sure if this is a just a problem with 2018 version all also previous versions.
Strange that it works under VBOX (where USB drive appears as a non-USB HDD).
Can you see and access the USB drive when under pmagic linux?
P.S. I tested it on a real system and now I get the same error on save! It picks up the Save file OK on boot, and if I choose 'delete Save file' then it deletes it OK, but it does not want to save it! Not sure if this is a just a problem with 2018 version all also previous versions.
Strange that it works under VBOX (where USB drive appears as a non-USB HDD).
SteveSi
05/03/2018
Re: Re: Re: Parted Magic's save session: doesn't work
OK - I think I have figured out what is going on!
For *detection* and loading of the save file on boot, the SQFS filename can be upper or lower case.
BUT, when *saving* the Save file, the SQFS filename must be all uppercase!
P.S. You don't need a mnu file - if you select the ISO file in the E2B menu and hold down the SHIFT key, it will run ISOBOOT and run the 32-bit version of pmagic and the Save feature will be enabled (if the SQFS file is present).
For *detection* and loading of the save file on boot, the SQFS filename can be upper or lower case.
BUT, when *saving* the Save file, the SQFS filename must be all uppercase!
P.S. You don't need a mnu file - if you select the ISO file in the E2B menu and hold down the SHIFT key, it will run ISOBOOT and run the 32-bit version of pmagic and the Save feature will be enabled (if the SQFS file is present).
SteveSi
05/03/2018
Re: Re: Re: Re: Parted Magic's save session: doesn't work
> P.S. You don't need a mnu file - if you select
> the ISO file in the E2B menu and hold down the
> SHIFT key, it will run ISOBOOT and run
> the 32-bit version of pmagic and the Save
> feature will be enabled (if the SQFS file
> is present).
But I would like to run the 64bit version: any chance to do that (e.g. with mnu file and SQFS file with its name all uppercase)? Thanks a lot Steve, You've been very fast.
> the ISO file in the E2B menu and hold down the
> SHIFT key, it will run ISOBOOT and run
> the 32-bit version of pmagic and the Save
> feature will be enabled (if the SQFS file
> is present).
But I would like to run the 64bit version: any chance to do that (e.g. with mnu file and SQFS file with its name all uppercase)? Thanks a lot Steve, You've been very fast.
dexter
05/03/2018
Re: Re: Re: Re: Re: Parted Magic's save session: doesn't work
Your .mnu file should work fine (I assume).
Just make sure the filename of the actual file on the E2B drive is in uppercase -
\pmagic\pmodules\PMAGIC_2018_01_08.SQFS
Just make sure the filename of the actual file on the E2B drive is in uppercase -
\pmagic\pmodules\PMAGIC_2018_01_08.SQFS
SteveSi
05/03/2018
Re: Re: Re: Re: Re: Re: Parted Magic's save session: doesn't work
I tried with uppercase file name: It worked (on save session PM created the file xxx..sqfm next to file xxx.SQFS)!!!!
many thanks Steve!!!
many thanks Steve!!!
dexter
06/03/2018
Strange list
After some update I get strange moving to scroll.
Please see video: https://youtu.be/329cajdl3s0
Please see video: https://youtu.be/329cajdl3s0
Yura
27/02/2018
Re: Strange list
strange - but without more details I cannot help.
See the FAQ pages for help with debugging.
See the FAQ pages for help with debugging.
SteveSi
27/02/2018
Re: Re: Strange list
You are using GFX=NONE but you have not changed the menu size parameters.
The defaults menu parameters for a 800x600 screen and are:
set noitems=24
set tophelp=26
set HBTM=3502
But if you use text mode GFX=NONE, then you have 640x400 pixels which has 80 chars by 25 lines. So the default values need to be changed.
# if GFX=NONE then may be in 640x400 = 80 x 25 lines (sometimes 80 x 30 with some BIOSes)
set noitems=17
set tophelp=19
set HBTM=2400
set HELPTEXT=Here is help text
# if you want 640x480 80x30 lines - use this in your MyE2B.cfg
graphicsmode -1 640 480
set noitems=18
set tophelp=20
set HBTM=2900
set HELPTEXT=Here is help text
tophelp is normally set to topstart+noitems
The defaults menu parameters for a 800x600 screen and are:
set noitems=24
set tophelp=26
set HBTM=3502
But if you use text mode GFX=NONE, then you have 640x400 pixels which has 80 chars by 25 lines. So the default values need to be changed.
# if GFX=NONE then may be in 640x400 = 80 x 25 lines (sometimes 80 x 30 with some BIOSes)
set noitems=17
set tophelp=19
set HBTM=2400
set HELPTEXT=Here is help text
# if you want 640x480 80x30 lines - use this in your MyE2B.cfg
graphicsmode -1 640 480
set noitems=18
set tophelp=20
set HBTM=2900
set HELPTEXT=Here is help text
tophelp is normally set to topstart+noitems
SteveSi
28/02/2018
Easy2Boot - How to disable unattend for Windows 2008 R2 Server ISO?
I'm trying to install Windows 2008 R2 Server, but it keeps saying the ProductKey can't be found. This is because I wish to manually enter this. How can I disable unattend and just install as normal?
I've tried deleting the xml files, and I don't have this issue with Windows 10 installations.
My setup for the USB was as simple as running the Easy2Boot installation, and copying the ISO files, then defragmenting the drive.
I've tried deleting the xml files, and I don't have this issue with Windows 10 installations.
My setup for the USB was as simple as running the Easy2Boot installation, and copying the ISO files, then defragmenting the drive.
PaydenKP
06/02/2018
Re: Easy2Boot - How to disable unattend for Windows 2008 R2 Server ISO?
In order to make an unmodified Windows Install ISO load the ISO file as a 'virtual DVD' so it can access the files on the 'DVD', E2B has to use an XML file with commands inside the XML file which tell Setup to load the ISO file.
Unfortunately, most Win8 and Win10 install ISOs require a Product key to be specified inside the XML file or else it does not work.
Why don't you just pick a generic SVR2K8R2 install key as already provided. Then once the OS is installed, you can manually enter your own product key.
The alternative would be to convert the ISO to a .imgPTN file using MakePartImage. Then no XML is used and no key is required and you can enter your own key at Setup.
Unfortunately, most Win8 and Win10 install ISOs require a Product key to be specified inside the XML file or else it does not work.
Why don't you just pick a generic SVR2K8R2 install key as already provided. Then once the OS is installed, you can manually enter your own product key.
The alternative would be to convert the ISO to a .imgPTN file using MakePartImage. Then no XML is used and no key is required and you can enter your own key at Setup.
SteveSi
06/02/2018
Re: Re: Easy2Boot - How to disable unattend for Windows 2008 R2 Server ISO?
That makes a lot of sense. Thanks. I will use a generic key and go forward with that.
PaydenKP
06/02/2018
show e2b drive as one partition
i'm trying to start ghost 11.5 from the e2b drive, but it will not show the e2b drive in the dropdown list when ghost is loaded.
It works from my old single partition multiboot drive, so I guess it's because ghost doesn't recognize the multi-partition e2b drive.
Is there a way to make this work?
It works from my old single partition multiboot drive, so I guess it's because ghost doesn't recognize the multi-partition e2b drive.
Is there a way to make this work?
Nikolaj
31/01/2018
Re: show e2b drive as one partition
I see it works on new computers, but my old computers will not see the drive.
Nikolaj
31/01/2018
Re: Re: show e2b drive as one partition
If it works on new computers but not on old (with exactly same E2B USb stick, same MBR boot, all same conditions) then the problem must be with the old computer's BIOS or hardware. E2B has always made two partitions, it's just that the 2nd partition was not formatted on earlier versions.
P.S. Ghost 11.5 is based on Vista PE and only support USB 2 ports and older USB controllers.
P.S. Try using .isoPE01 file extension.
P.S. Ghost 11.5 is based on Vista PE and only support USB 2 ports and older USB controllers.
P.S. Try using .isoPE01 file extension.
SteveSi
31/01/2018
Re: Re: Re: show e2b drive as one partition
I think this Ghost is based on Dos.
Ghost starts fine and if I attach the old yumiboot usb and boots from e2b and ghost, then from ghost I'm able to choose the old yumi drive, but not the e2b drive. It just doesn't show in the list.
So I think it's because of the extra partitions. But that's just my guess.
Ghost starts fine and if I attach the old yumiboot usb and boots from e2b and ghost, then from ghost I'm able to choose the old yumi drive, but not the e2b drive. It just doesn't show in the list.
So I think it's because of the extra partitions. But that's just my guess.
Nikolaj
01/02/2018
Re: Re: Re: Re: show e2b drive as one partition
I don't see why 2 partitions would cause a problem.
The DOS version of Ghost works fine on my E2B drive which has 2 partitions as .iso.
Try a file extension of .iso01
The DOS version of Ghost works fine on my E2B drive which has 2 partitions as .iso.
Try a file extension of .iso01
SteveSi
01/02/2018
Re: Re: Re: Re: Re: show e2b drive as one partition
Hi
If I make these edits to my mnu file then Ghosts works after a second reboot:
partnew (hd0,3) 0 0 0
partnew (hd0,1) 0 0 0
So it must be something about the partitions it doesn't like.
Is there some builtin functions to make this easier?
Or to skip the reboot before it works?
And will this destroy the e2b functions?
Thanks.
If I make these edits to my mnu file then Ghosts works after a second reboot:
partnew (hd0,3) 0 0 0
partnew (hd0,1) 0 0 0
So it must be something about the partitions it doesn't like.
Is there some builtin functions to make this easier?
Or to skip the reboot before it works?
And will this destroy the e2b functions?
Thanks.
Nikolaj
09/02/2018
Re: Re: Re: Re: Re: Re: show e2b drive as one partition
I am afraid I do not know what your .mnu file contains, so it is difficult to comment.
Can you post the contents of the .mnu file?
What exactly is the file you are trying to boot from (.iso? .wim? .img?) - did you use the file extension recommended (.iso01) if an ISO file? Did you try other file extensions (use .isoask if an ISO).
Can you describe in detail, exactly what steps you followed to 'fix' the problem?
Are both partnew commands actually required or only one of them?
E2B runs partnew (hd0,3) when it boots, but if you just use .iso as a file extension, it will create a new hd0,3 partition when it boots the ISO.
Can you post the contents of the .mnu file?
What exactly is the file you are trying to boot from (.iso? .wim? .img?) - did you use the file extension recommended (.iso01) if an ISO file? Did you try other file extensions (use .isoask if an ISO).
Can you describe in detail, exactly what steps you followed to 'fix' the problem?
Are both partnew commands actually required or only one of them?
E2B runs partnew (hd0,3) when it boots, but if you just use .iso as a file extension, it will create a new hd0,3 partition when it boots the ISO.
SteveSi
10/02/2018
Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
My mnu file is not exactly working. I'm just playing around for now.
I've tried those extensions and more, but they have no effect on this problem.
I have these 15 year old desktop machines I need to re-image with symantec ghost 11.5.
Somehow on these machines ghost will only see the removable flash drive if it has just 1 partition. Hiding partition 2-4 is not enough.
If I do the partnew on the used partitions 2+4 and then do a reboot, then starting the ghost.iso will show the usb flash drive. But only after the reboot. So it's like the partnew first takes effect after a reboot.
On all other machines I have no problems.
I've tried those extensions and more, but they have no effect on this problem.
I have these 15 year old desktop machines I need to re-image with symantec ghost 11.5.
Somehow on these machines ghost will only see the removable flash drive if it has just 1 partition. Hiding partition 2-4 is not enough.
If I do the partnew on the used partitions 2+4 and then do a reboot, then starting the ghost.iso will show the usb flash drive. But only after the reboot. So it's like the partnew first takes effect after a reboot.
On all other machines I have no problems.
Nikolaj
10/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
OK - well the DOS version of Ghost probably uses the system BIOS for disk access. So on reboot, the BIOS would see a USB drive with one partition.
The 2nd partition is not needed - but some systems will boot as a floppy disk and fail with flashing cursor if it is not present. The 4th ptn is created by E2B when you pick an ISO to run, but it is deleted the next time you load the E2B menu and is type 0 anyway so should be ignored by BIOS and DOS.
When testing BIOS issues like this - ALWAYS switch off the PC - insert USB drive - switch on PC. Do this each time you test booting. This is because, with some BIOSes, they only determine the USB 'type' on a cold boot (power up or hard reset) and not a warm reboot (software reset).
You could convert the ISO to a .imgPTN file and use a file extension of .imgptnAauto and see if that works... then you should only get one partition.
The 2nd partition is not needed - but some systems will boot as a floppy disk and fail with flashing cursor if it is not present. The 4th ptn is created by E2B when you pick an ISO to run, but it is deleted the next time you load the E2B menu and is type 0 anyway so should be ignored by BIOS and DOS.
When testing BIOS issues like this - ALWAYS switch off the PC - insert USB drive - switch on PC. Do this each time you test booting. This is because, with some BIOSes, they only determine the USB 'type' on a cold boot (power up or hard reset) and not a warm reboot (software reset).
You could convert the ISO to a .imgPTN file and use a file extension of .imgptnAauto and see if that works... then you should only get one partition.
SteveSi
10/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
The imgptn does kind of solve the partition problem, but gives me other problems as I would need to put all images inside too and for now they are too big for DOS and FAT.
And my idea about this project was to have all the restore software: Ghost, Acronis and Clonezilla on one usb flash with easy access to add or renew the images.
And my idea about this project was to have all the restore software: Ghost, Acronis and Clonezilla on one usb flash with easy access to add or renew the images.
Nikolaj
10/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
I see your point.
Have you tried holding down the SHIFT key as E2B boots to load the grub4dos USB driver? Maybe that will fix the issue? i.e. Standard normal E2B drive - boot and hold down SHIFT key (check driver sees USB drive) - run ghost iso...
Have you tried holding down the SHIFT key as E2B boots to load the grub4dos USB driver? Maybe that will fix the issue? i.e. Standard normal E2B drive - boot and hold down SHIFT key (check driver sees USB drive) - run ghost iso...
SteveSi
10/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
Also try these tests on standard 2ptn E2B USB drive.
Test 1
1. Boot to E2B menu
2. Run partnew (hd0,1) 0 0 0 from a .mnu file
3. Reboot and run Ghost.iso from E2B drive - check symptom
Test 2 (standard E2B drive with 2 ptns)
1. ReName Ghost.iso to Ghost.isogz
2. Run Ghost.isogz from E2B - check symptom
3. Reboot and run Ghost.isogz again - check symptom
Test 1
1. Boot to E2B menu
2. Run partnew (hd0,1) 0 0 0 from a .mnu file
3. Reboot and run Ghost.iso from E2B drive - check symptom
Test 2 (standard E2B drive with 2 ptns)
1. ReName Ghost.iso to Ghost.isogz
2. Run Ghost.isogz from E2B - check symptom
3. Reboot and run Ghost.isogz again - check symptom
SteveSi
10/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
Test 1 is working once. After first time I need to clear p4 too.
Test 2 is not working.
Shift is working and showing all partitions in Ghost.
But somehow my keyboard stops working in the bootmenu.
Test 2 is not working.
Shift is working and showing all partitions in Ghost.
But somehow my keyboard stops working in the bootmenu.
Nikolaj
10/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
For test 1, can you describe step by step what you mean by 'after first time I need to clear ptn 4 as well'? How did you run ISO and clear ptn 4 at same time?
For SHIFT kbd issue - did you try unplugging USB kbd and the re-connecting it?
For SHIFT kbd issue - did you try unplugging USB kbd and the re-connecting it?
SteveSi
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
For test1:
If I run it just as an iso it makes some changes to ptn 4, which after a reboot is enough to prevent Ghost from finding the drive again. So clearing ptn 4 and another reboot will make it work once more.
Is there some BIOS tricks to make the refresh without a reboot?
Shift:
Here I can make it work if instead of using my usb-hub I use 3 ports for my keyboard, mouse and flash. I can do this on my test-machine, but in real life it's hard enough just to find one port.
If I run it just as an iso it makes some changes to ptn 4, which after a reboot is enough to prevent Ghost from finding the drive again. So clearing ptn 4 and another reboot will make it work once more.
Is there some BIOS tricks to make the refresh without a reboot?
Shift:
Here I can make it work if instead of using my usb-hub I use 3 ports for my keyboard, mouse and flash. I can do this on my test-machine, but in real life it's hard enough just to find one port.
Nikolaj
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
When you boot to the E2B menu, then E2B will run partnew (hd0,3) 0 0 0 automatically.
So this process should work.
1. Boot to E2B and run a .mnu file which runs partnew (hd0,1) 0 0 0
2. Reboot - run ghost iso
Can you test please?
I don't understand what the BIOS\Ghost is doing in your system. If the BIOS is booting from the E2B drive, then the E2B drive should be BIOS ID 80h = HDD0 and you should be able to list files on it under grub4dos or DOS (e.g. using UTILITIES menu options). So why cannot Ghost see the E2B partition?? If you quit Ghost and go back to DOS - can you see the E2B files? I just don't understand why it cannot see the E2B partition under Ghost.
So this process should work.
1. Boot to E2B and run a .mnu file which runs partnew (hd0,1) 0 0 0
2. Reboot - run ghost iso
Can you test please?
I don't understand what the BIOS\Ghost is doing in your system. If the BIOS is booting from the E2B drive, then the E2B drive should be BIOS ID 80h = HDD0 and you should be able to list files on it under grub4dos or DOS (e.g. using UTILITIES menu options). So why cannot Ghost see the E2B partition?? If you quit Ghost and go back to DOS - can you see the E2B files? I just don't understand why it cannot see the E2B partition under Ghost.
SteveSi
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
P.S. Do you have Ghost 11.5.0 2008 or Ghost 11.5.1 2009 or some other version?
SteveSi
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
I see about partnew. If I boot to the menu and just do a reboot, then ghost works again. So this partnew requires a reboot and is set everytime.
I can't see the drive in dos. I guess because it's ntfs.
Ghost is 11.5 from 2008
I can't see the drive in dos. I guess because it's ntfs.
Ghost is 11.5 from 2008
Nikolaj
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
If it works without a usb hub then that explains why no one else has reported a problem. It might have helped if you had mentioned that fact!
Why not try the latest version of Ghost 2009?
Also try a better usb hub.
Why not try the latest version of Ghost 2009?
Also try a better usb hub.
Stevesi
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
P.S. Why not use the hub for USB kbd and mouse and put the E2B USB key into the PC port?
SteveSi
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
It doesn't work without the usb hub. Only the Grub usb driver conflicts with the hub.
I can try to find a newer Ghost. For now I have just tried to combine the software from the flash drives I have been provided.
I can try to find a newer Ghost. For now I have just tried to combine the software from the flash drives I have been provided.
Nikolaj
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
What do you mean 'it doesn't work without the USB hub'? Is this another piece of information that you failed to mention?
So if you connect the kbd, mouse and E2B drive directly to the PC, then it cannot be made to work no matter how you use partnew or anything else? Is that correct?
So if you connect the kbd, mouse and E2B drive directly to the PC, then it cannot be made to work no matter how you use partnew or anything else? Is that correct?
SteveSi
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
No, I mean the hub makes no difference to the e2b/ghost functions. With or without the hub I have the same problems.
Only when I try the shift key with grub usb drivers the usb hub gives problems with the keyboard.
Only when I try the shift key with grub usb drivers the usb hub gives problems with the keyboard.
Nikolaj
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
OK - please try to reply clearly.
So as it seems to rely on booting with a single ptn, we need two boots.
1. Boot to E2B - select 'remove ptn 2 and reboot' menu
2. Boot to E2B again (now BIOS sees only 1 ptn) and automatically re-instates ptn 2.
3. Pick Ghost ISO from E2B menu.
To make this happen, please can you re-run your tests as before, but instead of using partnew (hd0,1) 0 0 0 can you use parttype (hd0,1) 0 and parttype (hd0,3) 0
If that works, then I may be able to devise something for you easily. If it does not work and we must use partnew, then it will be more difficult (but not impossible).
So as it seems to rely on booting with a single ptn, we need two boots.
1. Boot to E2B - select 'remove ptn 2 and reboot' menu
2. Boot to E2B again (now BIOS sees only 1 ptn) and automatically re-instates ptn 2.
3. Pick Ghost ISO from E2B menu.
To make this happen, please can you re-run your tests as before, but instead of using partnew (hd0,1) 0 0 0 can you use parttype (hd0,1) 0 and parttype (hd0,3) 0
If that works, then I may be able to devise something for you easily. If it does not work and we must use partnew, then it will be more difficult (but not impossible).
SteveSi
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
I tried the e2b 1.98 and it looks like if I use the freedos on there and start the ghost.exe I can see the drive. It shows the drive twice. Once with drive letter and once without. But that might not matter much.
Is there a way to make it autostart ghost.exe?
Is there a way to make it autostart ghost.exe?
Nikolaj
11/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
yes, use 7zip to extract the .ima file
Load .ima file in WinImage
Extract autoexec.bat
add
A:\ghost.exe to end of the file using notepad
copy autoexec.bat back to image
copy ghost.exe into image
save image as .ima
Now you can run .ima in E2B
If you want to try the reboot scheme for the ISO file see https://1drv.ms/u/s!AqlrQcdsFA-Koz4Y2HAYbHrbp5ii
Load .ima file in WinImage
Extract autoexec.bat
add
A:\ghost.exe to end of the file using notepad
copy autoexec.bat back to image
copy ghost.exe into image
save image as .ima
Now you can run .ima in E2B
If you want to try the reboot scheme for the ISO file see https://1drv.ms/u/s!AqlrQcdsFA-Koz4Y2HAYbHrbp5ii
SteveSi
12/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
Thanks. The reboot is working.
But I would like to try the freedos too.
I tried what you said, but there is not enough room for the Ghost.exe. I even made it 2.88.
Is it possible to delete some files from the ima or are all used?
But I would like to try the freedos too.
I tried what you said, but there is not enough room for the Ghost.exe. I even made it 2.88.
Is it possible to delete some files from the ima or are all used?
Nikolaj
12/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
You can copy the ghost.exe to the root of the E2B drive and add
C:\Ghost.exe
to the end of the autoexec.bat file.
Most of the files in \FREEDOS are not required - e.g. edit, fdisk, part
C:\Ghost.exe
to the end of the autoexec.bat file.
Most of the files in \FREEDOS are not required - e.g. edit, fdisk, part
SteveSi
12/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
Try the floppy disk image in E2B v1.98f. It is now 7.6MB in size, FAT32, and has mouse driver added. You should be able to add Ghost.exe to it now.
SteveSi
13/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
Thanks. Now it fits :)
But sadly it seems like I was tricked.
It still needs the reboot. It just showed the PTN2 drive, so I thought it worked with several partitions, but that might be the trick of your config mnu file.
Thanks a lot for helping.
I will use the reboot thing for now. And maybe see if I can find a newer ghost.
But sadly it seems like I was tricked.
It still needs the reboot. It just showed the PTN2 drive, so I thought it worked with several partitions, but that might be the trick of your config mnu file.
Thanks a lot for helping.
I will use the reboot thing for now. And maybe see if I can find a newer ghost.
Nikolaj
13/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
You originally said that if you boot from the ISO on an E2B drive, Ghost cannot see the E2B drive.
Did you actually mean 'drive' or did you mean 'partition'.
i.e. can Ghost see PTN2 on the E2B drive but not partition 1 (the E2B volume) when you boot from an ISO on the old system?
Did you actually mean 'drive' or did you mean 'partition'.
i.e. can Ghost see PTN2 on the E2B drive but not partition 1 (the E2B volume) when you boot from an ISO on the old system?
SteveSi
13/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
I mean drive.
What tricked me this time was something I think happens with your reboot menu and restore.
I tried the freedos and ghost.exe and suddenly I could see both E2B and PTN2 partitions. I've never seen both before.
When it worked the PTN2 was always cleared.
So I thought suddenly it could see both partitions with this freedos.
But I guess this happens when you restore the PTN2, but we don't refresh the BIOS with a reboot.
Another thought could be if it's possible when you boot iso's to clear the ptn 3 before reboot. So the drive would always show just 1 partition to the bios.
What tricked me this time was something I think happens with your reboot menu and restore.
I tried the freedos and ghost.exe and suddenly I could see both E2B and PTN2 partitions. I've never seen both before.
When it worked the PTN2 was always cleared.
So I thought suddenly it could see both partitions with this freedos.
But I guess this happens when you restore the PTN2, but we don't refresh the BIOS with a reboot.
Another thought could be if it's possible when you boot iso's to clear the ptn 3 before reboot. So the drive would always show just 1 partition to the bios.
Nikolaj
13/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
I see.
I cannot clear ptn 4 because it is needed to boot linux.
i.e. set ptn 4 to iso file, boot to linux, reboot to E2B.
So I have no way to clear it once linux has booted.
Anyway, when booting to E2B, ptn 2 needs to be present or it won't boot on some systems.
I cannot clear ptn 4 because it is needed to boot linux.
i.e. set ptn 4 to iso file, boot to linux, reboot to E2B.
So I have no way to clear it once linux has booted.
Anyway, when booting to E2B, ptn 2 needs to be present or it won't boot on some systems.
SteveSi
13/02/2018
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: show e2b drive as one partition
Yes, I also couldn't see how it could be done.
If I start ghost from the mini windows xp from hbcd, then I can see all partitions. So I think my way forward will be to find some winpe.
If I start ghost from the mini windows xp from hbcd, then I can see all partitions. So I think my way forward will be to find some winpe.
Nikolaj
13/02/2018
Second partition to put Windows ISO's
Hello, I succesfully created a second partition on my 256GB USB Key. ISOs like Antivirus, linux, etc... works, but not the Windows one. How can we do this?
Thanks
Thanks
J-F Gagnon
22/01/2018
Re: Second partition to put Windows ISO's
I forgot to say that I put all my ISOs in the second partition
J-F Gagnon
22/01/2018
Re: Re: Second partition to put Windows ISO's
Windows ISOs need to be in the first partition.
If you want them in the 2nd partition, convert them to .imgPTN files.
It is a bad idea to put E2B or any payload files past 128GB on the drive because of a very common BIOS bug which cant access files on a USB drive (in MBR mode) past 128GB.
If you want them in the 2nd partition, convert them to .imgPTN files.
It is a bad idea to put E2B or any payload files past 128GB on the drive because of a very common BIOS bug which cant access files on a USB drive (in MBR mode) past 128GB.
SteveSi
22/01/2018
Re: Re: Re: Second partition to put Windows ISO's
Ok, I wanted to put all the ISO files in the partition that Windows doesn't see to keep other files visible. So I read that BIOS doesn't read over 128GB put I was thinking it was 128GB of a partition and not from a drive. So I can create a 256GB partition and try to put all payload in the first 128GB?
J-F Gagnon
22/01/2018
Re: Re: Re: Re: Second partition to put Windows ISO's
Exactly - Windows (pre Creators update) cannot see the ISO file if it is on the 2nd partition - therefore it will not be able to load the ISO and use the install.wim file.
If you use a 256GB partition, you must ensure all files are before 128GB, but this is very hard to do because the NTFS filesystem will always use the unused clusters first. So once you have filled the partition with over 128GB of files - even if you delete 120GB afterwards - the NTFS filesystem will put the next file you copy past 128GB on the drive.
Hence I recommend making a 128GB first partition because then you know the files will not go past the 128GB point.
If you use a 256GB partition, you must ensure all files are before 128GB, but this is very hard to do because the NTFS filesystem will always use the unused clusters first. So once you have filled the partition with over 128GB of files - even if you delete 120GB afterwards - the NTFS filesystem will put the next file you copy past 128GB on the drive.
Hence I recommend making a 128GB first partition because then you know the files will not go past the 128GB point.
SteveSi
22/01/2018
Re: Re: Re: Re: Re: Second partition to put Windows ISO's
Ok, but if I put my "other" files in the second partition and want to access it in Windows 7? I saw that we have a little program "SWITCH_E2B.exe" but when I press "Access Partition 2", it does nothing, the same partition is loaded.
J-F Gagnon
22/01/2018
Re: Re: Re: Re: Re: Re: Second partition to put Windows ISO's
Both partitions must be Primary ptns.
Primary+Logical does not work when swapping the partition table entries.
Primary+Logical does not work when swapping the partition table entries.
SteveSi
22/01/2018
Desktop not found if not at default location
MPI-tool's CreateDesktopShortcuts.cmd
uses the default Desktop location - and fails if that was changed:
the real path then is:
REG QUERY "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" /v Desktop
uses the default Desktop location - and fails if that was changed:
the real path then is:
REG QUERY "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" /v Desktop
Jesko
27/12/2017
Re: Desktop not found if not at default location
Thanks, can you try this version instead?
https://1drv.ms/u/s!AqlrQcdsFA-KoUo8nSin83ogdT6X
https://1drv.ms/u/s!AqlrQcdsFA-KoUo8nSin83ogdT6X
SteveSi
27/12/2017
Re: Re: Desktop not found if not at default location
Works! Thank You.
Jesko
27/12/2017
Re: Re: Re: Desktop not found if not at default location
Fixed in v0.079 of MPI Tool Pack
SteveSi
07/01/2018
Can I use E2B to make an ISO from a USB key?
Thanks
DrPepperCan
22/12/2017
Re: Can I use E2B to make an ISO from a USB key?
Use the Site Map...
http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-and-burn-an-e2b-dvd/
http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-and-burn-an-e2b-dvd/
SteveSi
22/12/2017
Erro Warning Bad XML file
Hello my dear friend I have a problem when I try to boot into windows systems, for some reason it asks to select an .xml file but regardless of which I choose to give the following error .. ** WARNING: Bad XML file (/ _ISO / WINDOWS / Win7 / Load_ISO. ... or missing AutoUnattend.xml in root (or using VM)! Could you help me?
Andre rds
21/12/2017
Re: Erro Warning Bad XML file
You may get this error if you have a faulty USB drive, or if using QEMU_MENU_TEST.cmd or other VM which does not lock the volume. It should work on a real system or using VBOX+VMUB.
SteveSi
21/12/2017
Serial key menu
Hi
Thank you to people who made E2B possible :-) what do I need to do when I am not getting any prompts or menu to choose serial keys start wih or without repair option I have several windows ,iso to imgPTN in their appropiate folders. I have tried to get around this forum to find info, best part way over my head, i dont want to edit xml files. Im wondering why I am not getting any options.
TY
Pete
Thank you to people who made E2B possible :-) what do I need to do when I am not getting any prompts or menu to choose serial keys start wih or without repair option I have several windows ,iso to imgPTN in their appropiate folders. I have tried to get around this forum to find info, best part way over my head, i dont want to edit xml files. Im wondering why I am not getting any options.
TY
Pete
Pete
05/12/2017
Re: Serial key menu
If you are using .imgPTN files for Windows Installs, it is just the same as if you used the Windows USB tool or Rufus to make a bootable USB drive.
i.e. the same as using a DVD. You will not be prompted for an XML file. You can enter a key if Win8/10 because it will ask you if you want to OR you can just choose skip option.
If you want to automate Setup, you will have to use an XML file and place the XML file in the root (or inside the boot.wim file) - so you will need some expertise\knowledge for this.
http://www.easy2boot.com/add-payload-files/automating-windows-install-from-imgptn-files/
i.e. the same as using a DVD. You will not be prompted for an XML file. You can enter a key if Win8/10 because it will ask you if you want to OR you can just choose skip option.
If you want to automate Setup, you will have to use an XML file and place the XML file in the root (or inside the boot.wim file) - so you will need some expertise\knowledge for this.
http://www.easy2boot.com/add-payload-files/automating-windows-install-from-imgptn-files/
SteveSi
05/12/2017
Re: Re: Serial key menu
Thank you for the reply SteveSi I will take a look at the link you gave me. I have only just discovered E2B and think its brilliant! ;-}
Regards
Pete
Regards
Pete
Pete
05/12/2017
Re: Re: Serial key menu
SteveSi
say if i wanted to use I:\_ISO\WINDOWS\WIN10 how to choose a product key from the list, Im thinking its some sort of menu for keys click a number then install? would this need to be at root folder or have I missed the point?
TY
Pete
say if i wanted to use I:\_ISO\WINDOWS\WIN10 how to choose a product key from the list, Im thinking its some sort of menu for keys click a number then install? would this need to be at root folder or have I missed the point?
TY
Pete
Pete
05/12/2017
Re: Re: Re: Serial key menu
When you 'switch' to a .imgPTN file, the E2B partition disappears. So the \_ISO folder and all other files are no longer present.
The only reason to use imgPTN files for Windows Installs is to UEFI-boot. So if you need to choose from a range of different keys, you need to have a range of different XML files present.
You should make the .imgPTN file using Chandra's Split_WinISO utility and choose the MySetup.cmd option when offered.
http://www.com/add-payload-files/split-winiso/
I am afraid it involves editing a \auto.cmd file and knowledge of .cmd script language, etc. and is not for beginners.
The only reason to use imgPTN files for Windows Installs is to UEFI-boot. So if you need to choose from a range of different keys, you need to have a range of different XML files present.
You should make the .imgPTN file using Chandra's Split_WinISO utility and choose the MySetup.cmd option when offered.
http://www.com/add-payload-files/split-winiso/
I am afraid it involves editing a \auto.cmd file and knowledge of .cmd script language, etc. and is not for beginners.
SteveSi
05/12/2017
Small problem adding Windows 10 to main menu
When you add windows 10 to main menu via $$AddWin2Main.mnu file you can't redirect runwin8.g4b to runwin10.g4b because this file not exist in grub folder. When you start windows 10 from main menu it shows windows 8 xml alternatives. Can you add runwin10.g4b file to grub folder?
dnecro
03/12/2017
Re: Small problem adding Windows 10 to main menu
runwin8.g4b is correct. It is used for Win8, Win10, SVR2012 and SVR2016. Please ensure you have set MFOLDER to point to the folder that contains your ISO file and your .XML and .KEY files.
# Win10 Example
# use this for Win8/8.1/SVR2012/WIN10 ISOs - all use RunWin8.g4b
iftitle [if exist /_ISO/WINDOWS/Win10/Win10_64.iso] Install Win10 64-bit \nInstall from the ISO
set MFOLDER=/_ISO/WINDOWS/WIN10
set ISO=Win10_64.iso
# to choose XML or Product Key do not set XML variable to anything
set XML=
# OR - Specify XML file name (must be in MFOLDER folder) e.g. Win10\ has\ spaces\ in\ name.xml - DO NOT USE FULL PATH!
# set XML=NO\ KEY\ (choose\ a\ version\ to\ install).xml
# Do not change next line...
/%grub%/RunWin8.g4b %MFOLDER% %XML%
boot
# Win10 Example
# use this for Win8/8.1/SVR2012/WIN10 ISOs - all use RunWin8.g4b
iftitle [if exist /_ISO/WINDOWS/Win10/Win10_64.iso] Install Win10 64-bit \nInstall from the ISO
set MFOLDER=/_ISO/WINDOWS/WIN10
set ISO=Win10_64.iso
# to choose XML or Product Key do not set XML variable to anything
set XML=
# OR - Specify XML file name (must be in MFOLDER folder) e.g. Win10\ has\ spaces\ in\ name.xml - DO NOT USE FULL PATH!
# set XML=NO\ KEY\ (choose\ a\ version\ to\ install).xml
# Do not change next line...
/%grub%/RunWin8.g4b %MFOLDER% %XML%
boot
SteveSi
03/12/2017
Re: Re: Small problem adding Windows 10 to main menu
It seems worked that way. Thank you for your help.
dnecro
04/12/2017
Re: Re: Re: Small problem adding Windows 10 to main menu
P.S. for E2B v1.A1 and later, you also need to set HDG to the menu heading, e.g.
set HDG=My New Menu Heading
set HDG=My New Menu Heading
SteveSi
10/08/2018
Easy2Boot v1.96A bug
Tried ubuntu-17.10-desktop-amd64.iso and Fedora-Workstation-Live-x86_64-24-1.2.iso and got "no-live media found" errors. Downgraded to previous version Easy2Boot v1.95 and both isos loaded without issues. Something got broken in the latest version.
cheetoh
23/11/2017
Re: Easy2Boot v1.96A bug
Did you use 1.96A or 1.96ADPMS?
No one else has reported a problem. Can you re-test v.1.96a (just run Update E2B).
You can easily revert to 1.95 by running Update E2B from the 1.95 exe.
No one else has reported a problem. Can you re-test v.1.96a (just run Update E2B).
You can easily revert to 1.95 by running Update E2B from the 1.95 exe.
SteveSi
23/11/2017
Re: Re: Easy2Boot v1.96A bug
I used 1.96A, and tested it multiple times. I have now tried 1.97c and everything works. I'll just stick to the beta for now. By the way, thanks for your quick reply.
cheetoh
23/11/2017
Re: Re: Re: Easy2Boot v1.96A bug
That's odd. I cannot find any issue and I was just live chatting to someone who is happily using 1.96A.
There have been over 20,000 downloads of 1.96A already and no one else has reported a problem. Could you investigate further?
There have been over 20,000 downloads of 1.96A already and no one else has reported a problem. Could you investigate further?
SteveSi
23/11/2017
Re: Re: Re: Re: Easy2Boot v1.96A bug
You're right, it's odd. Did a fresh install of 1.96A on another flash drive and both live isos worked. Ver 1.96A was the first ever e2b for me, and I used the QEMU on both the installer and RMPrepUSB quite a lot. This time, I didn't use QEMU. Could it be that some corruption occurs through menu emulation?
I'm sorry if I caused you some alarm.
I'm sorry if I caused you some alarm.
cheetoh
24/11/2017
Re: Re: Re: Re: Easy2Boot v1.96A bug
To further investigate, ran QEMU on the new flash drive, and could not replicate the errors. Perhaps my first flash drive is defective. Once again, my apologies.
cheetoh
24/11/2017
Re: Re: Re: Re: Re: Easy2Boot v1.96A bug
You may need to allow time after file writes for flush of file system. Under Windows, some sticks seem to need 30 seconds or so before all files are written to USB drive. Under linux and QEMU, you seem to need to flush and eject and reconnect before using QEMU.
SteveSi
24/11/2017
windows version?
Hi there!
As it is said, there is a lot of informations on the site, no easy for a neophyte to find his way...
Is there a windows installer or portable version of E2B so as to use it as a more intuitive bootable usb creator?
Thank you
As it is said, there is a lot of informations on the site, no easy for a neophyte to find his way...
Is there a windows installer or portable version of E2B so as to use it as a more intuitive bootable usb creator?
Thank you
*human$bootmgr&missing-reboot~or#cancel
17/11/2017
Re: windows version?
The Easy2Boot download is a portable program that makes a bootable E2B USB drive in a few clicks.
It's pretty easy!
It's pretty easy!
SteveSi
17/11/2017
Re: Re: windows version?
ok, I keep trying
'[email protected]|boot/ini
17/11/2017
Menu Help Text & Pimp my drive
Is it possible to remove pimp my drive once its been run ? Also can you edit which menu items it adds.
Also the menu help text that appears with each entry can you change the number of displayed lines from 4 to 2 or even remove it altogether ?
Also the menu help text that appears with each entry can you change the number of displayed lines from 4 to 2 or even remove it altogether ?
Varkanoid
14/11/2017
Re: Menu Help Text & Pimp my drive
http://www.easy2boot.com/configuring-e2b/pimpmydrive/
http://www.easy2boot.com/configuring-e2b/
to remove help lines use
set tophelp=70
E2B v1.97c also has some changes which you may like. You can change the help text width and position. ;-)
http://www.easy2boot.com/configuring-e2b/
to remove help lines use
set tophelp=70
E2B v1.97c also has some changes which you may like. You can change the help text width and position. ;-)
SteveSi
14/11/2017
PTN2 to Windows 10
Why is this partition displayed?
If I remove it, the entire USB flash drive is removed.
PS. In Windows 7, there is no such thing
If I remove it, the entire USB flash drive is removed.
PS. In Windows 7, there is no such thing
БлагоЯр Тишина
07/11/2017
Re: PTN2 to Windows 10
Latest Windows 10 editions (1607+) show the second hidden partition. It is a new 'feature' in Windows 10!!!
You should keep the partition there because some systems will not boot to E2B if you delete it.
If it is unformatted (31K), just use Windows to format it when you see the pop-up.
You should keep the partition there because some systems will not boot to E2B if you delete it.
If it is unformatted (31K), just use Windows to format it when you see the pop-up.
SteveSi
07/11/2017
2nd partition accessible from imgPTN
I set up a drive successfully but the wanted to add a partition with PortableApps and other personal files. Using minitool partition wizard, I reduced the 1st partition (contains _ISO) and added a 2nd primary (contains PotableApps) and deleted the small hidden partition. Everything works but I do not see the 2nd partition in any boot images. I only see the 2nd partition when I am in the "main" easy2boot menu table. How do I make the 2nd partition "stick" on the part tables when switching between boot images?
THANK YOU
THANK YOU
L D
31/10/2017
Re: 2nd partition accessible from imgPTN
Hi, just rename the file extension to .imgPTNLBAa23 or .imgPTN23.
See http://www.easy2boot.com/add-payload-files/list-of-file-extensions-recognised-by-e2b/
See http://www.easy2boot.com/add-payload-files/list-of-file-extensions-recognised-by-e2b/
SteveSi
31/10/2017
E2B UEFI with imgptn files
Hello Steve,
Would like to know if I could make all the iso files imgptn files (linux iso, win 10 iso, live av cd iso's). And if so, I should be able to ditch all the folder premade, and make my own Win10,Linux,Bitdefender folders, such that it appears in the main menu with custom backgrounds for each? How would I go about doing so?
Thanks
Would like to know if I could make all the iso files imgptn files (linux iso, win 10 iso, live av cd iso's). And if so, I should be able to ditch all the folder premade, and make my own Win10,Linux,Bitdefender folders, such that it appears in the main menu with custom backgrounds for each? How would I go about doing so?
Thanks
Shaan Subbaiah
25/10/2017
Re: E2B UEFI with imgptn files
You do not need to convert the ISOs to imgPTN for MBR booting, they will work from any folder.
You can convert most to .imgPTN but you may run into trouble with some of them.
You can create new menu folders and use them with any iso (but you will need to create special .mnu files for WIndows Install ISOs).
http://www.easy2boot.com/configuring-e2b/multiple-backgrounds/
http://www.easy2boot.com/configuring-e2b/add-a-new-menu-folder/
http://www.easy2boot.com/configuring-e2b/wininstmenu/
You can convert most to .imgPTN but you may run into trouble with some of them.
You can create new menu folders and use them with any iso (but you will need to create special .mnu files for WIndows Install ISOs).
http://www.easy2boot.com/configuring-e2b/multiple-backgrounds/
http://www.easy2boot.com/configuring-e2b/add-a-new-menu-folder/
http://www.easy2boot.com/configuring-e2b/wininstmenu/
SteveSi
25/10/2017
Re: Re: E2B UEFI with imgptn files
Thankyou, was able to implement the custom folders. For linux iso's, do you recommend converting them to imptn files? As they seem to work properly as iso's. Im planning to use both windows and linux, shall make only the windows 10 iso imptn?
Thanks
Thanks
Shaan Subbaiah
25/10/2017
Re: Re: Re: E2B UEFI with imgptn files
if you only want to MBR-boot linux, then I suggest you use the .ISO files.
If you convert Windows Install ISOs to .imgPTN, take care to answer the EI.cfg file question carefully and then you can install all the different Editions which are inside the install.wim file.
If you name the file extension as .imgPTNAUTO then it will switch without prompting you.
If you convert Windows Install ISOs to .imgPTN, take care to answer the EI.cfg file question carefully and then you can install all the different Editions which are inside the install.wim file.
If you name the file extension as .imgPTNAUTO then it will switch without prompting you.
SteveSi
25/10/2017
Re: Re: Re: Re: E2B UEFI with imgptn files
I didnt get the last part, wont prompt you to switch what? As a failsafe, nming all iso's as isoauto should help right? Also The windows version im using has only a single edition in it (enterprise x64) so the ei.cfg shouldnt affect it if i keep/delete it right?
Thanks
Thanks
Shaan Subbaiah
25/10/2017
Re: Re: Re: Re: Re: E2B UEFI with imgptn files
When you run a .imgPTN file from the E2B menu, it will prompt you to switch partitions and you have to press ENTER or Y+ENTER to switch in the .imgPTN file. Using a file extension of .imgPTNAUTO just suppresses the prompt.
.isoauto is not a valid file extension.
.isoauto is not a valid file extension.
SteveSi
25/10/2017
Easy2Boot on UEFI system
Hello, if I want to boot from stick with installed E2B, I need to switch booting in BIOS to legacy compatibility mode and back then.
This is inconvenient, is there a possibility that my stick will boot even if BIOS is set in UEFI mode?
This is inconvenient, is there a possibility that my stick will boot even if BIOS is set in UEFI mode?
solstiv
22/10/2017
Re: Easy2Boot on UEFI system
Hi
You can use \_ISO\Switch_E2B.exe to switch in any .imgPTN file.
I totally agree that it is inconvenient!
However, the reason it is done this way is:
1. Some UEFI BIOSes have a very annoying bug. If a valid UEFI boot file is present, these BIOSes will NEVER MBR-boot from the USB drive. So if you want to boot to Hirens say in MBR mode (or just the E2B menu), you cannot do that (even if CSM mode is enabled in the BIOS settings).
2. FAT32 would be required which means large files >4GB could not be added.
3. grub4dos does not boot via UEFI
4. It makes adding/configuring/deleting UEFI payloads very complex.
5. You would have to use an application to add/delete UEFI payloads and that app would need to 'know' about all possible payloads and be maintained monthly and ongoing.
6. Secure boot would be compromised
If you just want a Windows payload multiboot USB drive, take a look at WinSetupFromUSB. This does support MBR+UEFI, but if you are using it on lots of different systems, snag #1 above may catch you out!
You can use \_ISO\Switch_E2B.exe to switch in any .imgPTN file.
I totally agree that it is inconvenient!
However, the reason it is done this way is:
1. Some UEFI BIOSes have a very annoying bug. If a valid UEFI boot file is present, these BIOSes will NEVER MBR-boot from the USB drive. So if you want to boot to Hirens say in MBR mode (or just the E2B menu), you cannot do that (even if CSM mode is enabled in the BIOS settings).
2. FAT32 would be required which means large files >4GB could not be added.
3. grub4dos does not boot via UEFI
4. It makes adding/configuring/deleting UEFI payloads very complex.
5. You would have to use an application to add/delete UEFI payloads and that app would need to 'know' about all possible payloads and be maintained monthly and ongoing.
6. Secure boot would be compromised
If you just want a Windows payload multiboot USB drive, take a look at WinSetupFromUSB. This does support MBR+UEFI, but if you are using it on lots of different systems, snag #1 above may catch you out!
SteveSi
22/10/2017
Change any WinPE - add shortcuts, change wallpaper, autorun apps, etc.
If you have lots of WinPE ISOs or WIM files on your E2B drive, you can easily add your own shortcuts, change the wallpaper, add drivers and autorun commands on startup. No need to change the ISO\WIM file. See the PEStartup Tutorial at http://www.rmprepusb.com/tutorials/143_pestartup
SteveSi
05/10/2017
Issue cannot copy: Robocopy or winXP?
Hi Steve. I use winXP x32 from my user account with admin attributes.
I deleted some files on Easy2Boot pendrive, hoping to copy them on E2B updating. However, this could not copy "Make this drive contiguos.cmd", and maybe other files that I don't know.
Image E2B folder device: https://s6.postimg.org/9sldrzs1d/Cannot-copy-makethisdrivecontiguos-and-others.png
This displays the dialog window, but really E2B could not copy these files on second try, neither:
E2B USB Drive Letter to update? (e.g. E) : F
"robocopy" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
Using XCOPY /d to update - please wait...
C:\DOCUME~1\User~1\CONFIG~1\Temp\RarSFX0\MAKE_E2B_USB_DRIVE (run as admin).cmd
C:\DOCUME~1\User~1\CONFIG~1\Temp\RarSFX0\MAKE_THIS_DRIVE_CONTIGUOUS.cmd
C:\DOCUME~1\User~1\CONFIG~1\Temp\RarSFX0\QEMU_MENU_TEST (run as admin).cmd
C:\DOCUME~1\User~1\CONFIG~1\Temp\RarSFX0\UPDATE_E2B_DRIVE.CMD
4 archivos copiados
Presione una tecla para continuar . . .
I once tried to install a robocopy (2005 version) downloaded from the internet, but this did not work.
I deleted some files on Easy2Boot pendrive, hoping to copy them on E2B updating. However, this could not copy "Make this drive contiguos.cmd", and maybe other files that I don't know.
Image E2B folder device: https://s6.postimg.org/9sldrzs1d/Cannot-copy-makethisdrivecontiguos-and-others.png
This displays the dialog window, but really E2B could not copy these files on second try, neither:
E2B USB Drive Letter to update? (e.g. E) : F
"robocopy" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
Using XCOPY /d to update - please wait...
C:\DOCUME~1\User~1\CONFIG~1\Temp\RarSFX0\MAKE_E2B_USB_DRIVE (run as admin).cmd
C:\DOCUME~1\User~1\CONFIG~1\Temp\RarSFX0\MAKE_THIS_DRIVE_CONTIGUOUS.cmd
C:\DOCUME~1\User~1\CONFIG~1\Temp\RarSFX0\QEMU_MENU_TEST (run as admin).cmd
C:\DOCUME~1\User~1\CONFIG~1\Temp\RarSFX0\UPDATE_E2B_DRIVE.CMD
4 archivos copiados
Presione una tecla para continuar . . .
I once tried to install a robocopy (2005 version) downloaded from the internet, but this did not work.
Bertholdouz-2
16/09/2017
Re: Issue cannot copy: Robocopy or winXP?
Is there any free space on the USB drive?
Try just copying all the E2B files to the USB drive using Explorer.
Maybe your Anti-Virus is stopping it?
Maybe your USB flash drive is faulty?
Try just copying all the E2B files to the USB drive using Explorer.
Maybe your Anti-Virus is stopping it?
Maybe your USB flash drive is faulty?
SteveSi
16/09/2017
Re: Re: Issue cannot copy: Robocopy or winXP?
I wonder if maybe it's a lack of winXP.
The XP remains without AV and internet, currently, just XP-Firewall turned On.
The USB Drive is the Kingston DataTraveler SE9 16GB. It's filled by 46%, 54% free space.
I write you from a GNU/Linux distribution.
The XP remains without AV and internet, currently, just XP-Firewall turned On.
The USB Drive is the Kingston DataTraveler SE9 16GB. It's filled by 46%, 54% free space.
I write you from a GNU/Linux distribution.
Bertholdouz-2
20/09/2017
Re: Re: Re: Issue cannot copy: Robocopy or winXP?
So what happens if you just copy the files yourself. ?
P.S. Why are 8.3 short folder names listed by xcopy (as shown in your example in first post)? Usually XP will show the full folder names and not the short file name?
P.S. Why are 8.3 short folder names listed by xcopy (as shown in your example in first post)? Usually XP will show the full folder names and not the short file name?
Stevesi
20/09/2017
What was the previous wallpaper (red sky)?
Hi Steve. Thanks, great work!
Plz, I want to download the previous wallpaper (Red Sky, and others), but I have not found it in Alternate Area.
P.S: Google+ to gmail users it's a problem to answer on rmprepusb.blogspot.com
Thanks.
Plz, I want to download the previous wallpaper (Red Sky, and others), but I have not found it in Alternate Area.
P.S: Google+ to gmail users it's a problem to answer on rmprepusb.blogspot.com
Thanks.
Bertholdouz
13/09/2017
Re: What was the previous wallpaper (red sky)?
I have added all (?) default wallpapers to Themes - Default E2B Backgrounds folder on Alternate Download Sites now.
SteveSi
13/09/2017
Greek language Beta files for E2B
https://rmprepusb.blogspot.co.uk/2017/08/beta-version-of-greek-language-available.html
Also in E2B v1.95c Beta
If you speak Greek, please test and correct.
Also in E2B v1.95c Beta
If you speak Greek, please test and correct.
SteveSi
18/08/2017
rebootPro Forum
Hello SteveSi,
Two questions:
Do you remember, I asked for your convenience about a reboot.pro account issue? I can't complete the change of email address, and all the forum operations got blocked to me. Also, I couldn't email the admins. Although I might have given the impression that it worked, this topic haven't reached it's end. Waiting for another update, thanks.
This forum page 2 and beyond doesn't exhibit the further discussions. It gives Error 502.
Two questions:
Do you remember, I asked for your convenience about a reboot.pro account issue? I can't complete the change of email address, and all the forum operations got blocked to me. Also, I couldn't email the admins. Although I might have given the impression that it worked, this topic haven't reached it's end. Waiting for another update, thanks.
This forum page 2 and beyond doesn't exhibit the further discussions. It gives Error 502.
Ivan
17/08/2017
Re: rebootPro Forum
If you email me or use the Contact Me form, I will give you nuno's email address.
Is the forum page 2 issue fixed now?
Is the forum page 2 issue fixed now?
SteveSi
18/08/2017
UEFI .imgPTN direct booting from menu
I want to UEFI boot from an .imgPTN file from E2B main menu (I removed Windows sub menu with your instructions) but I don't know how to do it. I can only boot from UEFI by switching partitions but with that i can't use the main menu (Only windows setup) which is i want to use. I will be glad if you help me.
Thank you.
Thank you.
Allen
02/08/2017
Re: UEFI .imgPTN direct booting from menu
If it was possible to UEFI-boot to the E2B menu, I would have done it!
E2B uses grub4dos which cannot be UEFI-booted.
You may like to try the complex E2B Grub2 Menu system. This needs to be 'switched' too, but once switched you can MBR and UEFI-boot to many different linux payloads/ISOs. However, it does not support Windows ISOs/payloads.
If your main usage is for Windows and MBR\UEFI, you should try WinSetupFromUSB.
If you like it, you can make a .imgPTN file from a WInSetupFromUSB flash drive and add the image to your E2B USB drive. There is a page of instructions on this site.
Note that some 'buggy' BIOSes will not MBR-boot if there are valid UEFI-boot files on the drive. Also note that most UEFI-solutions use FAT32 which means you cannot have files >4gb.
Due to these limitations, E2B uses the partition-swap\Switch process. That way everything is kept separate but you can boot to 100's of different MBR and UEFI payloads on all types of systems.
E2B uses grub4dos which cannot be UEFI-booted.
You may like to try the complex E2B Grub2 Menu system. This needs to be 'switched' too, but once switched you can MBR and UEFI-boot to many different linux payloads/ISOs. However, it does not support Windows ISOs/payloads.
If your main usage is for Windows and MBR\UEFI, you should try WinSetupFromUSB.
If you like it, you can make a .imgPTN file from a WInSetupFromUSB flash drive and add the image to your E2B USB drive. There is a page of instructions on this site.
Note that some 'buggy' BIOSes will not MBR-boot if there are valid UEFI-boot files on the drive. Also note that most UEFI-solutions use FAT32 which means you cannot have files >4gb.
Due to these limitations, E2B uses the partition-swap\Switch process. That way everything is kept separate but you can boot to 100's of different MBR and UEFI payloads on all types of systems.
SteveSi
02/08/2017
WPI ISO
Hello i have downloaded WPI iso file how configure easy2boot to auto oper the WPI ISO?
karencho
12/07/2017
Re: WPI ISO
Can you give me a clue as to what WPI stands for?
Exact name of ISO? URL to download it from?
Exact name of ISO? URL to download it from?
SteveSi
12/07/2017
Re: Re: WPI ISO
here you go :
LINK REMOVED AS VIRUSES IN DOWNLOADS!
LINK REMOVED AS VIRUSES IN DOWNLOADS!
karencho
12/07/2017
Re: Re: Re: WPI ISO
I think I found the torrent- will download...
But for most ISOs that are AIO's you make a FAT32 .imgPTN file using the MPI Tool Kit.
But for most ISOs that are AIO's you make a FAT32 .imgPTN file using the MPI Tool Kit.
SteveSi
12/07/2017
Re: Re: Re: Re: WPI ISO
The ISO does not seem to be bootable.
Furthermore that URL is full of terrible malware\viruses\PUPs as .exe downloads!!!
Furthermore that URL is full of terrible malware\viruses\PUPs as .exe downloads!!!
SteveSi
12/07/2017
Re: Re: Re: Re: Re: WPI ISO
but how can i install applications plus have universal Lan Drives that is possible?
karencho
12/07/2017
Re: Re: Re: Re: Re: Re: WPI ISO
E2B is a USB multiboot solution.
It allows you to boot a wide variety of different payloads.
I can only answer questions directly related to E2B.
It allows you to boot a wide variety of different payloads.
I can only answer questions directly related to E2B.
SteveSi
12/07/2017
Re: Re: Re: Re: Re: WPI ISO
my antivirus showing nothing
karencho
12/07/2017
Re: Re: Re: Re: Re: Re: WPI ISO
Clicking on the first utorrent button downloads minstall-by-andreyonohov-leha342-lite-v_09_05_2017-x86-x64-2017-rus.zip
This contains minstall-by-andreyonohov-leha342-lite-v_09_05_2017-x86-x64-2017-rus.exe
Which if you run it puts lots of malicious nasty things on your Windows drive and infects your system and browser! Also known as bitchkeyru_key.exe and steam_api64.exe
https://www.virustotal.com/en/file/d85e30bd9c24ee361adc1b517f9f28f2667981fe0e3506a2e69b06394bac1e32/analysis/1499882771/
This contains minstall-by-andreyonohov-leha342-lite-v_09_05_2017-x86-x64-2017-rus.exe
Which if you run it puts lots of malicious nasty things on your Windows drive and infects your system and browser! Also known as bitchkeyru_key.exe and steam_api64.exe
https://www.virustotal.com/en/file/d85e30bd9c24ee361adc1b517f9f28f2667981fe0e3506a2e69b06394bac1e32/analysis/1499882771/
SteveSi
12/07/2017
Re: Re: Re: Re: Re: Re: Re: WPI ISO
sorry for the link i did bot know but when i download that iso file there was no .exe files((( but i have an .iso file that is not starting i just put it in main menu folder but cant run it,and for example i have a Folders and files that i need to be in E2B how can i create an iso file to run it from E2B?how to do it correctly?
karencho
12/07/2017
Re: Re: Re: Re: Re: Re: Re: Re: WPI ISO
It is not a bootable ISO. It does not contain boot files. It cannot boot. I am not sure what the ISO is supposed to do? I know nothing about it. It is not my software.
SteveSi
12/07/2017
Re: Re: Re: Re: Re: Re: Re: Re: Re: WPI ISO
but if it will be bootable it will work yes?
karencho
12/07/2017
Re: Re: Re: Re: Re: Re: Re: Re: Re: WPI ISO
for example i have Programm folders ,and there is many sub folders like ,CD&DVD,Codecs and etc.... in this folders there are .exe instalations files that i need... plus there is an autorun.exe file that is runing the whole program to use that intalation .exe files what i should do to put them in E2B?
karencho
13/07/2017
Force make e2b to identify internal hdd
It may seem counter productive, but i would really like to make the first partition of my fixed internal drive an e2b drive. This would allow me to use a vhd for my primary os, and make restoration as simple as copying a file. I can't get the "make e2b drive" program to identify any internal disk as an option. Any suggestions? (Other than taking the disk out and attaching it to my usb dock)
Zachary Haynes
01/07/2017
Re: Force make e2b to identify internal hdd
E2B is just a set of files.
You can make the internal hard disk boot to grub4dos by using RMPrepUSB - Install grub4dos.
Then extract all the E2B files to the first partition.
This will only work on FAT32 or NTFS volumes and only for MBR booting (not GPT disks or UEFI).
So I hope you know what you are doing or you could lose all your files!
You can make the internal hard disk boot to grub4dos by using RMPrepUSB - Install grub4dos.
Then extract all the E2B files to the first partition.
This will only work on FAT32 or NTFS volumes and only for MBR booting (not GPT disks or UEFI).
So I hope you know what you are doing or you could lose all your files!
SteveSi
01/07/2017
Re: Re: Force make e2b to identify internal hdd
That's why I love e2b... It takes all the guesswork out of the equation. Hd0 is currently blank and waiting for me to do something with it. I was just wondering if there was a line in one of the config files e2b uses that i could alter to make it identify fixed drives. Every time i have tried to manually configure boot loaders or grub i never seem to get it right.
Zachary Haynes
01/07/2017
Re: Re: Force make e2b to identify internal hdd
Thank you!!! At first the program seemed a little daunting... but once I realized what I was doing...
Everything about the work you are doing (while possibly intimidating to the uninitiated) is with out a doubt the greatest thing since sliced bread! No more yumi, No more unetbootin, No more any other program. You sir, have made me appear much smarter than I actually am. Thank you for the work you have done!
Everything about the work you are doing (while possibly intimidating to the uninitiated) is with out a doubt the greatest thing since sliced bread! No more yumi, No more unetbootin, No more any other program. You sir, have made me appear much smarter than I actually am. Thank you for the work you have done!
Zachary Haynes
01/07/2017
Hide a switched imgPTN
Hi
The "Hide E2B Partition" script works great for me. For maximum privacy though, is it possible to hide a switched in patrition image? So that you can hide the new partition when a imgPTN file is being switched in? That'd be great
The "Hide E2B Partition" script works great for me. For maximum privacy though, is it possible to hide a switched in patrition image? So that you can hide the new partition when a imgPTN file is being switched in? That'd be great
7root
28/06/2017
Re: Hide a switched imgPTN
If the .imgPTN is a FAT32 partition, you can add the following lines just below the set VER=0.076 line
# Hide this FAT32 partition from Windows
cat --locate=\x00\x00 --skip=0x2a --length=2 --replace=\xaa\xaa (hd0,0)+1
hide (hd0,0)
This will cause the FAT32 ptn to be hidden from windows but not from linux.
You need to boot to the CSM menu once so the code is run.
See http://www.rmprepusb.com/tutorials/130 for more details
# Hide this FAT32 partition from Windows
cat --locate=\x00\x00 --skip=0x2a --length=2 --replace=\xaa\xaa (hd0,0)+1
hide (hd0,0)
This will cause the FAT32 ptn to be hidden from windows but not from linux.
You need to boot to the CSM menu once so the code is run.
See http://www.rmprepusb.com/tutorials/130 for more details
SteveSi
28/06/2017
Re: Re: Hide a switched imgPTN
I found an even simpler solution to hide a switched in imgPTN from Windows (will still be visible to Grub4Dos and Linux): start diskmgmt.msc as admin and remove the drive letter!
Windows immediately unmounts the partition.
It works!
Windows immediately unmounts the partition.
It works!
7root
29/06/2017
Re: Re: Re: Hide a switched imgPTN
No - all that does it makes a registry entry in YOUR Windows system. It has no effect if you plug the drive into a different system.
SteveSi
29/06/2017
Re: Re: Re: Re: Hide a switched imgPTN
Which was exactly what I was trying to achieve
7root
30/06/2017
Re: Re: Re: Re: Re: Hide a switched imgPTN
So you don't mind other people being able to see the partition!
SteveSi
30/06/2017
Re: Re: Re: Re: Re: Re: Hide a switched imgPTN
As long as it remains attached to my computer physically, they won't!
7root
01/07/2017
Re: Hide a switched imgPTN
Another way to do it is to "unswitch" (i.e. restore the e2b partition table) upon shutdown. That would make it impossible to access the files in your imgPTN since it restores e2b when you shut down your PC. I dont know how to implement this into e2b tho, probably u need to edit some file. Maybe @Steve can help here?
lachance
02/07/2017
Boot options toggle
Hi
Great program - its so configurable its brilliant
I am trying to get my home PC to automatically boot between two options and it should choose the opposite choice from what was automatically chosen last time - ie a toggle. This should be totally automated and not require me to be at the boot screen (ie If I am in Windows I choose restart and it will via easy2boot - boot automatically into another environment).
So far I have got as far as getting it to the CSM menu which I am using with my image and menua defaulting it to choice 3 but as mentioned I want it so that because choice 3 was automatically chosen 3 last time, then next time I want F7 (HDD boot) to take place.
I thought I might be able to it by creating txt file and getting it to check for the existence of that txt file ie
(if exist lastchoice.txt then boot USB option 3,
del lastchoice.txt)
(if not exist lastchoice.txt then boot F7, create lastchoice.txt)
and so on - effectively making it boot into the CSM menu and choosing the opposite choice of what was automatically chosen last time.
Many thanks!
Great program - its so configurable its brilliant
I am trying to get my home PC to automatically boot between two options and it should choose the opposite choice from what was automatically chosen last time - ie a toggle. This should be totally automated and not require me to be at the boot screen (ie If I am in Windows I choose restart and it will via easy2boot - boot automatically into another environment).
So far I have got as far as getting it to the CSM menu which I am using with my image and menua defaulting it to choice 3 but as mentioned I want it so that because choice 3 was automatically chosen 3 last time, then next time I want F7 (HDD boot) to take place.
I thought I might be able to it by creating txt file and getting it to check for the existence of that txt file ie
(if exist lastchoice.txt then boot USB option 3,
del lastchoice.txt)
(if not exist lastchoice.txt then boot F7, create lastchoice.txt)
and so on - effectively making it boot into the CSM menu and choosing the opposite choice of what was automatically chosen last time.
Many thanks!
JimmyK
05/06/2017
Re: Boot options toggle
Do you really want a toggle or would you prefer to be able to boot or reboot into either OS?
What is Option 3 - I can't see your menu...
What OS is the HDD booting to and what is Option 3 booting to?
What is Option 3 - I can't see your menu...
What OS is the HDD booting to and what is Option 3 booting to?
SteveSi
05/06/2017
Re: Re: Boot options toggle
Set the default to boot to the Unraid entry
At the top of the \menu.lst (just under comments) use
find --devices=h /unraid.tag || map (hd0) (hd1) && map (hd1) (hd0) && map --hook && rootnoverify (hd0,0) && chainloader (hd0)0+2 && boot
This says - look for \unraid.tag on all hard drives (includes the USB) - if NOT found boot to internal HDD.
Create the \unraid.tag file using a batch file in Windows and create a script to delete the file in UnRaid to make it boot to Windows.
At the top of the \menu.lst (just under comments) use
find --devices=h /unraid.tag || map (hd0) (hd1) && map (hd1) (hd0) && map --hook && rootnoverify (hd0,0) && chainloader (hd0)0+2 && boot
This says - look for \unraid.tag on all hard drives (includes the USB) - if NOT found boot to internal HDD.
Create the \unraid.tag file using a batch file in Windows and create a script to delete the file in UnRaid to make it boot to Windows.
SteveSi
05/06/2017
Bad or Invalid E:\Unattend.xml
Hello!
I am trying to make a working USB flash helper drive for installing Windows 10 for some hours now, but it won't work.
The drive is recognized properly, and Windows is trying to maker us of it, but then there's always the Bad or Invalid E:\Unattend.xml error.
In your error messages collection I found this hint:
"check that the blank \AutoUnattend.xml and \Unattend.xml are at least as large as your original .xml file - if not you will need to make them larger! Check that no other drive contains these xml files in the root."
I tried increasing the size of the blank xml files to 2MegaByte, but it wouldn't help. And what do you mean by "original xml files"? I have no original xml files, I just want to plain install Windows 10.
Thank you in advance!
I am trying to make a working USB flash helper drive for installing Windows 10 for some hours now, but it won't work.
The drive is recognized properly, and Windows is trying to maker us of it, but then there's always the Bad or Invalid E:\Unattend.xml error.
In your error messages collection I found this hint:
"check that the blank \AutoUnattend.xml and \Unattend.xml are at least as large as your original .xml file - if not you will need to make them larger! Check that no other drive contains these xml files in the root."
I tried increasing the size of the blank xml files to 2MegaByte, but it wouldn't help. And what do you mean by "original xml files"? I have no original xml files, I just want to plain install Windows 10.
Thank you in advance!
ElMariachi
18/05/2017
Re: Bad or Invalid E:\Unattend.xml
Did you follow the guide
http://www.easy2boot.com/make-an-easy2boot-usb-drive/how-to-make-a-helper-usb-flash-drive/
Make sure no other flash drive or CD is present in the system.
Does E2B say WinHelper drive was found and it is wiping it, just before E2B menu is displayed?
Is drive E: the correct USB drive (press SHIFT+F10 to get command console in Windows Setup).
Original files are the 100K ones in the WinHelper docs folder
http://www.easy2boot.com/make-an-easy2boot-usb-drive/how-to-make-a-helper-usb-flash-drive/
Make sure no other flash drive or CD is present in the system.
Does E2B say WinHelper drive was found and it is wiping it, just before E2B menu is displayed?
Is drive E: the correct USB drive (press SHIFT+F10 to get command console in Windows Setup).
Original files are the 100K ones in the WinHelper docs folder
SteveSi
18/05/2017
Re: Re: Bad or Invalid E:\Unattend.xml
Hello!
I followed the instructions. I have tried multiple flash drives. A;; are of removable type. The path "E:" is correct. The xml files are the same as in helper directory, I have tried copying them over multiple times. Also I have tried FAT32 and NTFS.
I followed the instructions. I have tried multiple flash drives. A;; are of removable type. The path "E:" is correct. The xml files are the same as in helper directory, I have tried copying them over multiple times. Also I have tried FAT32 and NTFS.
ElMariachi
19/05/2017
Re: Re: Re: Bad or Invalid E:\Unattend.xml
When E2B boots, just before the Main menu loads, you should see a message that says
Wiping /AutoUnattend.xml and /Unattend.xml files on WINHELPER.USB
Do you see this when you boot to the E2B menu with the Helper USb drive also connected?
When do you see the E:\Unattend.xml message - after installation of Windows or before you can start the installation?
P.S. You can chat with me if the chat icon is displayed on website.
Wiping /AutoUnattend.xml and /Unattend.xml files on WINHELPER.USB
Do you see this when you boot to the E2B menu with the Helper USb drive also connected?
When do you see the E:\Unattend.xml message - after installation of Windows or before you can start the installation?
P.S. You can chat with me if the chat icon is displayed on website.
SteveSi
19/05/2017
Re: Re: Re: Re: Bad or Invalid E:\Unattend.xml
Did you get this working?
What does 'A;; are of removable type' mean??
Did you format the WinHelper USb drive using RMPrepUSB?
What does 'A;; are of removable type' mean??
Did you format the WinHelper USb drive using RMPrepUSB?
SteveSi
10/06/2017
Unbootable ISOs
Hello there, I need to decide about proper extension for some ISOs I can't make booting from E2B -
- Acronis Backup 11 (unknown)
- DLC Boot 2016 (unknown)
- Macrium Reflect 7 rescue media (appears to be WinPE)
- SystemRescueCD x86 (unknown)
Also I want to ask how to remove default main menu entries which are related to E2B menu, such as fonts demo, change menu default, timeout etc., or move them all to submenu, so that at top level only appear direct choices for bootable ISOs.
Thanks!
- Acronis Backup 11 (unknown)
- DLC Boot 2016 (unknown)
- Macrium Reflect 7 rescue media (appears to be WinPE)
- SystemRescueCD x86 (unknown)
Also I want to ask how to remove default main menu entries which are related to E2B menu, such as fonts demo, change menu default, timeout etc., or move them all to submenu, so that at top level only appear direct choices for bootable ISOs.
Thanks!
solstiv
11/05/2017
Re: Unbootable ISOs
Hi
You do not say what type of USB drive you have - Removable Flash drive or 'Fixed Disk' type?
E2B will usually suggest the best extension - did you turn this off? if so, press SCROLL LOCK before you select an ISO to see suggestions.
First search this page.
http://www.easy2boot.com/add-payload-files/list-of-tested-payload-files/
DLCD is a variant of Hirens so see
http://www.easy2boot.com/add-payload-files/hirens-isos
WinPE based ISOs may boot as .isoPE01 from a removable USB drive or convert to .imgPTN file.
SystemRescueCD.iso should just work.
If you ran PimpMyDrive.cmd then a \_ISO\MAINMENU\PIMP folder will have been created - delete any .mnu file in that folder you do not want.
Use
set DEFMENU=0 in \_ISO\MyE2B.cfg file
to remove Set Timeout and defaults menu entry.
See http://www.easy2boot.com/configuring-e2b/
To re-order menu entries, rename the payload and .mnu files in the menu folder.
If you have any specific issues with specific ISOs, please give details.
Remember that when you run E2B Update, the update process will copy the E2B files back, so if possible, use MyE2B.cfg settings or ADD extra files, but do not change existing files.
You do not say what type of USB drive you have - Removable Flash drive or 'Fixed Disk' type?
E2B will usually suggest the best extension - did you turn this off? if so, press SCROLL LOCK before you select an ISO to see suggestions.
First search this page.
http://www.easy2boot.com/add-payload-files/list-of-tested-payload-files/
DLCD is a variant of Hirens so see
http://www.easy2boot.com/add-payload-files/hirens-isos
WinPE based ISOs may boot as .isoPE01 from a removable USB drive or convert to .imgPTN file.
SystemRescueCD.iso should just work.
If you ran PimpMyDrive.cmd then a \_ISO\MAINMENU\PIMP folder will have been created - delete any .mnu file in that folder you do not want.
Use
set DEFMENU=0 in \_ISO\MyE2B.cfg file
to remove Set Timeout and defaults menu entry.
See http://www.easy2boot.com/configuring-e2b/
To re-order menu entries, rename the payload and .mnu files in the menu folder.
If you have any specific issues with specific ISOs, please give details.
Remember that when you run E2B Update, the update process will copy the E2B files back, so if possible, use MyE2B.cfg settings or ADD extra files, but do not change existing files.
SteveSi
11/05/2017
Re: Re: Unbootable ISOs
Firstly it's a removable drive.
As for DLC2016 I did already check suggestions at http://www.easy2boot.com/add-payload-files/hirens-isos/
.isowinvh seems work only for base Hiren's CD 15.2
.isowinvh seems work partially for Hiren's Boot DVD 15.2 Restored Edition 1.1 Proteus, only DOS utilities and no boot to Windows. i need a suggestion here too
DLCBoot2016 seems to fail with all suggested extensions <= suggestion here
SystemRescueCD and Macrium are sorted
As for DLC2016 I did already check suggestions at http://www.easy2boot.com/add-payload-files/hirens-isos/
.isowinvh seems work only for base Hiren's CD 15.2
.isowinvh seems work partially for Hiren's Boot DVD 15.2 Restored Edition 1.1 Proteus, only DOS utilities and no boot to Windows. i need a suggestion here too
DLCBoot2016 seems to fail with all suggested extensions <= suggestion here
SystemRescueCD and Macrium are sorted
solstiv
11/05/2017
Re: Re: Unbootable ISOs
Acronis Backup is also not fixed - kernel panic not syncing VFS
True Image 2017 ISO just boots fine as .isope
True Image 2017 ISO just boots fine as .isope
solstiv
11/05/2017
Re: Re: Re: Unbootable ISOs
Acronis Backup?? You mean Acronis True Image 2017? Works OK for me as .iso.
If it is linux based, then it should work.
Maybe there is a hardware compatibility issue?
Did you make the 32-bit version or 64-bit version?
If 32-bit you can try booting it using \QEMU_MENU_TEST.cmd in root of drive.
re. DLC - it says to use .isoHW
For some you may need to convert to .imgPTN. HBCD Proteus is listed on the page link I gave you as tested and working if you use .imgPTN.
If it is linux based, then it should work.
Maybe there is a hardware compatibility issue?
Did you make the 32-bit version or 64-bit version?
If 32-bit you can try booting it using \QEMU_MENU_TEST.cmd in root of drive.
re. DLC - it says to use .isoHW
For some you may need to convert to .imgPTN. HBCD Proteus is listed on the page link I gave you as tested and working if you use .imgPTN.
SteveSi
11/05/2017
Re: Re: Re: Re: Unbootable ISOs
About the Acronis
Acronis Backup Advanced 11.7.50064 Boot CD
there's a difference between TI and BA
the root structure is as
<boot.images>
<efi>
<Recovery Manager>
abr32ker.dat
abr32ram.dat
abr64ker.dat
abr64ram.dat
bootmenu.exe
bootmenu.xml
bootwiz.cfg
bootwiz.sys
C1.png
C2.png
cpp.so
dat4.dat
dat8.dat
fox.so
gen_boot.so
graphapi.so
icu38.so
icudt38.so
libc.so
libgcc_s.so
menulogo.png
mouse.com
osfiles.so
resource.so
sgn5.sgn
sgn9.sgn
SPL1.EXE
SPL5.EXE
threads.so
I have an additional question, if I want to preserve all the default e2b menu entries (Change font, boot to hd0 etc..) and move them to some 2nd level menu, what do I edit?
Acronis Backup Advanced 11.7.50064 Boot CD
there's a difference between TI and BA
the root structure is as
<boot.images>
<efi>
<Recovery Manager>
abr32ker.dat
abr32ram.dat
abr64ker.dat
abr64ram.dat
bootmenu.exe
bootmenu.xml
bootwiz.cfg
bootwiz.sys
C1.png
C2.png
cpp.so
dat4.dat
dat8.dat
fox.so
gen_boot.so
graphapi.so
icu38.so
icudt38.so
libc.so
libgcc_s.so
menulogo.png
mouse.com
osfiles.so
resource.so
sgn5.sgn
sgn9.sgn
SPL1.EXE
SPL5.EXE
threads.so
I have an additional question, if I want to preserve all the default e2b menu entries (Change font, boot to hd0 etc..) and move them to some 2nd level menu, what do I edit?
solstiv
11/05/2017
Re: Re: Re: Re: Re: Unbootable ISOs
They use bootwiz which seems to need a real CD.
You can convert to a .imgPTN file, but it will also need a special menu entry in the \menu.lst file which will need to be worked out
see http://rmprepusb.blogspot.co.uk/2017/03/boot-acronis-true-image-2017-ng-from.html
re. .mnu files. You can just copy them to any other standard menu folder, e.g. \_ISO\UTILITIES.
If you want to make a new sub-menu folder, then see http://www.easy2boot.com/configuring-e2b/add-a-new-menu-folder/
You can convert to a .imgPTN file, but it will also need a special menu entry in the \menu.lst file which will need to be worked out
see http://rmprepusb.blogspot.co.uk/2017/03/boot-acronis-true-image-2017-ng-from.html
re. .mnu files. You can just copy them to any other standard menu folder, e.g. \_ISO\UTILITIES.
If you want to make a new sub-menu folder, then see http://www.easy2boot.com/configuring-e2b/add-a-new-menu-folder/
SteveSi
11/05/2017
Re: Re: Re: Re: Re: Re: Unbootable ISOs
I made a DLC 2016 3.2 ISO.
This seems to work well just as .iso
This seems to work well just as .iso
SteveSi
12/05/2017
Re: Re: Re: Re: Re: Re: Re: Unbootable ISOs
Thanks, I'll have look at Acronis forum.
Except DLC which won't boot for me as .ISO everything cleared.
Except DLC which won't boot for me as .ISO everything cleared.
solstiv
12/05/2017
Re: Re: Re: Re: Re: Re: Re: Re: Unbootable ISOs
The first time I made the DLC2016 ISO it did not boot. I then used RMprepUSB - Ctrl+F11 (boot from ISO in QEMU) to test it and it reported a corrupted file. I then made the ISO again and that time it worked. So check your ISO actually works by booting directly from it in a VM.
SteveSi
12/05/2017
Re: Re: Re: Re: Re: Re: Re: Re: Re: Unbootable ISOs
Acronis Backup
\menu.lst (inside .imgPTN file) - add to bottom of menu...
title Acronis Backup 11.7.50064 (32-bit)
kernel /abr32ker.dat product=bootagent media_for_windows vga=791 quiet
initrd /abr32ram.dat /dat4.dat
boot
title Acronis Backup 11.7.50064 (64-bit)
kernel /abr64ker.dat product=bootagent media_for_windows vga=791 quiet
initrd /abr64ram.dat /dat8.dat
boot
\menu.lst (inside .imgPTN file) - add to bottom of menu...
title Acronis Backup 11.7.50064 (32-bit)
kernel /abr32ker.dat product=bootagent media_for_windows vga=791 quiet
initrd /abr32ram.dat /dat4.dat
boot
title Acronis Backup 11.7.50064 (64-bit)
kernel /abr64ker.dat product=bootagent media_for_windows vga=791 quiet
initrd /abr64ram.dat /dat8.dat
boot
SteveSi
12/05/2017
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Unbootable ISOs
http://rmprepusb.blogspot.co.uk/2017/05/add-dlc-boot-2016-to-e2b.html
SteveSi
12/05/2017
Auto GFX=NONE and or Enable GFX mode depending on hardware/Resolution/Components
I know you have the "prompt for faster boot option in the E2B.cfg...Wondering if there would be a way to have E2B detect if the machine is capable of running graphics/GFX mode or if it would be faster to use GFX=none. Either by checking date of machine make or cpu speed or ram size or other? Thoughts?
Jonathan
10/05/2017
Re: Auto GFX=NONE and or Enable GFX mode depending on hardware/Resolution/Components
You misunderstand.
Slow speed is due to slow USB access. This is caused by the BIOS having poor USB drivers (e.g. USB 1.0 or slow USB 2.0 drivers) and\or a slow USB drive.
The unifont font file (576Kb) is only used in graphics mode, it cannot be used in text mode. The wallpaper file (103k) cannot be used in text mode.
If we use text mode, then we don't have to load these files from a slow USB device, thus speeding up the boot process.
All systems with a USB port will be capable of 800x600x32 mode and any CPU will be fast enough.
We could run a speed test on the USB drive as it boots - but as this would take many seconds, there is no point!
Slow speed is due to slow USB access. This is caused by the BIOS having poor USB drivers (e.g. USB 1.0 or slow USB 2.0 drivers) and\or a slow USB drive.
The unifont font file (576Kb) is only used in graphics mode, it cannot be used in text mode. The wallpaper file (103k) cannot be used in text mode.
If we use text mode, then we don't have to load these files from a slow USB device, thus speeding up the boot process.
All systems with a USB port will be capable of 800x600x32 mode and any CPU will be fast enough.
We could run a speed test on the USB drive as it boots - but as this would take many seconds, there is no point!
SteveSi
10/05/2017
Re: Re: Auto GFX=NONE and or Enable GFX mode depending on hardware/Resolution/Components
Let me try this example, perhaps I am still misunderstanding..
EX: I have a graphic interface and wallpaper with animated logo on my USB 3.0 E2B drive. I plug it into a very old machine that has usb 1.0 ports and or a bad bios, this takes significantly longer to load...
Could E2B detect a system like this, usb 1.0 or bad bios notification and automatically select text mode to boot E2B?
Thank you!!
EX: I have a graphic interface and wallpaper with animated logo on my USB 3.0 E2B drive. I plug it into a very old machine that has usb 1.0 ports and or a bad bios, this takes significantly longer to load...
Could E2B detect a system like this, usb 1.0 or bad bios notification and automatically select text mode to boot E2B?
Thank you!!
Jonathan
10/05/2017
Re: Re: Re: Auto GFX=NONE and or Enable GFX mode depending on hardware/Resolution/Components
How could it detect such a system?
Can you detect such a system - if so how?
Can you detect such a system - if so how?
SteveSi
10/05/2017
Re: Re: Re: Re: Auto GFX=NONE and or Enable GFX mode depending on hardware/Resolution/Components
I know you have the bad bios detection. But that doesnt mean it would be a slow usb drive. SO I guess our only options would be to test the usb port at boot and you are right at that point it would take too long! Trying to automate too much me thinks..hehe.. oh well. Thank you!!
Jonathan
10/05/2017
Re: Re: Re: Re: Re: Auto GFX=NONE and or Enable GFX mode depending on hardware/Resolution/Components
Exactly!
You can always try holding down the SHIFT key just before E2B boots to load the grub4dos USB 2 driver.
You can always try holding down the SHIFT key just before E2B boots to load the grub4dos USB 2 driver.
SteveSi
10/05/2017
AHCI_XP_Z170
Hello, or put the AHCI files to be taken into account when installing xp on a z170 platform?
As are firadisk.
thank you
As are firadisk.
thank you
christophe
07/05/2017
Re: AHCI_XP_Z170
Hi
Go to Alternate Download Area - Other Files and download DMZ170_DPMS2.zip. This is 32-bit drivers. Note that E2B does not support 64-bit XP DPMS drivers.
Read ReadMe.txt inside for instructions.
Go to Alternate Download Area - Other Files and download DMZ170_DPMS2.zip. This is 32-bit drivers. Note that E2B does not support 64-bit XP DPMS drivers.
Read ReadMe.txt inside for instructions.
SteveSi
07/05/2017
New Utliman hack and windows 10 ISO
A long time ago, windows 8 days. Someone was able to make a modified wim that was basically just the recovery portion of the win 8 installer. (the special reboot screen you get if you hold shift down on windows 8+) basically from there you could also run commands, .exes, portableapps, with the help of a little loader baked in. I have the wim if you would like to look. But I wonder if there could be a way to do this with windows 10 to use with utilihack so we dont need a full win 10 ISO to use?
Jonathan
03/05/2017
Re: New Utliman hack and windows 10 ISO
Sure, just delete the \sources\Install.wim or .esd from a standard MS ISO and use it with E2B Removable flash drive.
SteveSi
03/05/2017
Re: Re: New Utliman hack and windows 10 ISO
It worked! Downloaded the dual 32/64 bit version for MS media creator. Removed the .esd, file size is now 1gb iso. I am sure I can get it smaller with some more tinkering or gimagex... thank you!!!!
Jonathan
04/05/2017
Re: Re: Re: New Utliman hack and windows 10 ISO
Why do you need a dual version? Just a 32-bit version will work.
Or if you have a WinPE ISO already, you could just boot to that and run the first .cmd file manually.
Or if you have a WinPE ISO already, you could just boot to that and run the first .cmd file manually.
SteveSi
04/05/2017
Re: Re: Re: Re: New Utliman hack and windows 10 ISO
Good point. I thought there was issues with 64/32bit uefis on some tablets. Some requiring one or the other?
Jonathan
04/05/2017
Re: Re: Re: Re: Re: New Utliman hack and windows 10 ISO
if you boot using UEFI you will need to convert the ISO to a .imgPTN file.
In that case, you will need to name the file \AutoUnattend.xml and put it in the root of the partition (if the USB drive is a Removable drive) or put the file in the boot.wim file (if the USB drive is the Fixed disk type).
In that case, you will need to name the file \AutoUnattend.xml and put it in the root of the partition (if the USB drive is a Removable drive) or put the file in the boot.wim file (if the USB drive is the Fixed disk type).
SteveSi
06/05/2017
Re: Re: Re: Re: Re: Re: New Utliman hack and windows 10 ISO
Thank you that works!!
Jonathan
10/05/2017
DBAN and Parted Magic?
Reboot.pro doesn't seem to work so hopefully someone will see this. I'm looking to make a flash drive that I can use for wiping hard drives. I've used DBAN for non-SSDs and Parted Magic for SSDs. Is there an easy way to put both of those on the same flash drive with a menu using E2B? I didn't see a tutorial about that but figured maybe someone had already done it.
Thanks!
Thanks!
Kel
17/04/2017
Re: DBAN and Parted Magic?
Hi - no need for a tutorial?
After you make the E2B USB drive, copy the ISOs to \_ISO\MAINMENU and boot!
After you make the E2B USB drive, copy the ISOs to \_ISO\MAINMENU and boot!
SteveSi
17/04/2017
Grub2 menu system.. how to install Kali 2.0
Hi, i successfully got to the installation menu of kali linux 2.0 by using loopback.cfg, but when the cd error thing comes up i cant find the iso mount in shell.
mikoloko
17/04/2017
Re: Grub2 menu system.. how to install Kali 2.0
I don't think that the loopback.cfg is the correct menu for an install.
Look inside the ISO at \isolinux\install.cfg for the way to invoke the install menu.
You could convert the ISO to a .imgPTN file. Then you should get the install option.
Look inside the ISO at \isolinux\install.cfg for the way to invoke the install menu.
You could convert the ISO to a .imgPTN file. Then you should get the install option.
SteveSi
17/04/2017
Re: Re: Grub2 menu system.. how to install Kali 2.0
yes i convert it to .imgptn and everything is working fine but i just want to try if grub2 is capable of installing os through .iso in uefi mode.
mikoloko
17/04/2017
Re: Re: Re: Grub2 menu system.. how to install Kali 2.0
Look at the kali EFI64 menu in the linux.grub2 file and make a new .grub2 file with just that entry.
Test it.
Then look at the \isolinux\install.cfg file inside the ISO file and use that to modify the new .grub2 menu - adapt the menu to use the install lines
#graphical install
linux /install/gtk/vmlinuz video=vesa:ywrap,mtrr vga=788 -- quiet
initrd /install/gtk/initrd.gz
However, Kali may not support UEFI installation??
Test it.
Then look at the \isolinux\install.cfg file inside the ISO file and use that to modify the new .grub2 menu - adapt the menu to use the install lines
#graphical install
linux /install/gtk/vmlinuz video=vesa:ywrap,mtrr vga=788 -- quiet
initrd /install/gtk/initrd.gz
However, Kali may not support UEFI installation??
Steve Si
18/04/2017
Re: Re: Re: Re: Grub2 menu system.. how to install Kali 2.0
hi sorry for the late reply, i confirmed that kali linux 2.0 weekly 15 supports uefi booting now, i am dual booting windows10 and kali on my uefi laptop. gonna try your suggestion on grub2 thank you very much :)
mikoloko
22/04/2017
100% disk usage booting vhd
hello
I got an intenso speedline 256 GB (usb 3.0)
Whenever i boot from my windows 10 VHD, it boots fine, but it is really slow. I open task manager and the disk shows 100% using only 0.1 MB.. What can i do to improve this?
Thank you for this wonderful tool!
I got an intenso speedline 256 GB (usb 3.0)
Whenever i boot from my windows 10 VHD, it boots fine, but it is really slow. I open task manager and the disk shows 100% using only 0.1 MB.. What can i do to improve this?
Thank you for this wonderful tool!
Legenda
16/04/2017
Re: 100% disk usage booting vhd
Some USB drives have really fast Sequential rd/wr access but terribly slow 4K random access.
http://rmprepusb.blogspot.co.uk/2016/10/beware-of-this-fast-usb-30-flash-drive.html
Test with CrystalDiskMark and check 4K times - should be well above 5
http://rmprepusb.blogspot.co.uk/2016/10/beware-of-this-fast-usb-30-flash-drive.html
Test with CrystalDiskMark and check 4K times - should be well above 5
SteveSI
16/04/2017
Re: Re: 100% disk usage booting vhd
Thanks i will read the link.
Would changing from VHD help increase performance a bit?..
Would changing from VHD help increase performance a bit?..
Legenda
16/04/2017
Re: Re: Re: 100% disk usage booting vhd
The problem is probably the drive itself - you can't fix that - test it with the CrystalDisk benchmark to find out and let us know the result.
SteveSi
16/04/2017
e2b stucks
Today i tried a new version of e2b (1.91) and new Windows 10 1703. So i formatted my pen drive, put win10 iso to win10 folder, rebooted pc. I was successfully booted to e2b (MBR mode) and i can go to UTILITIES menu to see my utils but when i'm choosing WINDOWS INSTALL Menu it just hangs. No errors, waiting didn't helps, just hang, that's all :(
Fourty
12/04/2017
Re: e2b stucks
What happens if you run \QEMU_MENU_TEST.cmd ?
Are you sure the format process when you made a new drive actually worked successfully?
Are you sure the format process when you made a new drive actually worked successfully?
Steve Si
12/04/2017
Re: Re: e2b stucks
Hi Steve!
I got it working, let me tell you what happened:
Even on old Win 10 Ent LTSB (that was pre 1703 for sure) i had a problems with formattind using v1.91, script said me he can't find "grubinst_new.exe" so i entered "Make_E2B_USB_Drive" dir and found there "grubinst.exe", renamed it to "grubinst_new.exe" and formatted my pen drive successfully.
After this i rebooted and stucked at WINDOWS INSTALL menu and come here to post my first message. Then i tried QEMU and it worked as planned, so i started to search the problem. First i tried another .iso, rebooted and stucked again (QEMU works).
I came to downloads section, found v1.90 on your google drive, unpacked it and just manually copied all contents to pen drive with overwriting, without reformatting (cuz i'm lazy and already copied bunch of .iso there and don't want to format again :)) to see what happens and it worked! Now i have working e2b pen drive with grub from 1.91 and all the stuff from 1.90.
I'm successfully installed new Win 10 Pro 1703 .iso, used Acronis Boot CD 2016 and 2017 .iso's and other stuff like HBCD 15.2 .iso without any problems.
By the way, i have only modified MyE2B.cfg file:
!BAT
if "%LANG%"=="" set LANG=ENG
set KBD=
set MYWBMP=0x000000
set EXTOFF=
set NOHELPER=1
Nothing else changed from original and ofc i'm making the drive contiguous after each new file that i put there.
I hope this will help, with best regards, FourtyTwo :)
P.S. Sorry for bad English :)
I got it working, let me tell you what happened:
Even on old Win 10 Ent LTSB (that was pre 1703 for sure) i had a problems with formattind using v1.91, script said me he can't find "grubinst_new.exe" so i entered "Make_E2B_USB_Drive" dir and found there "grubinst.exe", renamed it to "grubinst_new.exe" and formatted my pen drive successfully.
After this i rebooted and stucked at WINDOWS INSTALL menu and come here to post my first message. Then i tried QEMU and it worked as planned, so i started to search the problem. First i tried another .iso, rebooted and stucked again (QEMU works).
I came to downloads section, found v1.90 on your google drive, unpacked it and just manually copied all contents to pen drive with overwriting, without reformatting (cuz i'm lazy and already copied bunch of .iso there and don't want to format again :)) to see what happens and it worked! Now i have working e2b pen drive with grub from 1.91 and all the stuff from 1.90.
I'm successfully installed new Win 10 Pro 1703 .iso, used Acronis Boot CD 2016 and 2017 .iso's and other stuff like HBCD 15.2 .iso without any problems.
By the way, i have only modified MyE2B.cfg file:
!BAT
if "%LANG%"=="" set LANG=ENG
set KBD=
set MYWBMP=0x000000
set EXTOFF=
set NOHELPER=1
Nothing else changed from original and ofc i'm making the drive contiguous after each new file that i put there.
I hope this will help, with best regards, FourtyTwo :)
P.S. Sorry for bad English :)
Fourty
13/04/2017
Re: Re: Re: e2b stucks
If QEMU worked but a real system did not, then the problem is with your system's BIOS.
The usual reason is that you are using a partition of >137GB and the BIOS can only access sectors on a USB drive that are before 137GB.
grubinst_new.exe should never be used by the script because grubinst.exe is present in the directory and will always be used (unless there is a problem with your Windows somewhere).
The code is (where GR=grubinst.exe)
%GR% -h 2> gr.txt
set SILENT=
find "--silent-boot" gr.txt > nul
if not errorlevel 1 set SILENT=--silent-boot
if "%SILENT%"=="" set GR=grubinst_new.exe
so the find command should *always* be successful because the output from grubinst.exe included in the download will have the --silent text in the help output.
Please check you Windows PATH environment variable - maybe it is running the Cygwin version of FIND instead of the Windows version?
The usual reason is that you are using a partition of >137GB and the BIOS can only access sectors on a USB drive that are before 137GB.
grubinst_new.exe should never be used by the script because grubinst.exe is present in the directory and will always be used (unless there is a problem with your Windows somewhere).
The code is (where GR=grubinst.exe)
%GR% -h 2> gr.txt
set SILENT=
find "--silent-boot" gr.txt > nul
if not errorlevel 1 set SILENT=--silent-boot
if "%SILENT%"=="" set GR=grubinst_new.exe
so the find command should *always* be successful because the output from grubinst.exe included in the download will have the --silent text in the help output.
Please check you Windows PATH environment variable - maybe it is running the Cygwin version of FIND instead of the Windows version?
SteveSi
13/04/2017
windows 10 creators update got 2 usb e2b drive
Windows 10 X64 Build 15063.11 v1703 (windows 10 creators update) seems to had 2 usb drives. when i try to create new usb e2b drive. anyone can verify ??
Samuel
04/04/2017
Re: windows 10 creators update got 2 usb e2b drive
http://rmprepusb.blogspot.co.uk/2017/04/windows-10-creator-edition-brings-major.html
SteveSi
04/04/2017
On Debian 8.7.1 Live mate desktop ISO No Persistence Despite Following Prescribed Procedure.../
I have followed following procedure prescribed in FAQ.
"You MUST run WinContig after preparing the USB drive and making the ext2 file - all files including the ext2 file need to be contiguous.
Check that you have created the ext2 file according to the instructions in the .mnu file (use the latest RMPrepUSB version 2.1.711+ which allows you to set the file name and volume name separately). Check the file name and the volume name are correct - you can edit\change the ext2 filename but do NOT change the name of the Volume name from the one specified in the .mnu file."
Despite following suggested procedure, no persistence observed.
"You MUST run WinContig after preparing the USB drive and making the ext2 file - all files including the ext2 file need to be contiguous.
Check that you have created the ext2 file according to the instructions in the .mnu file (use the latest RMPrepUSB version 2.1.711+ which allows you to set the file name and volume name separately). Check the file name and the volume name are correct - you can edit\change the ext2 filename but do NOT change the name of the Volume name from the one specified in the .mnu file."
Despite following suggested procedure, no persistence observed.
Sidheshwar
31/03/2017
Re: On Debian 8.7.1 Live mate desktop ISO No Persistence Despite Following Prescribed Procedure.../
What instructions did you follow?
What .mnu file are you using?
What is exact name of ISO?
I tried the debian-live-8.7.1-amd64-mate-desktop.iso and debian-live-8.1.0-amd64-mate-desktop_Persistent.mnu
and found the echo command gave a 'permission denied' error after following the instructions in the .mnu file!
You need to use
sudo bash -c "echo '/ union' > /mnt/usb/persistence.conf"
instead
What .mnu file are you using?
What is exact name of ISO?
I tried the debian-live-8.7.1-amd64-mate-desktop.iso and debian-live-8.1.0-amd64-mate-desktop_Persistent.mnu
and found the echo command gave a 'permission denied' error after following the instructions in the .mnu file!
You need to use
sudo bash -c "echo '/ union' > /mnt/usb/persistence.conf"
instead
SteveSi
31/03/2017
Increase payload description detail lines
Hi Steve
My E2B drive is working great. I did notice though that the payload detail description lines is limited to 4 even though I see the screen allows for 3 more lines.
How do I increase the number of detail lines? ...I'll continue to look for this in the sample file and the other help pages as well.
Thank you
My E2B drive is working great. I did notice though that the payload detail description lines is limited to 4 even though I see the screen allows for 3 more lines.
How do I increase the number of detail lines? ...I'll continue to look for this in the sample file and the other help pages as well.
Thank you
Chuck
20/03/2017
Re: Increase payload description detail lines
The maximum number of menu help lines is 4 - it is a limitation of grub4dos.
grub4dos can use the 5th line for its own messages/prompts, so any menu should leave 5 lines free below the menu area to allow for a maximum of 5 lines.
grub4dos can use the 5th line for its own messages/prompts, so any menu should leave 5 lines free below the menu area to allow for a maximum of 5 lines.
SteveSi
20/03/2017
Re: Re: Increase payload description detail lines
It would be helpful to have another line but I understand. Thanks for your reply Steve.
Chuck
23/03/2017
Re: Re: Re: Increase payload description detail lines
Why not re-design the menu to make the menu wider. Then you can use longer lines and get more words into each line?
SteveSi
23/03/2017
Re: Re: Re: Re: Increase payload description detail lines
Ah ok. I guess I'll look into that. If that works, it should take care of the extra line of text I'd like to add on some payloads. Thanks.
Chuc
27/03/2017
Hiding payload names as sub menu loads
First, thanks a ton for all the work you have put into E2B. Fantastic.
I have setup a password with MD5 to hide certain payloads in various menus. This is all working great. However, by default many payloads are hidden as I want but when you go into the menu E2B seems to take an inventory of the items for that menu and you can see *ALL* payloads in that list just prior to the menu being shown with the appropriate payloads hidden.
How can I stop E2B from showing all payloads it is discovering prior to displaying the actual menu?
Thanks!
I have setup a password with MD5 to hide certain payloads in various menus. This is all working great. However, by default many payloads are hidden as I want but when you go into the menu E2B seems to take an inventory of the items for that menu and you can see *ALL* payloads in that list just prior to the menu being shown with the appropriate payloads hidden.
How can I stop E2B from showing all payloads it is discovering prior to displaying the actual menu?
Thanks!
Chuck
16/03/2017
Re: Hiding payload names as sub menu loads
Hi
If you add
set redir=> nul
in your \_ISO\MyE2B.cfg file, then E2B will not show the files that are being enumerated.
It also reduces other messages too, like QRUN autosuggest messages. See http://www.easy2boot.com/configuring-e2b/reducing-the-e2b-messages/
http://www.easy2boot.com/configuring-e2b/autosuggest/
Tip: Check the \_ISO\Sample_MyE2B.cfg file for lots of different settings.
If you add
set redir=> nul
in your \_ISO\MyE2B.cfg file, then E2B will not show the files that are being enumerated.
It also reduces other messages too, like QRUN autosuggest messages. See http://www.easy2boot.com/configuring-e2b/reducing-the-e2b-messages/
http://www.easy2boot.com/configuring-e2b/autosuggest/
Tip: Check the \_ISO\Sample_MyE2B.cfg file for lots of different settings.
SteveSi
16/03/2017
Re: Re: Hiding payload names as sub menu loads
Thank you! setting redir= worked perfectly.
Yes I have been referring to the Sample_MyE2B.cfg file a lot and have been reading a lot of the very well written help pages on your site.
The http://www.easy2boot.com/configuring-e2b/reducing-the-e2b-messages/ page that you referenced was exactly what I needed and I didn't find my way there before when I was reading. Thanks for pointing me in the right direction.
At this point, I think my e2b tools thumbdrive is done. I learned a lot relating to how e2b works and I know I still have a lot to learn but this is an excellent environment for creating these types of toolkits. Thanks again for all your work on this and also for your quick and helpful reply to my question here. :)
Yes I have been referring to the Sample_MyE2B.cfg file a lot and have been reading a lot of the very well written help pages on your site.
The http://www.easy2boot.com/configuring-e2b/reducing-the-e2b-messages/ page that you referenced was exactly what I needed and I didn't find my way there before when I was reading. Thanks for pointing me in the right direction.
At this point, I think my e2b tools thumbdrive is done. I learned a lot relating to how e2b works and I know I still have a lot to learn but this is an excellent environment for creating these types of toolkits. Thanks again for all your work on this and also for your quick and helpful reply to my question here. :)
Chuck
16/03/2017
Troubles with Hiren Extracted
So I extracted the entire Hirens contents onto the root of my flash drive & tried to put Hiren's Extracted.mnu in my Utilities folder of E2B.
Doesn't seem to be working :-(
Tried the contact form once a few weeks ago.. no dice.. figured once I got an address to reply to I'd send some pictures of my directory structures.
Doesn't seem to be working :-(
Tried the contact form once a few weeks ago.. no dice.. figured once I got an address to reply to I'd send some pictures of my directory structures.
Andrew
13/03/2017
Re: Troubles with Hiren Extracted
There are many different Hirens ISOs - exactly which one do you have?
The Contact Me form seems to work OK for me - can you try it again pls?
There is also an anonymous suggestions link too.
The Contact Me form seems to work OK for me - can you try it again pls?
There is also an anonymous suggestions link too.
SteveSi
13/03/2017
Re: Re: Troubles with Hiren Extracted
FYI - Andrew had a DLC ISO file but was using the Hirens .mnu file instead of the DLC .mnu file. It works now!
SteveSi
23/03/2017
UEFI, stuck at shell
Hi Steve!
I have been at it all day trying to make my usb hdd uefi boot. I have read and watched nearly all you have put up, but I can't find anything about being stuck at the uefi shell in virtualbox. It loads fine non-efi VMs both mbr and csm but when I load a efi enabled VM I just get a UEFI Interactive Shell. It tries to load a start.nsh but just goes to Shell> and then nothing.
I am using a windows 7 32 bit aio which should work on both types of "bios". It is sourced from a localized retail dvd so not downloaded. Could it be that the iso I made from it is the problem? I have multiple machines running the 64 bit version from that source also with no problems but that was bios/mbr machines.
Sincerely Michael
I have been at it all day trying to make my usb hdd uefi boot. I have read and watched nearly all you have put up, but I can't find anything about being stuck at the uefi shell in virtualbox. It loads fine non-efi VMs both mbr and csm but when I load a efi enabled VM I just get a UEFI Interactive Shell. It tries to load a start.nsh but just goes to Shell> and then nothing.
I am using a windows 7 32 bit aio which should work on both types of "bios". It is sourced from a localized retail dvd so not downloaded. Could it be that the iso I made from it is the problem? I have multiple machines running the 64 bit version from that source also with no problems but that was bios/mbr machines.
Sincerely Michael
Michael
12/03/2017
Re: UEFI, stuck at shell
I would just like stop wasting your time. I tried the mediacreationtool for windows 8.1 and that works just fine. So it is my win7 isos that have some kind of efi error. Sorry for bothering you and a big thank you for all your time giving us e2b!
Michael
12/03/2017
Re: UEFI, stuck at shell
Win7 32-bit does not support UEFI. It does not contain the UEFI boot files, etc. and is not supported by Microsoft.
Win 7 64-bit does support UEFI, but you must modify the files inside the .imgPTN image.
http://www.easy2boot.com/add-payload-files/win7-uefi/
When you switch to a .imgPTN file, E2B will tell you what UEFI-boot files are present and also it is listed below the CSM menu too.
Win 7 64-bit does support UEFI, but you must modify the files inside the .imgPTN image.
http://www.easy2boot.com/add-payload-files/win7-uefi/
When you switch to a .imgPTN file, E2B will tell you what UEFI-boot files are present and also it is listed below the CSM menu too.
SteveSi
12/03/2017
Acronis 2017 NG
Installed Acronis 2017 NG and installed the product key This allows me to create a Acronis image file for booting ether from a CD or for easy2boot usb works fine But when converting to a imgPTN file system it say's its a Trial version which it is not ,
is the conversion overwriting the product keys
Any advice would be appreciated
is the conversion overwriting the product keys
Any advice would be appreciated
Warren
12/03/2017
Re: Acronis 2017 NG
Is it the linux-based version or WinPE-based?
Did you try creating a USB drive using Acronis and then making a .imgPTN file from the USB drive?
Did you try UEFI-booting from .imgPTN file?
Did you try creating a USB drive using Acronis and then making a .imgPTN file from the USB drive?
Did you try UEFI-booting from .imgPTN file?
SteveSi
12/03/2017
Re: Re: Acronis 2017 NG
Add this to the end of your \menu.lst
#Acronis - must use quiet switch or get busybox error!
iftitle [if exist /Recovery\ Manager/kernel.dat if exist /dat3.dat && if exist /dat2.dat] Acronis 32-bit \n Acronis True Image
kernel /dat2.dat vga=791 force_modules=usbhid quiet
if exist /dat4.dat set d4=/dat4.dat
initrd /dat3.dat %d4%
boot
#Acronis 64 - must use quiet switch or get busybox error!
iftitle [checkrange 2,3 is64bit && if exist /Recovery\ Manager/kernel.dat if exist /dat10.dat && if exist /dat11.dat] Acronis 64-bit\n Acronis True Image
kernel /dat10.dat vga=791 force_modules=usbhid quiet
if exist /dat12.dat set d12=/dat12.dat
initrd /dat11.dat %d12%
boot
http://rmprepusb.blogspot.co.uk/2017/03/boot-acronis-true-image-2017-ng-from.html
#Acronis - must use quiet switch or get busybox error!
iftitle [if exist /Recovery\ Manager/kernel.dat if exist /dat3.dat && if exist /dat2.dat] Acronis 32-bit \n Acronis True Image
kernel /dat2.dat vga=791 force_modules=usbhid quiet
if exist /dat4.dat set d4=/dat4.dat
initrd /dat3.dat %d4%
boot
#Acronis 64 - must use quiet switch or get busybox error!
iftitle [checkrange 2,3 is64bit && if exist /Recovery\ Manager/kernel.dat if exist /dat10.dat && if exist /dat11.dat] Acronis 64-bit\n Acronis True Image
kernel /dat10.dat vga=791 force_modules=usbhid quiet
if exist /dat12.dat set d12=/dat12.dat
initrd /dat11.dat %d12%
boot
http://rmprepusb.blogspot.co.uk/2017/03/boot-acronis-true-image-2017-ng-from.html
SteveSi
12/03/2017
Re: Re: Re: Acronis 2017 NG
will try inserting the instructions in the menu.lst later
Thank You for the quick response
Thank You for the quick response
Warren
12/03/2017
Re: Re: Acronis 2017 NG
Yes to all parts created iso with Acronis and that works ok with easy2boot but need it to work with a image file imgptn
warren
12/03/2017
Re: Re: Re: Acronis 2017 NG
The ISO will work for MBR booting.
The .imgPTN will work for UEFI booting.
If you add the lines I gave to the end of the \menu.lst file (inside the .imgPTN file - just switch to the .imgPTN file to get CSM menu and then you can edit the \menu.lst file using Notepad) then you will get MBR booting from .imgPTN also working.
The .imgPTN will work for UEFI booting.
If you add the lines I gave to the end of the \menu.lst file (inside the .imgPTN file - just switch to the .imgPTN file to get CSM menu and then you can edit the \menu.lst file using Notepad) then you will get MBR booting from .imgPTN also working.
SteveSi
13/03/2017
Partition setup?
I'm a little confused about how I should partition the drive before I use easy2boot... did I miss that in the docs? Or does it not matter?
My goal is to have a USB drive that I can use to store files like any standard USB, from windows, mac, linux, etc.. but also be able to boot linux and still access those same files.
Doesn't that require a separate partition?
My goal is to have a USB drive that I can use to store files like any standard USB, from windows, mac, linux, etc.. but also be able to boot linux and still access those same files.
Doesn't that require a separate partition?
James Newton
05/03/2017
Re: Partition setup?
Please define 'USB drive'?
What type? Removable or Fixed?
What size?
Plenty of docs available under 'Make a USB drive' pages.
Since the whole idea of E2B is that you just copy on or delete the ISO files from linux or Windows, you can also add any other files\folders you like.
What type? Removable or Fixed?
What size?
Plenty of docs available under 'Make a USB drive' pages.
Since the whole idea of E2B is that you just copy on or delete the ISO files from linux or Windows, you can also add any other files\folders you like.
SteveSi
05/03/2017
switch_e2b.exe reported as Trojan.
Hi,
My Symantec Antivirus 14 reporting it as a trojan.
My Symantec Antivirus 14 reporting it as a trojan.
Tyler Nguyen
26/02/2017
Re: switch_e2b.exe reported as Trojan.
Is there an actual forum with proper threads and posts that this this can be discussed on? I have some questions but this is site format is just too much.... I would even offer hosting and set up a forum deicated to it if that would help!
diggity
04/03/2017
Re: Re: switch_e2b.exe reported as Trojan.
I have already given a link for a proper Forum - reboot.pro - see top of page.
SteveSi
04/03/2017
.imgPTN files
Taking in account that i already have all .imgPTN files that i need Is it necesary to create again .imgPTN files when newer version of MPI Tool Pack is released and go to the process of creating E2B bootable USB again?
Jorge
15/02/2017
Re: .imgPTN files
No. Old .imgPTN files will still work as long as they worked before!
SteveSi
15/02/2017
How to display Directory locations when adding menu entry .txt files?
Hi Steve. Great work.
By default, when I select any ISO payload on Menu, E2B shows as Help text under menu the Directoy location of ISO payload.
When I make a .txt file to display title of each ISO payload, then I cannot see these Directory locations how was by default.
Please. What "variable" must I adding to .txt files to show that location data to each ISO?
Thanks.
P.S.: I suggest adding permanent links over Subjects (Topics) on forum.
This makes it easy to save them as bookmarks or local html offline files.
By default, when I select any ISO payload on Menu, E2B shows as Help text under menu the Directoy location of ISO payload.
When I make a .txt file to display title of each ISO payload, then I cannot see these Directory locations how was by default.
Please. What "variable" must I adding to .txt files to show that location data to each ISO?
Thanks.
P.S.: I suggest adding permanent links over Subjects (Topics) on forum.
This makes it easy to save them as bookmarks or local html offline files.
Bertholdoüz
15/02/2017
Re: How to display Directory locations when adding menu entry .txt files?
Please see the page about .txt files
http://www.easy2boot.com/add-payload-files/change-the-menu-entry-text-using-a-txt-file/
You can use $HOME$ and $NAME$
e.g. title Boot to $NAME$ \n Boot $HOME$/$NAME$.ISO
(but not for Windows Installer ISO .txt files)
This Forum page is pretty primitive and I cannot change it because it is a fixed feature provided by the WebNode host.
All info should be available on the site pages as I always add anything that is relevant if it comes up in the Forum questions if it is not already there. So just use the Search feature and the Site Map.
http://www.easy2boot.com/add-payload-files/change-the-menu-entry-text-using-a-txt-file/
You can use $HOME$ and $NAME$
e.g. title Boot to $NAME$ \n Boot $HOME$/$NAME$.ISO
(but not for Windows Installer ISO .txt files)
This Forum page is pretty primitive and I cannot change it because it is a fixed feature provided by the WebNode host.
All info should be available on the site pages as I always add anything that is relevant if it comes up in the Forum questions if it is not already there. So just use the Search feature and the Site Map.
SteveSi
15/02/2017
CSM is NOT UEFI!
Never have I seen/heard so much verbiage that appears intent to obfuscate the fact that Easy2Boot itself cannot boot in a UEFI environment; it can only boot under a 'standard' BIOS (whether actual or emulated as CSM).
Tell me I am wrong - nothing could please me more.
Better yet, show me how to create a Easy2Boot USB drive that itself boots under 'standard' UEFI (not CSM), preferably without mention (let alone half the discussion) of any virtual machine. Even better, present an approach that does not involve any Microsoft product other than FAT32
Tell me I am wrong - nothing could please me more.
Better yet, show me how to create a Easy2Boot USB drive that itself boots under 'standard' UEFI (not CSM), preferably without mention (let alone half the discussion) of any virtual machine. Even better, present an approach that does not involve any Microsoft product other than FAT32
Gobsmacked
12/02/2017
Re: CSM is NOT UEFI!
Hi
E2B supports UEFI-booting in two ways.
1. Use .imgPtN files
2. Use the grub2 menu system (MBR or UEFI-boot)
As you correctly point out, grub4dos cannot be booted in UEFI-mode. So with .imgPTN files, you need to switch-in the partition before you can UEFI-boot. It does mean that you can secure boot from a wide variety of UEFI OS's - something that no other multiboot USB solution can do!
There are videos about .imgPTN on YouTube and there is a page about the grub2 menu system (last in side menu tab).
grub2 menu systems are not generic, each menu has to be tailored to each individual payload. This means that those solutions need to be continuously updated/maintained.
If you want to GENERIC UEFI-multiboot for a variety of different payloads and want to prepare it under linux, then look elsewhere (and let me know if you find one)!
E2B supports UEFI-booting in two ways.
1. Use .imgPtN files
2. Use the grub2 menu system (MBR or UEFI-boot)
As you correctly point out, grub4dos cannot be booted in UEFI-mode. So with .imgPTN files, you need to switch-in the partition before you can UEFI-boot. It does mean that you can secure boot from a wide variety of UEFI OS's - something that no other multiboot USB solution can do!
There are videos about .imgPTN on YouTube and there is a page about the grub2 menu system (last in side menu tab).
grub2 menu systems are not generic, each menu has to be tailored to each individual payload. This means that those solutions need to be continuously updated/maintained.
If you want to GENERIC UEFI-multiboot for a variety of different payloads and want to prepare it under linux, then look elsewhere (and let me know if you find one)!
SteveSi
12/02/2017
Windows 10 don't open Flash-Easy2Boot
If flash-drive in .imgPTN mode - all is good, but in normal mode - "No access to H. Access denied"
http://savepic.ru/12853594.png
Why?
PS. Windows 10 Enterprise 14393. Log in as administrator.
http://savepic.ru/12853594.png
Why?
PS. Windows 10 Enterprise 14393. Log in as administrator.
BlagoYar
09/02/2017
Re: Windows 10 don't open Flash-Easy2Boot
If the drive is in normal E2B mode, how did you manage to copy any ISO files to it?
You need to describe how I can reproduce this issue.
It obviously is not a problem other people have - only you!
You need to describe how I can reproduce this issue.
It obviously is not a problem other people have - only you!
SteveSi
09/02/2017
Sample_MyE2B.cfg looks many changes Vs. MyE2B.cfg
Hi Steve.
Long ago I keep my old file MyE2B.cfg.
Now I have compared this Vs. Sample_MyE2B.cfg, and I notice that there are many differences, far more than the custom changes I had applied.
So, Do you suggest updating it manually by copying from Sample_MyE2B.cfg? and to apply custom changes again?
P.S.: Below, nice another topic about "Defrag NTFS USB drive on Linux"...
We should promote E2B on GNU/Linux forums. :-)
Long ago I keep my old file MyE2B.cfg.
Now I have compared this Vs. Sample_MyE2B.cfg, and I notice that there are many differences, far more than the custom changes I had applied.
So, Do you suggest updating it manually by copying from Sample_MyE2B.cfg? and to apply custom changes again?
P.S.: Below, nice another topic about "Defrag NTFS USB drive on Linux"...
We should promote E2B on GNU/Linux forums. :-)
Bertholdoux
08/02/2017
Re: Sample_MyE2B.cfg looks many changes Vs. MyE2B.cfg
Most of the settings in the Sample_MyE2B.cfg are commented out.
You are welcome to change anything you like.
You can also find some settings in the E2B_Editor.exe GUI to help design your own menus or look at the \_ISO\docs\Templates folder for ideas.
You are welcome to change anything you like.
You can also find some settings in the E2B_Editor.exe GUI to help design your own menus or look at the \_ISO\docs\Templates folder for ideas.
SteveSi
08/02/2017
Windows Install trying to install on EZ2BOOT USB
im trying to install windows and it always says its going to install on the ez2boot USB, how do i get it to install windows on the internal drive?
Matthew
06/02/2017
Re: Windows Install trying to install on EZ2BOOT USB
You mean the internal hard disk is not listed?
What Windows are you trying to install - XP, Vista, 98, Me, 7, 8, 10, server 2016 or something else?
Are you installing from an official Microsoft ISO?
If you are using XP ISO, are you using the DPMS version of E2B (hint: you should be!)?
What Windows are you trying to install - XP, Vista, 98, Me, 7, 8, 10, server 2016 or something else?
Are you installing from an official Microsoft ISO?
If you are using XP ISO, are you using the DPMS version of E2B (hint: you should be!)?
SteveSi
06/02/2017
Re: Re: Windows Install trying to install on EZ2BOOT USB
its all windows installs, i converted an official windows iso to a imgPTN and i go boot to the EZ2BOOT and select whatever windows im wanting to install and after i select it i get "WARNING: THE E2B DRIVE PARTITION TABLE IS ABOUT TO BE OVERWRITTEN!" with a bunch of other read text and some blue about UEFI booting then it asks "OK to replace E2B partitions ([Y]/ N) :
so from my understanding it is trying to install the windows i selected onto the E2B bootable, therefore overwritting it, is this correct or is it installing to the internal hard disk?
so from my understanding it is trying to install the windows i selected onto the E2B bootable, therefore overwritting it, is this correct or is it installing to the internal hard disk?
Matthew
07/02/2017
Re: Re: Re: Windows Install trying to install on EZ2BOOT USB
No - that is not correct.
It is replacing the partition containing E2B files with a new partition which contains the files that were inside the ISO so that it can run Windows Setup.
Why don't you just answer Y and you will see!
Or watch the YouTube videos or read the .imgPTN page on this site...
It is replacing the partition containing E2B files with a new partition which contains the files that were inside the ISO so that it can run Windows Setup.
Why don't you just answer Y and you will see!
Or watch the YouTube videos or read the .imgPTN page on this site...
SteveSi
07/02/2017
E2B 1.88 Symantec Heuristic Virus
I just updated to Easy2Boot 1.88 this morning and Symantec Endpoint 14 1904 is flagging Switch_E2B.exe as a Heur.Adv.ML.B Heuristic Virus and it is being Quarantined.
Also, what is the maximum size USB drive allowed without the use of a WinHelper USB? I have been using 128Gb without issue. someone I knwo bought a 256 and it is telling him he needs a WinHelper USB.
Also, what is the maximum size USB drive allowed without the use of a WinHelper USB? I have been using 128Gb without issue. someone I knwo bought a 256 and it is telling him he needs a WinHelper USB.
Rodommoc
01/02/2017
Re: E2B 1.88 Symantec Heuristic Virus
You will have to whitelist it
The size of drive is not important , it is whether it is a Removable type or Fixed type. Some USB flash drives are fixed type. Most are removable
The size of drive is not important , it is whether it is a Removable type or Fixed type. Some USB flash drives are fixed type. Most are removable
SteveSi
01/02/2017
Re: Re: E2B 1.88 Symantec Heuristic Virus
Sorry, I should have supplied the USB drive model info: Sandisk Ultra 256 USB 3.0. I'm trying different settings in RMPrep to see if I can get it to work. So far I have Used WinPEv2..., NTFS, and unchecked the boot as HDD option.
Rodommoc
01/02/2017
Re: Re: Re: E2B 1.88 Symantec Heuristic Virus
The type cannot be changed.
RMPrepUSB will tell you what type it is.
If it is Removable type then it is OK.
E2B only WARNS if any drive is over 128GB - it does not say that it will not work - it just says that Fixed disks will not work.
E2B (grub4dos) cannot distinguish between fixed and removable property - so it just looks at size and warns user if over 128GB because it is probably a HDD.
P.S. Many BIOSes have a USb driver bug and cannot access sectors past 137GB. For this reason, I don't recommend using a Removable USB Flash drive that is over 128GiB because if you make a 2nd partition it cannot be seen by Windows and this causes issues.
RMPrepUSB will tell you what type it is.
If it is Removable type then it is OK.
E2B only WARNS if any drive is over 128GB - it does not say that it will not work - it just says that Fixed disks will not work.
E2B (grub4dos) cannot distinguish between fixed and removable property - so it just looks at size and warns user if over 128GB because it is probably a HDD.
P.S. Many BIOSes have a USb driver bug and cannot access sectors past 137GB. For this reason, I don't recommend using a Removable USB Flash drive that is over 128GiB because if you make a 2nd partition it cannot be seen by Windows and this causes issues.
SteveSi
01/02/2017
Booting Windows ISOs
I am having problems booting Windows installation ISOs via Easy2Boot. I have got it set up fine booting to Acronis, Linux ISOs and various WinPE ISOs, but when I try to install Windows things generally go like this:
A) After choosing an ISO I get a menu of options, most of which I don't understand. I just want the ISO to behave in the normal fashion, so I choose the option that I guess is going to get closest to that.
B) 9 times out of 10, it doesn't work. e.g. I just installed W7 on a PC, that worked fine, but now I am trying to install W10 on the same PC and it's stuck at "Setup is starting". I have tried 2 different options.
Any advice?
A) After choosing an ISO I get a menu of options, most of which I don't understand. I just want the ISO to behave in the normal fashion, so I choose the option that I guess is going to get closest to that.
B) 9 times out of 10, it doesn't work. e.g. I just installed W7 on a PC, that worked fine, but now I am trying to install W10 on the same PC and it's stuck at "Setup is starting". I have tried 2 different options.
Any advice?
Paul R
31/01/2017
Re: Booting Windows ISOs
Any error messages at all from E2B? What is size of USB drive? What is type of E2B drive?
Delete the ISO. Then copy the ISO again to the \_ISO\WINDOWS\WIN10 folder.
Run \MAKE_THIS_DRIVE_CONTIGUOUS.cmd
Now use a Windows utility to get the CRC\MD5\SHA1 hash value of the file on the E2B drive and compare it with the same file that you downloaded onto the system hard disk (or with official published value). This will check the file for corruption. If not same you have bad USB drive.
Otherwise, it may be a hardware issue with Win10. If it was an E2B issue, I would expect some other sort of error. For Win10 you need to choose correct Product Key for the version you are installing - but you should get an error message from Windows Setup if it was wrong.
Delete the ISO. Then copy the ISO again to the \_ISO\WINDOWS\WIN10 folder.
Run \MAKE_THIS_DRIVE_CONTIGUOUS.cmd
Now use a Windows utility to get the CRC\MD5\SHA1 hash value of the file on the E2B drive and compare it with the same file that you downloaded onto the system hard disk (or with official published value). This will check the file for corruption. If not same you have bad USB drive.
Otherwise, it may be a hardware issue with Win10. If it was an E2B issue, I would expect some other sort of error. For Win10 you need to choose correct Product Key for the version you are installing - but you should get an error message from Windows Setup if it was wrong.
SteveSi
31/01/2017
Re: Re: Booting Windows ISOs
Thanks, it was a corrupt ISO.
That left me with another problem - booting via Easy2Boot does not behave like booting from a real disc. In this case, all the Easy2Boot options I tried either asked me for a Windows 10 key (which I don't have because the Windows 10 licence on this machine came via an upgrade from Windows 7) or left me with an installation that would not activate.
Booting from a real disc (actually an SD card with the ISO installed on it) installed & activated fine without entering a product key.
Is there any way I can make Easy2Boot Windows installs behave exactly like installs from real discs?
That left me with another problem - booting via Easy2Boot does not behave like booting from a real disc. In this case, all the Easy2Boot options I tried either asked me for a Windows 10 key (which I don't have because the Windows 10 licence on this machine came via an upgrade from Windows 7) or left me with an installation that would not activate.
Booting from a real disc (actually an SD card with the ISO installed on it) installed & activated fine without entering a product key.
Is there any way I can make Easy2Boot Windows installs behave exactly like installs from real discs?
Paul R
31/01/2017
Re: Re: Re: Booting Windows ISOs
The keys that are provided in E2B are installation keys. If you are installing Win 10 Pro (retail) simply pick the Win 10 Pro installation key.
Once you have booted to Desktop, you can enter the Win7 key and it should activate.
However, if you want it to be able to accept your Win7 key during Setup, use the MPI Tool Kit to convert the ISO to a .imgPTN file.
This will then behave like the DVD.
MPI will ask you about an EI.cfg file - if you have a retail ISO, say R and you will be able to install either Core or Pro (it will ask you to pick).
With .imgPTN (FAT32) you can also boot via UEFI too if you wish. See videos for more info and MPI pages on this site.
Once you have booted to Desktop, you can enter the Win7 key and it should activate.
However, if you want it to be able to accept your Win7 key during Setup, use the MPI Tool Kit to convert the ISO to a .imgPTN file.
This will then behave like the DVD.
MPI will ask you about an EI.cfg file - if you have a retail ISO, say R and you will be able to install either Core or Pro (it will ask you to pick).
With .imgPTN (FAT32) you can also boot via UEFI too if you wish. See videos for more info and MPI pages on this site.
SteveSi
31/01/2017
Re: Re: Re: Re: Booting Windows ISOs
Sorry but the explaination arounf this "IMPORTANT EI.CFG file", is very hard to understand what the process is (when reading the docs and the forum)
I understand that different ISO will need a different key and may require this file or not.
But if you could provide a typical example like
DL the 32/64bit win10 ISO from microsoft.com buy a Product Key (5x5)
create .imgPTN file choose R for retail.
...and this is the part I do not understand...
when installing Win10 installer will not ask for your Product Key because you chose "R", You will have to activate Win10 after installation, using your Product Key???
I have tons more questions, but slowly finding answers. Complicated Subject!!! You seem to have nailed it though!
I understand that different ISO will need a different key and may require this file or not.
But if you could provide a typical example like
DL the 32/64bit win10 ISO from microsoft.com buy a Product Key (5x5)
create .imgPTN file choose R for retail.
...and this is the part I do not understand...
when installing Win10 installer will not ask for your Product Key because you chose "R", You will have to activate Win10 after installation, using your Product Key???
I have tons more questions, but slowly finding answers. Complicated Subject!!! You seem to have nailed it though!
JamieB
28/01/2019
Re: Re: Re: Re: Re: Booting Windows ISOs
Can you point to the exact piece of text that you are referring too please.
Adding\replacing the EI.cfg file allows the user to manually choose from the list of available Editions. For instance a Windows 10 Pro x64 DVD will automatically install Pro but it actually contains many more Editions (Home, Pro, etc.). If you change\add an EI.cfg file, the user is presented with the full list of all Editions it contains.
The Product Key that you set in the XML file will override the EI.cfg file so the EI.cfg file is ignored - the Product Key in the XML file will determine which Edition is installed.
If you use a Generic Installation Product key in the XML file then it will not activate because the Key is only to allow installation NOT activation. So if you use a Generic Installation Key then you must later type in a key that will activate.
Full details and Exercises are detailed in my Windows eBook.
Adding\replacing the EI.cfg file allows the user to manually choose from the list of available Editions. For instance a Windows 10 Pro x64 DVD will automatically install Pro but it actually contains many more Editions (Home, Pro, etc.). If you change\add an EI.cfg file, the user is presented with the full list of all Editions it contains.
The Product Key that you set in the XML file will override the EI.cfg file so the EI.cfg file is ignored - the Product Key in the XML file will determine which Edition is installed.
If you use a Generic Installation Product key in the XML file then it will not activate because the Key is only to allow installation NOT activation. So if you use a Generic Installation Key then you must later type in a key that will activate.
Full details and Exercises are detailed in my Windows eBook.
SteveSi
28/01/2019
Is .mnu file cached somewhere?
I have created a .mnu file for unattended Centos 7 Installation using a Kickstart file.
I have modified the "title" inside the .mnu file but in the boot menu, it is still the same.
I also tried the delete that .mnu file from my usb key and the boot menu still list it !
So is that .mnu files cached somewhere? What to do to be absolutely sure the latest .mnu files is being used?
I have modified the "title" inside the .mnu file but in the boot menu, it is still the same.
I also tried the delete that .mnu file from my usb key and the boot menu still list it !
So is that .mnu files cached somewhere? What to do to be absolutely sure the latest .mnu files is being used?
Long Vu
17/01/2017
Re: Is .mnu file cached somewhere?
The Main menu is cached if you use FASTLOAD.
If so, just press F8 in the Main Menu to refresh the cache.
If you are not using FASTLOAD, are you using a VM to test or a real system? If a VM please describe how it is configured.
Where did you place the .mnu file and what does it contain?
If so, just press F8 in the Main Menu to refresh the cache.
If you are not using FASTLOAD, are you using a VM to test or a real system? If a VM please describe how it is configured.
Where did you place the .mnu file and what does it contain?
SteveSi
17/01/2017
Re: Re: Is .mnu file cached somewhere?
I am not sure what you mean by FASTLOAD, how do I verify this?
I tried F8 anyways and it did not work (did not delete the entry from the Linux iso list).
I was testing my usb key like this "sudo qemu-system-x86_64 -machine accel=kvm:tcg -m 512 -hda /dev/sdc"
Here is the content of my .mnu file (that has been deleted from my usb key but keeps showing on the Linux menu)
=========================
[[email protected]:6 16:04:02 Iso]$ cat CentOS7_AutoInstall.mnu
# CDLABEL must match ISO volume label (usually file name)
# NTFS is not supported! use FAT32 or ext2/3/4
# ISO must not have spaces in path or name
title Auto Install CentOS 7 from Kickstart\n Auto Install CentOS 7 from Kickstart
#ISO is full path to ISO (no spaces)
set ISO=$HOME$/CentOS-7-x86_64-Minimal-1611.iso
#LBL=CD VOLUME LABEL OF THE ISO use \\x20 instead of a space
set LBL=CentOS\\x207\\x20x86_64
map %ISO% (0xff) || echo -e $[0147]%ISO% IS NOT CONTIGUOUS! && map --mem %ISO% (0xff)
map --hook
root (0xff)
echo
echo -e $[1174]WARNING: THIS WILL NOT WORK ON NTFS DRIVES (use FAT32 or ext2/3/4).
echo
kernel /isolinux/vmlinuz root=live:CDLABEL=%LBL% iso-scan/filename='%ISO%' rd.live.image vga=791 inst.ks=nfs:it-deploy2.intelerad.com:/srv/exports/ks/wkstn_centos7-dev-ah.ks
initrd /isolinux/initrd.img
boot
==============================
The file was put under _ISO/Linux folder on the usb key, next to the CentOS-7-x86_64-Minimal-1611.iso it was refering to. Is that location allowed for .mnu file?
I tried F8 anyways and it did not work (did not delete the entry from the Linux iso list).
I was testing my usb key like this "sudo qemu-system-x86_64 -machine accel=kvm:tcg -m 512 -hda /dev/sdc"
Here is the content of my .mnu file (that has been deleted from my usb key but keeps showing on the Linux menu)
=========================
[[email protected]:6 16:04:02 Iso]$ cat CentOS7_AutoInstall.mnu
# CDLABEL must match ISO volume label (usually file name)
# NTFS is not supported! use FAT32 or ext2/3/4
# ISO must not have spaces in path or name
title Auto Install CentOS 7 from Kickstart\n Auto Install CentOS 7 from Kickstart
#ISO is full path to ISO (no spaces)
set ISO=$HOME$/CentOS-7-x86_64-Minimal-1611.iso
#LBL=CD VOLUME LABEL OF THE ISO use \\x20 instead of a space
set LBL=CentOS\\x207\\x20x86_64
map %ISO% (0xff) || echo -e $[0147]%ISO% IS NOT CONTIGUOUS! && map --mem %ISO% (0xff)
map --hook
root (0xff)
echo
echo -e $[1174]WARNING: THIS WILL NOT WORK ON NTFS DRIVES (use FAT32 or ext2/3/4).
echo
kernel /isolinux/vmlinuz root=live:CDLABEL=%LBL% iso-scan/filename='%ISO%' rd.live.image vga=791 inst.ks=nfs:it-deploy2.intelerad.com:/srv/exports/ks/wkstn_centos7-dev-ah.ks
initrd /isolinux/initrd.img
boot
==============================
The file was put under _ISO/Linux folder on the usb key, next to the CentOS-7-x86_64-Minimal-1611.iso it was refering to. Is that location allowed for .mnu file?
Long Vu
17/01/2017
Re: Re: Re: Is .mnu file cached somewhere?
FASTLOAD is not the problem if you have not enabled it and it only caches the MAIN Menu, not the Linux menu.
If you place the .mnu in \_ISO\LINUX and the CentOS ISo file in \_ISO\LINUX, you will see two menu entries - one for the ISO and one for the .mnu file.
Try booting on a real system?
If you place the .mnu in \_ISO\LINUX and the CentOS ISo file in \_ISO\LINUX, you will see two menu entries - one for the ISO and one for the .mnu file.
Try booting on a real system?
SteveSi
17/01/2017
Re: Re: Re: Re: Is .mnu file cached somewhere?
I actually want 2 menus. One to boot the .iso as-is and one that does full unattended install.
Have not tried on a real physical system yet. Need a real machine that I can zap the real harddrive under unattended mode.
Is there another way to test this "virtually"?
Have not tried on a real physical system yet. Need a real machine that I can zap the real harddrive under unattended mode.
Is there another way to test this "virtually"?
Long Vu
17/01/2017
Re: Re: Re: Re: Re: Is .mnu file cached somewhere?
The problem is that you cannot see the .mnu entry in the LINUX menu or that you can see it when it should not be there?
So boot on a real system to E2B, go to LINUX menu - What is in the menu?
You do not need to run anything.
Or run QEMU_MENU_TEST.cmd under Windows?
So boot on a real system to E2B, go to LINUX menu - What is in the menu?
You do not need to run anything.
Or run QEMU_MENU_TEST.cmd under Windows?
SteveSi
17/01/2017
Re: Re: Re: Re: Re: Re: Is .mnu file cached somewhere?
I see it when it should not be there (I deleted the .mnu file).
I'll wait until I can get a real physical system to test again.
Will report my results.
I'll wait until I can get a real physical system to test again.
Will report my results.
Long Vu
17/01/2017
Re: Re: Re: Re: Re: Re: Re: Is .mnu file cached somewhere?
OK. QEMU may be in snapshot mode or something...
You can also go to grub4dos console
SHIFT+P easy2boot
SHIFT+C
ls /_ISO/LINUX/
can you see .mnu file?
P.S. You are quitting QEMU before you edit the drive contents and then re-running QEMU?
You can also go to grub4dos console
SHIFT+P easy2boot
SHIFT+C
ls /_ISO/LINUX/
can you see .mnu file?
P.S. You are quitting QEMU before you edit the drive contents and then re-running QEMU?
SteveSi
17/01/2017
Re: Is .mnu file cached somewhere?
Tried on a real physical system, the menu behave as expected (it is there when the .mnu file is there and not there when the file is not there).
Retried in qemu, also good.
I think, in addition to shutdown qemu, I have to also disconnect the usb drive and reconnect again.
So I think this is due to some kind of filesystem caching and not easy2boot caching.
Sorry for the false alarm.
Retried in qemu, also good.
I think, in addition to shutdown qemu, I have to also disconnect the usb drive and reconnect again.
So I think this is due to some kind of filesystem caching and not easy2boot caching.
Sorry for the false alarm.
Long Vu
18/01/2017
Re: Re: Is .mnu file cached somewhere?
OK.
If you have an NTFS E2B drive, you could try using the partnew technique. You can adapt one of the other sample .mnu files (e.g. ubuntu) to see how it is done. Then the iso-scan/filename= is then not needed and i should work on NTFS or even exFAT.
If you have an NTFS E2B drive, you could try using the partnew technique. You can adapt one of the other sample .mnu files (e.g. ubuntu) to see how it is done. Then the iso-scan/filename= is then not needed and i should work on NTFS or even exFAT.
SteveSi
18/01/2017
bootmgr missing
bootmgr missing, using XP. I downloaded bootmgr from Microsoft.
TroubleShooting Instructions say to copy it to folder "\_ISO\e2b\grub\DPMS\NTBOOT.MOD" on the E2B drive.
But no such folder. The DPMS folder is there but pasting bootmgr to it don't work.
Any ideas?
Thanks
TroubleShooting Instructions say to copy it to folder "\_ISO\e2b\grub\DPMS\NTBOOT.MOD" on the E2B drive.
But no such folder. The DPMS folder is there but pasting bootmgr to it don't work.
Any ideas?
Thanks
EdP
04/01/2017
Re: bootmgr missing
Hi Ed
if you look at the E2B download zip file, you will see that it does contain that NTBOOT.MOD folder. If your E2B drive does not, then please update it.
if you look at the E2B download zip file, you will see that it does contain that NTBOOT.MOD folder. If your E2B drive does not, then please update it.
SteveSi
04/01/2017
Re: Re: bootmgr missing
So I copied the NTBOOT.MOD folder to the DPMS folder on the E2B drive with a WIN7 bootmgr file in it.
Getting the same bootmgr missing message.
Getting the same bootmgr missing message.
Ed
04/01/2017
Re: Re: Re: bootmgr missing
I said you need to UPDATE your E2B drive.
Download the latest version.
Unzip it into a new empty folder.
Run Update_E2B_DRIVE.cmd.
Also, you will need a Win8.1 version of bootmgr - not all versions are compatible - e2b will warn you if it is the wrong version.
Download the latest version.
Unzip it into a new empty folder.
Run Update_E2B_DRIVE.cmd.
Also, you will need a Win8.1 version of bootmgr - not all versions are compatible - e2b will warn you if it is the wrong version.
SteveSi
04/01/2017
Re: Re: Re: Re: bootmgr missing
P.S. What EXACTLY are you trying to boot?
SteveSi
04/01/2017
Re: Re: Re: Re: Re: bootmgr missing
@Ed - is it working now?
SteveSi
13/01/2017
onlymainmenu and unattended files
when **.iso.auto files in present windows iso folder it give "if exist %folder/%iso%.auto call %folder%/%iso%.auto"
error 13
Am I doing something wrong or missing ? maybe add something mye2b.cfg?
error 13
Am I doing something wrong or missing ? maybe add something mye2b.cfg?
dnecro
25/12/2016
Re: onlymainmenu and unattended files
.auto is not a valid file extension (for a normal payload file). ??
Stevesi
26/12/2016
Re: Re: onlymainmenu and unattended files
wait what? How not valid? unattended install guide and example files in folders already have these files. Then which extension I should use?
dnecro
26/12/2016
Re: Re: Re: onlymainmenu and unattended files
So you are following instructions on
http://www.easy2boot.com/add-payload-files/windows-install-isos/unattended-installs/
If so, you need to give all details. Exact paths and filenames you are using, contents of files, etc. What .mnu file you are using, etc.
http://www.easy2boot.com/add-payload-files/windows-install-isos/unattended-installs/
If so, you need to give all details. Exact paths and filenames you are using, contents of files, etc. What .mnu file you are using, etc.
SteveSi
26/12/2016
Re: Re: Re: Re: onlymainmenu and unattended files
P.S. Is the first line of your xxxxx.iso.auto file
!BAT
???
!BAT
???
SteveSi
26/12/2016
make drive contiguous
When an iso isn't contiguous, I get an error and a prompt to hit "ctrl+f2" to make drive contiguous, but when I press this key combination it doesn't do anything. Is it possible to use this function from usb stick?
dancaer69
17/12/2016
Re: make drive contiguous
It says Press Ctrl+F2 in **RMPrepUSB**.
or you can run USB drive \MAKE_THIS_DRIVE_CONTIGUOUS.cmd.
or you can run USB drive \MAKE_THIS_DRIVE_CONTIGUOUS.cmd.
SteveSi
17/12/2016
Re: Re: make drive contiguous
Thanks for the fast responce.
Yes this is the message, but I still don't understand. Can I make the drive contiguous from stick(without the need to reboot to windows/linux), and if yes which is exactly the procedure? It's not clear to me.
Yes this is the message, but I still don't understand. Can I make the drive contiguous from stick(without the need to reboot to windows/linux), and if yes which is exactly the procedure? It's not clear to me.
dancaer69
17/12/2016
Re: Re: Re: make drive contiguous
MAKE_THIS_DRIVE_CONTIGUOS.cmd and RMPrepUSB.exe are Windows programs - so they must be run under Windows.
If you are a linux user, see http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-using-linux/
If you are a linux user, see http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-using-linux/
SteveSi
17/12/2016
Re: Re: Re: Re: make drive contiguous
Yes, I've used both windows/linux. I just thought that you can do it from usb stick too and "ctrl-f2" was the combination to run the command.
Thanks.
Thanks.
dancaer69
17/12/2016
Re: Re: Re: Re: Re: make drive contiguous
If I could do it from grub4dos then I would not need to ask the user to do it!
SteveSi
06/05/2017
contiguous drive
if I create a new E2B drive, add ISOs, make contiguous, will I have to make contiguous again if I add non-E2B files to the drive after? non-E2B files would just be random stuff like videos, music, etc - essentially things not related to E2B AFTER the drive was made contiguous.
dimm0k
14/12/2016
Re: contiguous drive
No, the FILES are made contiguous by WinContig, not the drive. E2B needs contiguous payload files.
SteveSi
14/12/2016
w32.trojan.gen
Hi,
Webroot antivirus reports this program as a trojan. Is the downloaded files infected, or is it the program? (the function to override windows installation-files and default settings)
Webroot antivirus reports this program as a trojan. Is the downloaded files infected, or is it the program? (the function to override windows installation-files and default settings)
Gigante
12/12/2016
Re: w32.trojan.gen
What program> Which download?
Use the web based VirusTotal to check it with all virus scanners. https://www.virustotal.com/
E2B is used 1000's of times a day and is downloaded 100's of times a day. If it had a virus, I think it we would know about it!
Use the web based VirusTotal to check it with all virus scanners. https://www.virustotal.com/
E2B is used 1000's of times a day and is downloaded 100's of times a day. If it had a virus, I think it we would know about it!
SteveSi
12/12/2016
Re: Re: w32.trojan.gen
This file: %Documents% EASY2BOOT V1.86DPMS_MAKE_E2B_USB_DRIVE.EXE
I cannot find the file (maby temorary while installing? or removed by webroot?) It seems to warn when I make bootdisks with the cmd-file.
I have sent the question to Webroots support to see what exactly it warn for.
I cannot find the file (maby temorary while installing? or removed by webroot?) It seems to warn when I make bootdisks with the cmd-file.
I have sent the question to Webroots support to see what exactly it warn for.
Gigante
14/12/2016
Re: Re: Re: w32.trojan.gen
Got reply from Webroot that it was false alarm. :) (Y)
Gigante
14/12/2016
E2B and reports
Hi.
I have sort of hdd testing software in iso format.
thise software doesn't work for me becouse need to write reports after finish work.
Is there any way to use e2b with thise tool ?
Regards Filip
I have sort of hdd testing software in iso format.
thise software doesn't work for me becouse need to write reports after finish work.
Is there any way to use e2b with thise tool ?
Regards Filip
Filil J
09/12/2016
Re: E2B and reports
Are you using a Removable USB drive or Fixed Disk drive for E2B?
Did you try converting to .imgPTN file, then you may have better access?
If you tell me what s/w is or can send me a copy, I can help.
Did you try converting to .imgPTN file, then you may have better access?
If you tell me what s/w is or can send me a copy, I can help.
SteveSi
09/12/2016
Up to date OpenELEC/LibreELEC Live
Hi.
I'd like to be running OpenELEC or LibreELEC live from E2B. Not interested in the installation, just the live functionality.
I've seen a couple of articles from 2013/2014 here at E2B.com. Are they still up to date?
Could you please make an update on those articles?
Thanks in advance.
Cheers
I'd like to be running OpenELEC or LibreELEC live from E2B. Not interested in the installation, just the live functionality.
I've seen a couple of articles from 2013/2014 here at E2B.com. Are they still up to date?
Could you please make an update on those articles?
Thanks in advance.
Cheers
john3voltas
24/11/2016
Re: Up to date OpenELEC/LibreELEC Live
Yes, the 2014 instructions still work for the latest version 6.0.3
SteveSi
24/11/2016
Re: Re: Up to date OpenELEC/LibreELEC Live
Thanks, SteveSi.
john3voltas
24/11/2016
Usb drive does not boot anymore
I just bought a brand new Kingston SE9 G2 USB 3.0 64GB.
Formatted it with Easy2Boot.
It booted a first time.
I added more isos, it stopped booting. But I can still read and write to it as a data drive.
I format it again. Still do not boot.
Thinking it's my computer BIOS that is messed up, I tried an older usb drive that also has Easy2Boot and that worked.
Any pointers how to debug this weird problem?
Formatted it with Easy2Boot.
It booted a first time.
I added more isos, it stopped booting. But I can still read and write to it as a data drive.
I format it again. Still do not boot.
Thinking it's my computer BIOS that is messed up, I tried an older usb drive that also has Easy2Boot and that worked.
Any pointers how to debug this weird problem?
Long Vu
16/11/2016
Re: Usb drive does not boot anymore
See Troubleshooting page
http://www.easy2boot.com/faq-/troubleshooting-e2b/
http://www.easy2boot.com/faq-/troubleshooting-e2b/
SteveSi
16/11/2016
Re: Re: Usb drive does not boot anymore
Here's some surprising findings:
The problematic Kingston SE9 G2 USB 3.0 64G key works for:
- qemu
- my work machine Dell Precision T3610, all usb ports
- my older laptop Dell Vostro 3350, all usb ports
- my current laptop (where the problem originally occured) Dell Latitude E6230, only on the USB 2.0 port (USB 3.0 port do not boot). On the USB 2.0 port, it displays "Invalid Partition table!", then I press enter and it continue to boot the usb key.
Note that as previously stated, the USB 3.0 port did work once, then stopped working. Also that same USB 3.0 port was able to boot a smaller and supposely cheaper quality Kingston DataTraveler 101 G3 16 G.
I also destroyed the partition table on the 64G key, recreate from scratch, then format again, same result. This is using latest Easy2Boot_v1.86DPMS.zip, the fmt.sh script (Fat32).
I verified by Latitude e6230 is using Legacy BIOS and not UEFI. My ssd boot drive is using MBR partition anyways so it can not be using UEFI.
I am really stumped. Any other pointers as to why this weird problem happens?
I bought a bigger usb key so I can put my entire collection of Iso on it. I hope it is not the size of the key that is the problem because that will make me really sad.
The problematic Kingston SE9 G2 USB 3.0 64G key works for:
- qemu
- my work machine Dell Precision T3610, all usb ports
- my older laptop Dell Vostro 3350, all usb ports
- my current laptop (where the problem originally occured) Dell Latitude E6230, only on the USB 2.0 port (USB 3.0 port do not boot). On the USB 2.0 port, it displays "Invalid Partition table!", then I press enter and it continue to boot the usb key.
Note that as previously stated, the USB 3.0 port did work once, then stopped working. Also that same USB 3.0 port was able to boot a smaller and supposely cheaper quality Kingston DataTraveler 101 G3 16 G.
I also destroyed the partition table on the 64G key, recreate from scratch, then format again, same result. This is using latest Easy2Boot_v1.86DPMS.zip, the fmt.sh script (Fat32).
I verified by Latitude e6230 is using Legacy BIOS and not UEFI. My ssd boot drive is using MBR partition anyways so it can not be using UEFI.
I am really stumped. Any other pointers as to why this weird problem happens?
I bought a bigger usb key so I can put my entire collection of Iso on it. I hope it is not the size of the key that is the problem because that will make me really sad.
Long Vu
17/11/2016
Re: Re: Re: Usb drive does not boot anymore
The fmt.sh script does not add a small second partition. As explained on the website, when you use RMPrepUSB or the MAKE_E2B_USB_Drive.cmd Windows script, it makes a second small hidden partition on the USB drive. This is because some systems will try to boot a USB drive as a floppy disk if they only have one partition.
Can you add a small second PRIMARY partition to the USB drive or use the Windows script to make it?
Can you add a small second PRIMARY partition to the USB drive or use the Windows script to make it?
SteveSi
17/11/2016
Re: Re: Re: Re: Usb drive does not boot anymore
Added a 2nd primary partition, still the same weird behavior.
sudo fdisk -l /dev/sdb
[sudo] password for lvu:
Disk /dev/sdb: 57.8 GiB, 62087233536 bytes, 121264128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xefda3cf9
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 119566335 119564288 57G b W95 FAT32
/dev/sdb2 119566336 121264127 1697792 829M b W95 FAT32
sudo fdisk -l /dev/sdb
[sudo] password for lvu:
Disk /dev/sdb: 57.8 GiB, 62087233536 bytes, 121264128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xefda3cf9
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 119566335 119564288 57G b W95 FAT32
/dev/sdb2 119566336 121264127 1697792 829M b W95 FAT32
Long Vu
19/11/2016
Re: Re: Re: Re: Re: Usb drive does not boot anymore
Did you switch off the system and switch on again?
Did you check the BIOS settings. e.g. USB Settings?
Does it say USB HDD in the BIOS boot menu?
Is the first partition marked as Active (boot flag)?
Did you install grub4dos to both PBR and MBR?
Latest BIOS version is A16 25th Oct 2016 with improved USB support. Do you have this?
Did you check the BIOS settings. e.g. USB Settings?
Does it say USB HDD in the BIOS boot menu?
Is the first partition marked as Active (boot flag)?
Did you install grub4dos to both PBR and MBR?
Latest BIOS version is A16 25th Oct 2016 with improved USB support. Do you have this?
SteveSi
19/11/2016
Re: Re: Re: Re: Re: Re: Usb drive does not boot anymore
Did you switch off the system and switch on again?
Yes
Did you check the BIOS settings. e.g. USB Settings?
Yes, boot order is USB first.
Does it say USB HDD in the BIOS boot menu?
This is the interesting part, it doesn't say when the usb key is plugged into the usb 3.0 port. Looks like BIOS do not detect/see a usb hdd on usb 3.0 port ... but only for my new 64G usb key. The older 16G usb key was booting fine from that same usb 3.0 port.
Is the first partition marked as Active (boot flag)?
No.
Did you install grub4dos to both PBR and MBR?
I don't know, I just run the fmt.sh script.
Latest BIOS version is A16 25th Oct 2016 with improved USB support. Do you have this?
I only have A15.
I also tried to format the usb key using Windows instead of linux. This is the latest fdisk output after Windows format:
sudo fdisk -l /dev/sdb
[sudo] password for lvu:
Disk /dev/sdb: 57.8 GiB, 62087233536 bytes, 121264128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xfc5ed0c2
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 63 121242491 121242429 57.8G c W95 FAT32 (LBA)
/dev/sdb2 121242492 121242554 63 31.5K 21 unknown
Still the same behavior (usb 3.0 port do not boot) with formatting using Windows. However at least usb 2.0 port stop staying "invalid partition table!".
I guess a new BIOS might be the fix. At least now the usb 2.0 port boots properly so I have a fall back. I'll reply my findings if I feel brave enough to update the BIOS. I got burned once in the past updating BIOS.
Thanks for all the help. Looks like formatting on Windows does a more complete job than Linux. Is it because Linux is lacking any functionality or you just didn't get around to have feature parity between Windows and Linux?
I am still puzzled as to why my older 16G usb drive was working fine on that same usb 3.0 port although it was formatted on Linux.
Yes
Did you check the BIOS settings. e.g. USB Settings?
Yes, boot order is USB first.
Does it say USB HDD in the BIOS boot menu?
This is the interesting part, it doesn't say when the usb key is plugged into the usb 3.0 port. Looks like BIOS do not detect/see a usb hdd on usb 3.0 port ... but only for my new 64G usb key. The older 16G usb key was booting fine from that same usb 3.0 port.
Is the first partition marked as Active (boot flag)?
No.
Did you install grub4dos to both PBR and MBR?
I don't know, I just run the fmt.sh script.
Latest BIOS version is A16 25th Oct 2016 with improved USB support. Do you have this?
I only have A15.
I also tried to format the usb key using Windows instead of linux. This is the latest fdisk output after Windows format:
sudo fdisk -l /dev/sdb
[sudo] password for lvu:
Disk /dev/sdb: 57.8 GiB, 62087233536 bytes, 121264128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xfc5ed0c2
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 63 121242491 121242429 57.8G c W95 FAT32 (LBA)
/dev/sdb2 121242492 121242554 63 31.5K 21 unknown
Still the same behavior (usb 3.0 port do not boot) with formatting using Windows. However at least usb 2.0 port stop staying "invalid partition table!".
I guess a new BIOS might be the fix. At least now the usb 2.0 port boots properly so I have a fall back. I'll reply my findings if I feel brave enough to update the BIOS. I got burned once in the past updating BIOS.
Thanks for all the help. Looks like formatting on Windows does a more complete job than Linux. Is it because Linux is lacking any functionality or you just didn't get around to have feature parity between Windows and Linux?
I am still puzzled as to why my older 16G usb drive was working fine on that same usb 3.0 port although it was formatted on Linux.
Long Vu
19/11/2016
Re: Re: Re: Re: Re: Re: Re: Usb drive does not boot anymore
The * in
/dev/sdb1 * 63 121242491 121242429 57.8G c W95 FAT32 (LBA)
I think means that the partition is active. So one difference is that the first partition was not active until you used Windows to prepare the USB stick.
The fmt.sh script only formats an existing partition it does not create partitions.
Did you enable both options in the BIOS under System Setup - USB Configuration - Enable Boot Support and Enable External USB Port?
/dev/sdb1 * 63 121242491 121242429 57.8G c W95 FAT32 (LBA)
I think means that the partition is active. So one difference is that the first partition was not active until you used Windows to prepare the USB stick.
The fmt.sh script only formats an existing partition it does not create partitions.
Did you enable both options in the BIOS under System Setup - USB Configuration - Enable Boot Support and Enable External USB Port?
SteveSi
20/11/2016
Re: Re: Re: Re: Re: Re: Re: Re: Usb drive does not boot anymore
P.S. I have improved the linux fmt.sh script in E2B v1.87b so that it makes the partition active and installs grub4dos to the PBR.
The only thing it does not do is make a 2nd small partition on the USB drive. You should do this yourself or it may not boot on some systems.
The only thing it does not do is make a 2nd small partition on the USB drive. You should do this yourself or it may not boot on some systems.
SteveSi
20/11/2016
E2B Multi-Boot
Dear Stevesi,
first of all thank you for the software package development and that for free!
I've been trying to make a Multiboot USB Stick/HDD usable for both UEFI and Legacy Mode Bioses and I've already read several tutorials on E2B website and have also seen several videos from other resources. But still haven't been able to make such a drive, which would work on both kind of Bios types (MBR/UEFI). The best results have been either working on some MBRs OR on some UEFIs, not both at the same time.
Therefor my first question is that, if you could recommend one main method/tutorial to focus on; because as I mentioned there are several Versions suggesting different methods, like using RMPrepUSB (and that with variety of options like choosing between ntfs or fat32, Boot as HDD as checked or not etc.) or using the scripts like MAKE_E2B_USB_DRIVE .cmd
My other question is that, if you by any chance know some tool to convert usb "fixed" drives into "removable" disks? Most of my USB drives are detected as "fixed" drives. I assume that, first of all they have to be "removable" drives for being able to make them bootable using E2B.
first of all thank you for the software package development and that for free!
I've been trying to make a Multiboot USB Stick/HDD usable for both UEFI and Legacy Mode Bioses and I've already read several tutorials on E2B website and have also seen several videos from other resources. But still haven't been able to make such a drive, which would work on both kind of Bios types (MBR/UEFI). The best results have been either working on some MBRs OR on some UEFIs, not both at the same time.
Therefor my first question is that, if you could recommend one main method/tutorial to focus on; because as I mentioned there are several Versions suggesting different methods, like using RMPrepUSB (and that with variety of options like choosing between ntfs or fat32, Boot as HDD as checked or not etc.) or using the scripts like MAKE_E2B_USB_DRIVE .cmd
My other question is that, if you by any chance know some tool to convert usb "fixed" drives into "removable" disks? Most of my USB drives are detected as "fixed" drives. I assume that, first of all they have to be "removable" drives for being able to make them bootable using E2B.
Farid
07/11/2016
Re: E2B Multi-Boot
E2B will work on Removable drives or Fixed Disk type.
The website explains the difference.
Not all payloads (ISOs) support UEFI booting.
Look at the 'List of tested payloads' page to see the best way to add each payload file.
The website explains the difference.
Not all payloads (ISOs) support UEFI booting.
Look at the 'List of tested payloads' page to see the best way to add each payload file.
SteveSi
07/11/2016
Find Only in hd0
Dear Stevesi
iftitle [find /ntldr] OS * Windows XP Loader..
how to set find only search in hd0.. If not found ntldr in hd0 then message not found ntld in hd0.
How to make menu like that's..??
iftitle [find /ntldr] OS * Windows XP Loader..
how to set find only search in hd0.. If not found ntldr in hd0 then message not found ntld in hd0.
How to make menu like that's..??
SalimS
05/11/2016
Re: Find Only in hd0
That is tricky!
When you boot from USB, hd0 will be the USB drive.
hd1 will be the first internal hard disk.
So if you want to boot from the internal disk try
iftitle [ls (hd1,0)/ntlrd] Boot from NTLDR
or maybe
iftitle [ls (hd1,0)/ntldr || ls (hd1,1)/ntldr] Boot from NTLDR
When you boot from USB, hd0 will be the USB drive.
hd1 will be the first internal hard disk.
So if you want to boot from the internal disk try
iftitle [ls (hd1,0)/ntlrd] Boot from NTLDR
or maybe
iftitle [ls (hd1,0)/ntldr || ls (hd1,1)/ntldr] Boot from NTLDR
SteveSi
05/11/2016
Re: Re: Find Only in hd0
For interest
# Ignore boot device and boot to Windows XP, Vista, 7 or 8 from the internal hard disk
# This works by mapping the boot device (bd) which may have bootmgr or ntldr on it, to a virtual memory drive so that files on it are not found by the find command
title Boot to Windows from an internal hard disk
map --mem (md)+8 (bd)
map --hook
find --set-root --ignore-floppies --ignore-cd /bootmgr || find --set-root --ignore-floppies --ignore-cd /ntldr
map (bd) (bd)
map --rehook
chainloader /bootmgr || chainloader /ntldr
# Ignore boot device and boot to Windows XP, Vista, 7 or 8 from the internal hard disk
# This works by mapping the boot device (bd) which may have bootmgr or ntldr on it, to a virtual memory drive so that files on it are not found by the find command
title Boot to Windows from an internal hard disk
map --mem (md)+8 (bd)
map --hook
find --set-root --ignore-floppies --ignore-cd /bootmgr || find --set-root --ignore-floppies --ignore-cd /ntldr
map (bd) (bd)
map --rehook
chainloader /bootmgr || chainloader /ntldr
SteveSi
08/12/2016
Unable to defrag NTFS USB drive on Linux
Hi,
I got this error on Ubuntu 16.04:
[[email protected]:12 12:47:29 linux_utils]$ sudo ./udefrag -om /dev/sdc1
[sudo] password for lvu:
sudo: unable to execute ./udefrag: No such file or directory
[[email protected]:12 12:53:38 linux_utils]$
USB drive was created using Easy2Boot_v1.86DPMS.zip.
I used 'sudo bash ./fmt_ntfs.sh' to create the drive initially.
Then I copy over some .iso.
I got this error on Ubuntu 16.04:
[[email protected]:12 12:47:29 linux_utils]$ sudo ./udefrag -om /dev/sdc1
[sudo] password for lvu:
sudo: unable to execute ./udefrag: No such file or directory
[[email protected]:12 12:53:38 linux_utils]$
USB drive was created using Easy2Boot_v1.86DPMS.zip.
I used 'sudo bash ./fmt_ntfs.sh' to create the drive initially.
Then I copy over some .iso.
Long Vu
05/11/2016
Re: Unable to defrag NTFS USB drive on Linux
Does the file exist?
Did you use chmod on it?
Did you use chmod on it?
SteveSi
05/11/2016
Re: Re: Unable to defrag NTFS USB drive on Linux
The udefrag binary is a 32-bit program.
If you have Ubuntu 64-bit, you may need to add 32-bit support. See the linux page on this site.
If you have Ubuntu 64-bit, you may need to add 32-bit support. See the linux page on this site.
SteveSi
05/11/2016
Re: Re: Re: Unable to defrag NTFS USB drive on Linux
udefrag came from the tools.zip file at
http://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g.html#download
If anyone would like to supply me with a 64-bit version of udefrag (find it or compile it), I will include it in E2B.
http://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g.html#download
If anyone would like to supply me with a 64-bit version of udefrag (find it or compile it), I will include it in E2B.
SteveSi
05/11/2016
Re: Re: Re: Re: Unable to defrag NTFS USB drive on Linux
Yes udefrag file exist. Yes I chmod a+x it.
I will try to add additional 32-bits libraries to my 64-bits machine to see if I can run udefrag.
Thanks.
I will try to add additional 32-bits libraries to my 64-bits machine to see if I can run udefrag.
Thanks.
Long Vu
06/11/2016
Re: Re: Re: Re: Re: Unable to defrag NTFS USB drive on Linux
Confirmed able to defrag NTFS on Ubuntu 16.04 by following intructions on Linux page:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
(change to _ISO/docs/linux_utils folder)
sudo chmod 777 *
sudo udefrag -om /dev/sdX1 (where sdX1 is your NTFS USB partition)
Thanks.
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
(change to _ISO/docs/linux_utils folder)
sudo chmod 777 *
sudo udefrag -om /dev/sdX1 (where sdX1 is your NTFS USB partition)
Thanks.
Long Vu
13/11/2016
Administrative rights for RestoreE2B script
Hi!
I just wanted to thank you for the hugely useful software package development and also for providing that for free. I haven't been able to give much back to you. I noticed that I might be able to contribute with some code though. The thing is that its quite annoying to start the RestoreE2B script with administrative rights. Usually on broken computer the right click menu might take ages to pop up in Windows Explorer. Here is how I make batch scripts ask administrative rights, use it however you like:
In the beginning I usually add:
set "_FilePath=%~f0"
set "_FileDir=%~dp0"
setlocal EnableExtensions EnableDelayedExpansion
And then in the appropriate location the admin rights prompt trigger:
fltmc >nul 2>&1 || (
echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\GetAdmin.vbs"
echo UAC.ShellExecute "!_FilePath!", "", "", "runas", 1 >> "%temp%\GetAdmin.vbs"
"%temp%\GetAdmin.vbs"
del /f /q "%temp%\GetAdmin.vbs" >nul 2>&1
exit
)
I hope that helps. I feel that I cannot thank you enough for your kindness. So thank you again.
Kind regards,
Codeplayer
I just wanted to thank you for the hugely useful software package development and also for providing that for free. I haven't been able to give much back to you. I noticed that I might be able to contribute with some code though. The thing is that its quite annoying to start the RestoreE2B script with administrative rights. Usually on broken computer the right click menu might take ages to pop up in Windows Explorer. Here is how I make batch scripts ask administrative rights, use it however you like:
In the beginning I usually add:
set "_FilePath=%~f0"
set "_FileDir=%~dp0"
setlocal EnableExtensions EnableDelayedExpansion
And then in the appropriate location the admin rights prompt trigger:
fltmc >nul 2>&1 || (
echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\GetAdmin.vbs"
echo UAC.ShellExecute "!_FilePath!", "", "", "runas", 1 >> "%temp%\GetAdmin.vbs"
"%temp%\GetAdmin.vbs"
del /f /q "%temp%\GetAdmin.vbs" >nul 2>&1
exit
)
I hope that helps. I feel that I cannot thank you enough for your kindness. So thank you again.
Kind regards,
Codeplayer
Codeplayer
04/11/2016
Re: Administrative rights for RestoreE2B script
Thanks for the code. I haven't seen that before.
The thing is that RestoreE2B needs to work in a minimal WinPE environment and not rely on fltmc or vb script runtime components.
Why not use SWITCH_E2B.exe instead?
The thing is that RestoreE2B needs to work in a minimal WinPE environment and not rely on fltmc or vb script runtime components.
Why not use SWITCH_E2B.exe instead?
SteveSi
04/11/2016
Boot from a USB HDD with two partitions
I have a 1Tb USB3 External HDD
Two primary partitions, the second one has data, the first one is empty.
I would like to install EASY2BOOT in the first one.
When I launch the installer, it says "WARNING: ALL PARTITIONS ON DRIVE 1 WILL BE DESTROYED..."
I don't want to destroy the second partition.
What can I do?
Thanks.
Two primary partitions, the second one has data, the first one is empty.
I would like to install EASY2BOOT in the first one.
When I launch the installer, it says "WARNING: ALL PARTITIONS ON DRIVE 1 WILL BE DESTROYED..."
I don't want to destroy the second partition.
What can I do?
Thanks.
John
26/10/2016
Re: Boot from a USB HDD with two partitions
The cmd script is only for making a new drive.
See http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-and-e2b-usb-drive-using-rmprepusb/
Use RMPrepUSB to add the grub4dos boot code using 'Install grub4dos' button and just copy E2B files to the first partition.
See http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-and-e2b-usb-drive-using-rmprepusb/
Use RMPrepUSB to add the grub4dos boot code using 'Install grub4dos' button and just copy E2B files to the first partition.
SteveSi
26/10/2016
Re: Re: Boot from a USB HDD with two partitions
Thanks SteveSi for the fast answer
John
26/10/2016
Unable to launch the setup application
Hello, Sir,
I found a problem while trying to install Windows 7 and 8. Both of them are AIO x84/x64 activated ISO files . When i pick which system type to install, i see Windows logo and then a blue screen with an error: "Unable to launch the setup application". I tried all of the methods to somehow fix it, (renaming iso to isope, rewriting the program, editing autounattend.xml) except converting iso to imgptn. I also tried to find something about this problem on e2b forums and pretty much on the whole e2b site, but unfortunately, it's not even listed in the list of errors. For example, Windows 10 works fine, without any problems at all. I really like this program and i don't really want to change it if it has such malfunctions.
Thank you in advance for the help.
I found a problem while trying to install Windows 7 and 8. Both of them are AIO x84/x64 activated ISO files . When i pick which system type to install, i see Windows logo and then a blue screen with an error: "Unable to launch the setup application". I tried all of the methods to somehow fix it, (renaming iso to isope, rewriting the program, editing autounattend.xml) except converting iso to imgptn. I also tried to find something about this problem on e2b forums and pretty much on the whole e2b site, but unfortunately, it's not even listed in the list of errors. For example, Windows 10 works fine, without any problems at all. I really like this program and i don't really want to change it if it has such malfunctions.
Thank you in advance for the help.
Crave
21/10/2016
Re: Unable to launch the setup application
AIO ISOs may not work because they have been changed a lot by the developer. You should convert them to a .imgPTN file if they don't work as an ISO file.
SteveSi
21/10/2016
win 7 pe.wi kas iso boot
Hi sir,
Sorry for my poor english.
I have latest version of e2b.
Recently i add win7pe.wim but getting winload.exe missing error. Try with almost wim and no luck. I have bootmgr on root of hdd partition. (format as fat32).
Also i want to know if i can add kas.iso to e2b, because my usb hdd has more than 2 partitions so partnew method cannot get to work.
I know that we can extract kas to rescue folder but i do not want to use this method (may not safe to extract since kas is antivirus rescue)
Try iso boot with some code from rmprep site too, but no luck.
Finally tks for your greate project.
God bless u :)
Sorry for my poor english.
I have latest version of e2b.
Recently i add win7pe.wim but getting winload.exe missing error. Try with almost wim and no luck. I have bootmgr on root of hdd partition. (format as fat32).
Also i want to know if i can add kas.iso to e2b, because my usb hdd has more than 2 partitions so partnew method cannot get to work.
I know that we can extract kas to rescue folder but i do not want to use this method (may not safe to extract since kas is antivirus rescue)
Try iso boot with some code from rmprep site too, but no luck.
Finally tks for your greate project.
God bless u :)
zhuanglee
17/10/2016
Re: win 7 pe.wi kas iso boot
A Windows bootable wim file should contain one image and a \windows\system32\loader.exe file should be present. Please check using 7Zip.
What is 'kas.iso' ? Do you mean Kaspersky AntiVirus Rescue disk iso? If so it can be booted directly using E2B. Only one free partition entry is needed.
http://rmprepusb.blogspot.co.uk/2014/04/adding-kaspersky-rescue-iso-to.html
What is 'kas.iso' ? Do you mean Kaspersky AntiVirus Rescue disk iso? If so it can be booted directly using E2B. Only one free partition entry is needed.
http://rmprepusb.blogspot.co.uk/2014/04/adding-kaspersky-rescue-iso-to.html
SteveSi
17/10/2016
Windows ISOs and imgPTN boot issues
Hello, my apologies if I've missed something obvious, but I've been attempting to create a multiboot windows install / linux E2B USB for a couple of days and am flummoxed by windows ISO issues. I've looked through all the tutorials and topics I can but can't find the solution.
I can boot a linux ISO, and create a imgPTN from it and boot it no bother - tested with Puppy Linus.
However, Windows ISOs downloaded from the 'Windows Iso Downloaded' recommended on the site are another story.
- If the plain ISO is used in the correct folder, I get Error 13 Invalid or unsuppoted executable format.
- If I convert to imgPTN I get 'has no menu.lst file'.
- I created working Winsetupfromusb, Sagefile and Rufus USBs, and converted them to ISO/imgPTN, but get the same error
- For each attempt, I can mount the img using Imdisk as a removable drive and explore the contents, but after I attempt to boot, the image becomes corrupted and can no longer be accessed.
- I've tried different USB pens, same problem.
Any advice would be much appreciated!
I can boot a linux ISO, and create a imgPTN from it and boot it no bother - tested with Puppy Linus.
However, Windows ISOs downloaded from the 'Windows Iso Downloaded' recommended on the site are another story.
- If the plain ISO is used in the correct folder, I get Error 13 Invalid or unsuppoted executable format.
- If I convert to imgPTN I get 'has no menu.lst file'.
- I created working Winsetupfromusb, Sagefile and Rufus USBs, and converted them to ISO/imgPTN, but get the same error
- For each attempt, I can mount the img using Imdisk as a removable drive and explore the contents, but after I attempt to boot, the image becomes corrupted and can no longer be accessed.
- I've tried different USB pens, same problem.
Any advice would be much appreciated!
Liam
12/10/2016
Re: Windows ISOs and imgPTN boot issues
Can you describe what USB drive you are using and how you made it, size, make, model, etc.
If it is a flash drive, did you test it with H2TESTW or FakeFlashTest to see if it is a fake one?
You say you can mount an .imgPTN file using ImDisk and see the \menu.lst file and other contents - is the file on your internal Windows drive or are you using the .imgPTN file directly on the USB drive?
If it is a flash drive, did you test it with H2TESTW or FakeFlashTest to see if it is a fake one?
You say you can mount an .imgPTN file using ImDisk and see the \menu.lst file and other contents - is the file on your internal Windows drive or are you using the .imgPTN file directly on the USB drive?
SteveSi
12/10/2016
There is not enough space on the disk
I have a problem using MPI to create imgPTN. It always says "there is not enough space on the disk" even though I have increase the size.
Please help. thanks a lot!
Please help. thanks a lot!
Bruce
23/09/2016
Re: There is not enough space on the disk
I include the screenshot here for visual ref. https://drive.google.com/open?id=0B7VPcKBuhELCMGgzc1k1YUNsYUU
Bruce
23/09/2016
Re: Re: There is not enough space on the disk
AOI ISOs tend to be heavily compressed. There is a special option when making an ISO that allows an image to contain a single file with multiple entries for duplicate files in the same ISO.
You may have to add a LOT more to the size before it works.
You may have to add a LOT more to the size before it works.
SteveSi
23/09/2016
Windows 10 UEFI install choosing a version?
Is there a way for me to choose a version for UEFI install? For regular windows installation, I have the options to choose between pro and home. But for UEFI it would just install the Pro version every single time. Any workaround here? Thank you so much!
Charles
08/09/2016
Re: Windows 10 UEFI install choosing a version?
When you use the MakePartImage script, it should prompt you to delete or make a EI.CFG file. For a Win8/10 standard Retail\OEM ISO, choose R=Retail.
SteveSi
08/09/2016
Error on Windows iso
I have a 6,4GB iso of Windows 10 with both 32 and 64 bit Pro & Home edition. When i choose the version to install and pick 64bit i get a fvevol.sys error. Can someone help? Thanks in advance.
JimP
29/08/2016
Re: Error on Windows iso
From Googling, it seems that this is something to do with BitLocker. Several people have fixed it by updating the BIOS/firmware to a later version.
Does this error only happen on one type of system?
Does this error only happen on one type of system?
SteveSi
29/08/2016
Re: Re: Error on Windows iso
It happens on every system i try to install the 64 bit version.
JimP
29/08/2016
Re: Re: Re: Error on Windows iso
Try a different ISO. If that gives the same problem, then it must be a problem with your systems?
SteveSi
29/08/2016
Debian (lxde) multiboot + persistence
Hello, There is a E2B page where linux with persistence, one should use imgPTN for multiboot + persistence. Which leads to http://rmprepusb.blogspot.com.br/2015/08/add-debian-live-iso-with-persistence-to.html but not a word about imgPTN tutorial. What's the proper way of doing it? Or should I look other distro tutorial for equivalence. Have patience and a great time! Capum
Capum
19/08/2016
Re: Debian (lxde) multiboot + persistence
Hi,
The Debian-live-8.5.0-amd64-lxde-desktop.iso does not contain EFI boot files. So I don't think it will be UEFI-bootable. Why don't you use an ISO file + persistence and MBR booting?
The Debian-live-8.5.0-amd64-lxde-desktop.iso does not contain EFI boot files. So I don't think it will be UEFI-bootable. Why don't you use an ISO file + persistence and MBR booting?
SteveSi
19/08/2016
Re: Re: Debian (lxde) multiboot + persistence
UEFI with legacy boot? sure! actually this notebook is BIOS, just checked that. I could manage it if I wasn't kind lost, you have two pages about linux persistence. Could I use the the guide page with more reliable ext3,4 volume instead? thanks it's amazing tool.
Capum
19/08/2016
Re: Re: Re: Debian (lxde) multiboot + persistence
If you just want legacy BIOS boot, then you dont need a .imgPTN file.
See \_ISO\docs\Sample mnu files\linux
debian-live-8.1.0-amd64-mate-desktop_Persistent.mnu
and the blog post on how to make a persistence file.
A persistence file of ext3 or ext4 is more reliable in case of file corruption (which happens a lot with USB drives because you tend to just switch off the system or remove the drive without shutting down properly!).
See \_ISO\docs\Sample mnu files\linux
debian-live-8.1.0-amd64-mate-desktop_Persistent.mnu
and the blog post on how to make a persistence file.
A persistence file of ext3 or ext4 is more reliable in case of file corruption (which happens a lot with USB drives because you tend to just switch off the system or remove the drive without shutting down properly!).
SteveSi
19/08/2016
Re: Debian (lxde) multiboot + persistence
This way... would it be multiboot ?
Capum
19/08/2016
Re: Re: Debian (lxde) multiboot + persistence
Yes, you can have as many Debian ISOs as you like and as many persistence files as you like - just use a different persistence file for each one and edit the .mnu file to use the named ISO and persistence file.
SteveSi
19/08/2016
Manual Key input for Windows description
Hello!
Thank you for the best working USB-MUltiboot solution (at least for me). :)
Recently I had to enter the Generíc Windows setup key multiple times for different setups. When choosing to manually enter a key in E2B, the description says something like "25 digits". So I sometimes entered the key unhyphenated (without dashes) because otherwise it wouldn't have been 25 digits, but 29. Of course this was wrong and I had to enter the key a second time, including dashes. So I wanted to suggest that you might add a little hint, that dashes have to be input, too?
:)
Thank you for the best working USB-MUltiboot solution (at least for me). :)
Recently I had to enter the Generíc Windows setup key multiple times for different setups. When choosing to manually enter a key in E2B, the description says something like "25 digits". So I sometimes entered the key unhyphenated (without dashes) because otherwise it wouldn't have been 25 digits, but 29. Of course this was wrong and I had to enter the key a second time, including dashes. So I wanted to suggest that you might add a little hint, that dashes have to be input, too?
:)
ElMariachi
19/08/2016
Re: Manual Key input for Windows description
Hi
Thanks for the feedback. In the English version of 1.82 it says
'Product keys must be in AAAAA-BBBBB-CCCCC-DDDDD-EEEEE format (29 characters)'
So are you using an old version or a different language?
Also, what Generic Product Key are you entering? I thought that I had all the generic keys in the list?
Thanks for the feedback. In the English version of 1.82 it says
'Product keys must be in AAAAA-BBBBB-CCCCC-DDDDD-EEEEE format (29 characters)'
So are you using an old version or a different language?
Also, what Generic Product Key are you entering? I thought that I had all the generic keys in the list?
SteveSi
19/08/2016
Re: Re: Manual Key input for Windows description
I looked through the languages files and the German one says 25 instead of 29. I will fix this in next v1.83 Beta.
SteveSi
19/08/2016
SDI_CHOCO
Has anyone tried the SDI_CHOCO feature in v1.82 yet? Any questions? Just looking for feedback...
SteveSi
08/08/2016
how can I use ghost.exe
I want to use ghost11
the file name is "ghost.exe"
not .iso and .img
how can I use it in E2B? dos? or other ways
thanks
the file name is "ghost.exe"
not .iso and .img
how can I use it in E2B? dos? or other ways
thanks
hao
19/07/2016
Re: how can I use ghost.exe
Ghost.exe is (probably) a Windows executable, so it must be run under Windows.
You could try booting to a Windows 10 ISO to Setup, then press SHIFT+F10 and then run Ghost from the E2B USb drive (e.g. D:\Ghost.exe if D: is the USB drive).
You could try booting to a Windows 10 ISO to Setup, then press SHIFT+F10 and then run Ghost from the E2B USb drive (e.g. D:\Ghost.exe if D: is the USB drive).
SteveSi
19/07/2016
Error grub
Hi!
I have problem and I want to avoid reinstall.
message error:
Booting from hard disk...
GRUB loading.
error: no such device: 4d074ea1-008f-4cf9-a6c5-1a7fb76c38f2
Entering rescue mode...
grub rescue>
ty
I have problem and I want to avoid reinstall.
message error:
Booting from hard disk...
GRUB loading.
error: no such device: 4d074ea1-008f-4cf9-a6c5-1a7fb76c38f2
Entering rescue mode...
grub rescue>
ty
Sheeddy
19/07/2016
deleted
nada
nobody
19/07/2016
Re: Error grub
It sounds like the partition has been changed/deleted/formatted. Try booting from USB and use gparted to look at the partition or try an automatic boot repair utility
http://rmprepusb.blogspot.co.uk/2015/07/add-boot-repair-disk-isos-to-e2b-multi.html
http://rmprepusb.blogspot.co.uk/2015/07/add-boot-repair-disk-isos-to-e2b-multi.html
SteveSi
19/07/2016
Re: Re: Error grub
sorry, I was not specific.
The error is in the booting from USB and room "QEMU_MENU_TEST"
view the image->
http://prntscr.com/bux02v
TY and sorry for hassle.
The error is in the booting from USB and room "QEMU_MENU_TEST"
view the image->
http://prntscr.com/bux02v
TY and sorry for hassle.
Sheeddy
19/07/2016
Re: Re: Re: Error grub
E2B uses grub4dos not grub.
It looks like something has installed grub onto the USB drive. Use RMPrepUSB - Install grub4dos and run twice, once with Yes and once with No option.
It looks like something has installed grub onto the USB drive. Use RMPrepUSB - Install grub4dos and run twice, once with Yes and once with No option.
SteveSi
20/07/2016
Slackware Live with persistence.
Hi,
1. How to create Slackware Live with persistence (Ext2 / Ext4 persistence file). http://alien.slackbook.org/blog/slackware-live-edition-1-1-0-comes-with-the-latest-plasma5-on-iso/
2. How to make Remix OS / Phoenix OS with persistence.
Thanks.
1. How to create Slackware Live with persistence (Ext2 / Ext4 persistence file). http://alien.slackbook.org/blog/slackware-live-edition-1-1-0-comes-with-the-latest-plasma5-on-iso/
2. How to make Remix OS / Phoenix OS with persistence.
Thanks.
babam
19/06/2016
Re: Slackware Live with persistence.
See blog tutorials
http://rmprepusb.blogspot.co.uk/p/easy2boot-useful-blogs.html
http://rmprepusb.blogspot.co.uk/p/easy2boot-useful-blogs.html
SteveSi
20/06/2016
Mastering E2B
Hey guys,
1st thanks for your great tools.
I've been trying for almost 3 hours now, i swear you, but i can't build that multiboot usb.
Tried the standard iso way, tried the conversion to .imgPTN also ... with NTFS or FAT32 (the drive and the files).
My BIOS can even handle both UEFI and legacy mode, i switched couple of times ... but i always fail, i must be noob.
I also checked /EFI/BOOT stuff.
Does the problem could be because i have multi os on my drive (seven and 8.1)? The default one is Windows 7 x64.
It's GPT NTFS formating.
It never wants to boot on this USB key.
Am i really that noob ?
Maybe I missed a useful link ???
1st thanks for your great tools.
I've been trying for almost 3 hours now, i swear you, but i can't build that multiboot usb.
Tried the standard iso way, tried the conversion to .imgPTN also ... with NTFS or FAT32 (the drive and the files).
My BIOS can even handle both UEFI and legacy mode, i switched couple of times ... but i always fail, i must be noob.
I also checked /EFI/BOOT stuff.
Does the problem could be because i have multi os on my drive (seven and 8.1)? The default one is Windows 7 x64.
It's GPT NTFS formating.
It never wants to boot on this USB key.
Am i really that noob ?
Maybe I missed a useful link ???
Palteza
13/06/2016
Re: Mastering E2B
Booting from GPT USb drives is not supported
SteveSi
14/06/2016
Re: Re: Mastering E2B
Ok that means i have to format my hard drive in MBR ?
Palteza
14/06/2016
Re: Re: Re: Mastering E2B
Yes - format as two partitions.
First one 137GB NTFS for E2B, 2nd one as rest (up to 2TB).
Instructions are on this site
http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-and-e2b-usb-drive-using-rmprepusb/
First one 137GB NTFS for E2B, 2nd one as rest (up to 2TB).
Instructions are on this site
http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-and-e2b-usb-drive-using-rmprepusb/
SteveSi
14/06/2016
Lenovo tools
Hi sir, I have a lenovo tools that can update and edit machine type model of laptop,it is used and run only on a usb flash disk, i convert this utility into an iso (converting all contents into 1 file) when i copy this iso to my easy drive, the utility run but when i tried to use the functionality it always prompts that eeprom is write protected..is there other way to avoid this error anytime i used this utility.
jojo baquir
07/06/2016
Re: Lenovo tools
You should convert the flash drive to a .imgPTN file and boot from that. P.S. Are you sure that when you use the Lenovo USB flash drive it works on the same system?
SteveSi
07/06/2016
Re: Re: Lenovo tools
You can also make a .ima floppy disk image - see http://rmprepusb.blogspot.com/2016/06/adding-lenovo-maintenance-utilities-ibm.html
SteveSi
07/06/2016
Windows 7 Install Now, contains all other available versions, menu was slow to load
Hi Steve. Please these questions and experience.
1). I tried Install Windows 7, Easy2Boot displays various commands inbox, but, ¿Is it normal that E2B does not display the "Windows 7 Install Now" window?:
http://s6.postimg.org/9ku02l981/windows7_install_5.jpg
2). Is it normal that E2B displays all other available versions of Windows 7? They are not hidden from view.
Does E2B ignore the ei.cfg file inside ISO?
http://s6.postimg.org/fn1mt2xo1/windows_7_iso_ei_file_removed.png
3). I experienced the trouble that E2B takes a long time to display the Main Menu.
I fixed Load Optimized Defaults from BIOS. Still it works.
Mobo: MSI 760GM-P34 (FX), AMI BIOS version 2013-04-28.
https://www.msi.com/Motherboard/support/760GM-P34-FX.html#down-bios
Thanks!
1). I tried Install Windows 7, Easy2Boot displays various commands inbox, but, ¿Is it normal that E2B does not display the "Windows 7 Install Now" window?:
http://s6.postimg.org/9ku02l981/windows7_install_5.jpg
2). Is it normal that E2B displays all other available versions of Windows 7? They are not hidden from view.
Does E2B ignore the ei.cfg file inside ISO?
http://s6.postimg.org/fn1mt2xo1/windows_7_iso_ei_file_removed.png
3). I experienced the trouble that E2B takes a long time to display the Main Menu.
I fixed Load Optimized Defaults from BIOS. Still it works.
Mobo: MSI 760GM-P34 (FX), AMI BIOS version 2013-04-28.
https://www.msi.com/Motherboard/support/760GM-P34-FX.html#down-bios
Thanks!
Berthollucci
26/05/2016
Re: Windows 7 Install Now, contains all other available versions, menu was slow to load
Q1 - for win7, it is normal
Q2. yes ei.cfg is ignored because we use an unattend.xml file
Q3. Either slow USB drive or slow USB BIOS driver.
Read FAQ - menu is slow to load.
If you want the more standard install experience, convert the ISO to a .imgPTN file.
Q2. yes ei.cfg is ignored because we use an unattend.xml file
Q3. Either slow USB drive or slow USB BIOS driver.
Read FAQ - menu is slow to load.
If you want the more standard install experience, convert the ISO to a .imgPTN file.
SteveSi
26/05/2016
need an E2B HELPER USB FLASH DRIVE
Hi.
when I tried to install using a 500GB hard drive appears caption
"install windows froam a sub hard disk you also an E2B HELPER USB flashdrive. if you do not have one you will get a "DVD drive device driver is missing" message"
please help me
when I tried to install using a 500GB hard drive appears caption
"install windows froam a sub hard disk you also an E2B HELPER USB flashdrive. if you do not have one you will get a "DVD drive device driver is missing" message"
please help me
luqman
24/05/2016
Re: need an E2B HELPER USB FLASH DRIVE
http://www.easy2boot.com/add-payload-files/windows-install-isos/installing-windows-with-a-helper-drive/
SteveSi
25/05/2016
USB formats
Just found this site/program and looks very handy. I do wonder if you use UDF format for the usb device? I have use UDF formats to move large files between Windows and Linux computers. (don't have any apples to play with)
Mark Keith
22/05/2016
RestoreE2B alert ?
Steve,
E2B is the best !
One little suggestion for us beginners about rebuilding an E2B flash drive though . . .
I started out just making an .imgPTN of Gandalf, dropped it into ISO\MAINMENU and the thing booted right off, no problem.
But when I went back to add another .iso, there was no ISO directory to be found because of the repartitioning from booting into an .imgPTN and I was a bit confused.
It took me a while to figure out I would have to run the "RestoreE2B" to get the expected partitions back. Up until then I was starting to think I'd have to rebuild the E2B drive each time I added something new.
Maybe I missed it but you might want to put an alert in there for us beginners.
Nonetheless, thanks a million for all your efforts developing this - it's really cool and I'm looking forward to experimenting and playing around with it.
E2B is the best !
One little suggestion for us beginners about rebuilding an E2B flash drive though . . .
I started out just making an .imgPTN of Gandalf, dropped it into ISO\MAINMENU and the thing booted right off, no problem.
But when I went back to add another .iso, there was no ISO directory to be found because of the repartitioning from booting into an .imgPTN and I was a bit confused.
It took me a while to figure out I would have to run the "RestoreE2B" to get the expected partitions back. Up until then I was starting to think I'd have to rebuild the E2B drive each time I added something new.
Maybe I missed it but you might want to put an alert in there for us beginners.
Nonetheless, thanks a million for all your efforts developing this - it's really cool and I'm looking forward to experimenting and playing around with it.
Kent
17/05/2016
Re: RestoreE2B alert ?
Hi, yes that catches quite a few people.
When you select the .imgPTN file in the E2B menu, you should see a WARNING in lots of colours which you are supposed to read. if you don't read it then you may get a surprise. The first item on the CSM menu is to restore the E2B menu.
You can also use SWITCH_E2B.exe to switch and restore the partition.
How do you suggest I can improve the warning?
When you select the .imgPTN file in the E2B menu, you should see a WARNING in lots of colours which you are supposed to read. if you don't read it then you may get a surprise. The first item on the CSM menu is to restore the E2B menu.
You can also use SWITCH_E2B.exe to switch and restore the partition.
How do you suggest I can improve the warning?
SteveSi
17/05/2016
Re: Re: RestoreE2B alert ?
Actually I saw that warning and wrote it down, not really knowing what it was about. I figured it was some expert optional choice as, when you're really excited to see something boot up and run, you're not really in the frame of mind to stop and contemplate something that comes up unexpectedly.
The whole notion that your flash drive is going to have partitions remade and shifted around takes a while for your head to wrap around (but now I get it).
And you don't really absorb it until you run into it. (Very ingenious though.)
So I was thinking, maybe on the "Adding Payload" or "Adding-uefi-images" page(s) something like, "NOTE : once you boot into an .imgPTN . . . . ".
That is, some page where you're in learning mode, so to speak.'
Just an idea.
The whole notion that your flash drive is going to have partitions remade and shifted around takes a while for your head to wrap around (but now I get it).
And you don't really absorb it until you run into it. (Very ingenious though.)
So I was thinking, maybe on the "Adding Payload" or "Adding-uefi-images" page(s) something like, "NOTE : once you boot into an .imgPTN . . . . ".
That is, some page where you're in learning mode, so to speak.'
Just an idea.
Kent
17/05/2016
E2B asking for a helper usb, haven't needed one before
I have been using e2b for quite a while with no problems, but today I went to install windows server 2012 and it said I needed a helper usb. I looked into this and it said if my device showed as a fixed device in windows explorer I would need one, but mine shows as a removable device.. Am I missing something?
Josh
13/05/2016
Re: E2B asking for a helper usb, haven't needed one before
grub4dos/E2B cannot tell if the USB device is a Removable type, so E2B just looks at the size of the device and warns you if the USB device appears to be a large device. The inference being that most large USB devices are USB HDDs or Fixed-type removable USB flash drives. If you are sure that your device is a Removable type (as displayed by RMPrepUSB) then just go ahead and press C and ENTER as prompted.
What USB device are you using?
What USB device are you using?
SteveSi
14/05/2016
grub2
Hi Steve.
After booting to grub2 in EFI mode, does it allow for a menu entry to boot the E2B drive in legacy mode (grldr)?
I'm currently using rEFInd on my E2B drive for EFI booting, but it doesn't support manual legacy entries, only those scanned at boot. This boot scan for legacy bootloaders usually fails for external USB drive, depending on mobo, requiring enabling deep_scan option. And deep_scan is too agressive, as it rewrites the mobo boot options permanently (reset to defaults required).
After booting to grub2 in EFI mode, does it allow for a menu entry to boot the E2B drive in legacy mode (grldr)?
I'm currently using rEFInd on my E2B drive for EFI booting, but it doesn't support manual legacy entries, only those scanned at boot. This boot scan for legacy bootloaders usually fails for external USB drive, depending on mobo, requiring enabling deep_scan option. And deep_scan is too agressive, as it rewrites the mobo boot options permanently (reset to defaults required).
Starla
08/05/2016
Re: grub2
You cannot change from UEFI to Legacy mode.
You can go from Legacy to UEFI by using Clover because Clover is a BIOS-in-RAM implementation of a UEFI BIOS, but AFAIK, there is no equivalent Legacy BIOS-in-RAM for a UEFI-BIOS.
You can go from Legacy to UEFI by using Clover because Clover is a BIOS-in-RAM implementation of a UEFI BIOS, but AFAIK, there is no equivalent Legacy BIOS-in-RAM for a UEFI-BIOS.
SteveSi
13/05/2016
E2B partition placement problem.
Hello again!
Part II: Continuation of the vicissitudes.
I have decided to merge my Easy2Boot USB Pendrive #1 with my external USB HDD 500GB
used for my PC's internal HDD files backup so that I have
E2B boot & repair stuff (partition 1) + the PC's internal HDD's files backup (partition 2)
on a single device (the external USB HDD 500GB)
so that I later can get rid of the unnessesary USB Pendrive.
So I begun to install E2B on the external USB HDD 500GB
following instructions from:
http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-and-e2b-usb-drive-using-rmprepusb/
I wanted 20 GB E2B partition,
but because space from 4 GB to 99GB on the external USB HDD 500GB is damaged (bad sectors)
I created 137 000 (137GB) WinPE & NTFS E2B partition (unticked Boot as HDD)
and then in some partition program I shrunk that partition from 137 GB to 20 GB from left to right, (as I did not see in RMPrepUSB a possibility to set start & end of E2B partition, only can set size, thus I had to use so trick) leaving first 99 GB as an unallocated space before E2B partition.
Then behind it, I created a second 346 GB NTFS partition for the PC's internal HDD's files backup.
Then I run "Install grub4dos" thing two times.
Everything completed successfully.
So I got following structure:
0 GB - 99 GB - an unallocated space
99 GB - 119 GB - the first primary 20 GB NTFS partiton with E2B boot & repair stuff
119 GB - 465 GB - the second primary 346 GB NTFS partiton with the PC's internal HDD's files backup
Then I copied all my boot images from Easy2Boot USB Pendrive #1 onto the external USB HDD 500GB onto E2B partition.
Then I begun testing phase 1:
1) I Rebooted my PC, and booted successfully to E2B menu.
Then I begun testing phase 2:
2) I Rebooted my PC again to OS, and run SWITCH_E2B.exe, and double-clicked one of imgPTN images to test imgPTN images UEFI booting, and I got an error:
MBR is not an E2B MBR ?
ERROR: MBR on drive 1 does not contain a partition near the start of the drive.
Use 'Safely Remove Drive' System Tray icon and re-insert USB drive.
But I cannot make a 20GB partition near the start of the drive because as I already mentioned before , space from 4GB to 99GB of the drive is unusable and damaged.
So now my question is: does E2B partition must be near the start of the drive?
If not, then how to solve the SWITCH_E2B.exe error issue? (maybe some hack/trick/sector swap?)
If not then maybe for ex. as first 4GB of the drive are undamaged I may create a small 4 GB primary E2B partiton and put E2B stuff there (it takes something like 600+MB) + some of the images and then behind the damaged space, make two logical partitions, and on the first one put rest of the images files, then edit somehow E2B settings to boot the rest of the images from this partition. (I have read somewhere on E2B webpages that this is possible). The second logical partiton will be for the PC's internal HDD's files backup.
This way I will have:
0 GB - 4 GB - the primary 4 GB NTFS partiton with E2B boot & repair stuff (some of the images)
99 GB - 115 GB - the logical 16 GB NTFS partiton with the rest of the images
115 GB - 461 GB - the logical 346 GB NTFS partiton with the PC's internal HDD's files backup
But I would rather prefer to fix the issue in a better way than complicated jugglery of partitions.
Steve, I know you can find the solution,
You are the man !
please help.
Thank You!
Part II: Continuation of the vicissitudes.
I have decided to merge my Easy2Boot USB Pendrive #1 with my external USB HDD 500GB
used for my PC's internal HDD files backup so that I have
E2B boot & repair stuff (partition 1) + the PC's internal HDD's files backup (partition 2)
on a single device (the external USB HDD 500GB)
so that I later can get rid of the unnessesary USB Pendrive.
So I begun to install E2B on the external USB HDD 500GB
following instructions from:
http://www.easy2boot.com/make-an-easy2boot-usb-drive/make-and-e2b-usb-drive-using-rmprepusb/
I wanted 20 GB E2B partition,
but because space from 4 GB to 99GB on the external USB HDD 500GB is damaged (bad sectors)
I created 137 000 (137GB) WinPE & NTFS E2B partition (unticked Boot as HDD)
and then in some partition program I shrunk that partition from 137 GB to 20 GB from left to right, (as I did not see in RMPrepUSB a possibility to set start & end of E2B partition, only can set size, thus I had to use so trick) leaving first 99 GB as an unallocated space before E2B partition.
Then behind it, I created a second 346 GB NTFS partition for the PC's internal HDD's files backup.
Then I run "Install grub4dos" thing two times.
Everything completed successfully.
So I got following structure:
0 GB - 99 GB - an unallocated space
99 GB - 119 GB - the first primary 20 GB NTFS partiton with E2B boot & repair stuff
119 GB - 465 GB - the second primary 346 GB NTFS partiton with the PC's internal HDD's files backup
Then I copied all my boot images from Easy2Boot USB Pendrive #1 onto the external USB HDD 500GB onto E2B partition.
Then I begun testing phase 1:
1) I Rebooted my PC, and booted successfully to E2B menu.
Then I begun testing phase 2:
2) I Rebooted my PC again to OS, and run SWITCH_E2B.exe, and double-clicked one of imgPTN images to test imgPTN images UEFI booting, and I got an error:
MBR is not an E2B MBR ?
ERROR: MBR on drive 1 does not contain a partition near the start of the drive.
Use 'Safely Remove Drive' System Tray icon and re-insert USB drive.
But I cannot make a 20GB partition near the start of the drive because as I already mentioned before , space from 4GB to 99GB of the drive is unusable and damaged.
So now my question is: does E2B partition must be near the start of the drive?
If not, then how to solve the SWITCH_E2B.exe error issue? (maybe some hack/trick/sector swap?)
If not then maybe for ex. as first 4GB of the drive are undamaged I may create a small 4 GB primary E2B partiton and put E2B stuff there (it takes something like 600+MB) + some of the images and then behind the damaged space, make two logical partitions, and on the first one put rest of the images files, then edit somehow E2B settings to boot the rest of the images from this partition. (I have read somewhere on E2B webpages that this is possible). The second logical partiton will be for the PC's internal HDD's files backup.
This way I will have:
0 GB - 4 GB - the primary 4 GB NTFS partiton with E2B boot & repair stuff (some of the images)
99 GB - 115 GB - the logical 16 GB NTFS partiton with the rest of the images
115 GB - 461 GB - the logical 346 GB NTFS partiton with the PC's internal HDD's files backup
But I would rather prefer to fix the issue in a better way than complicated jugglery of partitions.
Steve, I know you can find the solution,
You are the man !
please help.
Thank You!
Marcinoo
05/05/2016
Re: E2B partition placement problem.
That is a safety feature of SWITCH_E2B to prevent someone from accidentally 'restoring' a drive that contains grub4dos but is not an E2B drive.
You should be able to use the E2B menu to switch partitions (e.g. boot it on a real system or under QEMU or VBox to E2B).
I don't recommend using a known faulty drive. It is bound to let you down just at the wrong time!
You should be able to use the E2B menu to switch partitions (e.g. boot it on a real system or under QEMU or VBox to E2B).
I don't recommend using a known faulty drive. It is bound to let you down just at the wrong time!
SteveSi
05/05/2016
Re: Re: E2B partition placement problem.
Astounding,
it really works !
Since it did not work in OS, I was supposing that it won't work also in menu, thus I didn't even checked nor made sure, however, just right after your post I checked and it really works in menu!
Thanks for creating E2B, it make life easier !
And as regards damaged disks, I am aware of risks and danger, however you're right, such damaged disks may fail at any time. I don't know myself why I still keep data on it - I think I have gambler :)
Best Regards :)
it really works !
Since it did not work in OS, I was supposing that it won't work also in menu, thus I didn't even checked nor made sure, however, just right after your post I checked and it really works in menu!
Thanks for creating E2B, it make life easier !
And as regards damaged disks, I am aware of risks and danger, however you're right, such damaged disks may fail at any time. I don't know myself why I still keep data on it - I think I have gambler :)
Best Regards :)
Marcinoo
05/05/2016
Boot XP VHD from bootmgr blog post (cont).
Ok Steve I've been reviewing the latest English release by SS and the following procedure is used to boot provided ISO/IMG files from DOS bootmgr. Sadly I haven't yet a XP VHD for a quick test. Would you be so kind to confirm it's able to boot yours?
1. Copy your grldr file of choice (ie the one provided at E2B root) to the folder containing your XP VHD file.
2. Rename grldr to payload.mbr (ie Fullxpvhd.mbr).
3. Run BOOTICE>Utilities>Grub4DOS Menu Editor and open Fullxpvhd.mbr.
4. Replace displayed default embedded menu.lst with the commands on your blog post and save changes.
5. BOOTICE>BCD>Other BCD and select your BCD. I use Professional Mode for editing.
6. Right-click any entry under "Application objects" and select "New RealMode Entry".
7. Select the created entry, then on the main panel, right-click "Aplication path", select "Edit" and point to Fullxpvhd.mbr file. You can also edit the "Description" value.
That should work: bootmgr>Fullxpvhd.mbr>ntldr within XP VHD file.
1. Copy your grldr file of choice (ie the one provided at E2B root) to the folder containing your XP VHD file.
2. Rename grldr to payload.mbr (ie Fullxpvhd.mbr).
3. Run BOOTICE>Utilities>Grub4DOS Menu Editor and open Fullxpvhd.mbr.
4. Replace displayed default embedded menu.lst with the commands on your blog post and save changes.
5. BOOTICE>BCD>Other BCD and select your BCD. I use Professional Mode for editing.
6. Right-click any entry under "Application objects" and select "New RealMode Entry".
7. Select the created entry, then on the main panel, right-click "Aplication path", select "Edit" and point to Fullxpvhd.mbr file. You can also edit the "Description" value.
That should work: bootmgr>Fullxpvhd.mbr>ntldr within XP VHD file.
Starla
04/05/2016
Unable to boot sedutil *.img images
Hello,
I have a problem !
I used Win32DiskImager and burned successfully two images:
1) UEFI64_Debug.img
2) Rescue.img
downloaded from
https://github.com/Drive-Trust-Alliance/sedutil/wiki/Executable-Distributions
onto my USB Pendrive #2, and they both successfully booted in UEFI mode.
You may read more about the images here:
https://github.com/Drive-Trust-Alliance/sedutil/wiki/Test-the-PBA (UEFI64_Debug.img)
https://github.com/Drive-Trust-Alliance/sedutil/wiki/Test-the-Rescue-system (Rescue.img)
Now what I want is to add the images to my main Easy2Boot USB Pendrive #1 as I always have all boot things on a single pendrive.
First try was simply to put the *.img images into Easy2Boot USB Pendrive #1\_ISO\LINUX folder (just out of curiosity and for test purposes as I already know they are UEFI images and won't boot this way), thus as I expected, they both didn't boot, I got a black screen with a char indicator flashing in left-top corner of the screen and I had to reset the computer.
Another try was a proper way, to convert the *.img images to *.imgPTN format.
I made it by program "MakePartImage_AutoRun_FAT32.cmd" from the tool "MPI_Tool_Pack_Plus_CloverLite_064".
I made all strongly with instructions from ReadMe.txt file (except I didn't convert the *.img to *.iso first, but another time I converted to *.iso, and that made no difference) Result was: successfully!
Then I used "SWITCH_E2B.exe" to enable the UEFI images on my Easy2Boot USB Pendrive #1 and rebooted the computer but again they fails to boot, the one image just don't even boot, nothing happens, and just the OS boots as usual, and the another one boot to CSM menu (and when I choose boot from current image as MBR) the same thing happens like in "First try", I got a black screen with a char indicator flashing in left-top corner of the screen and the USB Pendrive flashing to infinity and I had to reset the computer.
Perhaps the images require some special settings to get booting?
Please, help!
Thanks.
I have a problem !
I used Win32DiskImager and burned successfully two images:
1) UEFI64_Debug.img
2) Rescue.img
downloaded from
https://github.com/Drive-Trust-Alliance/sedutil/wiki/Executable-Distributions
onto my USB Pendrive #2, and they both successfully booted in UEFI mode.
You may read more about the images here:
https://github.com/Drive-Trust-Alliance/sedutil/wiki/Test-the-PBA (UEFI64_Debug.img)
https://github.com/Drive-Trust-Alliance/sedutil/wiki/Test-the-Rescue-system (Rescue.img)
Now what I want is to add the images to my main Easy2Boot USB Pendrive #1 as I always have all boot things on a single pendrive.
First try was simply to put the *.img images into Easy2Boot USB Pendrive #1\_ISO\LINUX folder (just out of curiosity and for test purposes as I already know they are UEFI images and won't boot this way), thus as I expected, they both didn't boot, I got a black screen with a char indicator flashing in left-top corner of the screen and I had to reset the computer.
Another try was a proper way, to convert the *.img images to *.imgPTN format.
I made it by program "MakePartImage_AutoRun_FAT32.cmd" from the tool "MPI_Tool_Pack_Plus_CloverLite_064".
I made all strongly with instructions from ReadMe.txt file (except I didn't convert the *.img to *.iso first, but another time I converted to *.iso, and that made no difference) Result was: successfully!
Then I used "SWITCH_E2B.exe" to enable the UEFI images on my Easy2Boot USB Pendrive #1 and rebooted the computer but again they fails to boot, the one image just don't even boot, nothing happens, and just the OS boots as usual, and the another one boot to CSM menu (and when I choose boot from current image as MBR) the same thing happens like in "First try", I got a black screen with a char indicator flashing in left-top corner of the screen and the USB Pendrive flashing to infinity and I had to reset the computer.
Perhaps the images require some special settings to get booting?
Please, help!
Thanks.
Marcinoo
04/05/2016
Re: Unable to boot sedutil *.img images
I forgot to add that I already have Windows 7 64 SP1 UEFI.imgPNT on my Easy2Boot USB Pendrive #1 and it boot with no problems (as I also used it to install W7 on my computer)
Marcinoo
04/05/2016
Re: Unable to boot sedutil *.img images
Hi
Something odd is going on when 7zip upacks the images. When you use the rescue.img file with MPI_FAT32 you get a 0.img file inside the .imgPTN file instead of it extracting the files!
However, if you copy this 0.img file and place it on the E2B partition at \_ISO\LINUX (for instance) it boots fine!
Its a similar story with the EFI DEBUG file - for this, just extract the contents to an empty folder and then drag and drop the folder onto the MPI_FAT32 shortcut. Then you can boot the .imgPTN file (but it doesn't seem to like booting with Clover - you must UEFI-boot from a UEFI system).
Something odd is going on when 7zip upacks the images. When you use the rescue.img file with MPI_FAT32 you get a 0.img file inside the .imgPTN file instead of it extracting the files!
However, if you copy this 0.img file and place it on the E2B partition at \_ISO\LINUX (for instance) it boots fine!
Its a similar story with the EFI DEBUG file - for this, just extract the contents to an empty folder and then drag and drop the folder onto the MPI_FAT32 shortcut. Then you can boot the .imgPTN file (but it doesn't seem to like booting with Clover - you must UEFI-boot from a UEFI system).
SteveSi
04/05/2016
Re: Re: Unable to boot sedutil *.img images
Hi again,
I confirm, odd things happens when extracting the both images by 7zip., it seems that there is some bug in 7zip or the images are corrupted in some way or there is some conflict between 7zip and the images.
I extracted both images by 7zip but at the end of the both extractions I got:
"Warning: there are some data after the end of the payload data" for Rescue image and
"Unexpected end of data" for EFI Debug image.
However, I followed your workarounds and both image are booting this way.
Thanks.
Best Regs
I confirm, odd things happens when extracting the both images by 7zip., it seems that there is some bug in 7zip or the images are corrupted in some way or there is some conflict between 7zip and the images.
I extracted both images by 7zip but at the end of the both extractions I got:
"Warning: there are some data after the end of the payload data" for Rescue image and
"Unexpected end of data" for EFI Debug image.
However, I followed your workarounds and both image are booting this way.
Thanks.
Best Regs
Marcinoo
04/05/2016
XP not in C drive
Hi.
After successfully installing XP to my Win 7 laptop, all is well, except I have some old software that has to be installed to drive C: - but C is a small system partition and XP is in a partition called D.
Is there a way to get the XP to be in C: not D:
Hope that makes sense!
After successfully installing XP to my Win 7 laptop, all is well, except I have some old software that has to be installed to drive C: - but C is a small system partition and XP is in a partition called D.
Is there a way to get the XP to be in C: not D:
Hope that makes sense!
Graham
03/05/2016
Re: XP not in C drive
I don't think you can change it (at least not easily and without some risk of it not booting again!).
I would re-order the partitions and then re-install XP.
http://www.computing.net/answers/windows-xp/rename-drive-letter-on-xp-installation/196484.html
OR
hide the first small partition (e.g. set to Type=27hex or 17hex instead of 07hex if NTFS) and then delete the large ptn and reformat it. Then *reboot* to XP Setup and install to the large ptn (which is the only one XP should see).
Also, make sure you boot using the BIOS Boot Selection Pop-Up box, do not set the E2B USB drive as the first hard disk in the BIOS.
I would re-order the partitions and then re-install XP.
http://www.computing.net/answers/windows-xp/rename-drive-letter-on-xp-installation/196484.html
OR
hide the first small partition (e.g. set to Type=27hex or 17hex instead of 07hex if NTFS) and then delete the large ptn and reformat it. Then *reboot* to XP Setup and install to the large ptn (which is the only one XP should see).
Also, make sure you boot using the BIOS Boot Selection Pop-Up box, do not set the E2B USB drive as the first hard disk in the BIOS.
SteveSi
03/05/2016
Re: Re: XP not in C drive
Thanks for the reply!
The weird thing is, when I boot into Win7, the 300MB System partition is there, but it has no drive letter allocated, so Win 7 in in C: .... When I boot XP, the Win 7 partition appears as F:, the system partition appears as C instead of no letter.
Previously, the machine dual booted Win7 32 or 64 bit, in both cases the booted partition appeared as C. I wonder if there's something in the MBR that controls this?
The weird thing is, when I boot into Win7, the 300MB System partition is there, but it has no drive letter allocated, so Win 7 in in C: .... When I boot XP, the Win 7 partition appears as F:, the system partition appears as C instead of no letter.
Previously, the machine dual booted Win7 32 or 64 bit, in both cases the booted partition appeared as C. I wonder if there's something in the MBR that controls this?
Graham
03/05/2016
Re: Re: Re: XP not in C drive
What partition type is the 300MB system partition? Is it hidden? If it is set as the Active partition then maybe XP assumes that it is the system partition? If you set the larger boot partition as Active, then installed XP and then changed it back so the 300MB ptn was active (and re-installed your boot manager), it would be happy?
SteveSi
03/05/2016
Re: Re: Re: Re: XP not in C drive
Good thoughts, thank you.. I'll have a poke around. At first I thought it was a quirk of e2b, or rmprepusb, but then Win 7 would likely be the same. Ideally I'd get rid of that partition, but re-installing W7 would be a nightmare, so much installed software....
Graham
03/05/2016
Re: Re: Re: Re: Re: XP not in C drive
XP Setup tells you what drive letter it is going to use. So only start the install if it says C:.
SteveSi
03/05/2016
Re: Re: Re: Re: Re: Re: XP not in C drive
Can I assign a drive letter via e2b? As when I create the partition I'm in win7, and that already uses drive C. I actually told it not to assign a drive letter, but I've never been convinced Windows pays attention to that.
Meanwhile, the boot manager entries are:
Entry #1
Name: Windows 7
BCD ID: {current}
Drive: C:\
Bootloader Path: \windows\system32\winload.exe
Entry #2
Name: Microsoft Windows XP
BCD ID: {e7ae09f6-96a4-11e0-ae57-d033c0a160e3}
Device: \Device\HarddiskVolume1
Bootloader Path: \NST\ntldr
... does the device: setting come from e2b? If I could alter that to match the Win7 entry it may also work?
Meanwhile, the boot manager entries are:
Entry #1
Name: Windows 7
BCD ID: {current}
Drive: C:\
Bootloader Path: \windows\system32\winload.exe
Entry #2
Name: Microsoft Windows XP
BCD ID: {e7ae09f6-96a4-11e0-ae57-d033c0a160e3}
Device: \Device\HarddiskVolume1
Bootloader Path: \NST\ntldr
... does the device: setting come from e2b? If I could alter that to match the Win7 entry it may also work?
Graham
03/05/2016
Re: Re: Re: Re: Re: Re: Re: XP not in C drive
Ok, so it seems Win7 creates a small hidden partition for it's boot stuff, and to allow for bitlocker.
Win XP can't boot from an un-lettered partition.
So, I either have to delete the system partition, or try and symlink C: to D: in Xp...
http://www.sevenforums.com/tutorials/71363-system-reserved-partition-delete.html
Win XP can't boot from an un-lettered partition.
So, I either have to delete the system partition, or try and symlink C: to D: in Xp...
http://www.sevenforums.com/tutorials/71363-system-reserved-partition-delete.html
Graham
04/05/2016
Re: Re: Re: Re: Re: Re: Re: Re: XP not in C drive
So, I fixed this.. Hope it will help someone else too!
I removed the small system partiton as per this process:
https://www.terabyteunlimited.com/kb/article.php?id=409
Thanks for helping!
I removed the small system partiton as per this process:
https://www.terabyteunlimited.com/kb/article.php?id=409
Thanks for helping!
Graham
04/05/2016
Boot XP VHD from bootmgr blog post.
Hi Steve.
Very interesting post. I've seen that approach before being used in Sergei Strelec's DOS section of his distros, for booting different ISOs, IMGs, etc, from a bootmgr menu, but didn't know how those .MBR files (which seem to contain grldr + corresponding boot commands) where generated.
According to your blog post, .MBR files act as the the grldr written to the MBR in our E2B drives, but also includes info about the correct ANGx file to load. And the ANGx files would be the equivalent of grldr at E2B root, but including custom boot command for each payload.
On SS distros, only .MBR + payload pairs are used, there aren't multiple ANGx equivalents at distro root or elsewhere. So my question is: are the .MBR files (as created by EasyBCD) actually required as the entry point in BCD? Could the BCD entry simply point to the ANGx file of choice?
Very interesting post. I've seen that approach before being used in Sergei Strelec's DOS section of his distros, for booting different ISOs, IMGs, etc, from a bootmgr menu, but didn't know how those .MBR files (which seem to contain grldr + corresponding boot commands) where generated.
According to your blog post, .MBR files act as the the grldr written to the MBR in our E2B drives, but also includes info about the correct ANGx file to load. And the ANGx files would be the equivalent of grldr at E2B root, but including custom boot command for each payload.
On SS distros, only .MBR + payload pairs are used, there aren't multiple ANGx equivalents at distro root or elsewhere. So my question is: are the .MBR files (as created by EasyBCD) actually required as the entry point in BCD? Could the BCD entry simply point to the ANGx file of choice?
Starla
28/04/2016
Re: Boot XP VHD from bootmgr blog post.
If it was possible, then there would be no need for the mbr file!
The mbr file is just the same as the boot mbr+first 20 sectors which searches for grldr. They have modified it so it searches for ang0. Ang0 is just grldr but with an embedded menu which loads the payload.
The mbr file is just the same as the boot mbr+first 20 sectors which searches for grldr. They have modified it so it searches for ang0. Ang0 is just grldr but with an embedded menu which loads the payload.
Stevesi
28/04/2016
Strelec WinPE WinPE8 x86 WinPE10 x64 06.06.2016
Hey Starla & Steve. Reboot.Pro isn't allowing me to validate my registration email today so I'll go ahead and post this here instead.
I'm having some difficulty getting the latest Strelec (WinPE8 x86 WinPE10 x64) 06.06.2016 to work with my Easy2Boot as an .imgPTN.
I have a UASP mSATA drive in a USB 3 enclosure that's working great for the Win7 & Win10 .imgPTN I have on it. However, when I attempt to boot the Strelec .imgPTN on either PC I have I just get "an operating system wasn't found." I've attempted it as NTFS & Fat32. No change. Also Easy2Boot prompts as follows near the end of the .imgPTN creation.
INFORMATION: LABEL occurs in .LST files
UUID should use F694-A790
CDLABEL should be LABEL
LABEL should use EASY2BOOT
'media=cdrom' should be 'media=usb'
AUTO-CORRECT these? ([Y]/N) :
Whether I select autocorrect or not, still no luck with booting it.
Strelec's boot disc is in the list of tested payload files (it says to do it as FAT32 .imgPTN) however I'm guessing that was previous version???
I didn't pick up on anything in the FAQ, sample menu files, or forum thread on Easy2Boot.com that may help me to figure this out.
The latest Strelec works great with a USB flash drive...albeit mind numbingly slow compared to my high 4k iops mSata. Any ideas how I might debug this???
I'm pretty sure the ISO file extensions would only work if I was using a USB flash drive...even so I tried .isope01 without any luck. Should I try .isowinvh or .isoask or is that a waste of time like I think it would be???
I'm having some difficulty getting the latest Strelec (WinPE8 x86 WinPE10 x64) 06.06.2016 to work with my Easy2Boot as an .imgPTN.
I have a UASP mSATA drive in a USB 3 enclosure that's working great for the Win7 & Win10 .imgPTN I have on it. However, when I attempt to boot the Strelec .imgPTN on either PC I have I just get "an operating system wasn't found." I've attempted it as NTFS & Fat32. No change. Also Easy2Boot prompts as follows near the end of the .imgPTN creation.
INFORMATION: LABEL occurs in .LST files
UUID should use F694-A790
CDLABEL should be LABEL
LABEL should use EASY2BOOT
'media=cdrom' should be 'media=usb'
AUTO-CORRECT these? ([Y]/N) :
Whether I select autocorrect or not, still no luck with booting it.
Strelec's boot disc is in the list of tested payload files (it says to do it as FAT32 .imgPTN) however I'm guessing that was previous version???
I didn't pick up on anything in the FAQ, sample menu files, or forum thread on Easy2Boot.com that may help me to figure this out.
The latest Strelec works great with a USB flash drive...albeit mind numbingly slow compared to my high 4k iops mSata. Any ideas how I might debug this???
I'm pretty sure the ISO file extensions would only work if I was using a USB flash drive...even so I tried .isope01 without any luck. Should I try .isowinvh or .isoask or is that a waste of time like I think it would be???
Rangle_Newfangle
26/08/2016
Re: Strelec WinPE WinPE8 x86 WinPE10 x64 06.06.2016
I drag-and-dropped the SS 06.06.2016 ISO onto the MPI_FAT32 desktop shortcut and the .imgPTN seems to work OK for me.
If you boot it as an ISO from a fixed disk, you will need to use ImDisk to mount the ISO file as a virtual CD and then click on the blue MInstall icon in the bottom task bar.
If you boot it as an ISO from a fixed disk, you will need to use ImDisk to mount the ISO file as a virtual CD and then click on the blue MInstall icon in the bottom task bar.
SteveSi
10/09/2016
error 13 for ancient Linux
Hello to everybody!
My problem is:
Error 13:(http://grub4dos.chenall.net/e/13)
Invalid or unsupported executable format
I have very ancient RedHat of 2002 year (Linux 2.4.10). It works good.
Now I need to make bootable USB-device with this system.
I have made all the instructions from here:
http://www.easy2boot.com/make-an-easy2boot-usb-drive/
but I have this error message about error 13.
FAQ sais:
This usually means your payload file (.ISO, .IMA, etc) was not bootable or it is corrupt.
Some Windows ISOs are upgrade CDs or DVDs and are not bootable - they are designed to run
from within Windows.
I have tried simple DD-image from my partition /boot
and ISO-image made by "mkisofs" - error 13 both.
Please, help!
Thanks.
My problem is:
Error 13:(http://grub4dos.chenall.net/e/13)
Invalid or unsupported executable format
I have very ancient RedHat of 2002 year (Linux 2.4.10). It works good.
Now I need to make bootable USB-device with this system.
I have made all the instructions from here:
http://www.easy2boot.com/make-an-easy2boot-usb-drive/
but I have this error message about error 13.
FAQ sais:
This usually means your payload file (.ISO, .IMA, etc) was not bootable or it is corrupt.
Some Windows ISOs are upgrade CDs or DVDs and are not bootable - they are designed to run
from within Windows.
I have tried simple DD-image from my partition /boot
and ISO-image made by "mkisofs" - error 13 both.
Please, help!
Thanks.
torrvic
16/04/2016
Re: error 13 for ancient Linux
Do you mean you have an installed system running Linux (or a Linux 2.4.10 ISO?).
If a live system, what partitions does it have (swap, etc.). You cannot just make an ISO from a live system and expect it to boot! You could maybe try clonezilla to copy the live system to a fresh USB drive. You may have to re-install grub to the USB drive to get it to boot.
If a live system, what partitions does it have (swap, etc.). You cannot just make an ISO from a live system and expect it to boot! You could maybe try clonezilla to copy the live system to a fresh USB drive. You may have to re-install grub to the USB drive to get it to boot.
SteveSi
16/04/2016
Re: Re: error 13 for ancient Linux
Yes, it is installed system running Linux. Partitions: "/boot", "/" and "swap".
I made ISO-image by command "mkisofs" from "/dev/hdb1" (/boot).
I looked in image by command "od -x rh24boot.iso | more" and saw: first 512 bytes are not zeroes.
(But in DD-image they are zeroes.)
I tried make my own MBR:
1). copy first 512 bytes of "/dev/hdb" (not "/dev/hdb1" !)
2). combined MBR: 446 bytes from Linux (loader) and Partiton Tables from Windows where I have
"easy2boot".
I have the same results: error 13.
May be I understand wrong, (please tell me about it), but I think:
old BIOS-es did not have interruption for reading from USB-devices, due of that old kernels
did not have calls to it,
old kernels (at the first stage of booting) call only BIOS-interruption for reading from
hard disk, therefore they can not mount partitions, can not do anything with USB-device.
I think "easy2boot" makes this job instead Linux-kernel. If I am wrong?
Thanks.
I made ISO-image by command "mkisofs" from "/dev/hdb1" (/boot).
I looked in image by command "od -x rh24boot.iso | more" and saw: first 512 bytes are not zeroes.
(But in DD-image they are zeroes.)
I tried make my own MBR:
1). copy first 512 bytes of "/dev/hdb" (not "/dev/hdb1" !)
2). combined MBR: 446 bytes from Linux (loader) and Partiton Tables from Windows where I have
"easy2boot".
I have the same results: error 13.
May be I understand wrong, (please tell me about it), but I think:
old BIOS-es did not have interruption for reading from USB-devices, due of that old kernels
did not have calls to it,
old kernels (at the first stage of booting) call only BIOS-interruption for reading from
hard disk, therefore they can not mount partitions, can not do anything with USB-device.
I think "easy2boot" makes this job instead Linux-kernel. If I am wrong?
Thanks.
torrvic
19/04/2016
Re: Re: Re: error 13 for ancient Linux
AFAIK, you cannot easily make an ISO from a fully installed linux OS. What you are trying to do will not work (maybe you can find instructions on the internet). A full OS expects to be booting from a rd/wr disk of some sort, not a cd.
You may be able to make a .imgPTN file from the installed OS, but not an ISO. Sorry.
You may be able to make a .imgPTN file from the installed OS, but not an ISO. Sorry.
SteveSi
20/04/2016
Re: Re: Re: Re: error 13 for ancient Linux
Thank you for the hint about ".imgPTN" file.
I made it by program "MakePartImage.cmd" from the tool "MPI_Tool_Pack_Plus_CloverLite_064".
I made all strongly with instructions from ReadMe.txt file. Result was: successfully!
Then I have copied it to my USB-drive in the folder "_ISO\MAIN_MENU".
It's name is "rh24b-mkisofs.imgPTN".
When rebooting from my USB-device and selecting my image I have the message:
"(hd0,0) rh24b-mkisofs.imgPTN
WARNING: THIS E2B DRIVE'S PARTITION TABLE IS ABOUT OVERWRITEN!
..............................................................
..............................................................
INFORMATION: *** NO UEFI BOOT FILES IN FIRST PARTITION ***
To boot using UEFI, reboot and select the UEFI:xxxx boot option from your UEFI boot menu.
To switch back to Easy2Boot, boot in non-UEFI mode (Legacy or CSM Mode)
and select the Easy2Boot menu option.
(OPTIONS: a=Make-Active, LBA=Adjust-LBA)
OK to replace the E2B partitions ([Y]/N): "
I am surprised why "hd0,0"? May be "hd1,0"?
I am very surprised why E2B wants to overwrite my Partition Table !
BIOS of my computer is enough old and has not UEFI mode.
If I answer "N" I return back to E2B menu.
If I answer "Y" I get another message:
"Easy2Boot CSM Menu (v0.63) (UUID=..................)
rh24b-mkisofs
0 EASY2BOOT - switch back to Easy2Boot menu
1 BOOT from this drive (MBR mode)
2 Boot from internal Hard Disk [F7]
3 Rebbot [F9]
4 Shutdown [F10]"
The Line "1 BOOT from this drive (MBR mode)" is highlighted.
If I press "Enter" I get the next message:
"BOOTMGR is missing
Press Ctrl+Alt+Del to restart"
I tried this for FAT32, NTFS and ExFat -the same result.
Please, tell me what I do wrong?
Thanks.
I made it by program "MakePartImage.cmd" from the tool "MPI_Tool_Pack_Plus_CloverLite_064".
I made all strongly with instructions from ReadMe.txt file. Result was: successfully!
Then I have copied it to my USB-drive in the folder "_ISO\MAIN_MENU".
It's name is "rh24b-mkisofs.imgPTN".
When rebooting from my USB-device and selecting my image I have the message:
"(hd0,0) rh24b-mkisofs.imgPTN
WARNING: THIS E2B DRIVE'S PARTITION TABLE IS ABOUT OVERWRITEN!
..............................................................
..............................................................
INFORMATION: *** NO UEFI BOOT FILES IN FIRST PARTITION ***
To boot using UEFI, reboot and select the UEFI:xxxx boot option from your UEFI boot menu.
To switch back to Easy2Boot, boot in non-UEFI mode (Legacy or CSM Mode)
and select the Easy2Boot menu option.
(OPTIONS: a=Make-Active, LBA=Adjust-LBA)
OK to replace the E2B partitions ([Y]/N): "
I am surprised why "hd0,0"? May be "hd1,0"?
I am very surprised why E2B wants to overwrite my Partition Table !
BIOS of my computer is enough old and has not UEFI mode.
If I answer "N" I return back to E2B menu.
If I answer "Y" I get another message:
"Easy2Boot CSM Menu (v0.63) (UUID=..................)
rh24b-mkisofs
0 EASY2BOOT - switch back to Easy2Boot menu
1 BOOT from this drive (MBR mode)
2 Boot from internal Hard Disk [F7]
3 Rebbot [F9]
4 Shutdown [F10]"
The Line "1 BOOT from this drive (MBR mode)" is highlighted.
If I press "Enter" I get the next message:
"BOOTMGR is missing
Press Ctrl+Alt+Del to restart"
I tried this for FAT32, NTFS and ExFat -the same result.
Please, tell me what I do wrong?
Thanks.
torrvic
27/04/2016
Re: Re: Re: Re: Re: error 13 for ancient Linux
As I said, you need a bootable source. You can't just copy some files from a partition and expect it to boot.
Via what mechanism did the redhat system boot? Syslinux, grub, grub2? Do you have the boot files in the source?
Via what mechanism did the redhat system boot? Syslinux, grub, grub2? Do you have the boot files in the source?
SteveSi
27/04/2016
Re: Re: Re: Re: Re: Re: error 13 for ancient Linux
In the source I have partition /boot with all files: vmlinux-2.4.7-10, etc.
I have the directory "grub" with all files: grub.conf, etc.
The version of grub is 0.90.
I think "mkisofs" doesn't make simple copy.
I looked in image by command "od -x rh24b-mkisofs.iso | more" and saw: first 446 bytes are not zeroes.
(But in DD-image they are zeroes. Command "dd" makes just a copy.)
File "rh24b-mkisofs.imgPTN" was made from this source: "rh24b-mkisofs.iso".
Do you mean I should make the .imgPTN from "/dev/hdb1", not from file "rh24b-mkisofs.iso"?
I have the directory "grub" with all files: grub.conf, etc.
The version of grub is 0.90.
I think "mkisofs" doesn't make simple copy.
I looked in image by command "od -x rh24b-mkisofs.iso | more" and saw: first 446 bytes are not zeroes.
(But in DD-image they are zeroes. Command "dd" makes just a copy.)
File "rh24b-mkisofs.imgPTN" was made from this source: "rh24b-mkisofs.iso".
Do you mean I should make the .imgPTN from "/dev/hdb1", not from file "rh24b-mkisofs.iso"?
torrvic
28/04/2016
Re: Re: Re: Re: Re: Re: error 13 for ancient Linux
You said: "... you cannot easily make an ISO from a fully installed linux OS."
Now I have found the source of this distro:
http://archive.download.redhat.com/pub/redhat/linux/7.2/es/iso/i386/
May be it would be more easy way?
But there are two ISO files here... I have burned them to CDs. What should I do with them
to get a bootable USB-device? (If I simply copy them to the subdirectory _ISO\LINUX
I get installation USB-device, but I need not installation USB-device, I need bootable.)
In the other words I wish now to make LiveCD USB-device.
Thanks.
Now I have found the source of this distro:
http://archive.download.redhat.com/pub/redhat/linux/7.2/es/iso/i386/
May be it would be more easy way?
But there are two ISO files here... I have burned them to CDs. What should I do with them
to get a bootable USB-device? (If I simply copy them to the subdirectory _ISO\LINUX
I get installation USB-device, but I need not installation USB-device, I need bootable.)
In the other words I wish now to make LiveCD USB-device.
Thanks.
torrvic
30/04/2016
Re: Re: Re: Re: Re: Re: Re: error 13 for ancient Linux
Can you not find a LiveCD version?
If you only have the Install CD, then I suggest you install to a spare USB flash drive, but to a single partition with no swap partition (i.e. \ root and \boot on same partition on USB drive). Use FAT32.
Then you can make an imgptn FAT32 file from the flash drive and put the .imgPTN file on your E2B drive.
If you only have the Install CD, then I suggest you install to a spare USB flash drive, but to a single partition with no swap partition (i.e. \ root and \boot on same partition on USB drive). Use FAT32.
Then you can make an imgptn FAT32 file from the flash drive and put the .imgPTN file on your E2B drive.
SteveSi
30/04/2016
Re: Re: Re: Re: Re: error 13 for ancient Linux
got the fix
www.deskdecode.com/how-to-fix-bootmgr-is-missing-error-on-windows-desktop-or-laptop/
www.deskdecode.com/how-to-fix-bootmgr-is-missing-error-on-windows-desktop-or-laptop/
kinjo
02/07/2016
Suggestion: add Option to clear/empty keyboard buffer before showing MAIN MENU?
I'm afraid I annoy you by too many posts/suggestions...
Your package is best that can be found, that's why I'm here and not on other site.
(I know about 7-8 programs that make bootable USB drives (I tested only the old XBOOT)
I don't like those that can put only one "thing" on the USB (and waste the entire drive for e.g. 100MB)
I don't like those that extract files because: 1) to copy 100s of small files to an old slow USB flash is just ... very slow; 2) extracted ISO usually prevents using several versions of the "same" ISO)
So, if you are still not (very) annoyed:
Suggestion: add Option to clear/empty keyboard buffer before showing the MAIN MENU
(or do we already have that Option?)
Maybe only when the MAIN MENU is first shown?
_____________________
What happened: during an experiment with Animated_BritneyLZMA I "accidentally" hit [Enter] several times and that sequence was executed (one of the ISO started) after showing the MAIN MENU
I start the Animated_BritneyLZMA from my real MyE2B.cfg by:
!BAT
call /_ISO/docs/BritneyLZMA/BritneyLZMA2.cfg
set GMODE=800
........
Since this was running very slow on QEMU I attempted to cancel it (sorry, I didn't read the code in detail) by [Esc] [Space] [Enter]
in QEMU (I still don't find a time to try VirtualBox + VMUB despite I Downloaded them a week ago):
Can the Animate be cancelled/skipped?
Can the picture be centred (it is in top-left for me)?
I see yellow vertical line of 1-2 pixels wide at the right of the small pictures (like big text cursor?), is this supposed to happen?
Your package is best that can be found, that's why I'm here and not on other site.
(I know about 7-8 programs that make bootable USB drives (I tested only the old XBOOT)
I don't like those that can put only one "thing" on the USB (and waste the entire drive for e.g. 100MB)
I don't like those that extract files because: 1) to copy 100s of small files to an old slow USB flash is just ... very slow; 2) extracted ISO usually prevents using several versions of the "same" ISO)
So, if you are still not (very) annoyed:
Suggestion: add Option to clear/empty keyboard buffer before showing the MAIN MENU
(or do we already have that Option?)
Maybe only when the MAIN MENU is first shown?
_____________________
What happened: during an experiment with Animated_BritneyLZMA I "accidentally" hit [Enter] several times and that sequence was executed (one of the ISO started) after showing the MAIN MENU
I start the Animated_BritneyLZMA from my real MyE2B.cfg by:
!BAT
call /_ISO/docs/BritneyLZMA/BritneyLZMA2.cfg
set GMODE=800
........
Since this was running very slow on QEMU I attempted to cancel it (sorry, I didn't read the code in detail) by [Esc] [Space] [Enter]
in QEMU (I still don't find a time to try VirtualBox + VMUB despite I Downloaded them a week ago):
Can the Animate be cancelled/skipped?
Can the picture be centred (it is in top-left for me)?
I see yellow vertical line of 1-2 pixels wide at the right of the small pictures (like big text cursor?), is this supposed to happen?
BilBg
07/04/2016
Re: Suggestion: add Option to clear/empty keyboard buffer before showing MAIN MENU?
re. SoakKeys - It is a feature of E2B that whilst it is booting, you can press a key (e.g. Ctrl-I) and it will jump to the next menu. If I add SoakKeys code, then this will not be possible. You can add the code yourself if you wish (I can tell you how).
re. Animation- if you have it set as 'play' rather than 'infinite' then you cannot abort it.
The position can be changed by specifying a different offx/offy position.
Britney is not a very 'clean' animation in transparent mode, you may see some odd pixels around the edges. Try DNA animation.
re. Animation- if you have it set as 'play' rather than 'infinite' then you cannot abort it.
The position can be changed by specifying a different offx/offy position.
Britney is not a very 'clean' animation in transparent mode, you may see some odd pixels around the edges. Try DNA animation.
SteveSi
09/04/2016
Re: Re: Suggestion: add Option to clear/empty keyboard buffer before showing MAIN MENU?
Here is the contents of a SoakKeys.g4b batch file
!BAT
# soak up any previous key presses
:loopk
# Check for key in BIOS keyboard buffer
call Fn.20
# Call Fn. 19 to get the key character if present
if not %@retval%==-1 call Fn.19 && goto :loopk
I will include \_ISO\e2b\grub\SoakKeys.g4b in the next version of E2B. To use it, add
call /_ISO/e2b/grub/SoakKeys.g4b
anywhere that you want all key presses to be absorbed (e.g. after an animation 'play' command).
!BAT
# soak up any previous key presses
:loopk
# Check for key in BIOS keyboard buffer
call Fn.20
# Call Fn. 19 to get the key character if present
if not %@retval%==-1 call Fn.19 && goto :loopk
I will include \_ISO\e2b\grub\SoakKeys.g4b in the next version of E2B. To use it, add
call /_ISO/e2b/grub/SoakKeys.g4b
anywhere that you want all key presses to be absorbed (e.g. after an animation 'play' command).
SteveSi
09/04/2016
Sample_MyE2B.cfg - not commented line
in Sample_MyE2B.cfg this line have no #
GMODE is set in the lines above - run graphicsmode before splashimage
GMODE is set in the lines above - run graphicsmode before splashimage
BilBg
06/04/2016
Re: Sample_MyE2B.cfg - not commented line
Thanks - will fix in next 1.80c
SteveSi
06/04/2016
FASTLOAD bug in new Easy2Boot versions (v1.78h is OK, v1.79 have the bug)
I think this bug was introduced when NOWINXP checks were implemented.
I don't set NOWINXP - while v1.79 is "installed" I searched for string NOWINXP all the files < 1 MB on the USB (using Total Commander) and the only 2 are:
U:\_ISO\e2b\grub\MenuWinInstall.lst
U:\_ISO\Sample_MyE2B.cfg
Reproduce:
1) install Easy2Boot v1.79 (final) (UPDATE_E2B_DRIVE.CMD)
2) put one ISO in \_ISO\WINDOWS\XP\ (no other ISOs in any \_ISO\WINDOWS\ subdirectory), e.g.:
Windows_XP_Professional_SP3_Nov_2013_Incl_SATA_Drivers.iso
3) boot from USB (I used QEMU_MENU_TEST (run as admin).cmd)
4) Enable FASTLOAD
5) Rebuild Main Menu [F8]
Observe how "WINDOWS INSTALL Menu [Ctrl+I]" is shown
The Bug:
6) Reboot [F9]
"WINDOWS INSTALL Menu [Ctrl+I]" disappears
Notes:
Easy2Boot_v1.78h do not have the bug
in Easy2Boot_v1.78h\_ISO\e2b\grub\menu.lst is this line which is deleted in menu.lst of v1.79 (I don't know if this is the cause of bug):
# add Windows counts to menu for FASTLOAD
if not exist WINCOUNT if exist /FASTLOAD.YES echo -e iftitle [set CALL=%CALL% \&\& set CXP=%CXP% \&\& set CV=%CV% \&\& set C7=%C7% \&\& set C8=%C8% \&\& set C28=%C28% \&\& set C12=%C12% \&\& set C10=%C10% \&\& if 1=0] dummy\nboot\n >> (md)0x3000+0x50
I don't set NOWINXP - while v1.79 is "installed" I searched for string NOWINXP all the files < 1 MB on the USB (using Total Commander) and the only 2 are:
U:\_ISO\e2b\grub\MenuWinInstall.lst
U:\_ISO\Sample_MyE2B.cfg
Reproduce:
1) install Easy2Boot v1.79 (final) (UPDATE_E2B_DRIVE.CMD)
2) put one ISO in \_ISO\WINDOWS\XP\ (no other ISOs in any \_ISO\WINDOWS\ subdirectory), e.g.:
Windows_XP_Professional_SP3_Nov_2013_Incl_SATA_Drivers.iso
3) boot from USB (I used QEMU_MENU_TEST (run as admin).cmd)
4) Enable FASTLOAD
5) Rebuild Main Menu [F8]
Observe how "WINDOWS INSTALL Menu [Ctrl+I]" is shown
The Bug:
6) Reboot [F9]
"WINDOWS INSTALL Menu [Ctrl+I]" disappears
Notes:
Easy2Boot_v1.78h do not have the bug
in Easy2Boot_v1.78h\_ISO\e2b\grub\menu.lst is this line which is deleted in menu.lst of v1.79 (I don't know if this is the cause of bug):
# add Windows counts to menu for FASTLOAD
if not exist WINCOUNT if exist /FASTLOAD.YES echo -e iftitle [set CALL=%CALL% \&\& set CXP=%CXP% \&\& set CV=%CV% \&\& set C7=%C7% \&\& set C8=%C8% \&\& set C28=%C28% \&\& set C12=%C12% \&\& set C10=%C10% \&\& if 1=0] dummy\nboot\n >> (md)0x3000+0x50
BilBg
06/04/2016
Re: FASTLOAD bug in new Easy2Boot versions (v1.78h is OK, v1.79 have the bug)
Yes, somehow those two lines got deleted!
Try putting them back in and see if that fixes the problem.
Try putting them back in and see if that fixes the problem.
SteveSi
06/04/2016
Re: Re: FASTLOAD bug in new Easy2Boot versions (v1.78h is OK, v1.79 have the bug)
Don't test using QEMU_TEST because writes don't work very well. Use VBox+VMUB or a real system.
SteveSi
06/04/2016
Re: Re: Re: FASTLOAD bug in new Easy2Boot versions (v1.78h is OK, v1.79 have the bug)
In this case they are OK
I compared the generated FASTLOAD.MNU from v1.78h and v1.79 - they are different:
v1.78h:
..............
password --md5 $1$1$okAQ3AJUdhqf3TVrwKvJP1
debug 0
set MFOLDER=/_ISO/MAINMENU
#SS
default 1
timeout -1
iftitle [set CALL=1 && set CXP=1 && set CV=0 && set C7=0 && set C8=0 && set C28=0 && set C12=0 && set C10=0 && if 1=0] dummy
boot
set MFOLDER=/_ISO/MAINMENU
..............
v1.79:
..............
password --md5 $1$1$okAQ3AJUdhqf3TVrwKvJP1
debug 0
set MFOLDER=/_ISO/MAINMENU
#menu_defaults.txt
default 1
timeout -1
set MFOLDER=/_ISO/MAINMENU
..............
I compared the generated FASTLOAD.MNU from v1.78h and v1.79 - they are different:
v1.78h:
..............
password --md5 $1$1$okAQ3AJUdhqf3TVrwKvJP1
debug 0
set MFOLDER=/_ISO/MAINMENU
#SS
default 1
timeout -1
iftitle [set CALL=1 && set CXP=1 && set CV=0 && set C7=0 && set C8=0 && set C28=0 && set C12=0 && set C10=0 && if 1=0] dummy
boot
set MFOLDER=/_ISO/MAINMENU
..............
v1.79:
..............
password --md5 $1$1$okAQ3AJUdhqf3TVrwKvJP1
debug 0
set MFOLDER=/_ISO/MAINMENU
#menu_defaults.txt
default 1
timeout -1
set MFOLDER=/_ISO/MAINMENU
..............
BilBg
06/04/2016
Re: Re: Re: Re: FASTLOAD bug in new Easy2Boot versions (v1.78h is OK, v1.79 have the bug)
Try v1.80b in Alternate Download Area
SteveSi
06/04/2016
Re(5): FASTLOAD bug in new Easy2Boot versions (v1.78h is OK, v1.79 have the bug)
Yes, v1.80b is OK
(Was this affecting only XP or all Windows?)
I can only guess what happened for the 2 lines to disappear - maybe you used Ctrl+X to move the lines up/down and then forget about it (no Ctrl+V)
Phone-call? ;)
(Was this affecting only XP or all Windows?)
I can only guess what happened for the 2 lines to disappear - maybe you used Ctrl+X to move the lines up/down and then forget about it (no Ctrl+V)
Phone-call? ;)
BilBg
07/04/2016
Re: Re(5): FASTLOAD bug in new Easy2Boot versions (v1.78h is OK, v1.79 have the bug)
Don't know how it happened (maybe WinMerge accident??). Yes, it would affect all Windows Install menu entries, not just XP.
SteveSi
07/04/2016
MPI_Tool_Pack - MakePartImage.cmd fails in rare (my) case
in MakePartImage.cmd , line:
for %%a in (U T S R Q P O N M L K I H G F E D) do (
- is there a special reason to omit J and V W X Y Z in search for a free drive letter?
In my case the only free drive letters are V W Z so the above fails with:
"Can't find an spare driveletter to mount RAMDRIVE on."
(3 HDDs (c-i, x, y), DVD j, Alcohol 120% (k-t), USB flash (u) = free are V W Z)
I changed the line and .imgPTN was created OK using V as the first found free:
for %%a in (U T S R Q P O N M L K J I H G F E D V W X Y Z) do (
for %%a in (U T S R Q P O N M L K I H G F E D) do (
- is there a special reason to omit J and V W X Y Z in search for a free drive letter?
In my case the only free drive letters are V W Z so the above fails with:
"Can't find an spare driveletter to mount RAMDRIVE on."
(3 HDDs (c-i, x, y), DVD j, Alcohol 120% (k-t), USB flash (u) = free are V W Z)
I changed the line and .imgPTN was created OK using V as the first found free:
for %%a in (U T S R Q P O N M L K J I H G F E D V W X Y Z) do (
BilBg
04/04/2016
Re: MPI_Tool_Pack - MakePartImage.cmd fails in rare (my) case
Missing J was an oversight
I omitted VWXYZ just because I thought that no one would have more than 20 drives!
I will fix in next version 0.065
I omitted VWXYZ just because I thought that no one would have more than 20 drives!
I will fix in next version 0.065
SteveSi
04/04/2016
What USB 2.0 flash drive works with E2B?
Hi Steve,
What USB 2.0 flash drives have you tested that work with Easy2Boot? I am going to buy a new one but i'm afraid that it could be one of the Windows To Go drives that are recognized as fixed disk by Windows.
What USB 2.0 flash drives have you tested that work with Easy2Boot? I am going to buy a new one but i'm afraid that it could be one of the Windows To Go drives that are recognized as fixed disk by Windows.
Carlos
24/03/2016
Re: What USB 2.0 flash drive works with E2B?
I recommend a SanDisk Cruzer Extreme USB 3.0.
It is removable and compatible with USB 2.0. Fast and reasonably priced with retractable connector (so no cap to lose).
It is removable and compatible with USB 2.0. Fast and reasonably priced with retractable connector (so no cap to lose).
SteveSi
25/03/2016
Bug report - Robocopy 5.1.2600.26 for XP do Not support /MT:1 switch
(This report is only for info - fix only if/as you wish)
Windows XP
Easy2Boot_v1.77A ... 1.79b
Robocopy 5.1.2600.26 (Robocopy GUI 3.1.2.0 - 2006) (I think the last Robocopy for XP)
Robocopy GUI (UtilitySpotlight2006_11.exe) from:
https://technet.microsoft.com/en-us/magazine/2006.11.utilityspotlight.aspx
Before installing: UPDATE_E2B_DRIVE.CMD was working using XCOPY
After installing:
ROBOCOPY.EXE is in D:\WINDOWS\system32\
UPDATE_E2B_DRIVE.CMD gives error about Robocopy fail and exits (do not try to use XCOPY)
To remedy: I just edit the .CMD file to remove /MT:1 so the line for me is:
robocopy "%~dp0\" %USB%:\\ /E /NFL /NDL /NJH /r:2 /w:3 /XF %~nx0 "MAKE_E2B_USB_DRIVE (run as admin).cmd" E2B_ReadMe.txt
Windows XP
Easy2Boot_v1.77A ... 1.79b
Robocopy 5.1.2600.26 (Robocopy GUI 3.1.2.0 - 2006) (I think the last Robocopy for XP)
Robocopy GUI (UtilitySpotlight2006_11.exe) from:
https://technet.microsoft.com/en-us/magazine/2006.11.utilityspotlight.aspx
Before installing: UPDATE_E2B_DRIVE.CMD was working using XCOPY
After installing:
ROBOCOPY.EXE is in D:\WINDOWS\system32\
UPDATE_E2B_DRIVE.CMD gives error about Robocopy fail and exits (do not try to use XCOPY)
To remedy: I just edit the .CMD file to remove /MT:1 so the line for me is:
robocopy "%~dp0\" %USB%:\\ /E /NFL /NDL /NJH /r:2 /w:3 /XF %~nx0 "MAKE_E2B_USB_DRIVE (run as admin).cmd" E2B_ReadMe.txt
BilBg
24/03/2016
Re: Bug report - Robocopy 5.1.2600.26 for XP do Not support /MT:1 switch
Thanks,
The MT:1 is needed for Vista+ because without it we get fragmented files. The Xp version is single-threaded anyway (I think). Most people won't have robocopy in XP and it is MS copyright so I cannot include it in E2B.
The MT:1 is needed for Vista+ because without it we get fragmented files. The Xp version is single-threaded anyway (I think). Most people won't have robocopy in XP and it is MS copyright so I cannot include it in E2B.
SteveSi
24/03/2016
Re: Re: Bug report - Robocopy 5.1.2600.26 for XP do Not support /MT:1 switch
From:
https://technet.microsoft.com/en-us/library/cc733145.aspx
"
/MT[:N]
Creates multi-threaded copies with N threads. N must be an integer between 1 and 128.
The default value for N is 8.
Note
The /MT parameter applies to Windows Server 2008 R2 and Windows 7.
"
So:
1) It seems to me "The default value for N is 8" applies Only if you actually use /MT and omit [:N]
i.e. without /MT on cmdline Robocopy will not "Create multi-threaded copies with 8 threads" (= will just use 1 copy thread)?
2) Are you sure Vista version of Robocopy have /MT switch? ("Note: The /MT parameter applies to Windows Server 2008 R2 and Windows 7")
https://technet.microsoft.com/en-us/library/cc733145.aspx
"
/MT[:N]
Creates multi-threaded copies with N threads. N must be an integer between 1 and 128.
The default value for N is 8.
Note
The /MT parameter applies to Windows Server 2008 R2 and Windows 7.
"
So:
1) It seems to me "The default value for N is 8" applies Only if you actually use /MT and omit [:N]
i.e. without /MT on cmdline Robocopy will not "Create multi-threaded copies with 8 threads" (= will just use 1 copy thread)?
2) Are you sure Vista version of Robocopy have /MT switch? ("Note: The /MT parameter applies to Windows Server 2008 R2 and Windows 7")
BilBg
25/03/2016
Re: Re: Re: Bug report - Robocopy 5.1.2600.26 for XP do Not support /MT:1 switch
No, the default of 8 applies if you do not specify the switch. I found that when I used just Robocopy default switches to copy the files, it produces fragmented files. That is why I had to specify 1.
Maybe also not in Vista (I haven't tested that).
Maybe also not in Vista (I haven't tested that).
SteveSi
25/03/2016
Re(4): Bug report - Robocopy 5.1.2600.26 for XP do Not support /MT:1 switch
In old unused installation of original Vista 32-bit (no SP1) I found Robocopy.exe in the usual place (\Windows\System32\)
It can't start on Windows XP ("Robocopy.exe is not a valid Win32 application.") to use /? but Unicode strings are visible inside the Robocopy.exe (using Total Commander - F3 View)
It also don't have /MT switch
(I don't know how it is on Vista SP1, SP2)
The Properties of the two files (all is Copy/Paste):
XP file:
ROBOCOPY.EXE 212992 22.11.2005 06:14
1bf6e85078ca54fed534afdb436b2ecc *ROBOCOPY.EXE
File version: 5.1.2600.26
Product Version: XP026
Copyright 1995-2005
Vista file:
Robocopy.exe 87040 02.11.2006 11:45
f7a0790ebc72bd740137fa0c12aaf79f *Robocopy.exe
File version: 5.1.10.1027
Product Version: XP027
Copyright 1995-2004
It can't start on Windows XP ("Robocopy.exe is not a valid Win32 application.") to use /? but Unicode strings are visible inside the Robocopy.exe (using Total Commander - F3 View)
It also don't have /MT switch
(I don't know how it is on Vista SP1, SP2)
The Properties of the two files (all is Copy/Paste):
XP file:
ROBOCOPY.EXE 212992 22.11.2005 06:14
1bf6e85078ca54fed534afdb436b2ecc *ROBOCOPY.EXE
File version: 5.1.2600.26
Product Version: XP026
Copyright 1995-2005
Vista file:
Robocopy.exe 87040 02.11.2006 11:45
f7a0790ebc72bd740137fa0c12aaf79f *Robocopy.exe
File version: 5.1.10.1027
Product Version: XP027
Copyright 1995-2004
BilBg
26/03/2016
Re: Re(4): Bug report - Robocopy 5.1.2600.26 for XP do Not support /MT:1 switch
v1.79 should work with the XP version of robocopy now.
SteveSi
01/04/2016
Re(6): Bug report - Robocopy 5.1.2600.26 for XP do Not support /MT:1 switch
:) Yes, v1.79 works (I didn't expected such kind of detection using /? ;) )
BilBg
05/04/2016
Re: Re(6): Bug report - Robocopy 5.1.2600.26 for XP do Not support /MT:1 switch
Yes, it's a nice way to check different versions which I thought of, and I have used it several times before (e.g. checking grub4dos versions).
SteveSi
06/04/2016
Grub4dos dd command
Hi Steve,
You're grub4dos master while i'm new with grub4dos. Please forgive me if my question is a stupid question. Tks
With dd command
dd if=(hd0)30+1 of=(hd0,0)/MBR.BIN
dd if=(hd0)60+1 of=(hd0,0)/MBR.BIN
these command backup grub4dos MBR.
So my question is: grub4dos always locate at (hd0)30 and (hd0)60 ?? Can you explain what (hd0)30 vs 60 mean?
And to backup current PBR, we use
if=()+1 of=()/PBR.BIN
so my question is how can I backup PBR at partition 2?
and some other "special" parameter such as skip= seek= bs= count=
Tks.
You're grub4dos master while i'm new with grub4dos. Please forgive me if my question is a stupid question. Tks
With dd command
dd if=(hd0)30+1 of=(hd0,0)/MBR.BIN
dd if=(hd0)60+1 of=(hd0,0)/MBR.BIN
these command backup grub4dos MBR.
So my question is: grub4dos always locate at (hd0)30 and (hd0)60 ?? Can you explain what (hd0)30 vs 60 mean?
And to backup current PBR, we use
if=()+1 of=()/PBR.BIN
so my question is how can I backup PBR at partition 2?
and some other "special" parameter such as skip= seek= bs= count=
Tks.
thailand_guy
09/03/2016
Re: Grub4dos dd command
http://www.rmprepusb.com/tutorials/grub4dos#TOC-Using-dd-to-edit-sectors
so to back up PBR of ptn 2 use
dd if=(hd0,1)0+1 of=(hd0,0)/PBR2.BIN
but file PBR2.BIN must already exist and be 512 bytes or larger in size.
so to back up PBR of ptn 2 use
dd if=(hd0,1)0+1 of=(hd0,0)/PBR2.BIN
but file PBR2.BIN must already exist and be 512 bytes or larger in size.
SteveSi
09/03/2016
Re: Re: Grub4dos dd command
Dear master,
Your tut is very very detail.
I'll read it carefully.
And another question, from your tut, it say that the best way to install grub4dos for USB is use RMPrepUSB.
After download and use RMprepUSB, i foud that grub4dos is not latest ver, and i replace grldr with grldr from E2B.
But after replace, grub4dos stuck with text say that
grub4dos 0.4.6a 2016-03-03, root is (0x80,0)
Processing the preset menu ....
grub4dos 0.4.6a 2016-03-03, root is (0x80,0)
Processing menu file /menu.lst ....
My menu.lst is very very simple.
If replace it with menu.lst from E2B then it work.
Can you tell me why?
Tks, master.
Your tut is very very detail.
I'll read it carefully.
And another question, from your tut, it say that the best way to install grub4dos for USB is use RMPrepUSB.
After download and use RMprepUSB, i foud that grub4dos is not latest ver, and i replace grldr with grldr from E2B.
But after replace, grub4dos stuck with text say that
grub4dos 0.4.6a 2016-03-03, root is (0x80,0)
Processing the preset menu ....
grub4dos 0.4.6a 2016-03-03, root is (0x80,0)
Processing menu file /menu.lst ....
My menu.lst is very very simple.
If replace it with menu.lst from E2B then it work.
Can you tell me why?
Tks, master.
thailand_guy
09/03/2016
Re: Re: Re: Grub4dos dd command
This forum is about E2B, not grub4dos.
If you have any questions about grub4dos or RMPrepUSB, etc. either use Contact Me form or reboot.pro forums.
If you have questions about E2B then post here.
If you have any questions about grub4dos or RMPrepUSB, etc. either use Contact Me form or reboot.pro forums.
If you have questions about E2B then post here.
SteveSi
09/03/2016
Re: Re: Re: Re: Grub4dos dd command
Oh, i'm sorry.
I will create an account then start new topic. tks
I will create an account then start new topic. tks
thailand_guy
09/03/2016
DLCD/DLC MiniXP BSOD
Hi Steve,
i'm come from Vietnam and i use DLC/DLCD Boot instead Hiren's.
After some works, I found that if I boot DLC.ISO with map 0xff or map hd32, then MiniXP get BSOD error.
But if I boot to DLC with extract method then boot to MiniXP and it boot fine.
Can you explain what differences between ISO boot with extract Boot? Tks
p/s: I'm sorry for my bad English
p/s2: ISO Boot work fine with E2B (.WH extension), I just want to know why map 0xff not work
Tks :)
i'm come from Vietnam and i use DLC/DLCD Boot instead Hiren's.
After some works, I found that if I boot DLC.ISO with map 0xff or map hd32, then MiniXP get BSOD error.
But if I boot to DLC with extract method then boot to MiniXP and it boot fine.
Can you explain what differences between ISO boot with extract Boot? Tks
p/s: I'm sorry for my bad English
p/s2: ISO Boot work fine with E2B (.WH extension), I just want to know why map 0xff not work
Tks :)
congnt92
06/03/2016
Re: DLCD/DLC MiniXP BSOD
http://rmprepusb.blogspot.co.uk/2013/09/why-is-it-so-difficult-to-boot-iso.html
SteveSi
06/03/2016
Re: Re: DLCD/DLC MiniXP BSOD
Hi Steve,
Tks for your reply.
Your link is useful for newbie like me. But this problem only happen for me, not others.
If extract ISO then MiniXP boot OK.
Tks for your reply.
Your link is useful for newbie like me. But this problem only happen for me, not others.
If extract ISO then MiniXP boot OK.
congnt92
06/03/2016
Re: Re: Re: DLCD/DLC MiniXP BSOD
What do you mean 'it only happens for me'?
How does it know who you are?
What if you wear a mask?
Seriously, what do you mean?
Do you mean that it only happens on one particular computer? How many have you tried? Have you tried booting via QEMU or VBox? It should boot OK. So the problem is that your system is different from normal systems?
So maybe look at your system memory size, CPU, etc?
How does it know who you are?
What if you wear a mask?
Seriously, what do you mean?
Do you mean that it only happens on one particular computer? How many have you tried? Have you tried booting via QEMU or VBox? It should boot OK. So the problem is that your system is different from normal systems?
So maybe look at your system memory size, CPU, etc?
SteveSi
06/03/2016
Re: Re: Re: Re: DLCD/DLC MiniXP BSOD
Hi Steve,
I'm sorry if I say something make you not happy.
I just want to say that: with same XP.WIM, i can boot it with extract method, but if i boot with ISO boot then get BSOD.
With the same ISO Boot code, virtualbox or some other machines boot fine (my friend laptop, and some other DLC Boot user). My laptop 5 years old, corei3, 2gb RAM
Here the code in case you need. Tks
title DLC Boot (ISO)
set isoname=/DLC.ISO
map %isoname% (0xff)
map --hook
root (0xff) || rootnoverify (0xff)
chainloader (0xff)
boot
I'm sorry if I say something make you not happy.
I just want to say that: with same XP.WIM, i can boot it with extract method, but if i boot with ISO boot then get BSOD.
With the same ISO Boot code, virtualbox or some other machines boot fine (my friend laptop, and some other DLC Boot user). My laptop 5 years old, corei3, 2gb RAM
Here the code in case you need. Tks
title DLC Boot (ISO)
set isoname=/DLC.ISO
map %isoname% (0xff)
map --hook
root (0xff) || rootnoverify (0xff)
chainloader (0xff)
boot
congnt92
06/03/2016
Re: Re: Re: Re: Re: DLCD/DLC MiniXP BSOD
I have already communicated with you on reboot.pro, and we discussed using e820cycles parameter and also loading whole ISO into memory using map --mem (which you have not replied to). Except that discussion was about Hirens not DLC.
The BIOS on your system is 'bad'. If there is no new version of BIOS, you just have to try different methods and see what works.
The BIOS on your system is 'bad'. If there is no new version of BIOS, you just have to try different methods and see what works.
SteveSi
06/03/2016
Re: Re: Re: Re: Re: Re: DLCD/DLC MiniXP BSOD
Hi Steve,
May you have a confusing here.
After you hint me try map --mem method, I reported it's still BSOD via inbox.
And it's is MiniXP from LiveXP project with wimboot method not Hiren.
After each advice that you give me, I alway try and report to you.
Please forgive me if I say something wrong via inbox.
Tks
May you have a confusing here.
After you hint me try map --mem method, I reported it's still BSOD via inbox.
And it's is MiniXP from LiveXP project with wimboot method not Hiren.
After each advice that you give me, I alway try and report to you.
Please forgive me if I say something wrong via inbox.
Tks
congnt92
07/03/2016
E2B NTFS+FAT32
Hi sir,
I want to create USB multi partition with FAT32 for some Linux persistence and NTFS for ISO Windows install.
I do not know why grub4dos can map an ISO put on another partition while you say that
"You can move and run payload files (but not Windows Install ISOs) to other partitions or even on other drives."
ISO was map to (0xff) and chainload from (0xff) so it's not important where to put Windows Install ISO, right?
Tks
I want to create USB multi partition with FAT32 for some Linux persistence and NTFS for ISO Windows install.
I do not know why grub4dos can map an ISO put on another partition while you say that
"You can move and run payload files (but not Windows Install ISOs) to other partitions or even on other drives."
ISO was map to (0xff) and chainload from (0xff) so it's not important where to put Windows Install ISO, right?
Tks
kayathone
05/03/2016
Re: E2B NTFS+FAT32
Windows and linux boot in two stages:
1. Use BIOS (or UEFI) to boot from media
2. Load own OS drivers and access media direct
Consider Windows ISO. grub4dos can map ISO as a CD and we can start Phase 1 because it uses BIOS calls to access media and load OS drivers. Now in Phase 2, Windows uses Windows drivers. All grub4dos BIOS mapping is lost - Windows drivers do not use BIOS, they access the media direct but all they find is .ISO file, not \sources\install.wim, etc. because it is inside the ISO. Also, if E2B is a Removable USB drive, Windows can only access 1st partition.
http://rmprepusb.blogspot.co.uk/2013/09/why-is-it-so-difficult-to-boot-iso.html
http://www.easy2boot.com/faq-/how-e2b-works/
1. Use BIOS (or UEFI) to boot from media
2. Load own OS drivers and access media direct
Consider Windows ISO. grub4dos can map ISO as a CD and we can start Phase 1 because it uses BIOS calls to access media and load OS drivers. Now in Phase 2, Windows uses Windows drivers. All grub4dos BIOS mapping is lost - Windows drivers do not use BIOS, they access the media direct but all they find is .ISO file, not \sources\install.wim, etc. because it is inside the ISO. Also, if E2B is a Removable USB drive, Windows can only access 1st partition.
http://rmprepusb.blogspot.co.uk/2013/09/why-is-it-so-difficult-to-boot-iso.html
http://www.easy2boot.com/faq-/how-e2b-works/
SteveSi
05/03/2016
Re: Re: E2B NTFS+FAT32
For linux persistence, use NTFS E2B drive and create ext2 files.
http://www.easy2boot.com/add-payload-files/linux-isos/linux-with-persistence/
http://www.easy2boot.com/add-payload-files/persistence/
or can have full linux OS (not boot from ISO but fully installed)
http://rmprepusb.blogspot.co.uk/2015/06/how-to-have-multiple-fully-installed.html
http://www.easy2boot.com/add-payload-files/linux-isos/linux-with-persistence/
http://www.easy2boot.com/add-payload-files/persistence/
or can have full linux OS (not boot from ISO but fully installed)
http://rmprepusb.blogspot.co.uk/2015/06/how-to-have-multiple-fully-installed.html
SteveSi
05/03/2016
Re: Re: Re: E2B NTFS+FAT32
Hi sir,
Tks for your reply.
And i'm sorry but can i ask a question?
I do not think that Linux can work with NTFS USB.
I tried to boot ubuntu ISO file from harddisk with grub4dos, it boot fine if ISO put on FAT32 partition but fail if i put it to NTFS partition.
If you need screenshot, i can give you later.
Tks for your reply.
And i'm sorry but can i ask a question?
I do not think that Linux can work with NTFS USB.
I tried to boot ubuntu ISO file from harddisk with grub4dos, it boot fine if ISO put on FAT32 partition but fail if i put it to NTFS partition.
If you need screenshot, i can give you later.
kayathone
05/03/2016
Re: Re: Re: Re: E2B NTFS+FAT32
Many linux distros work OK with NTFS.
It depends on what linux distro you have and how you are booting it.
Please use Contact Me form and I will email back.
I need details.
It depends on what linux distro you have and how you are booting it.
Please use Contact Me form and I will email back.
I need details.
SteveSi
05/03/2016
Re: Re: Re: Re: Re: E2B NTFS+FAT32
Hi sir,
Because partnew will not work with my HDD, so I use this code
title ubuntu
find --set-root /ISO/ubuntu.iso
map /ISO/ubuntu.iso (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper persistent iso-scan/filename=/ISO/ubuntu.ISO splash
initrd /casper/initrd.lz
boot
On NTFS partition, I create ISO folder, then rename Ubuntu ISO to Ubuntu.ISO and put it here. Boot and error.
But if I format this partition to Fa32, then it boot fine.
Tks
p/s: I'm not test with many ISO, just Ubuntu, Kubuntu.
Because partnew will not work with my HDD, so I use this code
title ubuntu
find --set-root /ISO/ubuntu.iso
map /ISO/ubuntu.iso (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper persistent iso-scan/filename=/ISO/ubuntu.ISO splash
initrd /casper/initrd.lz
boot
On NTFS partition, I create ISO folder, then rename Ubuntu ISO to Ubuntu.ISO and put it here. Boot and error.
But if I format this partition to Fa32, then it boot fine.
Tks
p/s: I'm not test with many ISO, just Ubuntu, Kubuntu.
kayathone
06/03/2016
Re: Re: Re: Re: Re: Re: E2B NTFS+FAT32
older versions of Ubuntu does not like 'persistent' on NTFS.
Remove word persistent and try.
http://www.rmprepusb.com/tutorials/ubuntu
Ubuntu 13 and 15 do work on NTFS+persistent cheat code.
P.S. case-sensitive - .iso .ISO ???
If you need 'persistent' then check casper-rw volume is not corrupt.
Remove word persistent and try.
http://www.rmprepusb.com/tutorials/ubuntu
Ubuntu 13 and 15 do work on NTFS+persistent cheat code.
P.S. case-sensitive - .iso .ISO ???
If you need 'persistent' then check casper-rw volume is not corrupt.
SteveSi
06/03/2016
Re: Re: Re: Re: Re: Re: Re: E2B NTFS+FAT32
Hi sir,
i use lastest ubuntu ISO, download from homepage.
And you say that ubuntu 15 do work on NTFS with cheat code. So you meant "partnew" command.
I cannot use partnew command on HDD.
Tks.
i use lastest ubuntu ISO, download from homepage.
And you say that ubuntu 15 do work on NTFS with cheat code. So you meant "partnew" command.
I cannot use partnew command on HDD.
Tks.
kayathone
06/03/2016
Re: Re: Re: Re: Re: Re: Re: Re: E2B NTFS+FAT32
This works OK for me on NTFS
title Ubuntu 15.10\n Boot using .mnu file
set ISO=/_ISO/LINUX/ubuntu-15.10-desktop-amd64.iso
map %ISO% (0xff)
map --hook
root (0xff)
set k=/casper/vmlinuz
if exist /casper/vmlinuz.efi set k=/casper/vmlinuz.efi
kernel %k% file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=%ISO% quiet splash --
initrd /casper/initrd.lz
boot
title Ubuntu 15.10\n Boot using .mnu file
set ISO=/_ISO/LINUX/ubuntu-15.10-desktop-amd64.iso
map %ISO% (0xff)
map --hook
root (0xff)
set k=/casper/vmlinuz
if exist /casper/vmlinuz.efi set k=/casper/vmlinuz.efi
kernel %k% file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=%ISO% quiet splash --
initrd /casper/initrd.lz
boot
SteveSi
06/03/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: E2B NTFS+FAT32
Tks sir,
I will try it now.
How can i use this code if i need a persistence.
I will try it now.
How can i use this code if i need a persistence.
kayathone
06/03/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: E2B NTFS+FAT32
As I said, it does not work using a \casper-rw file because it does not detect it on an NTFS partition.
You could create a separate partition on the hard disk with a volume name of casper-rw and formatted as ext2/3/4.
You could create a separate partition on the hard disk with a volume name of casper-rw and formatted as ext2/3/4.
SteveSi
06/03/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: E2B NTFS+FAT32
Greate. Now I clearly understand. Tks, Sir
kayathone
07/03/2016
Method 5 - NTFS UEFI
Hi Steve,
from e2b website, i found a method that we can use NTFS for UEFI.
After following your method5, UEFI boot fine but I get grub2 command instead of loading grub.cfg file
Can you tell me which step i did wrong
- Create 2 partition, one Fat32, one NTFS
- Copy EFI 2 go files to FAT32 partition
- Swap to NTFS by RMPrep
- Copy all contents of E2B to here
- install g4d to MBR and PBR by RMPrep
- Make imgPTN then rename to imgPTNlba23
- Swith to imgPTN by Switch USB.exe
- Boot to UEFI machine
Tks
from e2b website, i found a method that we can use NTFS for UEFI.
After following your method5, UEFI boot fine but I get grub2 command instead of loading grub.cfg file
Can you tell me which step i did wrong
- Create 2 partition, one Fat32, one NTFS
- Copy EFI 2 go files to FAT32 partition
- Swap to NTFS by RMPrep
- Copy all contents of E2B to here
- install g4d to MBR and PBR by RMPrep
- Make imgPTN then rename to imgPTNlba23
- Swith to imgPTN by Switch USB.exe
- Boot to UEFI machine
Tks
zhuanglee
04/03/2016
Re: Method 5 - NTFS UEFI
Once you have switched, check the partitions.
ptn 1 should be NTFS and contain the payload files
ptn2 should be FAT32 and contain the EFI folder and EFIToGo files.
ptn 1 should be NTFS and contain the payload files
ptn2 should be FAT32 and contain the EFI folder and EFIToGo files.
SteveSi
04/03/2016
Re: Re: Method 5 - NTFS UEFI
tks for your quick reply.
As you describe, i think you are saying about method 4. I follow method 5 which need rufus or EFI 2 Go files from download area.
That's right?
As you describe, i think you are saying about method 4. I follow method 5 which need rufus or EFI 2 Go files from download area.
That's right?
zhuanglee
04/03/2016
Re: Re: Re: Method 5 - NTFS UEFI
Sorry, you are right (I got confused with Method 4).
See previous edited post!
What do you mean about grub2?
What are you booting to?
See previous edited post!
What do you mean about grub2?
What are you booting to?
SteveSi
04/03/2016
Re: Re: Re: Re: Method 5 - NTFS UEFI
Hi Steve,
I have EFI folder put in NTFS partition and of course this NTFS par has E2B files.
In EFI folder, i have boox64.efi which configfile boot/grub/grub.cfg (this .efi file from Androidx86).
My goal is, if we boot on legacy machine, then E2B will work.
If we boot on UEFI machine, then EFI file from fat32 partition will call bootx64.efi file from NTFS par then this file config file grub.cfg and display menu for booting Androidx86 on UEFI.
Tks
I have EFI folder put in NTFS partition and of course this NTFS par has E2B files.
In EFI folder, i have boox64.efi which configfile boot/grub/grub.cfg (this .efi file from Androidx86).
My goal is, if we boot on legacy machine, then E2B will work.
If we boot on UEFI machine, then EFI file from fat32 partition will call bootx64.efi file from NTFS par then this file config file grub.cfg and display menu for booting Androidx86 on UEFI.
Tks
zhuanglee
05/03/2016
Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
If you can boot to grub2, then it has worked.
The grub.cfg may be wrong for working from the 2nd partition.
The grub.cfg may be wrong for working from the 2nd partition.
SteveSi
05/03/2016
Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
The E2B NTFS partition should not have an EFI folder (it does't need it).
You make a .imgPTNLBA23 file from the android iso using MPI_NTFS shortcut.
When you switch to it using Switch_E2B, then it should already have an EFI\boot folder with either bootx64.efi and/or bootia32.efi (from the android ISO). If it does not contain either, then the original source did not support UEFI-booting.
So we should have:
Ptn1: NTFS with all android files + CSM files
Ptn2: FAT32 EFIToGo files
I that what you have?
Why do you need NTFS? Why not just make a FAT32 .imgPTN file and use that?
You make a .imgPTNLBA23 file from the android iso using MPI_NTFS shortcut.
When you switch to it using Switch_E2B, then it should already have an EFI\boot folder with either bootx64.efi and/or bootia32.efi (from the android ISO). If it does not contain either, then the original source did not support UEFI-booting.
So we should have:
Ptn1: NTFS with all android files + CSM files
Ptn2: FAT32 EFIToGo files
I that what you have?
Why do you need NTFS? Why not just make a FAT32 .imgPTN file and use that?
SteveSi
08/03/2016
Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
Hi Steve,
After long time now i come back to e2b uefi ntfs. (my laptop has broken and it take long time to fix).
I follow your method 4 but do not know how efi2go file work.
I create android.imgptn and efi (no extension) and put to \_ISO\LINUX folder.
switch e2b drive by click on .imgptn
but i just got ntfs partition. how about efi file and fat32 partition?
Tks
After long time now i come back to e2b uefi ntfs. (my laptop has broken and it take long time to fix).
I follow your method 4 but do not know how efi2go file work.
I create android.imgptn and efi (no extension) and put to \_ISO\LINUX folder.
switch e2b drive by click on .imgptn
but i just got ntfs partition. how about efi file and fat32 partition?
Tks
zhuanglee
08/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
You need to create two partition images, e.g.
abc.imgPTN
abc
abc.imgPTN
abc
SteveSi
08/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
Hi Steve,
Tks for your reply.
I create 2 files: Android.imgptn and android (without extension).
When i run e2b switch, it only detect .imgptn file
I click .imgpnt file to switch USB but USB still NTFS. So i cannot boot to UEFI machine.
Tks
Tks for your reply.
I create 2 files: Android.imgptn and android (without extension).
When i run e2b switch, it only detect .imgptn file
I click .imgpnt file to switch USB but USB still NTFS. So i cannot boot to UEFI machine.
Tks
zhuanglee
09/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
As an experiment, name the android file as android1.imgPTN and use Switch_e2b to load just that file. This will check that it is actually the correct format and works as a partition image.
if not, explain how you made the android file.
if not, explain how you made the android file.
SteveSi
09/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
Hi Steve,
Here all of steps that I did.
- Run makee2b.cmd to create a "clean" e2b NTFS usb drive.
- Download make part image and create desktop shortcut.
- Download android.iso and drag it to MPI NTFS shortcut.
- ENTER all step to leave setting default.
- Copy android.imgptn to \_ISO\LINUX folder.
- Download EFI2Go folder and drag to MPI_FAT32 to make android (without extension)
- Copy android to LINUX folder
- Run switch e2b.exe and double click android.imgptn
- E2B switched, and its format is NTFS
- Boot from UEFI machine but it failed
Tks
Here all of steps that I did.
- Run makee2b.cmd to create a "clean" e2b NTFS usb drive.
- Download make part image and create desktop shortcut.
- Download android.iso and drag it to MPI NTFS shortcut.
- ENTER all step to leave setting default.
- Copy android.imgptn to \_ISO\LINUX folder.
- Download EFI2Go folder and drag to MPI_FAT32 to make android (without extension)
- Copy android to LINUX folder
- Run switch e2b.exe and double click android.imgptn
- E2B switched, and its format is NTFS
- Boot from UEFI machine but it failed
Tks
zhuanglee
10/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
I do not understand why you need to use two partition images? Why don't you just drag-and-drop the androidx86.iso onto the MPI_FAT32 Desktop shortcut to create a ,imgPTN file and use that file? Why do you need to create two partition images and why does one of them need to be NTFS???
Anyway, assuming you have made the NTFS+FAT32 files, does SWITCH_E2B v1.0.10 show:
android.imgPTN :&: android
i.e. two images? It should.
I followed your method using android-x86-4.4-r4.iso and it at least booted under VBox both on a 32-bit UEFI VM and a 64-bit UEFI VM to a console/shell.
You do not specify the EXACT ISO you are booting and you do not give any details except 'but it failed'. So it is difficult to diagnose the problem any further.
Anyway, assuming you have made the NTFS+FAT32 files, does SWITCH_E2B v1.0.10 show:
android.imgPTN :&: android
i.e. two images? It should.
I followed your method using android-x86-4.4-r4.iso and it at least booted under VBox both on a 32-bit UEFI VM and a 64-bit UEFI VM to a console/shell.
You do not specify the EXACT ISO you are booting and you do not give any details except 'but it failed'. So it is difficult to diagnose the problem any further.
SteveSi
10/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
P.S. I see androidx86 has a .img version which it says is for EFI - maybe the ISO does not work for UEFI. Did you try making a FAT32 .imgPTN file from the .img download?
SteveSi
10/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
I downloaded a copy of Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img and dropped it onto MPI_FAT32. It seems to boot OK on UEFI if you select Guest Mode (but not resident mode) on VBox. It doesn't MBR boot.
SteveSi
10/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
I also download the android 5.1.1rc5.img file and converted that via MPI_FAT32 to a .imgPTN file. This boots on my Z87 via 64-bit UEFI (but I had to type exit twice in the shell before it booted to the 'Desktop'). In fact, I am writing this now from within android!
SteveSi
10/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
Hi Steve, tks for your detail reply.
Also i'm sorry for my delay respone.
All of these day, i test many times with some Android base ISO: Androidx86, phoenixos, remixos and consoleos to make sure E2B Boot fine before ask you again.
And of cources all of it work fine if just use one NTFS partition for E2B then use FAT32 imgptn convert.
But It would be greate if we have 2 partition at one: 1 NTFS vs 1 very small FAT32 par with EFI2Go files.
I try to find on your E2B website and found method 4. it is very helpful for me. But i failed when try to test it.
E2B switch only display .imgptn extenstion, so android file (without extension) created from EFI2GO folder cannot be list on E2B switch.
Tks
Also i'm sorry for my delay respone.
All of these day, i test many times with some Android base ISO: Androidx86, phoenixos, remixos and consoleos to make sure E2B Boot fine before ask you again.
And of cources all of it work fine if just use one NTFS partition for E2B then use FAT32 imgptn convert.
But It would be greate if we have 2 partition at one: 1 NTFS vs 1 very small FAT32 par with EFI2Go files.
I try to find on your E2B website and found method 4. it is very helpful for me. But i failed when try to test it.
E2B switch only display .imgptn extenstion, so android file (without extension) created from EFI2GO folder cannot be list on E2B switch.
Tks
zhuanglee
14/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
Well, it works OK for me. Are you using the latest version? If so, use the Contact Me form and then we can try to find out what is going on by email.
SteveSi
14/04/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Method 5 - NTFS UEFI
Hi Steve,
yesterday i had a busy day.
Now I will take a screenshot for each step then send you via email.
Tks for your support.
yesterday i had a busy day.
Now I will take a screenshot for each step then send you via email.
Tks for your support.
zhuanglee
15/04/2016
Tut 96
Hi sir,
I'm very interested your #96 tut.
But automenulinux.bat just work for .ISO file.
Can you update newer version to show some other extensions, such as: .img, .ima, or can you help me make my own automenulinux.bat.
tks, sir
I'm very interested your #96 tut.
But automenulinux.bat just work for .ISO file.
Can you update newer version to show some other extensions, such as: .img, .ima, or can you help me make my own automenulinux.bat.
tks, sir
thailand_guy
02/03/2016
Re: Tut 96
I found this command in automenulinux.bat
WENV check "#.iso#"=="#%~x1#" || goto :EOF
so i need check some other extensions, can i edit it to something like
for %%x in (.iso .img .ima ...) WENV check "#%%x#"=="#%~x1#" || goto :EOF
tks
WENV check "#.iso#"=="#%~x1#" || goto :EOF
so i need check some other extensions, can i edit it to something like
for %%x in (.iso .img .ima ...) WENV check "#%%x#"=="#%~x1#" || goto :EOF
tks
thailand_guy
02/03/2016
Re: Re: Tut 96
The partnew trick only works for linux ISO files. It will not work for other extensions. You have to use different code and methods for other extensions.
Easy2Boot will work for many extensions. Look at the \_ISO\e2b\grub\QRUN.g4b file to see how it works.
Easy2Boot will work for many extensions. Look at the \_ISO\e2b\grub\QRUN.g4b file to see how it works.
SteveSi
02/03/2016
Re: Re: Re: Tut 96
Tks steve, i'll try e2b and see how it work.
thailand_guy
02/03/2016
Full icon for DLC/DLCD
Try rename to isowinvh but no luck. since we boot DLC/DLCD by iso boot, then we still need to extract some folder to USB??
Can we use firadisk to mount ISO after boot to winpe ?? Tks
Can we use firadisk to mount ISO after boot to winpe ?? Tks
vfcontig
27/02/2016
Re: Full icon for DLC/DLCD
DLCD normally works with .isowinvh, but why not try .isoask and then test a few other extensions - e.g. isofira.
The best thing for an Hirens ISO is to convert it to a .imgPTN file.
http://www.easy2boot.com/add-payload-files/hirens-isos/
The best thing for an Hirens ISO is to convert it to a .imgPTN file.
http://www.easy2boot.com/add-payload-files/hirens-isos/
SteveSi
27/02/2016
Re: Re: Full icon for DLC/DLCD
P.S. for Win8 you can use .isoPE file extension, but E2B must be running from a Removable drive. Otherwise, when you get to the Dekstop of Mini8, run \_ISO\e2b\firadisk\LOADISOPE.cmd to mount the ISO as drive Y:. Then run the menu.exe file from Y:.
E2B v1.78 has new .isoHW file extension.
E2B v1.78 has new .isoHW file extension.
SteveSi
27/02/2016
Re: Re: Re: Full icon for DLC/DLCD
tks for detail explain. i try DLCD 2015 ver1.0 with isowinvh but no luck. after boot to desktop, ISO was not mount.
I will try with isoask then report.
I will try with isoask then report.
vfcontig
28/02/2016
Re: Re: Re: Re: Full icon for DLC/DLCD
DLCD 2015 has two WinPEs - XP and Win8.
XP will work OK
Win8 will not work unless you have a Removable USB flash drive and name the file .isoPE.
If you use E2B v1.78h, then name the file as .isoHW and it should work for both WinPEs if you have a Removable USB E2B drive.
If your E2B USB drive is a fixed disk, then either extract the DLCD folder onto the E2B USB drive or make a .imgPTN file. This is all explained in the Hirens page in the link I already gave you.
XP will work OK
Win8 will not work unless you have a Removable USB flash drive and name the file .isoPE.
If you use E2B v1.78h, then name the file as .isoHW and it should work for both WinPEs if you have a Removable USB E2B drive.
If your E2B USB drive is a fixed disk, then either extract the DLCD folder onto the E2B USB drive or make a .imgPTN file. This is all explained in the Hirens page in the link I already gave you.
SteveSi
28/02/2016
Re: Re: Re: Re: Re: Full icon for DLC/DLCD
Oh, i'm using Removable USB, not HDD Box
But not ver1.78,
I will update it now then test and report.
tks sir.
But not ver1.78,
I will update it now then test and report.
tks sir.
vfcontig
29/02/2016
Re: Re: Re: Re: Re: Full icon for DLC/DLCD
Try isowinvh for DLCD on some laptop, MiniXP cannot boot to desktop
winvblock bug??
And where can I download ver1.78h
Tks
winvblock bug??
And where can I download ver1.78h
Tks
vfcontig
29/02/2016
Re: Re: Re: Re: Re: Re: Full icon for DLC/DLCD
Check Alternate Download Area on Download page for Beta versions.
What is model of system that does not work with .isowinvh ? Dell? What model? In what way does it 'not work'?
What is model of system that does not work with .isowinvh ? Dell? What model? In what way does it 'not work'?
SteveSi
29/02/2016
Re: Re: Re: Re: Re: Re: Re: Full icon for DLC/DLCD
Try .isowinvh from laptop Toshiba.
Not BSOD, just not logon to desktop
After Logo Windows XP show and disappear, MiniXP hang, screen goto blank.
P/s: Now i try with ver1.78 then report
Not BSOD, just not logon to desktop
After Logo Windows XP show and disappear, MiniXP hang, screen goto blank.
P/s: Now i try with ver1.78 then report
vfcontig
29/02/2016
Re: Re: Re: Re: Re: Re: Re: Re: Full icon for DLC/DLCD
ver 1.78h work very well.
but still same error with MiniXP, i don't know why but if i add # before line using winvblock then it work.
so i sure that this problem came from winvblock.
tks.
but still same error with MiniXP, i don't know why but if i add # before line using winvblock then it work.
so i sure that this problem came from winvblock.
tks.
vfcontig
01/03/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Full icon for DLC/DLCD
Hi steve,
I found that i can map firadisk with fd0 then use f6 to load firadisk then use code in menu.lst to tell where .ISO located to mount it after boot to minixp.
can you tell me how to do it?
where can i download firadisk.img
and what grub4dos menu.lst to do?
tks
I found that i can map firadisk with fd0 then use f6 to load firadisk then use code in menu.lst to tell where .ISO located to mount it after boot to minixp.
can you tell me how to do it?
where can i download firadisk.img
and what grub4dos menu.lst to do?
tks
vfcontig
01/03/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Full icon for DLC/DLCD
Does .isofira work?
SteveSi
01/03/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Full icon for DLC/DLCD
Use .isoask and try alternatives - e.g. .isowinvhe0 or other e0 alternatives.
SteveSi
01/03/2016
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Full icon for DLC/DLCD
Tks steve, rename to .ISOask then type HW then it works.
i.e. use .isoHW file extension.
i.e. use .isoHW file extension.
vfcontig
02/03/2016
Remove E2B and restore USB
Hi there,
I'm trying to find instructions to remove E2B from a USB and restore it to it's original size.
I've tried formatting but it only shows 4GB of the original 16GB.
Thank you
I'm trying to find instructions to remove E2B from a USB and restore it to it's original size.
I've tried formatting but it only shows 4GB of the original 16GB.
Thank you
Jason
22/02/2016
Re: Remove E2B and restore USB
Just formatting a drive under Windows will not change the partition size.
It sounds like you have used a .imgPTN image.
Under Windows you can run \e2b\SWITCH_E2B.exe and Restore E2B partitions - or just use RMPrepUSB to re-partition and re-format the drive.
It sounds like you have used a .imgPTN image.
Under Windows you can run \e2b\SWITCH_E2B.exe and Restore E2B partitions - or just use RMPrepUSB to re-partition and re-format the drive.
SteveSi
22/02/2016
Re: Re: Remove E2B and restore USB
Thanks Steve :)
Jason
24/02/2016
automenu
I use AUTOLINUXMENU for multibooting internal HDD.
Is possible to change the created automenu in order by date?
Is possible to change the created automenu in order by date?
dan
21/02/2016
Re: automenu
No. Grub4dos is not able to get the date of a file.
SteveSi
21/02/2016
Disk write error
Hi Steve
I recently bought a 16 GB Kingston DataTraveler DT 101G2 pen drive and installed Easy2Boot on it, but when i boot from the pen drive and select an ISO file from the Easy2Boot menu i get this error message:
if not exist CD dd if=(bd)%XML% of=()/AutoUnattend.xml > nul
Error 29(http://grub4dos.chennal.net/e/29)
Disk write error
Press any key to continue...
I have updated to the 1.78c beta but the problem persists.
I don't get this error when i boot from a 8 GB Sony Microvault pen drive, which is what i've been using before for Easy2Boot.
I recently bought a 16 GB Kingston DataTraveler DT 101G2 pen drive and installed Easy2Boot on it, but when i boot from the pen drive and select an ISO file from the Easy2Boot menu i get this error message:
if not exist CD dd if=(bd)%XML% of=()/AutoUnattend.xml > nul
Error 29(http://grub4dos.chennal.net/e/29)
Disk write error
Press any key to continue...
I have updated to the 1.78c beta but the problem persists.
I don't get this error when i boot from a 8 GB Sony Microvault pen drive, which is what i've been using before for Easy2Boot.
Carlos
20/02/2016
Re: Disk write error
It is probably a fake!
Test it using RMPrepUSB - Quick Size Test or FakeFlashTest.
P.S. DT10x are too slow. Alway buy USB 3.0 and preferably fast one like SanDisk Extreme.
Test it using RMPrepUSB - Quick Size Test or FakeFlashTest.
P.S. DT10x are too slow. Alway buy USB 3.0 and preferably fast one like SanDisk Extreme.
SteveSi
20/02/2016
Re: Re: Disk write error
The Quick Size Test didn't report any errors, what else can i do to fix this problem?
Also, i know there are faster pen drives but i can't afford them, they are expensive where i live.
Also, i know there are faster pen drives but i can't afford them, they are expensive where i live.
Carlos
21/02/2016
Re: Re: Re: Disk write error
Try using QEMU (RMPrepUSB - F11) and see if you get the same error.
What XML file did you pick? What ISO are you running and where is it located? Does it happen with any ISO and any XML file?
What XML file did you pick? What ISO are you running and where is it located? Does it happen with any ISO and any XML file?
SteveSi
21/02/2016
Re: Re: Re: Re: Disk write error
With QEMU i get error 21 with a Windows 7 x86 ISO. I always choose the Easy2Boot XML file, the ISO is located at _ISO/WINDOWS/WIN7 and i get the error with any of the XML files. The error also occurs with a Xubuntu 15.10 i386 ISO with persistence but with "partnew (%E2BDEV%,3) 0x0 %ISO%" command instead of the "if not exist..." command above the error 29 text, but after pressing a key to continue and reselecting Xubuntu 2 times, it boots.
Carlos
21/02/2016
Re: Re: Re: Re: Re: Disk write error
Something seems wrong with that drive!
It is failing on writes to the drive.
If a different drive works under the same set of conditions, then it points to a faulty drive.
It is failing on writes to the drive.
If a different drive works under the same set of conditions, then it points to a faulty drive.
SteveSi
21/02/2016
Re: Re: Re: Re: Re: Re: Disk write error
Well, i guess i'll have to buy a new one. Thanks for the help :).
Carlos
21/02/2016
Re: Re: Re: Re: Re: Re: Re: Disk write error
Hi,
Well, i'm not sure about this problem, but if your usb has a button that can switch on/off write protected mode then may it is reason.
Well, i'm not sure about this problem, but if your usb has a button that can switch on/off write protected mode then may it is reason.
vfcontig
01/03/2016
Accessing other partitions when booting imgptn
Hello,
I am using a large external usb drive with 2 partitions. The first for booting is 137GB, the second partition is used for storing data/manuals/utilities/various files.
Is there a way to boot from a imgPTN file and still access the second partition? It seems to vanish when an imgPTN file is booted from.
Thanks
I am using a large external usb drive with 2 partitions. The first for booting is 137GB, the second partition is used for storing data/manuals/utilities/various files.
Is there a way to boot from a imgPTN file and still access the second partition? It seems to vanish when an imgPTN file is booted from.
Thanks
Tec
17/02/2016
Re: Accessing other partitions when booting imgptn
Sure, just give the file a .imgPTNLBAa23 file extension.
http://www.easy2boot.com/add-payload-files/list-of-file-extensions-recognised-by-e2b/
http://www.easy2boot.com/add-payload-files/list-of-file-extensions-recognised-by-e2b/
SteveSi
17/02/2016
Grub4dos command
Hi Steve,
I'm new with grub4dos command.
I try cat --locate command and don't know how it work.
boot grub4dos from qemu
type c to get command line
type:
echo 123a > (md)0x300+1
cat --locate=a (md)0x300+1
result: 3
I don't know why is 3. From string "1233a", so the result must be 4??
Can u explain me why? Tks
p/s: i'm sorry for my poor English!
I'm new with grub4dos command.
I try cat --locate command and don't know how it work.
boot grub4dos from qemu
type c to get command line
type:
echo 123a > (md)0x300+1
cat --locate=a (md)0x300+1
result: 3
I don't know why is 3. From string "1233a", so the result must be 4??
Can u explain me why? Tks
p/s: i'm sorry for my poor English!
bighero
17/02/2016
Re: Grub4dos command
Cat --locate returns the offset (address of string)
byte at offset 0 = 1
byte at offset 1 = 2
byte at offset 2 = 3
byte at offset 3 = a
use cat --hex --length=16 (md)0x300+1
to see bytes
byte at offset 0 = 1
byte at offset 1 = 2
byte at offset 2 = 3
byte at offset 3 = a
use cat --hex --length=16 (md)0x300+1
to see bytes
SteveSi
17/02/2016
Re: Re: Grub4dos command
Oh, tks Steve.
Another question,
Why we must map mem winblock twice
map --mem /winvblock.img.gz (fd0)
map --mem /winvblock.img.gz (fd1)
when install XP from ISO or load Hiren ISO (use from QRUN easy2boot
Tks
Another question,
Why we must map mem winblock twice
map --mem /winvblock.img.gz (fd0)
map --mem /winvblock.img.gz (fd1)
when install XP from ISO or load Hiren ISO (use from QRUN easy2boot
Tks
bighero
18/02/2016
Re: Re: Re: Grub4dos command
You don't have to map twice on many systems. But some systems which have a floppy disk don't work (it has been reported to me), so I map to fd0 and fd1 for best chance of it working.
SteveSi
18/02/2016
openSUSE
Hi Steve,
openSUSE-Edu-li-f-e.x86_64-42.1.1.iso fails to boot under easry2boot(partnew)
openSUSE-Edu-li-f-e.x86_64-42.1.1.iso fails to boot under easry2boot(partnew)
dan
11/02/2016
Re: openSUSE
openSUSE live DVDs are a bit tricky!
See http://rmprepusb.blogspot.co.uk/2016/02/boot-opensuse-isos-from-e2b.html
See http://rmprepusb.blogspot.co.uk/2016/02/boot-opensuse-isos-from-e2b.html
SteveSi
11/02/2016
Re: Re: openSUSE
Thank you Steve, I read it.
This simple way works for me:
1. Format external HDD as NTFS
2. Install Grub4dos
3. Copy openSUSE-Edu-li-f-e.x86_64-42.1.1.iso
4. Create menu.lst:
title openSUSE-Edu-li-f-e.x86_64-42.1.1.iso
root (hd0,0)
set myiso=openSUSE-Edu-li-f-e.x86_64-42.1.1.iso
partnew (hd0,3) 0x00 /%myiso%
map --heads=0 --sectors-per-track=0 /%myiso% (0xff)
map --hook
root (0xff)
chainloader (0xff)
The problem is Partnew/opensuse does not create iso9660 partition but create udf partition instate.
I will email you a screenshot
This simple way works for me:
1. Format external HDD as NTFS
2. Install Grub4dos
3. Copy openSUSE-Edu-li-f-e.x86_64-42.1.1.iso
4. Create menu.lst:
title openSUSE-Edu-li-f-e.x86_64-42.1.1.iso
root (hd0,0)
set myiso=openSUSE-Edu-li-f-e.x86_64-42.1.1.iso
partnew (hd0,3) 0x00 /%myiso%
map --heads=0 --sectors-per-track=0 /%myiso% (0xff)
map --hook
root (0xff)
chainloader (0xff)
The problem is Partnew/opensuse does not create iso9660 partition but create udf partition instate.
I will email you a screenshot
dan
11/02/2016
Re: Re: Re: openSUSE
Glad it works for you - I cant get it to work for me.
Why is the ISO being visible as a udf a problem?
Why is the ISO being visible as a udf a problem?
SteveSi
11/02/2016
Re: Re: Re: Re: openSUSE
Sorry, I did some testing udf looks like cause a problem, but I think the problem is the opensuse.
I found, Easy2boot will work fine to boot opensuse.iso with partnew methode if no hidden/unknown or unallocated partition exist.
During booting opensuse will find in first place the hidden/unknown partition and convert/format to EXT4 and fail to continue booting.
The same with unallocated partition, opensuse will format it and fail to boot.
The solution is you have to format hidden/unknown/unallocated to NTFS/Vfat/ext* etc. or resize to one whole partition.
I found, Easy2boot will work fine to boot opensuse.iso with partnew methode if no hidden/unknown or unallocated partition exist.
During booting opensuse will find in first place the hidden/unknown partition and convert/format to EXT4 and fail to continue booting.
The same with unallocated partition, opensuse will format it and fail to boot.
The solution is you have to format hidden/unknown/unallocated to NTFS/Vfat/ext* etc. or resize to one whole partition.
dan
12/02/2016
Re: Re: Re: Re: Re: openSUSE
I think you are correct. It is making a type 0x83 partition out of any spare space on the drive and then failing to boot. If I use the ISO cheat codes then it doesn't do this. They seem to assume that the OS has been installed on the disk rather than live booting.
SteveSi
12/02/2016
Re: Re: Re: Re: Re: Re: openSUSE
I had a HDD with
PTN1 NTFS
PTN2 NTFS
(very little unused space)
This would not boot. I then reduced the 2nd partition to leave 3GB of unused space at the end of the drive. This still would not boot. I then changed the partnew command to use type 0x83 - now it boots and creates PTN3 as type 0x83 read-write partition.
PTN1 NTFS
PTN2 NTFS
(very little unused space)
This would not boot. I then reduced the 2nd partition to leave 3GB of unused space at the end of the drive. This still would not boot. I then changed the partnew command to use type 0x83 - now it boots and creates PTN3 as type 0x83 read-write partition.
SteveSi
12/02/2016
Re: Re: Re: Re: Re: Re: Re: openSUSE
Booting opensuse.iso using type 0x83 on external HDD works fine in any way: One whole disk or One PTN with unused big/small space or 3 primary PTNs with space or no space.
But never try booting opensuse.iso using type 0x83 on internal HDD.
But never try booting opensuse.iso using type 0x83 on internal HDD.
dan
15/02/2016
Removing Keybinds
Hi guys,
I'm really interested to know how to remove the keybinds.. or rather how to get the Chars in one line
Example:
0 Utilities [Ctrl+8]
1 Tools [Ctrl+4]
2 Things [Ctrl+2]
Would be nice if anyone could help._.
Thanks !:)
I'm really interested to know how to remove the keybinds.. or rather how to get the Chars in one line
Example:
0 Utilities [Ctrl+8]
1 Tools [Ctrl+4]
2 Things [Ctrl+2]
Would be nice if anyone could help._.
Thanks !:)
JGR
08/02/2016
Re: Removing Keybinds
Bad example..Thje lines correct theirselfes here ..
I hope you know what i mean
I hope you know what i mean
JGR
08/02/2016
Re: Removing Keybinds
Not sure what you mean, but the current hotkeys for the menu folders are set in the STRINGS.txt for each language.
e.g. Copy the \_ISO\e2b\grub\ENG\STRINGS.txt to the \_ISO folder and then change the entries
change
$$STRm018=^Ctrl+O DOS Menu [Ctrl+O]\n MS-DOS and FreeDOS utilities
to
$$STRm018=^Ctrl+2 DOS Menu [Ctrl+2]\n MS-DOS and FreeDOS utilities
e.g. Copy the \_ISO\e2b\grub\ENG\STRINGS.txt to the \_ISO folder and then change the entries
change
$$STRm018=^Ctrl+O DOS Menu [Ctrl+O]\n MS-DOS and FreeDOS utilities
to
$$STRm018=^Ctrl+2 DOS Menu [Ctrl+2]\n MS-DOS and FreeDOS utilities
SteveSi
08/02/2016
Re: Re: Removing Keybinds
I meant that the "[Ctrl+O]" and so on ... aren't in one row like it should be. The one is more left then then the other one. They are differently shifted.
JGR
09/02/2016
Re: Re: Re: Removing Keybinds
What language?
Stevesi
09/02/2016
Re: Re: Re: Re: Removing Keybinds
German
JGR
09/02/2016
Re: Re: Re: Re: Re: Removing Keybinds
They seem OK to me in E2B v.1.76 and 1.77m?
Are you using latest version? It is easy to update.
Are you using latest version? It is easy to update.
SteveSi
09/02/2016
Re: Re: Re: Re: Re: Re: Removing Keybinds
Yep. I updated it yesterday.
JGR
09/02/2016
Re: Re: Re: Re: Re: Re: Re: Removing Keybinds
Try latest v1.80e and use GERMAN_ALT as language.
SteveSi
14/04/2016
Just load Win8 ISO
How can I make E2B just load a Win8 Core ISO, without asking for a key input or an option with a pre-defined key? We have many machines with keys already embedded on BIOS, so it is not necessary to enter a key before instalation.
Thxdr
26/01/2016
Re: Just load Win8 ISO
If you install exactly the same version, then just pick the correct generic key that is in the E2B key files.
Once the system boots, it should use the BIOS key to activate via the internet.
Once the system boots, it should use the BIOS key to activate via the internet.
SteveSi
26/01/2016
Re: Re: Just load Win8 ISO
Thank you.
Thxdr
21/02/2016
About grldr.mbr vs g2ldr.mbr
Hi Steve
Can u tell me what does grldr.mbr do? I found that if we install grub4dos menu entry on windows vista and later, we need to copy grldr.mbr to C:\
So grldr.mbr is need to copy to usb if we install grub4dos to usb??
Same question with g2ldr.mbr.
Tks.
Can u tell me what does grldr.mbr do? I found that if we install grub4dos menu entry on windows vista and later, we need to copy grldr.mbr to C:\
So grldr.mbr is need to copy to usb if we install grub4dos to usb??
Same question with g2ldr.mbr.
Tks.
zhuanglee
17/01/2016
Re: About grldr.mbr vs g2ldr.mbr
It depends on how grub/grub4dos is launched. The .mbr files contain the MBR sector data boot code and can be run from the XP boot.ini or Vista+ BCD.
See http://diddy.boot-land.net/grub4dos/files/install_windows.htm for details.
So, if the boot sector of the disk does not contain grub4dos (or the PBR of the active partition), but we boot using Windows NTLDR or bootmgr, then we use a .mbr file to load grub\grub4dos.
See http://diddy.boot-land.net/grub4dos/files/install_windows.htm for details.
So, if the boot sector of the disk does not contain grub4dos (or the PBR of the active partition), but we boot using Windows NTLDR or bootmgr, then we use a .mbr file to load grub\grub4dos.
SteveSi
24/01/2016
Re: Re: About grldr.mbr vs g2ldr.mbr
Tks for your reply, Steve
grldr and grldr.mbr can be download from grub4dos pack. But I can't find where I can download g2ldr and g2ldr.mbr. Can you send me a link?
I need g2ldr because with g2ldr file I can chainload from grub4dos to grub2
title grub2
kernel /g2ldr
grldr and grldr.mbr can be download from grub4dos pack. But I can't find where I can download g2ldr and g2ldr.mbr. Can you send me a link?
I need g2ldr because with g2ldr file I can chainload from grub4dos to grub2
title grub2
kernel /g2ldr
zhuanglee
24/01/2016
Re: Re: Re: About grldr.mbr vs g2ldr.mbr
http://www.rmprepusb.com/tutorials/chainload-syslinux#TOC-Load-grub4dos-from-grub2
http://www.filewatcher.com/m/g2ldr.mbr.8192-0.html
http://www.filewatcher.com/m/g2ldr.mbr.8192-0.html
SteveSi
24/01/2016
Re: Re: Re: Re: About grldr.mbr vs g2ldr.mbr
that's great, steve. but how about g2ldr. where can i download it? I mean, latest version (grub2.02 beta)
zhuanglee
24/01/2016
Tut #27 Diagnose how your BIOS boots USB drives
I'm very interest tut #27. But in latest RMPrepUSB version, I cannot found File >> USB to load .bin file.
Can u show me how?
Can u show me how?
zhuanglee
14/01/2016
Re: Tut #27 Diagnose how your BIOS boots USB drives
File -> Drive button in RMPrepUSB utility.
SteveSi
14/01/2016
Re: Re: Tut #27 Diagnose how your BIOS boots USB drives
Ahh, tks Steve. I see
zhuanglee
15/01/2016
E2B on encrypted disk
hi Steve, there is a way to install E2B in a encrypted disk (any kind of encryption)?
because, some times (against of my desire) I need to borrow my HDD and the other plug it on inffected systems and everytime I need to make it again and again, and again.
there is a way to avoid it by using an encrypted file system?
can u answer me by email too?´
Luciano Branco
A.K.A llbranco
because, some times (against of my desire) I need to borrow my HDD and the other plug it on inffected systems and everytime I need to make it again and again, and again.
there is a way to avoid it by using an encrypted file system?
can u answer me by email too?´
Luciano Branco
A.K.A llbranco
Luciano (aka. llbranco)
06/01/2016
Re: E2B on encrypted disk
I have replied by email, but basically read
http://www.easy2boot.com/configuring-e2b/protection-and-security/
http://www.easy2boot.com/configuring-e2b/protection-and-security/
SteveSi
07/01/2016
UEFI and GPT
Hi Steve,
First, I'm sorry for my poor English!
From this link http://windowsitpro.com/windows-8/q-what-tips-will-help-me-install-windows-uefi-machine-i-built-myself,
I read a line which wrote: A UEFI system can boot only from a GPT disk
From easy2boot website - UEFI things to know, you wrote:
"Do I have to use GPT if I want to boot via UEFI?
This is a common misconception!"
I don't clearly understand why we have diffrences between 2 sites. Can you explain why? Tks
First, I'm sorry for my poor English!
From this link http://windowsitpro.com/windows-8/q-what-tips-will-help-me-install-windows-uefi-machine-i-built-myself,
I read a line which wrote: A UEFI system can boot only from a GPT disk
From easy2boot website - UEFI things to know, you wrote:
"Do I have to use GPT if I want to boot via UEFI?
This is a common misconception!"
I don't clearly understand why we have diffrences between 2 sites. Can you explain why? Tks
congnt92
04/01/2016
Re: UEFI and GPT
Since I can boot via UEFI from a FAT32+NTFS Removable USB drive by using a VHD, which do you think is more accurate!
Windows Setup will not allow you to install to an MBR partitioned disk if you UEFI-boot to Setup, but that doesn't mean it is not possible to UEFI-boot from an MBR partitioned drive!
Windows Setup will not allow you to install to an MBR partitioned disk if you UEFI-boot to Setup, but that doesn't mean it is not possible to UEFI-boot from an MBR partitioned drive!
SteveSi
04/01/2016
Re: Re: UEFI and GPT
Oh, install vs boot. I confuse two concepts.
Cannot INSTALL windows to MBR disk (in UEFI)
But we can BOOT uefi from MBR disk.
Tks Steve!
Cannot INSTALL windows to MBR disk (in UEFI)
But we can BOOT uefi from MBR disk.
Tks Steve!
congnt92
05/01/2016
Re: Re: UEFI and GPT
Hi Steve,
From #127 - How to make Dual-boot 32 & 64-bit MBR & UEFI WinPE USB drive
http://www.rmprepusb.com/tutorials/127-make-dual-32-64bit-pe
I just want to ask a question (Sorry because of rmprepusb.com not allow user leave a comment so I must be ask you here)
Why we must use both of 32 and 64bits Windows PE since we can install Windows 64bits from WinPE 32bits. I read this info from this link
https://technet.microsoft.com/en-us/library/hh824993.aspx
Quote: X:\windows\system32> D:\setup /InstallFrom:"N:\Windows_64-bit\sources\install.wim"
Tks
From #127 - How to make Dual-boot 32 & 64-bit MBR & UEFI WinPE USB drive
http://www.rmprepusb.com/tutorials/127-make-dual-32-64bit-pe
I just want to ask a question (Sorry because of rmprepusb.com not allow user leave a comment so I must be ask you here)
Why we must use both of 32 and 64bits Windows PE since we can install Windows 64bits from WinPE 32bits. I read this info from this link
https://technet.microsoft.com/en-us/library/hh824993.aspx
Quote: X:\windows\system32> D:\setup /InstallFrom:"N:\Windows_64-bit\sources\install.wim"
Tks
congnt92
06/01/2016
Re: Re: Re: UEFI and GPT
If you have a UEFI system and want to install Windows in UEFI-mode, you need to first boot via UEFI.
How can you do this on a 32-bit UEFI system and a 64-bit UEFI system unless you have both EFI boot files present?
How can you do this on a 32-bit UEFI system and a 64-bit UEFI system unless you have both EFI boot files present?