JackCarver Posted March 16, 2009 Share Posted March 16, 2009 Hi Jetman,wanted to say thx. Great Article you wrote here. I was able to integrate by now the following os on one DVD:Vista, XP, Knoppix, Knoppicillin (Linux Virus scan), Open Suse 10, Fedora (Live cd), Open Solaris 10, Gparted, Acronis Disk Director, Acronis True Image, Debian Squeeze CD1 (testing) and DSL.Tricky was the OpenSolaris integration because OpenSolaris needs the Rock Ridge Extensions to boot and the grub Bootloader. The problem was, that WinXP cant boot when i activate the -r switch in genisoimage. I read that the XP bootsector would be destroyed with Rock Ridge enabled. Dunno why or if i made another mistake.So i need a workaround to get both Open Solaris and XP to work. And the solution was Grub4Dos as it can directly start the NTLDR of xp without using the Bootsector via a chainload directive.The grub4dos package contains a file named grub.exe and this file is actually a linux kernel. So as i didnt know how to chainload other bootmanager via isolinux you can indirect start grub via isolinux withkernel grub.exeThen you have the ability to chainload via grub SETUPLDR.BIN from the i386 folder and this starts NTLDR. Thats it, and it works with Rock Ridge enabled.So you can start via the isolinux menu both WinXP and OpenSolaris via grub and both works with Rock Ridge enabled.JackCarver Link to comment Share on other sites More sharing options...
jetman Posted March 18, 2009 Author Share Posted March 18, 2009 Hi Jetman,wanted to say thx. Great Article you wrote here. I was able to integrate by now the following os on one DVD:<snip>kernel grub.exeThen you have the ability to chainload via grub SETUPLDR.BIN from the i386 folder and this starts NTLDR. Thats it, and it works with Rock Ridge enabled.So you can start via the isolinux menu both WinXP and OpenSolaris via grub and both works with Rock Ridge enabled.JackCarverJack: Thanx for the kind words, but you've introdued a very interesting wrinkle. I hope to experiment w/ this in the next few days. Was wondering:what (Grub4DOS) files did you incorporate into your image and where did you put them ?were you able to directly use GRUB as a chainloader as in:KERNEL /BOOT/GRUB/GRUB.EXEAPPEND --config-file="CHAINLOADER /I386/SETUPLDR.BIN"Thanx for the heads-up ! This definitely justifies a new round of experimentation w/ Grub4DOS....Jet Link to comment Share on other sites More sharing options...
JackCarver Posted March 18, 2009 Share Posted March 18, 2009 Hi Jet,i downloaded only the grub.exe file of the package Grub4DOS. As said I had the problem, that OpenSolaris 10 comes with a Grub bootloader. So i searches a pretty time the web to find a solution, that i can start grub via Isolinux and then i found this article:http://aronzak.wordpress.com/tag/syslinux/Look at the topic "Howto: Syslinux and Grub on one USB drive" at this site. There you can find the link i downloaded the grub.exe. I think you can also use the grub.exe from the lateset Grub4Dos package as well.To my DVD structure:I have a folder calles BOOT, i chose this cause Vista has this folder on DVD. In this folder i have the dirs "isolinux" and "grub". In the "grub" dir i put only the grub.exe file, in my "isolinux" dir there are all files which isolinux uses as isolinux.bin, ...cfg and the kernel and ramdisk files.In my root directory, i called it "Multiboot2" - as i now decided to make one Multiboot-DVD only with Live-Systems as knoppix and so and one with Systems to install on HD - there i put the grub menu.lst file and the splashscreen file as Grub4Dos seems to search in /root_dir, /grub, or /boot/grub but not in /BOOT/grub as i have.Now to start grub from isolinux put a directive as:LABEL VistaPE OpenSolarisMENU label 7 VistaPE OpenSolaris V10 (Grub4DOS Prompt)kernel /BOOT/grub/grub.exein your isolinux.cfg file. As grub.exe is a linux kernel you can put it in the kernel directive of isolinux.cfg. This directive now starts Grub4Dos and it searches for its menu.lst and splashscreen if you want to have one in the grubmenu.I took the menu.lst from OpenSolaris and made some new entries in it to start VistaPE, as example:title VistaPE chainloader /BOOTMGRtitle OpenSolaris 2008.11 snv_101b_rc2 X86 kernel /platform/i86pc/kernel/unix module /BOOT/x86.microrootThats it. Right after you push the VistaPE OpenSolaris Button in the isolinux menu, grub starts and shows its submenu with this entries. There choose your favourite and VistaPE or OpenSolaris boot. Pls let me know when you did some testing if this works for u. For me its a nice combining of isolinux and grub4dos as grub4dos is better in chainloading other bootloaders in my opinion.greetings Jack Link to comment Share on other sites More sharing options...
JackCarver Posted March 18, 2009 Share Posted March 18, 2009 Hmmm did a little testing of my own. The command you posted doesnt work. when i addAPPEND --config-file="CHAINLOADER /BOOTMGR"in my isolinux.cfg nothing happens. But even more strange, when i use the grub.exe from the latest Grub4Dos Build i get the error:Booting find /menu.lstfind --set-root --ignore-floppies --ignore-cd /menu.lstError 15 File not found...i think this happens cause of the --ignore-cd directive. the version before this one finds menu.lst without problems. dont know how i can change this, that grub doesnt use --ignore-cd or so.Jack Link to comment Share on other sites More sharing options...
JackCarver Posted March 19, 2009 Share Posted March 19, 2009 I got it ... I tested a little time with the latest version of grub4dos and i found out the following:The latest version cant find menu.lst if u do it like the version before. There you needed only kernel /path_to/grub.exe in ur isolinux.cfg. Now itskernel /path_to/grub.exe --configfile=(cd)/Path_to_menu.lstif u want ur splashimage its now splashimage (cd)/path_to_image.gzin ur menu.lst. otherwise grub doesnt find it. dont know why they made it so complicated compared with the older version i tried first but this works.then for example when u want to start vistaPE directly use:kernel /path_to/grub.exe --config-file=chainloader (cd)/path_to/BOOTMGRand PE starts directly without going in menu.lst. Btw u must use chainloader (cd)/path_to/BOOTMGR in ur menu.lst as well. without the (cd) the chainloader directive doesnt work.now i will test if its also possible to start OpenSolaris directly from the isolinux.cfg via grub. perhaps i can paste the kernel and module command from menu.lst directly in the isolinux.cfg.if it works i write it here in the forumgreetings Jack Link to comment Share on other sites More sharing options...
JackCarver Posted March 19, 2009 Share Posted March 19, 2009 Hehe ist works too in isolinux.cfg:kernel /BOOT/grub/grub.exe --config-file="kernel (cd)/platform/i86pc/kernel/unix;module=(cd)/BOOT/x86.microroot;boot"and solaris boots like a charm.Jack Link to comment Share on other sites More sharing options...
kof94 Posted March 22, 2009 Share Posted March 22, 2009 (edited) @PhylumJust in case it's your mkisofs commands this is my simple mkisofs script.This script is located in boot/isolinux along with mkisofs. If your using Windows just grab the commands lower down the script.#!/bin/bash# Script to create a bootable ISO imagecd -- "$(dirname "$0")"SOURCE=$(cd ../; pwd)APPID="Bootdisk"VOLID="Bootdisk"BOOT=boot/isolinux/isolinux.binCATALOG=boot/isolinux/boot.catOUTPUT=$HOME/Bootdisk.isohelp() { echo "-------------------------------------------------------------------------- This script creates a bootable ISO image using mkisofs. Usage: $(basename "$0") [options] Example: $(basename "$0") -o $OUTPUT --md5 -o, --output <file> Set output file name -m, --md5 Create MD5 check file -h, --help Help-------------------------------------------------------------------------- "}waiting() { chars=( "|" "/" "-" "\\" ) array=${#chars[*]} count=0 echo -n " " while [ -e "$1" ]; do count=$(( count + 1 )) echo -ne "\b${chars[$(( count % array ))]}"; sleep 0.2 done}while [ "$1" != "" ]; do case $1 in -h | --help ) help exit ;; -o | --output ) OUTPUT="$2" shift 2 ;; -m | --md5 ) MD5="1" shift ;; * ) shift esacdoneif [ -f "$OUTPUT" ]; then echo "$(basename $0): \`$OUTPUT' already exists" echo -n "Remove this file and continue? [Y/n]: " read retval case $retval in Y|y|[Yy][Ee][Ss]) rm -f $OUTPUT || exit 1 ;; *) help exit 1 esacfirm -f $SOURCE/contents.md5if [ "$MD5" = "1" ]; then if [ -x `type -path mktemp` ]; then md5tmp="`mktemp`" else md5tmp="/tmp/md5.$RANDOM" touch $md5tmp || exit 1 chmod 600 $md5tmp fi echo -n "Creating MD5 check file. Please wait..." waiting $md5tmp & ( cd $SOURCE find . -type f -exec md5sum {} \; | sort -k 2,2 > $md5tmp mv $md5tmp contents.md5 ) echo -e "\bDone"fiif [ ! -x "`type -path mkisofs`" ]; then echo "$(basename $0): \`mkisofs' command not found" exit 1fimkisofs \-iso-level 4 \-full-iso9660-filenames \-disable-deep-relocation \-rock \-joliet \-joliet-long \-no-emul-boot \-boot-info-table \-boot-load-size 4 \-appid "$APPID" \-volid "$VOLID" \-eltorito-boot $BOOT \-eltorito-catalog $CATALOG \-output $OUTPUT \$SOURCE || exit 1echo "$(basename $0): \`$OUTPUT' succesfully created"exit 0One more thing...You can use the file util in Linux to query a file type, I'm not sure but you might find a Windows port as part of cygwin. First decompress the image (gzip -d initrd.gz) then test the file.$ file initrdinitrd: ASCII cpio archive (SVR4 with no CRC) Edited November 16, 2009 by kof94 Link to comment Share on other sites More sharing options...
SXiPRATEEK Posted March 28, 2009 Share Posted March 28, 2009 i use g:\cdas my root folder& my file structure isfor boot filesg:\cd\boot\isolinuxg:\cd\boot\bartpeg:\cd\boot\xpsp3for respective cd contentg:\cd\bartpeg:\cd\xpsp3i use isolinux.cfg asDEFAULT /boot/isolinux/vesamenu.c32PROMPT 0TIMEOUT 300TOTALTIMEOUT 450####MENU BACKGROUND /boot/isolinux/splash.pngMENU TITLE XPSP3 + BARTPE######## The 1st byte of the fgnd color is brightness.#### blueMENU COLOR title 1;36;44 #ff0000ff #00000000 std#### blueMENU COLOR unsel 37;44 #ff0000ff #00000000 std#### white MENU COLOR sel 7;37;40 #c0ffffff #ff000000 std#### redMENU COLOR hotkey 1;37;44 #ffff0000 #00000000 std#### greenMENU COLOR hotsel 1;7;37;40 #ff00ff00 #ff000000 all####LABEL bootcMENU LABEL ^boot from C:MENU DEFAULTKERNEL /boot/isolinux/chain.c32APPEND hd0LABEL bartpeMENU LABEL ^BartPE/WinPEKERNEL /boot/bartpe/bSETUPLDR.BINLABEL xpsp3MENU LABEL ^Unattended XP SP# Pro InstallationKERNEL /boot/xpsp3/xSETUPLDR.BIN& edited SETUPLDR.BIN using hexedit & replace i386 to bartpe/i386 in case of bartpe& replace i386 to xpsp3/i386 in case of xpsp3& rename as bSETUPLDR.BIN &xSETUPLDR.BIN& place ing:\cd\boot\bartpeg:\cd\boot\xpsp3 respnow to make cd i have used mkisofs.exe of pebuilder& created bat to automate process@ECHO OFFECHO Starting @ (%TIME%) ....SET _VNBR_=01SET _ROOT_=G:\cdSET CDTITLE="cd-%_VNBR_%"SET CDFILENAME="%_ROOT_%%CDTITLE%.ISO"C:\pebuilder3110a\mkisofs.exe -N -V %CDTITLE% -b isolinux.bin -d -iso-level 4 -no-emul-boot -boot-load-size 4 -boot-info-table -o "G:\ISO.iso" "G:\cd\boot\isolinux"but all this creat bootable iso of 1.44mbthen i use magiciso to add other files from the cd folder & save itthe image is bootable but when i try to chk it with vmware it just do nothing no error no message & no progress just processing** please help me figureout where i have done mistake thanks in adv if u can tell me simply what to do instead of redirecting then i will really appriciate Link to comment Share on other sites More sharing options...
killr Posted April 7, 2009 Share Posted April 7, 2009 I have some problem i'm using programs ultra ISO for Add my multi-boot size 5 GB and chose Optimizelook picnow size 2,80test on VM working not problem and burn to DVD speed burn 12X test one my computer not problem test on another computer PC not working why where mistake Link to comment Share on other sites More sharing options...
jetman Posted April 16, 2009 Author Share Posted April 16, 2009 (edited) I have some problem i'm using programs ultra ISO for Add my multi-boot size 5 GB and chose Optimizelook pic<snip>now size 2,80test on VM working not problem and burn to DVD speed burn 12X test one my computer not problem test on another computer PC not working why where mistakeCan't help as I've made virtually all of my discs using UltraISO and have occasionally used the Optimization feature successfully. If it [Optimization] doesn't work, sometimes you have to re-organize the contents of a disc, to move some content from one disc to another or use a bigger (DL) disc and turn off Optimzation....Jet Edited April 16, 2009 by jetman Link to comment Share on other sites More sharing options...
Jotnar Posted June 16, 2009 Share Posted June 16, 2009 As an aside, syslinux now includes the Hardware Detection Tool, a module created just for the job of retrieveing hardware information.http://syslinux.zytor.com/wiki/index.php/H...Detection_Tool)Cheers Link to comment Share on other sites More sharing options...
LoR_D Posted July 5, 2009 Share Posted July 5, 2009 Well, hello, world!I followed this howto and I did my isolinux multiboot with linux, xp and win2000... I thought I would have no problem in booting a winbuilder LiveXP, but I was wrong... I couldnt find any bootsect.bin and i think isolinux cannot boot SETUPLDR.BINI knew I had to create an image that boot setupldr.bin & bootfix.bin in the i386 dir, and I did with bbie: I have no problem in booting if i copy the LiveXP "\" in my multiboot "\"......but, as you can guess, it means I can integrate just one LiveXP for dvd... Yeah, one LiveXP per dvd is enough but I just would like not to have such a messy isoI think the problem is redirecting the entire process from "\i386" folder to "\Livexp\i386"... I've tried modifying txtsetup, but i think i have to modify setupldr or doing something similar to the xp installer... and it's over my skills...Anyway, I realize I'm trying like a blind in a open space so, please: help! (like the beatles used to say) Link to comment Share on other sites More sharing options...
florin91 Posted July 11, 2009 Share Posted July 11, 2009 Hello! I tried to follow the how-to and at step 3 it says "From \syslinux, *COPY* (don't *MOVE*) vesamenu.c32, chain.c32, isolinux.bin, memdisk to boot\isolinux\.". The problem is that I don't see memdisk in the huge source of syslinux. Here is a screenshot. Link to comment Share on other sites More sharing options...
jaclaz Posted July 11, 2009 Share Posted July 11, 2009 Hello! I tried to follow the how-to and at step 3 it says "From \syslinux, *COPY* (don't *MOVE*) vesamenu.c32, chain.c32, isolinux.bin, memdisk to boot\isolinux\.". The problem is that I don't see memdisk in the huge source of syslinux.isn't it where it should be? I.e. in this file:http://www.kernel.org/pub/linux/utils/boot...slinux-3.82.zipin the "memdisk" directory, as a file 19.584 bytes in size, called "memdisk" (with no extension)jaclaz Link to comment Share on other sites More sharing options...
florin91 Posted July 11, 2009 Share Posted July 11, 2009 (edited) Oh, yes thanks. I wasn't carefull when extracted the archive ... And I thought it was in the root folder ... sorry. But at "4) Open the System Rescue ISO and copy vmlinuz1 and vmlinuz.igz to boot\sysdresccd\. Copy sysrescd.dat to sysresccd\. Copy memtest86 to boot\isolinux\." in my sysrescuecd-x86-1.2.1.iso I have in NTPASSWD folder the files "initrd.cgz"; "vmlinuz." and scsi.cgz" not vmlinuz1 and vmlinuz.igz. The only *.igz file is INITRAM.IGZ . Edited July 11, 2009 by florin91 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now