Topic: Easyboot 6 and Linux Live KAV/AVIRA live
started by: EB1000
Posted by EB1000 on Aug. 30 2011,13:29
Hello all, especially mr balderit's been awhile since my last post here. I decided to create a new updated multiboot DVD. I was able to get almost everything to work using a mix of old methods and new ones based on run iso command, except for 3 iso's
The first is linux ubuntu live 10.04. it works using grub menu with the following code:
find --set-root /UBUT.ISO
map /UBUT.ISO (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/UBUT.ISO splash
initrd /casper/initrd.lz
How can I do the same for ezboot6?
The second is AVIRA rescue cd. It is also linux based using isolinux.cfg file on the root of the avira.iso. The cfg menu uses this command:
kernel vmlinuz
append nofb initrd=initrd.gz ramdisk_size=108178 root=/dev/ram0 rw console=/dev/vc/4
The third is the goodold Kaspersky rescue 10 which use to work after extracting the iso to disk1 and using the command:
bcdw kav10.img
Now it does not work. it loads most of the process but then linux prompt complains about not finding boot media...
On the new multiboot I have the following working:
1 Acronis true image home 2011 (run iso)
2 Acronis Disk dicertor 2011 (run iso)
3 Paragon partition manager 2011 (run iso)
4 Hiren boot cd 14.1 (works thanks to balder script, did not try run iso yet)
5 Win7PE se (sp1) (memdisk pe7.img.gz)
6 Gold memory 7 pro ( run iso)
7 QuicktechPro 5/8 (run iso)
8 ActivebootDisk disk 5 (run iso)
9 Ultimate boot Disk 5 (run iso)
Still not working:
10 kaspersky rescue 10
11 Avira rescue
12 Linux live
disk size is almost 4GB (any other bootable iso's that I'm missing wll be welcomed :-) )
One more quastion to mr balder: did you update your script to be ezboot 6 compatible? Did you try hiren's 14.1 run iso command?
many thanks
Posted by balder on Aug. 30 2011,16:34
@EB1000Quote: "One more quastion to mr balder: did you update your script to be ezboot 6 compatible?"
Yes scripts been updated as we cannot any longer (at least for the moment) use the "memdisk-command", it doesn't work at all. Scripts been updated in many ways to better performance.
Quote: "Did you try hiren's 14.1 run iso command?"
Same as above. Download updated scripts to get the right menu command from script to use in Easyboot menu (as usual, push on button "Integrate Hiren's BOOT-CD" in easyboot-iso.script).
-----------------------------------
Quote: "Still not working:
10 kaspersky rescue 10
11 Avira rescue
12 Linux live
We have problems with "memdisk ***.img.gz " menu command in EasyBoot.
Download updated scripts to solve this issue
Tutorial for kaspersky-10.
1. Make a copy of kaspersky iso as we are going to manipulate iso
2. Extract from ISO folder rescue and file image.squashfs and file livecd to folder disk1
3. Delete folder rescue and file image.squashfs and file livecd from inside of ISO
4. Save ISO-file that now is much less in size with the name KASPERSKY10.ISO
5. Copy ISO to folder ezboot and use menu command in EasyBoot: run KASPERSKY10.ISO
6. Check "Joliet" when creating ISO in Easyboot.
Note: you can also use my script "easyboot-iso.script" to integrate KASPERSKY10.ISO into Easyboot as usual (read below the benefit of using my script)
Tutorial for Avira rescue.
1. Make a copy of avira iso as we are going to manipulate iso
2. Extract from AVIRA.ISO-file folder system and folder antivir and folder avupdate to folder disk1 in Easyboot
3. Delete folder system folder antivir and folder avupdate from inside of AVIRA.ISO-file
4. Save ISO-file that now is less in size with the name AVIRA.ISO
5 Use my script "easyboot-iso.script" to integrate AVIRA.ISO into Easyboot as usual and use menu command given by updated script (you must use updated script-collection)
Note: you cannot simply copy AVIRA.ISO to folder ezboot and use the new menu command in EasyBoot: run AVIRA.ISO as it doesn't work for avira but works for kaspersky.
However, my script do not fail, it works for any ISO-file without hesitating.
Read about the new facilities in EasyBoot < HERE >
And discussion < HERE >
And about updated scripts read post nr; 8 and 9 < HERE >
Tutorial for UBUNTU (Linux live 10.04).
1. Copy UBUNTU .ISO to folder disk1 (make sure iso-file is named exactly UBUNTU.ISO)
2. Download my "grub-kicker.image" from < HERE >
3. Extract ubuntu.ima from zip-file to folder ezboot
4. Use menu command in EasyBoot: bcdw ubuntu.ima
5. Check "Joliet" when creating ISO in EasyBoot.
Note: Some software cannot be tested with Microsoft Virtual PC
You can use this freeware < HERE >
regards balder
Posted by EB1000 on Aug. 30 2011,18:35
@ balderThank you very much! I will try this tomorrow morning and report back. BTW, do I still need to download "grub-kicker.image" even if I have the latest balder.zip?
One last question: is there a easy way to boot miniXP only from Hiren in EB6 (i.e does the same method used in EB5 sill work?)
Thanks again (if your not yet employed by Ezbsystems, they should send you a huge check for the great service your doing here...)
Posted by balder on Aug. 31 2011,03:22
@EB1000Quote: do I still need to download "grub-kicker.image"
I guess you are referring to UBUNTU?
And yes you need that specially designed "grub-kicker.image" to make it work.
For the common user of the bootloader grub this is no "hot news" - I haven't "invented" anything.
But I improvised how we can use grub via "grub-kicker.images" and there you have my "contribution" (if I may say) to how we can use EasyBoot.
And same to the option to launch EasyBoot from USB - another benefit (or shall we call it; "spin-off-effect")!
Note: The "easyboot-iso.script" creates a new specially designed "grub-kicker.image" each time you integrate ISO-file into EasyBoot - it's an pretty simple procedure if you know how to do it.
Method mentioned is extremely reliable - it never fails (though ISO-file itself may fail to boot, but that is a question about the ISO-file and not my "grub-kicker.image").
If integrating WinPE-ISO built from source of WinXP, you check "Run ISO from RAM" and when doing this, script behaves different.
Script now integrate "firadisk"-driver to launch WinPE-ISO - it is slightly more "advanced", but nothing difficult in anyway (credits to the brilliant "karyonix" for his development and efforts in this issue).
Again it's an question of improvising
-----------------------------------------------
Quote: "is there a easy way to boot miniXP only from Hiren in EB6"
It depends on what version of Hiren we are dealing with?
For reference also read post nr; 2 and 4 < HERE >
Generally in EasyBoot-version6 you must use menu command: bcdw and NOT run and NOT memdisk
For "older" Hiren (I tested Hiren-10) and only launching MiniXP you use menu command in the latest release of Easyboot (version6): bcdw /hbcd/xp.bin
And you don't need to check "Allow Lower Case" to make it work!
Note: we desperately trying to avoid the use of checking "Allow Lower Case" as it gives us some annoying side-effects
Keep that in mind!You can still use "easyboot-iso.script" to integrate Hiren-10.
Attention, to use the whole Hiren-10 (dos-tools etcetera) you must check the annoying "Allow Lower Case" and this "problem" is related to Hiren and not to EasyBoot.
For the Hiren-14.1 case.
Use "easyboot-iso.script" to integrate Hiren as usual.
To only launch MiniXP you use menu command in the latest release of Easyboot (version6): bcdw /hbcd/xp/xp.bin
And you don't need to check "Allow Lower Case" to make it work.
Attention, to use the whole Hiren-14.1 (dos-tools etcetera) you again must check the annoying "Allow Lower Case"!
Though we desperately trying to avoid the use of checking "Allow Lower Case" it is needed when run Hiren from CD\DVD-unit but NOT needed if run from USB device (you are automatically given the right menu command and recommended settings by script "easyboot-iso.script")
Note: This "Allow Lower Case"-syndrome in Hiren is most likely caused by that Hiren mix uppercase and lowercase to file-names in folder HBCD.
In theory you could manually change all names to uppercase (big letters) to all filenames (simply use "easyboot-uppercase.script" ).
However you must also change everything in the menu-system in Hiren to uppercase (a lot of efforts to change that).
Is it worth it - I don't now
-------------------------------------------------
Finally...
Quote: "(if your not yet employed by Ezbsystems, they should send you a huge check for the great service your doing here...)"
No I'm not employed by Ezbsystems
- but I do like that suggestion "huge check", he he that one for sure taste good 
regards balder
Posted by EB1000 on Aug. 31 2011,09:06
Thanks again for the comprehensive explanation. If it not too much to ask, can you look at the list of applications I posted and tell me if I should or shouldn't check "allow lower case" for the entire build? Are there any conflicts between those 12 applications as for the lower case issue. i.e could there be a problem for one application if lower case is allowed or not allowed to your knowledge and experience? If I understand correctly; Hiren 14 must have lower case allowed only for all dos apps to work, but not for miniXP and all of it's programs, right?BTW, do you think it's possible to modify the inside of XP.WIM image from Hiren (and/or the inside of win7pe.iso) so it can be renamed to boot.wim and put inside a win7pe.iso so it will trick ezb to load this xp-bases win7pe?? This could be interesting (or perhaps stupid as I probably don't know what I'm talking about.. :-) )
Posted by balder on Aug. 31 2011,09:47
@EB1000Quote: "Are there any conflicts between those 12 applications as for the lower case issue"
Well... put it this way; Any application that is launched from ISO - typically ActivebootDisk disk 5, Win7PE se etcetera - isn't normally not in conflicts with the "Allow Lower Case"-syndrome.
However no guaranties
Test and trial-concept is what must be used to such comprehensive build that you are creating here
Quote: "Hiren 14 must have lower case allowed only for all dos apps to work, but not for miniXP and all of it's programs, right?"
Correct - though it is possible to manipulate Hiren to avoid the "Lower case problem".
Open folder HBCD in folder disk1 and use notepad and open "menu.lst" (it is a plain text-file).
It looks like this for Hiren 14.1:
title Dos Programs\nRun Dos Programs
find --set-root /HBCD/Dos/dos.gz
map --mem /HBCD/Dos/dos.gz (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)
map --floppies=1
Change text to uppercase
title Dos Programs\nRun Dos Programs
find --set-root /HBCD/DOS/DOS.GZ
map --mem /HBCD/DOS/DOS.GZ (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)
map --floppies=1
Launch my "easyboot-uppercase.script" and run uppercase to files and folders inside folder HBCD in folder disk1.
Note: when script ask for the location of files and folders to be uppercased you simply scroll and open folder HBCD.
In a few seconds you have every name to file and folder inside folder HBCD uppercased
In easyboot menu you simply use menu command: run /hbcd/grldr
Now you can avoid checking "Allow Lower Case" when creating ISO in EasyBoot.
However you have more stuff in text to "menu.lst" that must be uppercased to launch the rest of applications in Hiren.
Or as I described it in post nr; 4 and I quote: "However you must also change everything in the menu-system in Hiren to uppercase (a lot of efforts to change that).
Is it worth it - I don't now"
BUT - It is fully possible - take some time (and in my case quite many swearword before finished
)Quote: "trick ezb to load this xp-bases win7pe??"
Doesn't sound as any bright idea.
Boot-sequence in NT6-systems (Vista\Win7\Server-2008) are to some point "hard-coded", and anyway you are mixing NT5-system into NT6-system - that is an hard nut to crack.
regards balder
Posted by EB1000 on Aug. 31 2011,11:03
Thanks, currently building and testing. The make all upper case cause Kaspersky not to boot BTW, so I remove kaspersky files, run your scrip for upper case, then place kaspersky files back to disk1. To make my built more useful I also want to add options for reboot and shutdown the PC. Do you know suck commands for EB6?Thanks
Posted by balder on Aug. 31 2011,12:51
@EB1000Quote: " options for reboot and shutdown the PC"
In downloaded script-collection balder\USB_Resources, you have a file "SHUTDOWN.IMA.GZ".
Extract SHUTDOWN.IMA to folder ezboot.
Use menu command in Easyboot: bcdw SHUTDOWN.IMA
This shutdown you computer
Note: you can use zip or 7z or similar program to extract file balder\USB_Resources\ SHUTDOWN.IMA.GZ
To reboot you use menu command in Easyboot menu: reboot
As far as I know, this still is working correctly.
Quote: " The make all upper case cause Kaspersky not to boot"
Well you probably didn't open folder HBCD that was the target.
You most likely only browsed and opened folder disk1 and hereby run uppercase to all files and folders in folder disk1 and also to all subfolders as well - and not the target-folder HBCD.
-----------------------------------------
The "frugal solution" to the "Hiren syndrome"...
To avoid check "Allow Lower Case" when integrating Hiren BOOT-CD_v14 and higher version into EasyBoot (only for Hiren_v14 and higher).
I'm currently working on a new script "easyboot-hiren.script"
Script works like this:
1. Extract from Hiren ISO-file needed files to EasyBoot\disk1
2. Deleting NOT needed files from inside of Hiren ISO-file
3. Finally create a new reduced Hiren ISO-file in folder ezboot
Question is what files can be deleted to reduce size of the total build - so it ends as close as possible in size to the size of Hiren original ISO
I'm not sure I can solve this issue but I'm working from time to time with a solution
The point with above arrangements is to avoid the need to check "Allow Lower Case" as it creates "annoying side effects"
regards balder
Posted by EB1000 on Sep. 01 2011,13:21
OK, everything seem to work OK, however, for strange reason Dos application of Hiren 14.1 are not working under VirtualBOX (getting file not found error from grub...), but they do work under QMENU and my physical machine... Updated to the latest VBOX version. same goes for Ultimate Boot CD, some of it's apps are failing to launch under VBOX but working under QMENU... So should I conclude that the project works and VirtualBox sucks? Or should I be worried that failing to fully work on VBOX means that it may also fail on another real machines?One more thing, dear balder, do know how can I disable the "press any key to boot from cd..." message that is found on some WinPE7 based iso's? I tried moving the boot.wim to another iso that does not have this annoying message, but it still shows, meaning it is embedded into the boot.wim image. Can it be edited out safely?
Thanks
Posted by balder on Sep. 01 2011,14:39
@EB1000Quote: "press any key to boot from cd... message that is found on some WinPE7 based iso's?"
Sure
Use UltraIso (or similar program) and open ISO-file (WinPE7.iso) continue with open folder "boot" and delete file "bootfix.bin".
Save changes to ISO-file and from now, no more annoying; " press any key to boot from cd..."
Note1: If you are building your own personalized WinPE7, you can already delete "bootfix.bin" in folder boot in your source folder - in this way file isn't copied at all
Note2: "bootfix.bin" is also used in WinXP-setup-CD (in folder I386) as well.
Quote: "Or should I be worried that failing to fully work on VBOX means that it may also fail on another real machines?"
I can't tell for sure...
But if build is working alright in ONE of the "virtually test systems", there is reasons to belive it works in "reality" as well.
However keep your fingers crossed
----------------------------------------------
News is soon coming regarding Hiren-v14.1
I'm in a progress to create a new special developed script that should be able to create an stand alone MiniXP based on Hiren (only MiniXP.ISO-file).
Script should also be able (if I can solve it) to completely integrate the whole Hiren - including dos-tools!
It's a he** lot of work to find out what files and where to put files to make MiniXP work correctly.
No guaranties I can solve this issue - but I'm trying my very best
regards balder
Posted by balder on Sep. 01 2011,17:54
@ EB1000Quote: "BTW, what about DOS(8.3) should this be checked or not?"
No DO NOT check DOS(8.3), as it is mostly only needed to "DOS-related" stuff, and your files in build has most likely no connection with that checkbox.
And by the way, checking DOS(8.3) gives some other annoying side-effects that can be difficult to follow
Quote: "I deleted bootfix.bin and now the press any key is not shown in QMENU, but it still shows in VBOX"
Quote: " many executable fail to start with error "not a win32 app...")."
Hmm.. It looks you are close to how much you can integrate into build of this size you are building
These kinds of builds (very large builds) like yours, is "sensitive" and could interfere between files and folders.
Even if TOC-table (Table-Of-Contents) should keep files and folders clear from each other - there still is possibility for "interference" (at lest in theory on physical DVD).
However it's a nice piece of software you "carpenter" together - very impressing
The name: "super boot dvd 2011" says it all
regards balder
Posted by EB1000 on Sep. 03 2011,08:42
Thanks balder. Following our previous discussion at post #12:< http://www.ezbsystems.com/cgi-bin....6;st=10 >
I"m still not clear about one thing: I understand that can use your script to compress the ISO to GZ and modify the menu.lst, but you are saying that even if I don't use fira (check load from ram option in the iso script), the compressed iso.gz image will still load into ram and occupy the same amount of ram as the original iso image size? So this will result in limited amount of ram available to the application that is ran from the ISO image. Isn't there a way to allow the user to select if he want to extract to ram or to a free space on any local hard drive (create a temp folder during boot)? One more thing I did not fully understand, is if I can load compress iso w/o using fira (checking load from ram), what are the benefits of just checking load from ram over using the compress script and modifying the menu.lst files? Sorry for all the questions, I"m very determined to finish with that project and get the best results (BTW, once it is over I"m going to compress/split the disk1 folder and upload it to my file hosting service for backup, so if you want i can later mp you the download link so you can use/test/modify it yourself)
Thanks
Posted by balder on Sep. 03 2011,09:55
@ EB1000Quote: "you are saying that even if I don't use fira (check load from ram option in the iso script), the compressed iso.gz image will still load into ram and occupy the same amount of ram as the original iso image size?"
Hmmm... Okay I was perhaps a little cryptic in my explanation
Let's say you integrate Ghost14-rescue-ISO-file.
If you put in --mem in "menu.lst" in "grub-kicker-image", ISO-file is loaded to RAM before executed.
If you load such ISO (NT6-system as Ghost14 is) it consumes proximally twice amount of RAM than "normal" load NOT run from RAM. That will say no "--mem" present in menu.lst.
However each ISO-file that ARE NOT Gzipped, take more space on your DVD, which you definitely is NOT interested in
And if you decide to Gzip ISO-files you are bound to run ISO from RAM, and hereby occupy twice amount of RAM than normal load of ISO-file.
Note1: Any WinPE built from NT6-source is loaded to RAM (*.WIM-file), that's why it occupy twice amount of RAM.
Note2: any WinPe built from NT5-source do not run from RAM itself (no WIM-file present) but must be loaded to RAM to reach drives loaded by "firadisk".
Basically any WinPE5-build consumes only the half of amount of RAM comparing to WinPE6-build as the WIM-files always also is loaded to RAM in NT6-system(s).
However your problem is definitely not the RAM-issue - your must focus on how to reduce each ISO-file as much as possible - using Gzip - and as a consequence of this - instead chose to run ISO's from RAM.
If your computer have 1GB RAM then forget the RAM-problems, because there is no problem loading ISO-file to RAM.
If you have 2GB RAM, relax even more, and take a cup of coffee or whatever
To clear things out:
1. Let's say you overdraw the size of your DVD-build and decide to Gzip ISO-files used in DVD-build to make it fit into DVD.
2. You can run Gzip to each ISO-file (use "easyboot-cab.script") and also modify text-file menu.lst (--mem) in each different "grub-kicker-image" in folder ezboot - this take some time and efforts - but is fully possible.
However ISO-file is now loaded to RAM (can take some minute(s) if using DVD, but works excellent.
Quote: "what are the benefits of just checking load from ram over using the compress script and modifying the menu.lst files?"
Read step 2 below
Different approach:
1. Let's say you overdraw the size of your DVD-build and decide to Gzip ISO-files used in DVD-build to make it fit into DVD.
2. You instead use "easyboot-iso.script" with "Run ISO from RAM" checked (basically rebuild integration of every ISO-file to your build) - you must do this to each ISO-file. BUT you don't need to edit any of all these "grub-kicker-images" that script creates in folder ezboot!
Further more, size to ISO-file(s) are automatically reduced by built-in Gzip in script!
When having "Run ISO from RAM" checked, also ONE tiny floppy image "firadisk" is integrated to build, but it is only ONE file "firadisk" that is integrated into build, and it is less than 0,05MB in size.
Each time you integrate some ISO-file with "Run ISO from RAM" checked, file "firadisk" is overwritten by script in build as we only need one file "firadisk".
Note: This odd file "firadisk" is only used by system if you integrate WinPE-build based on NT5-system (WinXP or similar NT5-system).
Every else ISO doesn't care if file "firadisk" is present or not, or if "firadisk" is up and run its tiny drivers!
All this is done fully automatically and do not interfere in any way to any else ISO-file. File (drivers) "firadisk" is only there to support NT5-systems (if integrated to build).
regards balder
Posted by EB1000 on Sep. 03 2011,10:22
Thanks! So if I finally understand correctly, using the iso script and checking "run from ram" is only preferable because it saves a lot of work, but the results are the same as doing it manually by using cab script and editing menu.lst files? So actually both method will result in the SAME iso boot method? Could one method fail/succeed on one machine while the other method succeed/fail on another machine? (i.e are truly the same technically even one uses fira drivers and the second isn't?).
Posted by balder on Sep. 03 2011,10:34
@ EB1000Quote: "using the iso script and checking "run from ram" is only preferable because it saves a lot of work, but the results are the same as doing it manually by using cab script and editing menu.lst files? "
Correct!
Quote: "So actually both method will result in the SAME iso boot method?"
Correct!
Quote: "Could one method fail/succeed on one machine while the other method succeed/fail on another machine"
No it can't, because these created "grub-kicker-image(s)" in folder ezboot basically use the same menu.lst to launch ISO-file.
If one machine refuse to load such ISO, it most likely is an "hardware"-problem, and not a "software"-problem related to "grub-kicker-image" itself.
To sum up: it doesn't help using the "manually method" (edit menu.lst with "--mem") comparing the "automatic way" (easyboot-iso.script with "Run ISO from RAM" checked).
regards balder
Posted by EB1000 on Sep. 03 2011,18:39
@balderThanks' thanks and many thanks for your help. I'm currently rebuilding the project with the load from ram method and also managed to add a few more apps such as MS ERD commander 2011... Now one more question that bothers me about grub and iso booting. Can you tell me what are the differences between these two booting sequences (they both seems to work):
method 1:
find --set-root /ISO/XXX.ISO
map /ISO/XXX.ISO (0xff)
map --hook
root (0xFF)
chainloader (0xFF)
boot
method 2:
find --set-root /ISO/XXX.ISO
map /ISO/XXX.ISO (hd32)
map --hook
chainloader (hd32)
boot
I mean what is the difference between (0xFF) and (hd32) and what are the benefits of each. Also, when do i must add the "boot" command, and when can it be omitted?
Thanks!
Posted by balder on Sep. 04 2011,02:14
@ EB1000Quote: "I mean what is the difference between (0xFF) and (hd32) and what are the benefits of each."
This has been discussed and bended up and down on Internet
Some users claim that (0xFF) is more reliable then the (hd32) command.
Frankly nobody (included myself) haven't found any differences in stability to this two commands in grub
Conclusion is that both works fine and you cannot for sure figure out if anyone is better then the other one
So I don't bother as (hd32) has never failed for me.
However if you find the (0xFF) in menu.lst it's there because I'm lazy and only used an menu.lst as it was!
Quote: "Also, when do i must add the "boot" command, and when can it be omitted?
Another part of my "lazy behaviour" (or am I getting to old
)You actually don't need the "boot" as it is the "chainloader" that do the "dirty" work.
This text line "boot" has been left in menu.lst by mistake, and has followed my "kicker-images" by mistake (basically as I have been too lazy - I'm not perfect
.---------------------------------------------
I'm curios about this large awesome build you are creating @ EB1000
As you use my script "easyboot-iso.script" with its "grub-kicker-images" it should be possible to transfer the whole build to USB - at least in theory
It is an question about time when CD\DVD-units won't be used any more (at least not frequently).
Already setup of Windows-7 is run much faster and convenient from USB stick.
Another benefit is that USB devices are smaller in size (you cant fold up an DVD) and still can hold much more data then DVD is able to hold.
Anyway - keep it up... @ EB1000
regards balder
Posted by josefo on Sep. 04 2011,20:49
Wow Balder, deep respects to all your knowledge. I just joined and already I found answers to some very "begginer" problems I've been having.Though I do have a question regarding Puppy Linux. I can't seem to get it boot from a multiboot DVD I'm creating.
My DVD consists of:
Win7 Ultimate Lite
WinXP Pro SP3 Lite
Hirens Boot CD v11
Puppy Linux (Live & Install)
I got all the others to work, but Puppy is being a real Dog.
Any tips?
Posted by balder on Sep. 05 2011,02:55
@josefoAs a new member I say welcome to the "party" @josefo
Quote: "I got all the others to work, but Puppy is being a real Dog."
He, he, is this the reason you are getting "green"
(I'm referring to text colour you use
)Note: I'm able to read text but only if I force my eyes - please use darker colour for better readability
Now to the subject - "puppylinux".
We can apply the "frugal solution" (simpel solution) to such ISO-file (actually you have the same solution to kaspersky in this topic you are reading - go back to page one in this topic and post nr; 2)
I downloaded "puppy-4.2retro-k2.6.21.7-seamonkey.iso" from < HERE >
Note1: it should work for other different puppy distros as well!
Note2: I'm a little bit unsure about that "install-thing" but test and see if you can get it up and run as you please
To integrate such build into easyboot test this:
(works great from USB as well)
1. Open puppy-iso-file (I use UltraIso to this operation)
2. Extract the "base-file" pup_420.sfs to folder disk1 (folder disk1 is the "root" for Easyboot if you wonder)
3. Still having puppy-iso-file opened in UltraIso you delete pup_420.sfs and chose to "save as" with name "puppy.iso" somewhere (best place is on your root C:\ or an folder on the root)
4. You now have two options.
Option A: copy your in size heavily reduced "puppy.iso"-file to folder ezboot and use menu command in Easyboot menu: run puppy.iso (note: only working if you have EasyBoot-version6 installed)
Option B: Use my script "easyboot-iso.script" to integrate puppy.iso-file into EasyBoot.
You automatically receive the right menu command to use in EasyBoot menu by script!
Note: If using script you don't need to worry what version of EasyBoot you are using - script is close to "bullet proof" in its action.
But read carefully how to use script (BIG LETTERS in name to iso-file and no space in folder or file-name etcetera).
I noticed that this new distros from puppy really is nice in the way the look and act - nice progress from these distros...
balder
Posted by josefo on Sep. 06 2011,04:42
Balder, I kneel at the alter of your knowledge.Tonight I will sacrifice a stack of DVDs and CDs
In your Honor.
You have saved me a lot of time and frustration.
I too, also ask. Why doesn't EZBSYSTEMS pay you a very
FAT check?
Your script worked like a charm...
All praise Balder.....
Auuuum, Auuuuum...
Posted by balder on Sep. 06 2011,04:53
@ josefoQuote: "Balder, I kneel at the alter of your knowledge."
He, he thanks
I'm going to fly on my "wings" (hopefully I don't crash when I realize that I doesn't own any "wings"
)However, I like this part best - really tasty
Quote: " Why doesn't EZBSYSTEMS pay you a very
FAT check?
However the real compensation is nice feedback from people like you @ josefo
Quote: "Tonight I will sacrifice a stack of DVDs and CDs
In your Honor."
Please note that script has built-in test tools to both CD\DVD (test ISO-files) as testing USB device
Another thing to have in mind; You cannot simply use your original build (post nr; 19) on USB to run setup of WinXP.
You need special tool for this - look in "USB-NT6-SETUP.script" ("Optional: Download ""Setup WinXP from USB")
Keep it up @ josefo
regards balder
Posted by balder on Sep. 06 2011,17:11
@ josefoFound tiny bug in "easyboot-grub-iso.script"
- Manually test of ISO failed when allocating RAM to qemu.It's now fixed
Users are advised to simply download updated zip-file and extract\overwrite existing folder "balder"
regards balder
Posted by josefo on Sep. 06 2011,19:12
(balder @ Sep. 06 2011,16:11)
QUOTE
@ josefo
Found tiny bug in "easyboot-grub-iso.script" - Manually test of ISO failed when allocating RAM to qemu.
It's now fixed
Users are advised to simply download updated zip-file and extract\overwrite existing folder "balder"
regards balder
Found tiny bug in "easyboot-grub-iso.script"
- Manually test of ISO failed when allocating RAM to qemu.It's now fixed
Users are advised to simply download updated zip-file and extract\overwrite existing folder "balder"
regards balder
Already downloaded my friend.
Keep up the great work.
Cheers!!!
Posted by EB1000 on Sep. 07 2011,15:18
OK. I"m almost finished with my project. I"ve manage to reduce the size down to 4.27GB without compressing the ISO's I just replaced the Ubunto 680MB iso with an alternatve and mush useful ubunto rescue remix 11.04 live Cd, which is only 270MB in size. here is the download ling to this ubuntu live:< http://ubuntu-rescue-remix.org/files/URR/iso/UbuntuRescueRemix1104.iso >
Now, here is the problem where I once again need your expertise dear balder, your method for booting Ubunto does not work here. I noticed that this iso has it's own isolinux menu which let you choose 3 bot options by typing their commands (it has memtest and boot from HDD). Can you please have a look and tell me how to boot directly into ubunto live w/o typing anything?
Regards
EB
Posted by balder on Sep. 08 2011,02:33
@EB1000Quote: "Now, here is the problem where I once again need your expertise dear balder"
Well I'm unsure if it can be called "expertise" but thank you
This "UbuntuRescueRemix1104.iso" is really a little bit confusing - you are right there
I cannot test this ISO in Virtual PC or Qemu - it halts
I therefore burned ISO to an CD-RW and rebooted computer to test fully out.
I wrote in "live" and all I got was a kind of command-line.
Is this what it suppose to be - or am I totally in the "ditch"
Anyway I decided to launch from both USB stick as from CD-RW and was presented the same "command-line" to both alternative.
And this is what I did to launch ISO from USB :
1. Extract folder "casper" from ISO to folder disk1 (I use UltraIso to this operation).
2. Open folder "casper" in opened ISO and delete file "filesystem.squashfs"
3. Save reduced ISO as ubunturescue.iso (or whatever name you prefer)
4. Launch script "easyboot-iso.script" and check "Run ISO from RAM" and integrate reduced ISO (ubunturescue.iso) as usual.
5. Now open folder casper in folder disk1 and delete every file except " filesystem.squashfs".
You can check "Joliet" or not as it doesn't have any impact to "UbuntuRescueRemix1104.iso" (you may need "Joliet"-switch by some other reason).
It's important you check "Run ISO from RAM"
I didn't manage to test ISO in an appropriated way in any "Virtual environment", but as told, I used script "easyboot-grub-iso.script" to transfer build to USB stick and that worked in the same way as CD-RW burned from original "UbuntuRescueRemix1104.iso"-file.
I also tested ISO created by EasyBoot and burned to CD-RW and rebooted computer and it worked the same as UbuntuRescueRemix1104.iso-file did.
Try it out and see if it works okay from your "super-dvd"
No guaranties
as it seems to be such odd ISO this "UbuntuRescueRemix1104.iso".regards balder
Posted by EB1000 on Sep. 08 2011,05:46
@balderThanks! it works but I still have to type "live" to load the datarecovery command prompt. I tried to edit the isolinux.cfg menu file to get rid of the multiple choice menu, but it gives me errors. I could only do it by reducing the timeout count to a few seconds. Do you know how to modify the cfg file so the "live" cd will boot automatically?
And yes you are right. This iso is not exactly a Live cd, it is only a command prompt based data recovery toll collection. I read on the forums that it is capable of doing wonders even when many commercial data recovery tools fail. It can rescue data from a dead hard disk. It uses the sudo commands to run the many included tools. Here is the guide for this cd:
< https://help.ubuntu.com/community/DataRecovery >
Sorry for all the trouble I put you through. BTW, the only virtual machine that can boot this cd is Vmware WS 7.1, all the others fail or hang...
Regards
EB
Posted by balder on Sep. 08 2011,08:41
@EB1000Quote: "Do you know how to modify the cfg file so the "live" cd will boot automatically?"
I'm really not that familiar with linux\isolinux aside from some basic knowledge
to the "boot-part"
I did take a look to isolonux.cfg without any success
However you at least was able to launch this odd ubuntu
regards balder
Posted by EB1000 on Sep. 08 2011,13:39
Thanks! I was able to find a workaround. I just changed to timeout count from 300 to 2 and now the screen appears just for 2 secs and it starts with the default into live cd (well, almost live cd)Any way, after replacing ubunto live (700MB) with ubunto rescue remix, I now have almost 400MB free space left, which I intent to fill with one or to more bootable cd's. The first one that I think is a must is the latest parted magic 6.6 found here:
< http://sourceforge.net/project....ownload >
I tried loading it with your script but it failed. I did not try checking boot from ram simply because the parted magic has some memory testing tools that can cause problems if ram is used by the entire iso for booting. So i need some alternative method. I guess this cd is another non- standard linux based cd. Any advice will be welcomed master balder..
BTW, I will later collect all your helpful tutorials for booting various iso's from this thread and many other and put them in one single new thread for easy reference. I think this forum could really benefit from one stop iso booting thread based your wonderful and detailed guides. I will then keep that thread updated. I think i will also share my project sources (the ezboot folder with all *.ima/g and mysuperboot.ezb so anyone will be able to use them to boot many different iso's easily). But first we got 2 more iso's to boot
The next challenge is to boot to different linux based iso that both use the casper folder. I wonder if that is possible to overcome (can casper be renamed so I can have 2 versions of casper on disk1 folder??)
regards
EB
Posted by balder on Sep. 08 2011,14:17
@EB1000Quote: "I intent to fill with one or to more bootable cd's"
Are you never satisfied
Quote: "The first one that I think is a must is the latest parted magic 6.6"
Solution to partedmagic-6.6
Please read post nr; 3 < HERE >
Note: You of course delete file “pmagic-6.6.sqfs” and not file “pmagic-6.3.sqfs” as you are using version6.6
Quote: "BTW, I will later collect all your helpful tutorials for booting various iso's from this thread and many other and put them in one single new thread for easy reference."
Excellent idea @EB1000
regards balder