Forum: EasyBoot Topic: Is it possible to chainboot multiple EZB ISOs? started by: srk999 Posted by srk999 on Mar. 31 2011,13:49
The main problem we face today with multiboot using EZB or any other method is overlapping content, such as I386 folders etc. If it was possible to extract bif from multiple EZB ISOs and put them into a new ISO, that could solve the problem.For example, let's say we have ERD 5.0 and ERD 6.5 in one EZB ISO, and WinXP and Win7 installers in another EZB ISO. Putting ERDs together with corresponding OS is fairly tricky. Is it possible to make another EZB ISO (containing the ERD and OS ISOs), that will call the ERD and OS ISOs (contents) from the menu? Note: I am using the term ISO loosely. I am thinking of this because I am facing problem with overlapping folders (i368, boot, etc.). If there is already a solution to this problem please let me know. Posted by balder on Mar. 31 2011,15:00
@srk999Wellcome to this forum @srk999 ![]() Quote: ” If there is already a solution to this problem please let me know” Well… yes and no at the same time ![]() I can understand your wishes to that “easy solution”. Unfortunately it’s not that easy! To have several different setup of NT5-systems (WinXP, server-2003, server-2000 etcetera) that all use the same folder i386 is easy to solve. There is now problem whatsoever to create a multi-boot DVD with all kinds of NT5-systems on the same root (folder disk1 is the root for EasyBoot if you wonder). You can also do the same to ERD5-series and ERD7 etcetera. But there is a problem with linux/isolinux-systems as it is common to use a folder “boot” in those systems. But salvation is close to solve this problem In most cases we are able to launch ISO-files of linux/isolinux-systems (ISO mostly used as “live-applications”) as the are. We are also able to launch ISO-files of ERD5,ERD7, Ghost15, MsDart60, MsDart65 etcetera. You don’t need to extract anything anywhere as ISO-files can be used as they are. To make this happen you can use my script collection (you find download below in every post I write). Read carefully “READ_ME.html” in download before you go ahead. Scripts can create All-In-One-setup for NT5-systems (WinXP etcetera with a breeze) ![]() Scripts can make USB devices bootable and launch EasyBoot from USB device (preferably USB stick\thumb-drives). And script can do more than that – download and find out your self ![]() The best part is that it is free to use for non-commercial use – no registration or anything ![]() balder Posted by srk999 on Mar. 31 2011,19:05
Hi Balder. Thanks for the quick reply.I am still having problem with ERD. Probably because when I use the AIO Script, it sees the ERDs as XP installers, and creates sif. AIO also seems to have trouble with regular XP installation. The XPSP3 ISO I am using is downloaded from MSDNAA, therefore in untouched form. I also tried a slipstreamed trimmed down version of XPSP3. In both cases the installation gets stuck at "Setup is checking for hardware..." black screen. I am going to try out the other scripts. Easyboot-ISO looks pretty tempting at the moment. If all fails, ERD is not the end of the world. ** EDIT ** ERDs belong to Live script I think. Should have read everything before I posted. ** EDIT 2** Balder, I know this is a winbuilder issue, in the next update can you please modify winbuilder so that we can keep the tutorials open while working on winbuilder, if possible. I have tried memorizing the instructions before getting to work. But a man can take in only so much before he feels stuffed. ** EDIT 3** Is it normal if Easyboot-ISO gets stuck at defragmentation? Defrag is marked "recommended". Posted by balder on Apr. 01 2011,00:10
@srk999Quote: “Setup is checking for hardware... black screen” A lot of people run this script without problem and I also have tested with sources from both English as my native language and tested XP_sp1, XP_sp2 and XP_sp3 without problems ![]() Slipstreamed source shouldn’t be any problems, except “Nlighted” source that can course some unwanted behaviour from source itself. ------------------------------------- Quote: “ERDs belong to Live script I think” Yes this is correct, as ERD is a “Live-system” and not a system that you install on your harddisk. Note: I advice you to use easyboot-iso.script to ERD and in this case, check “Run ISO from Ram” as this ERD is based on NT5-system (folder i386 - look inside ISO-file). Note: you can launch ISO-files of ERD5,ERD7, Ghost15, MsDart60, MsDart65 etcetera using script easyboot-iso.script You automatically get the right menu command by script in the end of process. ---------------------------------------- Quote: “But a man can take in only so much before he feels stuffed” Well you are similar to myself – are you by any chance a unknown distant relative (or collateral) ![]() He, he just joking ![]() Unfortunately I cannot modify WinBuilder as I haven’t designed this “script-engine” and further more – I don’t have the rights to modify the “core” anyway ![]() ----------------------------------------- Quote: “Is it normal if Easyboot-ISO gets stuck at defragmentation?” No it is not! However you can of course uncheck “defragmentation” to se if it runs smother that way. ----------------------------------------- I’m curios What system are you running? WinXP or Vista or Win7 ![]() If running Vista or Win7, you must run every script with “Full Admin rights" and even more important - set UAC (User-Account-Control) to the lowest level – otherwise command-lines tools that is used in script is prohibit to run smooth (built-in defragmentation tool in script is such command-line tool). However, running scripts in WinXP shouldn’t be any problem. balder Posted by srk999 on Apr. 01 2011,16:53
Hey balder. I can't thank you enough.I am getting very good success rate with Easyboot-ISO script. Whatever isn't working without "ISO from ram" (other than i386 ISOs) is working with "ISO from ram". Trying out 12 antivirus rescue CDs, and all of them work. Posted by balder on Apr. 01 2011,18:17
@srk999Quote: ” I can't thank you enough” Your success is the real “thank you” - though it’s nice with feedback that say “Thank you” ![]() Note: not all ISO-files can be launched directly but there is mostly “work-arounds” to solve the “impossible” ones - using my kind of “frugal solution” ![]() ----------------------------- Its bedtime - wife is already sleeping and snores ![]() ![]() Regards balder Posted by srk999 on Apr. 02 2011,02:46
I am facing a problem that seems to be common to all Linux based ISOs, including most of the AV rescue CDs, Trinity Rescue CD, and Ubuntu. Here are some of the error messages from several Linux based ISOs: QUOTE Cannot find boot device. Can't find Gdata filesystem No bootable medium found Unable to find a medium containing a live file system Unable to find a medium containing a live file system Unable to find a medium containing a live file system Unable to find a medium containing a live file system And, Windows XP and 7 seems to be unable to install from ISO (even with "Run ISO from RAM" option). Error message: QUOTE A required CD/DVD device driver is missing A required CD/DVD device driver is missing I am using VirtualBox to test out the resulting ISO. On the bright side, all the ERDs are working with the help of Easyboot-ISO script. Posted by balder on Apr. 02 2011,05:04
@srk999Quote: “On the bright side, all the ERDs are working with the help of Easyboot-ISO script” As expected ![]() ----------------------------------- Quote: ” Windows XP and 7 seems to be unable to install from ISO” Sure it doesn’t work – because it can’t work this way ![]() You cannot launch setup of WinXP or Win7 from ISO run from a DVD-unit! These kinds of ISO is “hard-coded”. I quote from description in script: “there is no such thing as a "free lunch" - grub cannot launch some ISO-files. Test and see your self what ISO-files that can bee launched directly this way”. For “hard-coded” ISO-files - you must extract files to the root (the root for easyboot is disk1 if you wonder) This is a fact at least when run from CD/DVD-unit. ---------------------------------------------- For the quote: “common to all Linux based ISOs” You need to use the “search”-function in the upper right corner ![]() Choose both “Older” as Newer” with search-words like ubuntu etcetera to see what solution that’s been presented. Note: I have no solution for trinity – as this is a real hard nut to crack ![]() As example - I searched for a solution to Ubuntu and found this < HERE > ------------------------------------------------ Quote: “AV rescue CDs” I guess you mean this one < HERE > I tested using easyboot-iso-file and it looks to run correctly (at least from virtual pc) ------------------------------------------------- Note: I cannot – and will not – test all this stuff from a “real CD/DVD” as this take far to much time and efforts ![]() I can only give you results for each solution tested in “virtual environment” and not the whole complex build (which I guess is very large in size). Regards balder Posted by srk999 on Apr. 02 2011,10:24
hi balderQUOTE Sure it doesn’t work – because it can’t work this way ![]() You cannot launch setup of WinXP or Win7 from ISO run from a DVD-unit! These kinds of ISO is “hard-coded”. I was thinking the same thing about windows xp and 7. Since they are not meant to be live CDs in the first place. I am going to try the Ubuntu method in all the Linux based ISOs. I'll let you know how it goes. QUOTE "I guess you mean this one < HERE >" Coincidentally that's the only AV rescue CD out of 12 that worked. Which is better than nothing. QUOTE Note: I cannot – and will not – test all this stuff from a “real CD/DVD” as this take far to much time and efforts ![]() I can only give you results for each solution tested in “virtual environment” and not the whole complex build (which I guess is very large in size). Please don't do my work. You are doing more enough to help me already. All the little bits and pieces of info I gave, such as- "I am using VirtualBox to test out the resulting ISO." are in hope that someone might have faced similar problems in similar settings. Cheers. Posted by balder on Apr. 02 2011,16:20
@srk999Quote: ”I am going to try the Ubuntu method in all the Linux based ISOs. I'll let you know how it goes” You cannot use downloaded “ubuntu.zip” to different Linux based ISO-files ![]() This “ubuntu.zip” is specially designed to support Ubuntu-10 or similar. It might look complicated but is in the end quite simple. What easyboot-iso.script do is: Creating floppy image (floppy image that have the special grub boot-sector and not a dos-boot-sector) and then inject a text-file “menu.lst” suitable to the name you set in script for your ISO-file. However in the case with ubuntu, there are more sophisticated command-lines that make it possible to launch ISO as it is – even it is a ubuntu.iso. Therefore I have a special made “kicker-image” suitable just for launching ubuntu and nothing else ![]() Note: you can open (extract) floppy image from ubuntu.zip and extract text-file “menu.lst” which is the file that controls commands in grub. This means that it is possible to modify this menu.lst to use different command-lines. In fact, you can create your own “grub-kicker-image” using “easyboot-kicker-image.script" ![]() Further more, script has capacity to create DOS-images and help you inject files into it and also has option to create a 2.88 MB-sized floppy image and on the top of that, compress floppy image (using gzip) to shrink image which then can be launched using “memdisk”-command in easyboot menu. You also have a link in script to DOS-files in case you have lost your own ![]() balder Posted by srk999 on Apr. 02 2011,19:27
@balderUnderstood. I ditched all the AV live CDs other than AVG and KAV. As well as made my very first successful XP based rescue DVD. For Ubuntu I found a tutorial on the internet to put x86 and x64 version of Ubuntu in the same ISO. Here it is: QUOTE You can create a DVD that contains both versions of the live CD: 1. Download ubuntu-10.10-desktop-i386.iso and ubuntu-10.10-desktop-amd64.iso. 2. Create a folder structure for the DVD: CODE $ mkdir -p ubuntu-10.10-desktop-i386-amd64/boot/{grub,iso} $ mv ubuntu-10.10-desktop-{i386,amd64}.iso ubuntu-10.10-desktop-i386-amd64/boot/iso/ 3. Save the following as ubuntu-10.10-desktop-i386-amd64/boot/grub/grub.cfg: CODE # Derived from /boot/grub/loopback.cfg from ubuntu-10.10-desktop-i386.iso and ubuntu-10.10-desktop-amd64.iso. menuentry "Try Ubuntu without installing (32-bit)" { loopback iso /boot/iso/ubuntu-10.10-desktop-i386.iso linux (iso)/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/boot/iso/ubuntu-10.10-desktop-i386.iso quiet splash -- initrd (iso)/casper/initrd.lz } menuentry "Try Ubuntu without installing (64-bit)" { set gfxpayload=keep loopback iso /boot/iso/ubuntu-10.10-desktop-amd64.iso linux (iso)/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/boot/iso/ubuntu-10.10-desktop-amd64.iso quiet splash -- initrd (iso)/casper/initrd.lz } menuentry "Install Ubuntu (32-bit)" { loopback iso /boot/iso/ubuntu-10.10-desktop-i386.iso linux (iso)/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity iso-scan/filename=/boot/iso/ubuntu-10.10-desktop-i386.iso quiet splash -- initrd (iso)/casper/initrd.lz } menuentry "Install Ubuntu (64-bit)" { loopback iso /boot/iso/ubuntu-10.10-desktop-amd64.iso linux (iso)/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity iso-scan/filename=/boot/iso/ubuntu-10.10-desktop-amd64.iso quiet splash -- initrd (iso)/casper/initrd.lz } menuentry "Check disc for defects (32-bit)" { loopback iso /boot/iso/ubuntu-10.10-desktop-i386.iso linux (iso)/casper/vmlinuz boot=casper integrity-check iso-scan/filename=/boot/iso/ubuntu-10.10-desktop-i386.iso quiet splash -- initrd (iso)/casper/initrd.lz } menuentry "Check disc for defects (64-bit)" { loopback iso /boot/iso/ubuntu-10.10-desktop-amd64.iso linux (iso)/casper/vmlinuz boot=casper integrity-check iso-scan/filename=/boot/iso/ubuntu-10.10-desktop-amd64.iso quiet splash -- initrd (iso)/casper/initrd.lz } menuentry "Test memory" { loopback iso /boot/iso/ubuntu-10.10-desktop-i386.iso linux16 (iso)/install/mt86plus } 4. Generate an ISO image: CODE $ grub-mkrescue --output ubuntu-10.10-desktop-i386-amd64.iso ubuntu-10.10-desktop-i386-amd64 You can now burn ubuntu-10.10-desktop-i386-amd64.iso (1.4 GB) to a DVD and choose either 32-bit or 64-bit options at boot. This works for both installation and live use. I have tested it by making an ISO myself. But I am not being able to integrate it into easyboot. If I am not mistaken this tutorial uses grub to load the x86 and x64 ISOs. I've tried to make it work both using ubuntu.zip and ubuntu.bif. Both failed. I think the method that would work for this is extract the ISO to /disk1/ and call ELTORITO.IMG. ELTORITO.IMG is the only file I am seeing in this ISO that looks like a loader, located in /BOOT/GRUB/I386_PC inside the ISO. Here is the complete folder tree in the ISO: CODE ubuntu-10.10-desktop-i386-amd64\ DIR [BOOT]\ DIR boot\ [BOOT]\ 2048 Bootable_NoEmulation.img boot\ DIR grub\ DIR iso\ boot\grub\ DIR i386-pc\ DIR locale\ 2006 grub.cfg boot\grub\i386-pc\ 8208 915resolution.mod 10488 acpi.mod 4536 affs.mod 4872 afs.mod 4896 afs_be.mod 1048 aout.mod 2672 at_keyboard.mod 8036 ata.mod 2228 ata_pthru.mod 4776 befs.mod 4792 befs_be.mod 4288 biosdisk.mod 2400 bitmap.mod 2904 bitmap_scale.mod 2020 blocklist.mod 2048 boot.cat 2568 boot.mod 19612 bsd.mod 1964 bufio.mod 2388 cat.mod 2476 chain.mod 1340 cmostest.mod 2144 cmp.mod 2033 command.lst 1784 configfile.mod 2864 cpio.mod 1608 cpuid.mod 1784 crc.mod 825 crypto.lst 4428 crypto.mod 4052 cs5536.mod 2316 date.mod 1824 datehook.mod 1241 datetime.mod 1896 dm_nv.mod 5488 drivemap.mod 1920 echo.mod 24168 efiemu.mod 6452 efiemu32.o 11018 efiemu64.o 4404 elf.mod 24055 eltorito.img 1636 example_functional_test.mod 5500 ext2.mod 3976 extcmd.mod 5932 fat.mod 11992 font.mod 128 fs.lst 2800 fshelp.mod 2508 functional_test.mod 1768 gcry_arcfour.mod 8144 gcry_blowfish.mod 35040 gcry_camellia.mod 17568 gcry_cast5.mod 2996 gcry_crc.mod 19280 gcry_des.mod 3268 gcry_md4.mod 4008 gcry_md5.mod 2636 gcry_rfc2268.mod 19204 gcry_rijndael.mod 9116 gcry_rmd160.mod 16652 gcry_seed.mod 18016 gcry_serpent.mod 8848 gcry_sha1.mod 3484 gcry_sha256.mod 5620 gcry_sha512.mod 11980 gcry_tiger.mod 39736 gcry_twofish.mod 24792 gcry_whirlpool.mod 3984 gettext.mod 38628 gfxmenu.mod 11280 gfxterm.mod 3720 gptsync.mod 165 grub.cfg 7828 gzio.mod 1460 halt.mod 0 handler.lst 4632 hashsum.mod 7440 hdparm.mod 1216 hello.mod 2488 help.mod 3244 hexdump.mod 6028 hfs.mod 5896 hfsplus.mod 2856 iorw.mod 6248 iso9660.mod 5844 jfs.mod 5944 jpeg.mod 1980 keystatus.mod 8732 linux.mod 5012 linux16.mod 5560 loadenv.mod 3032 loopback.mod 4168 ls.mod 1300 lsmmap.mod 4932 lspci.mod 6060 lvm.mod 2652 mdraid.mod 2080 memdisk.mod 2876 memrw.mod 4132 minicmd.mod 4336 minix.mod 8508 mmap.mod 2773 moddep.lst 2372 msdospart.mod 10488 multiboot.mod 11436 multiboot2.mod 6648 nilfs2.mod 98312 normal.mod 9992 ntfs.mod 3536 ntfscomp.mod 10556 ohci.mod 1688 part_acorn.mod 1672 part_amiga.mod 2112 part_apple.mod 2004 part_bsd.mod 2284 part_gpt.mod 2096 part_msdos.mod 1792 part_sun.mod 1704 part_sunpc.mod 82 partmap.lst 17 parttool.lst 4488 parttool.mod 1904 password.mod 2976 password_pbkdf2.mod 1328 pbkdf2.mod 1184 pci.mod 2472 play.mod 6620 png.mod 2664 probe.mod 5588 pxe.mod 1332 pxecmd.mod 6216 raid.mod 1400 raid5rec.mod 2812 raid6rec.mod 1564 read.mod 1120 reboot.mod 38636 regexp.mod 9796 reiserfs.mod 4104 relocator.mod 4128 scsi.mod 2356 search.mod 2168 search_fs_file.mod 2336 search_fs_uuid.mod 2256 search_label.mod 4920 serial.mod 690 setjmp.mod 5524 setpci.mod 4104 sfs.mod 2220 sleep.mod 2888 tar.mod 124 terminal.lst 3476 terminal.mod 12740 terminfo.mod 5188 test.mod 2884 tga.mod 1675 trig.mod 1276 true.mod 5484 udf.mod 4672 ufs1.mod 4988 ufs2.mod 5800 uhci.mod 7876 usb.mod 3428 usb_keyboard.mod 5440 usbms.mod 3624 usbtest.mod 6676 vbe.mod 2736 vbeinfo.mod 3048 vbetest.mod 4788 vga.mod 2288 vga_text.mod 33 video.lst 5388 video.mod 5500 video_bochs.mod 5744 video_cirrus.mod 18716 video_fb.mod 3876 videotest.mod 5856 xfs.mod 31396 xnu.mod 1936 xnu_uuid.mod 24384 zfs.mod 6208 zfsinfo.mod boot\grub\locale\ boot\iso\ 728754176 ubuntu-10.10-desktop-amd64.iso 726827008 ubuntu-10.10-desktop-i386.iso ***edit*** Looking back at the tutorial, it looks like "$ grub-mkrescue" automatically puts a boot loader in the ISO that it makes. Also there are so many .lst files, no idea which one to choose for kicker image. None of them look like a menu. I am way over my head, and completely lost. Posted by balder on Apr. 03 2011,02:51
@srk999I cannot find out the right menu parameters for such combinated ISO (ubuntu-i386 and ubuntu-64) ![]() BUT – have you tested using downloaded ubuntu.zip to your “super-ubuntu”.iso-file ![]() Test and rename iso to UBUNTU.ISO. Use CAPS to name= BIG LETTERS and copy ISO-file to the root= folder disk1 in EasyBoot Or do this instead: If I where you I should instead use separate ISO-files and make a copy of extracted ubuntu.ima (extracted from ubuntu.zip) and rename copy of ubuntu.ima to ubuntu64.ima. Extract menu.lst and modify parameters (name) to ubuntu64.iso-file This is how “my” created original “menu.lst” from download looks like: find --set-root /UBUNTU.ISO map /UBUNTU.ISO (0xff) map --hook root (0xff) kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/UBUNTU.ISO -- initrd /casper/initrd.lz boot You can change name to this: find --set-root /UBUNTU64.ISO map /UBUNTU64.ISO (0xff) map --hook root (0xff) kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/UBUNTU64.ISO -- initrd /casper/initrd.lz boot you of course must rename ubuntu64.iso-file to exactly: UBUNTU64.ISO (you also must use CAPS to name= BIG LETTERS and have it copied to the root= folder disk1 in EasyBoot) Attention! You don’t need to compress ubuntu.ima each time you test new menu-lines in text-file “menu.lst” inside ubuntu.ima, you can use floppy image as it is (not compressing) and still use menu command in EasyBoot: memdisk ubuntu.ima (instead of memdisk ubuntu.ima.gz). And for modified menu.lst (modified to launch UBUNTU64.ISO) you use: memdisk ubuntu64.ima Note: The point with using memdisk instead of “run” is to avoiding the need to check “Allow lower case” and memdisk-command can also launch compressed floppy images ![]() balder Posted by srk999 on Apr. 03 2011,04:03
@balderThank you, that worked flawlessly. And with that ends my quest for the perfect rescue DVD. I am not going to bother you anymore. at least for a while ![]() |