|
Post Number: 1
|
allgames71 

Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted on: Apr. 05 2013,03:09 |
|
 |
hello balder
If 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
|
 |
|
|
Post Number: 2
|
balder 

Group: Members
Posts: 1942
Joined: Oct. 2008
|
 |
Posted on: Apr. 05 2013,06:11 |
|
 |
@allgames71
I 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
Edited by balder on Apr. 06 2013,02:49
-------------- Download complete set of scripts including help file HERE Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
 |
|
|
Post Number: 3
|
allgames71 

Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted on: Apr. 05 2013,15:13 |
|
 |
hello balder
Thanks 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
|
 |
|
|
Post Number: 4
|
allgames71 

Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted 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 :
Attached Image
|
 |
|
|
Post Number: 5
|
allgames71 

Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted 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
|
 |
|
|
Post Number: 6
|
allgames71 

Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted 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
|
 |
|
|
Post Number: 7
|
balder 

Group: Members
Posts: 1942
Joined: Oct. 2008
|
 |
Posted on: Apr. 06 2013,15:45 |
|
 |
@allgames71
First 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
-------------- Download complete set of scripts including help file HERE Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
 |
|
|
Post Number: 8
|
allgames71 

Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted 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
|
 |
|
|
Post Number: 9
|
allgames71 

Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted 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.
|
 |
|
|
Post Number: 10
|
balder 

Group: Members
Posts: 1942
Joined: Oct. 2008
|
 |
Posted on: Apr. 09 2013,12:22 |
|
 |
@allgames71
Quote: "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
-------------- Download complete set of scripts including help file HERE Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
 |
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|