|
|
| Post Number: 11
|
balder 
Group: Members
Posts: 1942
Joined: Oct. 2008
|
 |
Posted on: Sep. 08 2012,02:25 |
|
   |
@ricfil
Quote: "The problem I´m facing on this one is the implementation of Bit Defender"
Please test given solution HERE
Most likely you must tick 'Joliet' when creating ISO in EasyBoot 
I call this kind of solution 'frugal solution' (simple solution) 
Note: solution might not work with the version you are using - it is related to version number 
But let's test and see if it works this way 
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: 12
|
ricfil
Group: Members
Posts: 22
Joined: Jun. 2012
|
|
Posted on: Sep. 10 2012,21:22 |
|
 |
Hello balder. Thanks for the reply once again. I´m afraid for the time being, It is not working this method. I always end up with "loading /casper/vmlinuz......
loading /casper/initrd.gz......" on the main screen both on qemu and virtual box. I´m using what seems like the version from 2010, still need to try the 2009 one. I´m in the process of burning a dvd to try on my real machine. We will see... Used the casper folder transfer method (Ultraiso), and the normal run xxx.iso command.
I should mencion my build does have knoppix on it(fully working with the "bootinfotable;run xxx.bif command), but the 2010 bit defender version has got "casper" folder on its .iso instead of the "knoppix" one...if that makes a diference...
Thanks again.
Will keep everyone interested posted 
|
|
|
|
| Post Number: 13
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Sep. 11 2012,05:37 |
|
|
@ricfil
Quote: "It is not working this method."
I downloaded Bitdefender ISO-file from HERE
Most likely this is the same 'rescue-cd' you already are using - if not - test using ISO from given link so that we use the same ISO-file
This is what I did:
1. Open ISO (I used UltraIso) and extracted folder 'casper' to folder 'EasyBoot\disk1'
2. Still having ISO opened in UltraIso I deleted file 'filesystem.squashfs' from inside of folder 'casper' in ISO-file
Attention! Only delete file 'filesystem.squashfs' and keeping folder 'casper' with the rest of files intact in ISO-file
3. Saved reduced ISO-file ('File>>Save As') to folder EZBOOT with name bitdefender10.iso
4. Used menu command in EasyBoot menu: run bitdefender10.iso
5. Ticked 'Joliet' when creating ISO in EasyBoot
Tested from CD-RW and also tested from USB drive (USB stick\Thumb-drive)
Worked excellent - especially when run from USB (faster response etcetera) 
If still having problems, test using my script 'easyboot-iso.script' to integrate reduced ISO into EasyBoot
Note: don't tick 'Run ISO from RAM' in script, as this is pointless in this 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: 14
|
ricfil
Group: Members
Posts: 22
Joined: Jun. 2012
|
|
Posted on: Sep. 11 2012,20:29 |
|
|
Hello there balder. I´ve just tested using the method you described (as I had done before), but this time, used the same iso image you used. Still using the ultraiso technic (and casper folder to easyboot) and run xxx.iso command/disk1) it still hangs loading those files I mencioned earlier(both on qemu,virtual box and physical machine) on my build. It certainly must be something due to some other iso boot files which break the Bit Defender boot process... BUT...  when I used your "build .iso" script, (along with the casper folder on /disk 1 and the shortened Bit Defender iso file)... and the .img comand it provides...voila! Bit Defender boots great! and fast! 
Will still test it more deeply to see if nothing is broken, but for now it seems on its good way , thanks to (offcourse) balder´s always precious and extremely useful help. Finnally I´ve got a pretty amazing set of tools to my own liking in my hands!
Thanks again for all the help man. I really apreciatte it.
Will come back with a definitive insight on the subject after more thoroughly tests
See you all.
|
|
|
|
| Post Number: 15
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Sep. 12 2012,01:59 |
|
|
@ricfil
Quote: "Bit Defender boots great"
I'm glad you made it so far
However it is a little bit strange you needed my script to solve this problem
In your case I would reinstall EasyBoot to fresh up the 'core' in EasyBoot to see if it works okay
There can be some 'scratches' in the 'core' - you never now
Anyway - it seems to work, and that's nice...
regards balder
Edited by balder on Sep. 12 2012,03:35
--------------
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: 16
|
ricfil
Group: Members
Posts: 22
Joined: Jun. 2012
|
|
Posted on: Sep. 16 2012,01:14 |
|
|
Hello balder. Sorry for the late answer (been busy with some important work stuff). Regardless of some problems that easyboot might have, as promised, and after several tests, I do confirm that the compilation is working properly (as in all boot compiled .isos and .img images are booting just fine). . Still, will try reinstalling easyboot and try the casper folder extraction technic once again. I do believe if I reinstall easyboot none off my later added files to the easyboot root and so force will be erased? Asking just thinking about my precious work putting all the suff there and all off a sudden all could be deleted from there (including menu configurations, etc)...
Anyway, will give that idea a go balder. Thanks for bringing it up, and of course, for all your precious help. Will post back as soon as possible.
|
|
|
|
| Post Number: 17
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Sep. 16 2012,03:07 |
|
|
@ricfil
Quote: "if I reinstall easyboot none off my later added files to the easyboot root and so force will be erased?"
Yes you draw the right conclusion - only the 'core' of EasyBoot is refreshed and nothing else
------------------------------------------
Quote: " I do confirm that the compilation is working properly"
Great news to hear
-------------------------
Here is some tricks that I use (including to have my 'old' builds untouched)
1. Create a new folder 'disk2' in folder EasyBoot
You should now have;
--EasyBoot\disk1
--EasyBoot\disk2
Note: you can have a lot of folders in here (disk3 etcetera)
2. Copy the whole folder EZBOOT to folder 'disk2'
You can now manipulate files in folder 'disk1' as you which
Next time you are interested to use the 'super-build' in folder 'disk2' you simply open ***.ezb-file (the main menu of course) in that 'disk2'-folder and create a new ISO
But remember that next time you launch EasyBoot files in 'disk2' is what EasyBoot is 'looking' into as ***.ezb-file in folder 'disk2' that was the folder\***.ezb-file last used.
If you instead double-click to the 'main menu' in folder 'disk1' (***.ezb) EasyBoot uses folder 'disk1' as the 'main target' folder next time EasyBoot is launched
Another trick...
You can rename folder 'disk2' (or folder 'disk1') to any reasonable letters length to what ever you like (including numerical)
This means you can have a lot of 'disk1'-folders that use names directly related to what kind of build you have in that specific folder.
Note: I'm unsure what the maximum length to folder name can be - I tested a 20 letters name (including several numerical numbers) and it worked okay
Another trick is to reduce files used in folder EZBOOT.
If not using memdisk or isolinux, you only need following files in folder EZBOOT to make it work:
loader.bin
ezldr
***.bmp (your background bmp-picture - can later be excluded when main menu ***.ezb-file is 'saved' and you are ready to create ISO in EasyBoot)
***.BM1 (the actual background used by EasyBoot core automatically created each time you push on 'Save' in EasyBoot, but then you again need the ***.bmp)
***.ezb-file (your main menu)
And of course all ISO-files and/or floppy images used in build
Note: you can use 'vfloppy' (vfloppy vivard.img as example) as menu command to avoid the need of memdisk
Above can be useful in case you run in to problems with size of the build (to fit into a CD or DVD)
regards balder
Edited by balder on Sep. 16 2012,05:39
--------------
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: 18
|
ricfil
Group: Members
Posts: 22
Joined: Jun. 2012
|
|
Posted on: Sep. 17 2012,12:30 |
|
|
Hie there balder. Thanks for the thorougly explanation. Still some doubts concerning using diferent folders.
If, for example I create a disk 2 folder and put the easyboot folder inside it, wouldn´t I still need the disk 1 files on it, not only the easyboot one (when creating boot images using the ultraiso extraction program, extracting also the boot files from the .iso image, those .iso files will go to folder "disk1" and not to the eazyboot (only the boot file info) ).... Wouldn´t I still need disk1 folder backed up? ...
Anyway, I did it my way. Made a backup of disk1, into disk 2. So that I could work on disk 1 as I wish. If the changes to the original disk 1 folder are many, and in the end I do not want to keep them I just delete disk 1 all together and rename disk2 to disk1... As you see, still a bit confused about using more than one build into easyboot "core"...To much work in the line here.
I´ve unistalled and reinstaled easyboot once again, did the casper transfer method and the run xxx.iso comand, still Bit Defender freezes when loading the same files....when using the build with your script, Bit Defender boots just fine... It must be something to do with other bootable .iso image, which is conflicting with the way the casper method works... I´m glad your script works fine
One more doubt. When creating a boot .iso, if I´ve tried the run xxx.iso command leaving the iso on the easyboot folder, and I see the method does not work, and later used the extraction method side of things and it works, when building the iso, will easyboot pick all he files on the folders adressed to building the iso or will it pick up ONLY the files needed by the menu commands provided? I´m asking just so I know if I can keep the files on the folders (for example the .iso on easyboot folder I talked above), or do I need to delete the one´s i don´t use, so the .iso building phase does not pick up all the "junk" on the folder... If you get my idea...
Thanks for any insight and all the help balder. still a semi noob on easyboot
See you
Edited by ricfil on Sep. 17 2012,12:31
|
|
|
|
| Post Number: 19
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Sep. 17 2012,13:24 |
|
|
@ricfil
Quote: "or do I need to delete the one´s i don´t use..."
and quote: "if I´ve tried the run xxx.iso command leaving the iso on the easyboot folder, and I see the method does not work..."
Hmm... I'm a little confused what you mean
Let me put it this way..
You can put ISO-file directly into folder 'disk1' but then you need to set 'absolute path' like this;
run /***.iso where '/' set the 'absolute path'
This also means you can use subfolders.
Let's say you create a subfolder 'linuxiso' inside folder EZBOOT (where you put all your linux ISO-files)
Then use this 'absolute path'; run /ezboot/isolinux/***.iso
Just an idea to keep a clean environment
You can create a folder 'FloppyImages' inside folder EZBOOT where you put your floppy images
Use 'absolute path' like this; vfloppy /ezboot/floppyimages/***.img
---------------------------
Quote: "If the changes to the original disk 1 folder are many, and in the end I do not want to keep them I just delete disk 1 all together and rename disk2 to disk1..."
Okay it can be a little bit confusing - it is only an idea - not a 'must do' thing
I generally don't use 'the ultraiso extraction program' - I simply open ISO with UltraIso mark files and folders and simply 'draw-and-drop' into wanted folder (disk1 or disk2 etcetera)
I guess 'each one is its own success' in what method that is preferred
-----------------
However most interesting is that my script again solved your problem - he, he - I think I grew an inch this week
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: 20
|
ricfil
Group: Members
Posts: 22
Joined: Jun. 2012
|
|
Posted on: Sep. 17 2012,19:44 |
|
|
[quote] "However most interesting is that my script again solved your problem - he, he - I think I grew an inch this week."
Indeed, and that is the most important thing for the end user. Glad the scripts are helpful..way helpful!
Regarding the paths to the run commands, I did not know we could create subfolders as we wished and run files from them. Always learning! A good way to help tide things up indeed.
[quote] "I generally don't use 'the ultraiso extraction program' - I simply open ISO with UltraIso mark files and folders and simply 'draw-and-drop' into wanted folder (disk1 or disk2 etcetera)"
in my case it leads to the same outcome (a bunch of files in disk 1 folder). And that was the main idea I was trying to pass. For example.
[QUOTE] "if I´ve tried the run xxx.iso command leaving the iso on the easyboot folder, and I see the method does not work..."
this was just an example of a bunch of files I could have to manage on diferenet folders. The .iso image on the easyboot one (if I try to run the iso directly with the run xxx.iso command) or the bunch of files (extracted or "drag and dropped" -its all the same really ) on the disk 1 folder using the extracted boot info from the iso in the menu command.
My doubt is, if i use one method over the other, BUT i´ve tried both, both the iso image (on the easyboot folder) AND the files extracted which belong to the image (on disk 1 folder) are still BOTH on the main easyboot folders (thus increasing disk space used). When compiling the iso image will the program pick up all the files (thus filling more the final image "size wise") or will it only pick up the files required for the command associated with that particular boot iso,img, etc? On the other hand will it join all files associated with the iso (even the iso image on the easyboot folder (which was not used-because the "extraction method was the one prevailing)?... that is my doubt... Willl I need to worry about deleting non used files (paths to those resident files) on the final compilation?
A bit confusing I know... Anyway, as you said, in the end booting the images fine is the main goal here. And that was all achieved, thanks to your help along the way balder. And for that I´m pretty much thankfull. .
See you.
Edited by ricfil on Sep. 17 2012,19:51
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
