Tip: If you donate £5 or more, you will be sent an alternate E2B URL which displays fewer adverts and a neater page format (the same format as this page)!
To post to the Forum, scroll to the bottom of the page and fill in the form (in English please).
Also check for the Chat icon >>> - if I am online, start chatting and I will respond (if I am away from my desk, leave your email address and I will email you).
Re: Bad or Invalid E:\Unattend.xml
Did you follow the guide
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
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.
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.
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.
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.
DLCD is a variant of Hirens so see
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.
set DEFMENU=0 in \_ISO\MyE2B.cfg file
to remove Set Timeout and defaults menu entry.
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.
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
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.
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
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/
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.
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?
Re: Auto GFX=NONE and or Enable GFX mode depending on hardware/Resolution/Components
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!
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?
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!!
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?
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).
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.
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.
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.
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
linux /install/gtk/vmlinuz video=vesa:ywrap,mtrr vga=788 -- quiet
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 :)
Some USB drives have really fast Sequential rd/wr access but terribly slow 4K random access.
Test with CrystalDiskMark and check 4K times - should be well above 5
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 :(
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:
if "%LANG%"=="" set LANG=ENG
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 :)
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
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?
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.
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"
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.
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.
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?
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/
Tip: Check the \_ISO\Sample_MyE2B.cfg file for lots of different settings.
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. :)
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.
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.
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!
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.
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.
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
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.
Please define 'USB drive'?
What type? Removable or Fixed?
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.
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!
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?
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?
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.
Re: How to display Directory locations when adding menu entry .txt files?
Please see the page about .txt files
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.
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
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)!
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. :-)
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.
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!)?
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?
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...
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.
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.
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 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.
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.
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?
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.
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?
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?
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)
[lvu@lvu: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)
#LBL=CD VOLUME LABEL OF THE ISO use \\x20 instead of a space
map %ISO% (0xff) || echo -e $%ISO% IS NOT CONTIGUOUS! && map --mem %ISO% (0xff)
echo -e $WARNING: THIS WILL NOT WORK ON NTFS DRIVES (use FAT32 or ext2/3/4).
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
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?
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?
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"?
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?
OK. QEMU may be in snapshot mode or something...
You can also go to grub4dos console
can you see .mnu file?
P.S. You are quitting QEMU before you edit the drive contents and then re-running QEMU?
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.
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.
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.
I said you need to UPDATE your E2B drive.
Download the latest version.
Unzip it into a new empty folder.
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.
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?
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.