Topic: 5GB iso file in Fat32
started by: allgames71
Posted by allgames71 on Apr. 05 2013,03:09
hello balderIf I were forced to use Fat32 boot active partition with Easyboot. But my Easyboot generated iso file is about 5GB in size. What can I do ?
In Easyboot program , different items can be save in different .ezb(s). Let's say if I've 6 .ezb(s) totally become a 5GB mydisk.iso file.
Is it possible , I use Easyboot to make 2 mydisk.iso , that is mydisk1.iso and mydisk2.iso And bootmenu.ezb in mydisk1.iso can call the bootmenu.ezb in mydisk2.iso or other .ezb in mydisk2.iso.
So when start to boot this Easyboot , only the mydisk1.iso bootmenu will show up , then to call the other .ezb in mydisk2.iso. And it seems there's only one bootmenu at the start up.
Is this possible ? Thanks
Posted by balder on Apr. 05 2013,06:11
@allgames71I think we can find a way out for this - but take some time to explain my ideas
However, I'm heavily occupied for at least 8 hours
I'll be in touch when home again
EDIT:
Did some test to find alternative solutions...
Create a new folder 'disk2' in folder EASYBOOT
And create a folder easy2 inside that folder disk2
You should now have this structure:
EasyBoot\disk1\ezboot
EasyBoot\disk2\easy2
Note: you can create several more 'disk1'-folders (disk3 disk4 etcetera)
Copy following fundamental needed files from folder EasyBoot\disk1\ezboot to folder EasyBoot\disk2\easy2:
Background picture(s) ***.BMP
***.ezb (of course including all ***.ezb files if using submenu etcetera)
You only need those two files to make it work
Start EasyBoot and choose to 'Open' and scroll to EasyBoot\disk2\easy2 and open you main menu file ***.ezb in that folder
Change background or whatever and create submenu or whatever
Then push 'Save' to save changes in folder 'easy2'
Go back and open your original ***ezb-file in folder EasyBoot\disk1\ezboot (the 'main menu')
Open grub-kicker-image 'harddisk.img' in my folder 'balder\usb-resources'
Extract text-file 'menu.lst' and delete all text and insert this text:
find --set-root /easy2/ezldr
chainloader --raw /easy2/ezldr
Save changes to text-file and inject back 'menu.lst' to 'harddisk.img' and choose to 'Save as' to folder EasyBoot\disk1\ezboot using name 'easy2.img'
Create menu entry: run easy2.img in your main menu in folder disk1\ezboot
Above grub-kicker-image launch ezldr in folder 'easy2'
You can create ISO as usual using 'main menu' in folder disk1\ezboot
Then 'Burn' to USB device as usual
Now simply copy folder 'easy2' to the root of USB device
Menu entry that launch 'easy2.img' then launch main menu in folder 'easy2'
You can of course create a menu entry in folder 'easy2' that launch menu in folder ezboot modifying 'easy2.img' to launch 'ezldr' in folder ezboot - simply like this:
find --set-root /ezboot/ezldr
chainloader --raw /ezboot/ezldr
This also shows you can have several folders 'easy2' (easy3 etcetera, or any name you prefer to use. But always push 'Save' in that folder easy2 or whatever the name is to that folder)
The point with this arrangement is that you easily can change the content in folder 'easy2' without touching the 'main menu' in folder ezboot on the root of the USB device
But we still only have one root (even I fail to conjure up a new root from my 'magic box'
) We only have one 'root' and that's is a fact
There are more solutions to test (use ISO-files created by EasyBoot - launched using grub-kicker-images)
But using folders reduce problems with that ISO-files must be 'contiguous'
regards balder
Posted by allgames71 on Apr. 05 2013,15:13
hello balderThanks for your long explanation. I've read it through.
But a stupid guy can only understand the concept , and actually understand 50% of it.
I've to do the test , really takes time for me , may be few days , and will let you know my result. Thanks
Posted by allgames71 on Apr. 06 2013,14:22
hello balder ,quote :
Start EasyBoot and choose to 'Open' and scroll to EasyBoot\disk2\easy2 and open you main menu file ***.ezb in that folder
Change background or whatever and create submenu or whatever
Then push 'Save' to save changes in folder 'easy2'
When I put "Save" , an error message comes out , as I use press [Esc] to return to bootmenu :
Posted by allgames71 on Apr. 06 2013,14:52
hello blader ,quote :
Create menu entry: run easy2.img in your main menu in folder disk1\ezboot
Above grub-kicker-image launch ezldr in folder 'easy2'
--------------------------------------------------------------
Sorry balder , I don't understand these 2 sentences mean :
1. Do you mean in the disk1...bootmenu.ezb add an entry , and in the menu command type : run easy2.img. And the Menu Text can be anything ?
2. What is "Above grub-kicker-image" mean ? How can I start this launch ?
Thanks
Posted by allgames71 on Apr. 06 2013,15:19
hello balder ,Something very strange , normally the Easyboot folder size is nearly the mydisk.iso size. But this time after I make the mydisk.iso , it's only 3.39GB. And the Easyboot folder size is 5.27GB.
Before following your instruction to modify my Easyboot , the mydisk.iso was 4.47GB. So where are the files gone ?
Thanks
Posted by balder on Apr. 06 2013,15:45
@allgames71First of all: I know that it looks a little bit cryptic when you look into it the first time (which I guess also is a part of my far from splendid explanation
)However I'm sure you in the end understand what I mean
Quote: "add an entry , and in the menu command type : run easy2.img. And the Menu Text can be anything ?"
Exactly what I mean!
What you put in Menu text is your personally thing (something like 'Launch second menu' or whatever)
Note: We can launch file 'ezldr' in folder 'easy2' on USB device using grub with text-file 'menu.lst' in the floppy image 'easy2.img' launched from the main menu (menu that first shows up and is the 'main menu' used in folder disk1)
Grub then tries to find file 'ezldr' in folder 'easy2' on the USB device
We have set this scenario by using menu.lst with this text:
find --set-root /easy2/ezldr
chainloader --raw /easy2/ezldr (this launch ezldr in folder easy2)
Note: you can use any name to folder ezboot (I used for fun 'easy2')
You can also use a different name to folder disk2 if you are amused by that
I don't understand why you get error with that file bootmenu.ezb
Try again copy any 'main menu' (including correct background ***.bmp-picture) to folder disk2\easy2
Launch EasyBoot and push to 'Open' and scroll to folder EasyBoot\disk2\easy2 and double-click to bootmenu.ezb (or whatever the name is to menu used in folder easy2)
Menu should then show up and you should be able to push to 'Save in EasyBoot (you may get messages typically 'Boot Image File 'C:\EasyBoot\Ezboot\winpe.iso' not Exist!)
But this is only because you have menu entries left in menu that must be cleared (or replaced with what ever you like to launch from this separate menu in folder easy2)
Quote: "So where are the files gone ?"
If you only copy ***.bmp background and any 'main menu' (***.ezb) to folder disk2\easy2 followed by 'Open' ***ezb in folder easy2 and finally pushing 'Save', the size of folder easy2 should end up close to less than 3.8 MB But if you put in more files winpe.iso or whatever the size of folder easy2 grows
Attention! Never create any 'mydisk.iso' using menu in folder easy2. Only use this folder (easy2) on the root of USB device
Mydisk.iso should always be created when 'main menu' in folder 'disk1\ezboot' is used
I don't understand what happens in you case
regards balder
Posted by allgames71 on Apr. 08 2013,04:36
hello balder ,Sorry for my late response , because I'm learning about UEFI Multi-boot with Easyboot in the reboot-pro forum.
I'll contact you as soon as possible.
Sorry
Posted by allgames71 on Apr. 09 2013,03:43
hello balder ,Sorry to ask you a question beyond this topic , unlike you , the reboot-pro wouldn't answer much. They just give me a way , with no brief explanation or example. Such a stupid man like me , really can't understand.
The problem is not the knowledge of UEFI , it's about bcdedit , but if I can't solve this problem , then I can't go on UEFI with Easyboot. So please help.
I've made with Easyboot an iso.iso and want to add this boot to a MBR ( F: ) , after adding this boot entry , it should be looked like this when boot :
Windows 8
Grub4DOS
They have a program which made this work fine , but this program include a lot of stuff that I don't want and can't be erased. After applying this program , in the bcdedit it looks like this :
Real Mode Boot Section
----------------------------------------------
identifider {default}
device boot
path \grldr.mbr
description Start GRUB4DOS
I made it this way (F: is the boot partition) :
1. bcdedit.exe /store F:\Boot\BCD /enum all
2. bcdedit.exe /store F:\Boot\BCD /create /d "Start GRUB4DOS" /application bootsector
3. bcdedit.exe /store F:\Boot\BCD /set {guid} device boot
4. bcdedit.exe /store F:\Boot\BCD /set {guid} path \grldr.mbr
5. bcdedit.exe /store F:\Boot\BCD /displayorder {guid} /addlast
The outcome is :
identifier {guid}
description Start GRUB4DOS
It seems :
I can't set the "identifier" to {default}
The above lines 3 and 4 are not effective with no result
Line 5 "addlast" can't be added
When I boot this thing , I don't have "Start Grub4DOS" to choose , instead , it goes to Win8 right the way.
Would you mind to tell me how to modify the bcdedit setting ? Thanks a lot and sorry for my impolite.
Posted by balder on Apr. 09 2013,12:22
@allgames71Quote: "Would you mind to tell me how to modify the bcdedit setting ?"
The (UEFI) Unified Extensible Firmware Interface is still a problem for me to handle
As I wrote earlier, I have a 'hardware problem' as I do not have such motherboard to test anything anywhere
Sorry not much I can do for the moment if not the EasyBoot develop team can figure out possibility to handle UEFI
regards balder
Posted by allgames71 on Apr. 09 2013,12:49
hello balder ,It's OK , nevermine. I'll try to find the answer again.
Thanks
Posted by allgames71 on Apr. 11 2013,10:19
hello balder ,I'm back , sorry for too late. Now I can make UEFI / MBR + Multi Boot + Easyboot.
It took a long time find out the solution as people in reboot-pro don't want to answer much or just give very short instruction. Finally the Gold Member even don't want to reply me at all !
Fortunatelly , I can find a tricky way to solve the probelm and made my wish.
Back to Easyboot , I've try again your tutor and do it as follow :
disk1\ezboot
\ezboot\BACK.BMP
\ezboot\easy2.img (command in bootmenu : run easy2.img)
\ezboot\easy3.img (command in bootmenu : run easy3.img)
\ezboot\easy4.img (command in bootmenu : run easy4.img)
\ezboot\ezldr
\ezboot\loader.bin
\ezboot\setupnt6.img
disk2\easy2\isofiles2
\easy2\backup.BM1
\easy2\backup.BMP
\easy2\backup.ezb
\easy2\bcdw.bin
\easy2\ezldr
\easy2\loader.bin
disk3\easy3\isofiles3
\easy3\ezldr
\easy3\isolinux
\easy3\loader.bin
\easy3\Part.BM1
\easy3\Part.BMP
\easy3\part.ezb
\easy3\syslinux
disk4\easy4\isofiles4
\easy4\ezldr
\easy4\loader.bin
\easy4\winpe.BM1
\easy4\winpe.BMP
\easy4\winpe.ezb
In Easyboot I made the mydisk.iso and run it in VMWare , when I choose easy2 in the startmenu , an error message comes out. I think it may not link the easy2 from the bootmenu.ezb in disk1 :
Posted by balder on Apr. 11 2013,12:37
@allgames71Quote:” an error message comes out
Well check that ‘menu.lst’ in grub-floppy-image ‘easy2.img’ in folder disk1 has these lines:
find --set-root /easy2/ezldr
chainloader --raw /easy2/ezldr
This works when using FAT32 – I have tested and made it work alright
Note: letters are not case sensitive in text-file ‘menu.lst’ as we are using FAT32 (any USB device of some sort)
But maybe there is a problem with UEFI as Grub may have problem to find USB device at all (no BIOS that grub can ‘collect information’ from)
You cannot by any chance test this from a ‘normal’ computer (that have ‘normal’ BIOS)
Regards balder
Posted by allgames71 on Apr. 11 2013,13:48
hello balder ,Thanks for replay , now I can understand your first instruction mean , in post number 12 , my file structure is correct. Now I can do what you expect.
After boot , when I choose to call disk2 (backup.ezb) , backup.ezb shows up. And some of the programs can run normally. It means your idea works. But I found a strange condition , for example :
run isofiles2/gpt.iso (menu command with "run") boot OK
bcdw isofiles2/acron2013.iso (menu command with "bcdw") boot fail
--------------------------------------------------------------
Error : Unexpected exiting.
Press any key to boot from hard disk or ESCape to reboot ...
--------------------------------------------------------------
I use this "bcdw" menu command for Acronis 2010 , 2012 , 2013. They all boot OK before when it was in one 5GB.iso . Why is different and boot fail now ?
I've tried to change the menu command to :
run isofiles2/acron2013.iso
But with the same error as above.
Any idea ? Thanks
Posted by allgames71 on Apr. 11 2013,14:30
hello balder ,Another strange thing happen. When bootmenu.ezb boot , I can boot up disk2 (backup.ezb). But when I boot disk3 (part.ezb) , an error message comes out :
Starting cmain( ) ... (hd0,0)
File not found : /EASY3/PART.EZBu.ezb
Press any key to restart ...
It should be /EASY3/PART.ezb ?
When I boot disk4 (winpe.ezb) , same error message comes out :
Starting cmain( ) ... (hd0,0)
File not found : /EASY4/WINPE.EZB.ezb
Press any key to restart ...
It should be /EASY4/WINPE.ezb
Please help. Thanks
Posted by allgames71 on Apr. 11 2013,14:34
hello balder ,I've checked easy2.img , easy3.img and easy4.img , they're all the same. Only the number is different.
Even I delete disk3 and disk4 and remake them , but with same result.
Please help. Thanks
Posted by balder on Apr. 12 2013,09:00
@allgames71Quote: ” bcdw isofiles2/acron2013.iso (menu command with "bcdw") boot fail”
Menu command ‘bcdw’ cannot work properly from FAT32 (only CDFS = CD\DVD)
Further more, try to use my script ‘easyboot-iso.script' without ticking ‘Run ISO from RAM’ (only used to WinPE based on NT5-system\WinXP\Server-2003, which means typically ISO-files ERD2005, BartPE, Reatogo etcetera using folder i386 inside ISO-file)
I think my script can launch acronis
…………………
Quote: “It should be /EASY3/PART.ezb”
EDIT!
Well no!
It is not the 'ezb-file' we launch from grub-kicker-image, it is the ezldr-file we launch by this text to 'menu.lst' inside kicker-image:
find --set-root /easy2/ezldr
chainloader --raw /easy2/ezldr
File 'ezldr then launch the 'main menu' ezb-file
In your case, part.ezb in folder easy3
Note: I’m not 100%sure but there can be a limit to how many ‘disk1’ folders that can be used at same time.
Try to only use 3 ‘disk1’ folders (part1, part2, and part3 or whatever)
Also try using same length to folder ´ezboot’ (6 letters) when changing name to that folder
And\or test with only using one extra ‘disk1’ folder (part1) and see if you can make that work before doing the ‘big thing’ with a ‘super build’
--------------------------
Quote: “It means your idea works”
Yes so far so good (but it is easy to reach ‘deep water’ when experimenting with this stuff, but that is a part of the game)
I’ll do some testing when home again (I'm in another city)
I have sold my house and have for the moment no idea where to find a apartment (or house) to start up fresh again (I’m mostly looking for a new house but hard to find a fresh building I like)
So I’m pretty occupied, but like to do something else to stress down a little bit
Interesting test you are doing – I’ continuously reading what’s going on
Regards balder
Posted by allgames71 on Apr. 12 2013,13:03
hello balder ,I tried acronis2013.iso with Easyboot-iso-script
But it fail with X Errors(1)
X FileCopy-Failed to copy [%BaseDir%\Temp\newwinimage\ACRONI.img] to: [C:\Easyboot\disk1\EZBOOT\ISOFILES\ACRONIS]
But still C:\Easyboot\disk1\ezboot\ISOFILES\ACRONI created , and in there , a ACRONI.ISO existed
I'm thinking if the Easyboot-iso-script will place the iso file in Disk1 , then Disk1 will become bigger and bigger to over 2GB.
1. Why write fail ?
2. I've tried , but fail to place the acronis2013.iso in Disk2 , as the Easyboot-iso-script didn't allow to and stop
Thanks
Posted by balder on Apr. 12 2013,15:46
@allgames71I can confirm that menu command: run ***.iso works correctly from USB device using FAT32
I have tested Acronis_True_Image2012.iso with success
Test this:
1. Use any USB device (I used a USB stick) that already have a easyboot menu working okay
2. Delete all files and folders from USB stick (don't format - simply delete)
3. Download my test-files from < HERE >
4. Open zip-file and folder USB and copy folder ezboot and folder test and file ezldr to USB stick
5. Test USB stick when finished with step 4
You should be able to jump between the two menus in example
EDIT!
I was wrong here.
Name to main menu must be exactly the same as the name you used when you 'burned' to USB stick
This is set in boot record when you burned to USB stick!!!
You can now copy Acronis ISO-file to inside of folder test
Make sure name to acronis ISO-file is acronis.iso
This is a little bit hazardous as ISO-file might get fragmented while copying to USB stick, but mostly it works okay
You should be able to launch acronis from menu in 'test'
Test and see if you can get it to work alright
Note: you can simply double-click to any of the two ***.ezb-files and open them with EasyBoot even from the USB stick to get a glue what menu command that is used in these menus
regards balder
Posted by balder on Apr. 13 2013,04:38
@allgames71Here is a modified version how it can be done
Download < HERE >
Launch easyboot and open folder usb\ezboot and open file 'mainmenu.ezb' and 'Burn' to USB stick.
Then manually copy folders 'test' and folder 'winpe' to the root of USB stick
That should do it
regards balder
Posted by allgames71 on Apr. 13 2013,12:02
hello balder ,Your last sample that leads me to success. I think mainly becuase it's simple. Simple is the best , it can avoid lots of unknown errors :
can't find PART.EZBu.ezb
can't find Disk3
can't find Disk4/easy4/easy4/isofiles4/xxx.iso
Just like you , I create :
Disk2 ...
Disk2\acron10.iso ................................ OK
Disk2\acron12.iso ................................ OK
Disk2\acron13.iso ................................ OK
Disk2\backup.bmp
Disk2\backup.ezb
Disk3 ...
Disk3\EaseusPM7.iso ........................... boot FAIL (Easeus Partition Master 7)
Disk3\EPM9.iso ..................................... OK
Disk3\MPW7.iso ................................... boot FAIL (MiniTool Partition Wizard 7)
Disk3\PHD12.iso ................................... OK
Disk3\part.bmp
Disk3\part.ezb
Disk4 ...
Disk4\RXPE.iso ...................................... boot FAIL (Remember this was hard to success and easy to Fail ? I hate it , but I need it)
Disk4\7PE_BS.iso .................................. OK
Disk4\7PE_My.iso ................................. OK
Disk4\8PE_BS.iso .................................. OK
Disk4\winpe.bmp
Disk4\winpe.ezb
For the above 3 "boot FAIL" items , I'll try them again. Why I'm happy now is because , with your tutor , I can make so many items success to boot normal.
balder , you're great :
1. Simple will minimized error.
2. Everytime if I've to edit my boot program , I can edit them individually and without having to remake the whole big "mydisk.iso" (5GB) again and wait for a long time
3. Even I've to edit the mainmenu (bootmenu.ezb) , now it's only about 80MB , it create "mydisk.iso" very fast without touching the other Disk2 , Disk3 and Disk 4
After trying the above 3 "boot FAIL" items , I'll let you know my result or need your help. Also I'll try the [Esc] key to go back to mainmenu (bootmenu.ezb) from Disk2 , Disk3 and Disk4
Thanks a lot again
Posted by allgames71 on Apr. 14 2013,05:18
hello balder ,I can run all my programs now normal. I want add a [Esc] key in Disk2 , Disk3 and Disk4 to go back to Disk1\bootmenu.ezb.
I made a disk1.img in Disk2 , like your harddisk.img , I modified the menu.lst like this :
find --set-root ezboot/BOOTMENU.EZB
chainloader --raw ezboot/BOOTMENU.EZB
or
find --set-root disk1/BOOTMENU.EZB
chainloader --raw disk1/BOOTMENU.EZB
(But actually disk1 is not exist in usb stick)
What's wrong with the disk1.img
Thanks
Posted by balder on Apr. 14 2013,06:08
@allgames71Quote: "find --set-root ezboot/BOOTMENU.EZB
chainloader --raw ezboot/BOOTMENU.EZB"
Must be:
find --set-root /ezboot/ezldr
chainloader --raw /ezboot/ezldr
Notice: /ezboot/ezldr
Also notice you only need to replace 'bootmenu.ezb' on USB device (in this case 'bootmenu.ezb in folder 'ezboot') and of course also copy modified 'grub-kicker-image' to (in this case) folder 'ezboot'
Don't forget to push 'Save' in EasyBoot so the changes in the menu 'bootmenu.ezb' is in place, before copying and overwriting existing 'boomenu.ezb' on USB device
EDIT!
I can confirm that '[Esc] key' using menu command: run ***.img with 'grub'kicker'image' as expected is working perfectly
Wow it gets better and better
........................
regards balder
Posted by allgames71 on Apr. 15 2013,14:02
hello balder ,Sorry , I don't mean it's a menu item to use menu command. I mean "Misc" colume :
[Misc] ... [Func Key] Esc ... [Command] ... run disk1.img
And the menu.lst in disk1.img is :
find --set-root /ezboot/BOOTMENU.EZB
chainloader --raw /ezboot/BOOTMENU.EZB
I place disk1.img in Disk2 , Disk3 , and Disk4 each. Normally the disk1.img should like the disk2.img , disk3.img and disk4.img
I put the disk2.img , disk3.img and disk4.img in \ezboot , that's why in bootmenu.ezb menu item with menu command :
run disk2.img
run disk3.img
run disk4.img
So bootmenu.ezb can find the Disk2 , Disk3 and Disk 4
Alternately , why disk1.img in Disk2 can't find bootmenu.ezb ?
Thanks
Posted by allgames71 on Apr. 15 2013,14:09
hello balder ,This is the structure :
Disk1\ezboot\bootmenu.ezb
\ezboot\back.bmp
\ezboot\disk2.img
\ezboot\disk3.img
\ezboot\disk4.img
Disk2\backup.ezb
\backup.ezb
\disk1.img
Disk3\part.ezb
\part.bmp
\disk1.img
Dsik4\winpe.ezb
\winpe.bmp
\disk1.img
Thanks
Posted by balder on Apr. 15 2013,14:59
@allgames71Quote: ”Alternately , why disk1.img in Disk2 can't find bootmenu.ezb ?”
Yes that’s a good question to ask
I cannot find any problem in your structure that should cause any problem for grub to find ‘bootmenu.ezb’ in folder ‘ezboot’
Unfortunately I’m not in my home residence until Tuesday this week, which stops me from doing needed tests
To clarify…
Is it only: “[Misc] ... [Func Key] Esc ... [Command] ... run disk1.img” that fails
I mean if you simply create a menu entry in let’s say ‘backup.ezb’ (run disk1.img), can you then jump back to ‘bootmenu.ezb’
Regards balder
Posted by allgames71 on Apr. 16 2013,06:32
hello balder ,It's not only happen in "[Misc] ... [Func Key] Esc ... [Command] ... run disk1.img” , but also in add item.
I find out the reason is there's no Disk1 in usb stick root. The menu.lst in disk1.img ask to find bootmenu.ezb , but there's no disk1 in root directory. So an hour-glass comes out and hang.
I've tried to copy the whole Disk1 folder to the root of usb stick , and in the "[Misc] ... [Func Key] Esc ... [Command] ... run /disk1/ezboot/bootmenu.ezb"
When boot , in disk2 , I can really go back to bootmenu.ezb , but surely that's usb stick\Disk1\ezboot\bootmenu.ezb. Still there's mistake , I can see the bootmenu.ezb but with no background , and but this moment , I can't go into either disk2 , disk3 or disk4.
I know of course this's not the right way to solve. But I don't know how. Sorry no other way in my mind.
I think the failure possibilities are :
run /disk1/ezboot/bootmenu.ezb
run /ezboot/bootmenu.ezb
run bootmenu.ezb
run /iso/iso
Any idea ? Thanks
Posted by balder on Apr. 16 2013,16:05
@allgames71Quote: ” run /ezboot/bootmenu.ezb”
Sorry, this can never work
When run from USB device following rules apply:
You can from the first menu (the main menu - menu that is launched when USB device boot up) use following ‘standard’ menu command (if I can recall correct):
Run ***.ezb (usually some jump to some sub menu inside folder 'ezboot')
But above only works from the folder you started (usually folder ezboot)
However, as we are interested to ‘fool’ EasyBoot to launch a ‘main menu’ from folder with a different name than folder ‘ezboot’, we need to use a ‘grub-kicker-image’ - typically with a grub command in text-file ‘menu’lst’ like this example:
find --set-root /ezboot/ezldr
chainloader --raw /ezboot/ezldr
This force the ‘main menu’ in folder ‘ezboot’ to launch
It is not menu file ***.ezb we launch, it is the binary file ‘ezldr’ that must be launched - in this example - ezldr in folder ‘ezboot’
Read in post nr;13 and also take a closer look into my example in download in post nr,20
Sorry I was under stress this days and didn’t notice you tried to launch ***.ezb when it must be file ‘ezldr’ that is the target - using grub-kicker-images’ to launch 'ezldr'
I have edit post nr; 23 to correct menu.lst command
Note: funny is that if only having two different folders on the root of USB device, let’s say one folder ‘ezboot’ and one folder ‘winpe’ (holding menu to launch WinPE-iso-files), then you can use menu command in EasyBoot (at least I managed it to work):
Run /winpe/ezldr
This launch menu in folder ‘winpe’
And to jump back to folder ‘ezboot’ with its ‘main menu’ you simply use menu command in menu in WinPE:
run /ezboot/ezldr
This launch ‘main menu’ in folder ‘ezboot’
But if using 3 different folders it fails completely
Regards balder
Posted by allgames71 on Apr. 17 2013,04:49
hello balder ,I've done this test :
1. By using your usb.zip which has folders ezboot and test , which in test folder , the menu.lst in ezboot.img is :
find --set-root /ezboot/ezldr
chainloader --raw /ezboot/ezldr
I know it calls the /ezboot/ezldr and not /ezboot/test.ezb
2. In my easyboot , I've C:\Easyboot\disk1\ezboot , Disk2 , Disk3 and Disk4.
I made a new folder in C:\Disk1 and copy all the contents from C:\Easyboot\disk1\ezboot to this new folder
Copy the whole Disk2 folder to C:\Disk2
Use Easyboot to open bootmenu.ezb in C:\Disk1 , save it.
When I compile to a C:\Easyboot\iso\mydisk.iso , this mydisk.iso should only be 82MB in size , but it takes a long time to complie , even with an error message.
balder , I think until now , what I need is already fulfilled , if it's only a minor problem that can't return back to the bootmenu.ezb , I really don't mind.
Thanks for your turoring all along.
Posted by balder on Apr. 17 2013,05:40
@allgames71Thanks for your information
However, I’ll continue to do tests for future use (I have some ideas what can be done to ’optimise’ jumps between different EasyBoot menus run from USB device)
It will take some days before I’m back in my home residence to start this procedure
Regards balder
Posted by allgames71 on Apr. 17 2013,13:30
hello balder ,There must be a lot of work to do when moving a house , especially when packing all the things in boxes. Also it's headache stuff for the boxing day in the new house.
Never mine about me , inter-communicating between different Easyboot menu is not that important and urge to me , as I've already finished my work under your tutoring.
Do your work first , my problem later. OK
Thanks