|
|
| Post Number: 1
|
Hannes 
Group: Members
Posts: 68
Joined: Dec. 2003
|
 |
Posted on: Aug. 09 2011,12:01 |
|
   |
I see that a new version of EasyBoot has been released (version 6).
Is there somewhere I can look to find out what is new? I'm not seeing any information yet.
|
 |
|
|
| Post Number: 2
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Aug. 11 2011,14:13 |
|
 |
@Hannes
Quote: "Is there somewhere I can look to find out what is new?"
Good question 
The only major difference I have noticed, is that my scripts to launch ISO-files and to launch EasyBoot from USB device doesn't work correctly any more 
Seems there are some problem between grub and EasyBoot
Users that are interested to launch all kinds of different ISO-files and also interested of launch EasyBoot from USB device, are advised to use older versions of EasyBoot (not the latest updated EasyBoot_v6) 
Hopefully there is some bug that xoben quickly can sort out, as EasyBoot over-all is such a fine boot-manager to being acquainted with 
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: 3
|
|
|
| Post Number: 4
|
|
|
| Post Number: 5
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Aug. 12 2011,08:17 |
|
|
@xoben
Quote: "Could you please provide a step by step instruction for how to reproduce this problem?"
Well I'll try my very best
1. To launch ISO-files I use grub (floppy image with grub - I call them "grub-kicker-image").
2. To avoid "Allow lower case" I use memdisk to launch "grub-kicker-image".
However I'm not longer able to use memdisk (memdisk easus.img as example to launch ISO-file of EASUS partition manager). However this command can easily be replaced with;  bcdw easus.img  this works great from CD/DVD-unit.
When using memdisk I get:
EF
014211EF
Boot failed: press a key to retry
As I frequently was using this command I run in to some problem - but after your statement of improvements to EasyBoot - now I'm instead impressed - read below 
Note: In "reality" this is not any major problem as I noticed I can launch ISO-file (NT6-PE-ISO) simply by using menu command:  run msdart60.iso  (but NT5-systems WinXP-PE does not work - as we need "firadisk")
Anyway, this is not only great achievements, I say it is more of a giant step forward for all users of Easyboot - this is very impressing - thank you @xoben 
However we are interested to use EasyBoot menu from USB device as well (USB stick or harddisk).
This was done using grub to launch ISO-file created by EasyBoot - and from Easyboot menu we can launch any ISO-file (using "grub-kicker-images" that are launched from inside of EasyBoot-ISO-file on USB device).
I can still make EasyBoot run from USB - but before I used a specially script to make it easier for other users.
Script use "mkisofs" to create new ISO (with files from folder ezboot), it was here I run in to major problems
When creating ISO with mkisofs and using files from Easyboot version-6, all I get is the menu text (background is lost - only black background) and nothing works in Easyboot menu - and there I'm stuck
But again - this is not any huge problem as I'm pretty sure I can solve this problem.
I have do some workarounds to solve this issues
Basically - there are so many improvements done to EasyBoot so I guess I need at least one week to rework my scripts 
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: 6
|
xoben
Group: Super Administrators
Posts: 2200
Joined: Nov. 2004
|
|
Posted on: Aug. 12 2011,08:37 |
|
|
Thank you balder for your explanations.
It will be helpful if you provide detailed mkisofs parameters you used to cretae an ISO image.
|
|
|
|
| Post Number: 7
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Aug. 12 2011,08:52 |
|
|
@xoben
Quote: "It will be helpful if you provide detailed mkisofs parameters you used to cretae an ISO image"
Sure
Heureaka - Problem seems to be solved
Here is the original from script:
ShellExecute,Open,%BaseDir%\mkisofs.exe," -iso-level 4 -l -T -U %Rockridge% %joliet% %alc% -b  bootfile.bin -no-emul-boot -boot-load-size 4 -V %pTextBox16% -o %BaseDir%\%pTextBox16%.iso %BaseDir%\iso"
Basic command lines look like this:
mkisofs.exe -iso-level 4 -l -T -U -b bootfile.bin -no-emul-boot -boot-load-size 4 -o
I got suspicious  and removed: "-iso-level 4"
And now it is working okay as far as I have found out
regards balder
Edited by balder on Aug. 12 2011,08:53
--------------
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
|
xoben
Group: Super Administrators
Posts: 2200
Joined: Nov. 2004
|
|
Posted on: Aug. 12 2011,09:24 |
|
|
Thnaks balder for sharing parameters of mkisofs.
Just did as the following:
1) Create an iso image with mkisofs
mkisofs -iso-level 4 -l -T -U -b loader.bin -no-emul-boot -boot-load-size 4 -V BootMenu -o c:\easyboot\iso\mycd.iso c:\easyboot\disk1
2) Tested mycd.iso with VMWare 7.1.4
EasyBoot worked with no problem.
|
|
|
|
| Post Number: 9
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Aug. 12 2011,11:06 |
|
|
@xoben
Quote: "Could Just did as the following"
Yes this is correct. I think we can call it "basic" setting for mkisofs - I fully agree
However my problem occurs when I used script - let me explain:
1. Script copy everything from folder disk1 (or folder disk2 etcetera depending how you set path to Easyboot files).
2. Script then create a new ISO-file (ISO.ISO) based on folder ezboot
3. Finally script create a new ISO-file and integrate ISO from above into this ISO - It was here the problem occurred.
Above make it very easy to transfer the whole build to USB device and of course make it easy to launch EasyBoot menu - which is our goal
I use this method as we must copy (extract) some files from ISO-files to the "new root" which definitely isn't inside ISO created by EasyBoot.
You can for sure launch Hiren's Boot-CD but it's functionality is limited
Parted magic cannot be run if you directly run Hiren's ISO-file
We need to extract "root-files" to the "root" (folder disk1 or to the root of USB if run from USB device)
Parted Magic is an typo for this - read example HERE
Same to kaspersky etcetera
Note: in mentioned tutorial above we instead of my ISO-script, from now on, simply can use "run isofile.iso" - we don't need the script for this anymore
Basically this new possibilities that Easyboot offers makes it much easier to the full-fill "our dreams" to create the ultimate BOOT-CD/DVD or bootable USB device - but some ISO-files need to have their "root-files" extracted to the root of EasyBoot (normally folder disk1).
Note: this is NOT any limit related to EasyBoot - these limits are related to each specific ISO-file!
regards balder
Edited by balder on Aug. 12 2011,12:45
--------------
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: 10
|
xoben
Group: Super Administrators
Posts: 2200
Joined: Nov. 2004
|
|
Posted on: Aug. 12 2011,20:34 |
|
|
Understand and thank you.
Regards
Xoben
|
|
|
|
|
|
