MSFN Forums > Super-Disc: Multi-Boot Project CD/DVD Using ISOLINUX

Daniel.o

Mar 14 2008, 02:23 PM

Hello all,

While I'd hate to sound like a rookie (even though I know I will

), I read about half of the thread and did not find an answer to a rookie-like question. So, even though I do understand this is a how-to and not a tutorial and I do understand what isolinux actually does (and does not) and I do understand what a boot information for each ISO is and how can be extracted, I still can't understand (/find) how I would end up having a multi-boot DVD when starting with the following "baseline":

- one ISO Acronis
- one ISO Dell Diagnostics
- one ISO Win XP SP2 (orig.)
- one ISO Mandriva Spring 2007
- one ISO Win XP SP2 May 2007 (nLite for desktop)
- one ISO Win XP SP2 Feb 2008 (nLite for laptop + Intel SCSI drivers)

My main concern is the layout of the data on the final DVD (where does each ISO content need to go). I understand that pushing the ISO's (as mere files) on it won't actually work (would it ?), but do I need to extract the contents of each ISO in the DVD root for the setup of each one to function (especially the XP ones) ? This, as I understand it, would be quite tricky for me, as the 3 XP "distributions" I need to push there are quite different one from each other.

So, does someone have some words for me around this ?

Thanks.

jetman

Apr 1 2008, 05:45 AM

QUOTE (Daniel.o @ Mar 14 2008, 02:23 PM)

Hello all,

While I'd hate to sound like a rookie (even though I know I will

), I read about half of the thread and did not find an answer to a rookie-like question. So, even though I do understand this is a how-to and not a tutorial and I do understand what isolinux actually does (and does not) and I do understand what a boot information for each ISO is and how can be extracted, I still can't understand (/find) how I would end up having a multi-boot DVD when starting with the following "baseline":

- one ISO Acronis
- one ISO Dell Diagnostics
- one ISO Win XP SP2 (orig.)
- one ISO Mandriva Spring 2007
- one ISO Win XP SP2 May 2007 (nLite for desktop)
- one ISO Win XP SP2 Feb 2008 (nLite for laptop + Intel SCSI drivers)

My main concern is the layout of the data on the final DVD (where does each ISO content need to go). I understand that pushing the ISO's (as mere files) on it won't actually work (would it ?), but do I need to extract the contents of each ISO in the DVD root for the setup of each one to function (especially the XP ones) ? This, as I understand it, would be quite tricky for me, as the 3 XP "distributions" I need to push there are quite different one from each other.

So, does someone have some words for me around this ?

Thanks.

Rookies to the entire Multi-Boot CD/DVD sub-forum make the same mistake over-and-over again: they have these super elaborate projects (exactly WHAT is the point of XPSP2 2007 and 2008 !?!?!) and expect someone to guide them to their destination. The entire point of this exercise is to start w/ a small, doable project and incrementally build it into exactly what you want, on your own.

To repeat what's been said before: The contents of ISOs must be extracted to the hdrive and the ISO's bootstrap must be extracted using BBIE (search the topic for the link and details.) The 1st msg in the topic explains most of one needs to know about disc layout. I've also pointed out Andre's MultiBoot DVD topic as the source for details about adding XP (or whatever) to a Super-Disc project.

Later....Jet

Daniel.o

Apr 1 2008, 07:56 AM

Hi,

Ok, thanks, but I actually got the entire project running with CD Shell, except for Acronis True Image 10, which I can either get to say something like "Boot error ..." or I can either get it to crash during it's own linux-based loader => has someone managed in some way to get it running ?

Thanks.

kof94

Apr 2 2008, 06:09 PM

Acronis True image is a pain in the a**. I had version 9 working about two years ago but to be honest Clonezilla does just as good a job (if not better). All the info you need is right here in the forum if you really want to get it working though, just search

.

jetman

Apr 3 2008, 07:48 AM

QUOTE (kof94 @ Apr 2 2008, 06:09 PM)

Acronis True image is a pain in the a**. I had version 9 working about two years ago but to be honest Clonezilla does just as good a job (if not better). All the info you need is right here in the forum if you really want to get it working though, just search

.

Isn't Clonezilla a client-server solution only ? I started playing w/ it aft you mentioned your work and dropped it for this reason, as I recall. Actually, I want to revisit PartImage this month bec I need a freeware solution for the disk imaging issue....Jet

kof94

Apr 3 2008, 08:48 AM

If you want to make use of multi-casting then you need to setup a DRBL server but if you just want to clone local disks or backup an image to a system on your network then you use the Clonezilla LiveCD! Incidentally Clonezilla implements Partimage, ntfsclone, UDPcast etc for this task.

An added bonus with Clonezilla is it can either create a traditional raw copy of the source disk (entire disk) or just clone the used part of the disk which obviously makes your image smaller and the process faster.

I know I'm starting to sound like an advert here but I've been using Clonezilla for a while now and I really can't see why anyone would spend out on a commercial piece of software that just provides a pretty Windowsy front end with less functionality.

End of rant

jetman

Apr 4 2008, 05:06 AM

QUOTE (kof94 @ Apr 3 2008, 08:48 AM)

If you want to make use of multi-casting then you need to setup a DRBL server but if you just want to clone local disks or backup an image to a system on your network then you use the Clonezilla LiveCD! Incidentally Clonezilla implements Partimage, ntfsclone, UDPcast etc for this task.

An added bonus with Clonezilla is it can either create a traditional raw copy of the source disk (entire disk) or just clone the used part of the disk which obviously makes your image smaller and the process faster.

I know I'm starting to sound like an advert here but I've been using Clonezilla for a while now and I really can't see why anyone would spend out on a commercial piece of software that just provides a pretty Windowsy front end with less functionality.

End of rant

If you're knowledgeable of a subj, it's okay to sound as if you like your choice. Yeah, NTFSCLONE; must try that too. Frankly, I only need one [program]. I've been holding on to copies of GHOST 8 from the days when they bundled it w/ every mboard, but I can't legitmately leave it anywhere even though it's everything I need, incl [and esp] its GDISK. I think PartImage has everything I need, exc they [the authors] won't completely finish it and release 1.0.

Anyway, TTYL....Jet

kof94

Apr 4 2008, 01:58 PM

QUOTE

I can't legitmately leave it anywhere

That's one of the reasons I always look for a FOSS alternative now.

I had a version of my multi-boot disc stolen from my desk at work recently but it doesn't matter because everything on it was FOSS or freeware.

I would have liked to have been asked but at least I've done that person a favor by introducing them to Linux (oops wrong forum

).

Cyborg_sa

Jun 18 2008, 12:35 AM

I added dsl as guided in the 1st post of this topic. After bootup, when I select dsl, it searches for usb devices after that it says Can't find KNOPPIX filesystem. Please help me here.

rageaddict

Jun 18 2008, 01:18 AM

did you forget to add the rock ridge file system?

Cyborg_sa

Jun 18 2008, 03:32 AM

I think I did. Can u give an example on how to enable rock ridge ?

EDIT:
I added the rock ridge but no use it shows the same error.

EDIT:
Added joliet and everything works fine.

rageaddict

Jun 18 2008, 04:37 AM

have you put the dsl files in root??

anyways, im using cdshell because i have widows on my multi boot... you could try pointing your dvd boot file to > cdshell > and cdshell to isolinux...
use cdshell to boot dsl... just a wild guess.

jetman

Jun 18 2008, 05:53 AM

QUOTE (rageaddict @ Jun 18 2008, 05:37 AM)

have you put the dsl files in root??

anyways, im using cdshell because i have widows on my multi boot... you could try pointing your dvd boot file to > cdshell > and cdshell to isolinux...
use cdshell to boot dsl... just a wild guess.

No. CDSHELL uses a hacked ISOLINUX and we speak the latest ISOLINUX around here. Besides, DSL (up to 3.3) definitely works w/ ISOLINUX. RockRidge isn't the answer, nor is putting the DSL files in the root....Jet

rageaddict

Jun 18 2008, 12:35 PM

i just downloaded DSL 4.4.1 and managed to multi boot it..

heres how..
1) i extracted everything from dsl-4.4.1.iso to a folder named DSL
2) i copied everything within folder DSL\BOOT\ISOLINUX to folder DSL
3) i copied everything within folder DSL\KNOPPIX to folder DSL
4) i deleted folder DSL\BOOT
5) i deleted DSL\LOST+FOUND

so the folder contents of DSL are...

QUOTE

boot.cat
boot.msg
f2
f3
german.kbd
isolinux.bin
isolinux.cfg
KNOPPIX
linux24
logo.16
minirt24.gz

finally here's the isolinux command i use to call DSL from cdshell.ini

QUOTE

if $lastKey == key[b]; then isolinux /SETUP/DSL/linux24 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 xmodule=fbdev initrd=/SETUP/DSL/minirt24.gz nomce noapic quiet knoppix_dir=/SETUP/DSL/ BOOT_IMAGE=knoppix

its all one line... and i made some changes...

1) i kept folder DSL in a folder called SETUP (doesn't matter where you put it. just remember to call perfectly from the cdshell.ini menu)

2) i use the above command to redirect to the following files LINUX24 / MINIRT24.GZ / KNOPPIX.

finally, i set my file system to ISO 9660 and ROCK RIDGE...

rageaddict

Jun 19 2008, 08:46 AM

EDIT : for some reason this method doesn't work with multi-boot... all the isolinux commands from cdshell.ini technically fail...

for example this one...

QUOTE

if $lastKey == key[b]; then isolinux /SETUP/DSL/linux24 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 xmodule=fbdev initrd=/SETUP/DSL/minirt24.gz nomce noapic quiet knoppix_dir=/SETUP/DSL/ BOOT_IMAGE=knoppix

this ends with the "filesystem not found" error screen.

however, make an iso with just and only dsl with cdshell and it boots up perfectly... no errors...

i always use rock ridge and iso 9660 as file systems...
does anybody know why this happens???

Cyborg_sa

Jun 21 2008, 04:14 AM

I added knoppix, tested it through vmware. Now I cant build an ISO when I try to add BartPE. I get the following error:

QUOTE

mkisofs -N -V "Multiboot-DVD" -b boot/isolinux/isolinux.bin -joliet -d -iso-level 4 -no-emul-boot -boot-load-size 4 -boot-info-table -o D:\Test.iso D:\Multiboot-DVD
Warning: creating filesystem that does not conform to ISO-9660.
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.
Warning: creating filesystem with (nonstandard) Joliet extensions
but without (standard) Rock Ridge extensions.
It is highly recommended to add Rock Ridge
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.NETWORKING.RTCDLL_659
5B64144CCF1DF_5.2.2.3_X-WW_D6BD8B95.CAT and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.W
INDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_D6BD8B95.MANIFEST have the same Joliet name

mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.NETWORKING.RTCDLL_659
5B64144CCF1DF_5.2.2.3_X-WW_D6BD8B95.CAT and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.W
INDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_D6BD8B95.MANIFEST have the same Joliet name

mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.1.MICROSOFT.WINDOWS.SYSTEMCOMP
ATIBLE_6595B64144CCF1DF_5.1.2600.2000_X-WW_E037A8A.CAT and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/
X86_POLICY.5.1.MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.2600.2000_X-WW_E037A8A.MANI
FEST have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.1.MICROSOFT.WINDOWS.SYSTEMCOMP
ATIBLE_6595B64144CCF1DF_5.1.2600.2000_X-WW_E037A8A.CAT and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/
X86_POLICY.5.1.MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.2600.2000_X-WW_E037A8A.MANI
FEST have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CON
TROLS_6595B64144CCF1DF_6.0.2600.5512_X-WW_790A60E8.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIF
ESTS/X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.2600.5512_X-WW_790A60E8
.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.7.0.MICROSOFT.WINDOWS.CPLUSPLUSR
UNTIME_6595B64144CCF1DF_7.0.2600.5512_X-WW_5CD6C02B.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANI
FESTS/X86_POLICY.7.0.MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.2600.5512_X-WW_5CD6C0
2B.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CON
TROLS_6595B64144CCF1DF_6.0.2600.5512_X-WW_790A60E8.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIF
ESTS/X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.2600.5512_X-WW_790A60E8
.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CON
TROLS_6595B64144CCF1DF_6.0.2600.5512_X-WW_790A60E8.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIF
ESTS/X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.2600.5512_X-WW_790A60E8
.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.2.2.3_X-WW_5F924D7B.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING
.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS
/X86_POLICY.5.2.MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_CF59288D.CAT hav
e the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595
B64144CCF1DF_5.1.2600.2000_X-WW_BCC9A281.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_M
ICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.2600.2000_X-WW_BCC9A281.CAT have the same J
oliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595
B64144CCF1DF_5.1.2600.2000_X-WW_BCC9A281.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_M
ICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.2600.2000_X-WW_BCC9A281.CAT have the same J
oliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.1.0.MICROSOFT.WINDOWS.GDIPLUS_65
95B64144CCF1DF_1.0.2600.5512_X-WW_ED7CE46C.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86
_POLICY.1.0.MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.2600.5512_X-WW_ED7CE46C.CAT have the sa
me Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_POLICY.1.0.MICROSOFT.WINDOWS.GDIPLUS_65
95B64144CCF1DF_1.0.2600.5512_X-WW_ED7CE46C.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86
_POLICY.1.0.MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.2600.5512_X-WW_ED7CE46C.CAT have the sa
me Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.NETWORKING.RTCRES_659
5B64144CCF1DF_5.2.2.3_EN_16A24BC0.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOF
T.WINDOWS.NETWORKING.RTCRES_6595B64144CCF1DF_5.2.2.3_EN_16A24BC0.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595
B64144CCF1DF_5.1.0.0_X-WW_FC342B0B.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSO
FT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.0.0_X-WW_FC342B0B.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.NETWORKING.RTCRES_659
5B64144CCF1DF_5.2.2.3_EN_16A24BC0.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOF
T.WINDOWS.NETWORKING.RTCRES_6595B64144CCF1DF_5.2.2.3_EN_16A24BC0.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.NETWORKING.RTCRES_659
5B64144CCF1DF_5.2.2.3_EN_16A24BC0.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOF
T.WINDOWS.NETWORKING.RTCRES_6595B64144CCF1DF_5.2.2.3_EN_16A24BC0.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595
B64144CCF1DF_7.0.0.0_X-WW_2726E76A.CAT and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WI
NDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A.MANIFEST have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595
B64144CCF1DF_7.0.0.0_X-WW_2726E76A.CAT and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WI
NDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A.MANIFEST have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF
1DF_1.0.2600.5512_X-WW_DFB54E0C.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.
WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.2600.5512_X-WW_DFB54E0C.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF
1DF_1.0.2600.5512_X-WW_DFB54E0C.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.
WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.2600.5512_X-WW_DFB54E0C.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.NETWORKING.DXMRTP_659
5B64144CCF1DF_5.2.2.3_X-WW_468466A7.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROS
OFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_468466A7.CAT have the same Joliet name

mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.NETWORKING.DXMRTP_659
5B64144CCF1DF_5.2.2.3_X-WW_468466A7.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROS
OFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.2.2.3_X-WW_468466A7.CAT have the same Joliet name

mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595
B64144CCF1DF_7.0.2600.5512_X-WW_3FD60D63.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_M
ICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.2600.5512_X-WW_3FD60D63.CAT have the same J
oliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF
1DF_1.0.0.0_X-WW_8D353F13.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOW
S.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595
B64144CCF1DF_7.0.2600.5512_X-WW_3FD60D63.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_M
ICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.2600.5512_X-WW_3FD60D63.CAT have the same J
oliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595
B64144CCF1DF_7.0.2600.5512_X-WW_3FD60D63.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_M
ICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.2600.5512_X-WW_3FD60D63.CAT have the same J
oliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B
64144CCF1DF_6.0.0.0_X-WW_1382D70A.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOF
T.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B
64144CCF1DF_6.0.0.0_X-WW_1382D70A.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOF
T.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A.CAT have the same Joliet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B
64144CCF1DF_6.0.2600.5512_X-WW_35D4CE83.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MI
CROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.2600.5512_X-WW_35D4CE83.CAT have the same Jol
iet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B
64144CCF1DF_6.0.2600.5512_X-WW_35D4CE83.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MI
CROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.2600.5512_X-WW_35D4CE83.CAT have the same Jol
iet name
mkisofs: Error: D:\Multiboot-DVD/I386/WINSXS/MANIFESTS/X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME
-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7.MANIFEST and D:\Multiboot-DVD/I386/WINSXS/MANIFE
STS/X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7.C
AT have the same Joliet name
mkisofs: Joliet tree sort failed.

If I remove -joliet parameter, ISO file is created but KNOPPIX does not work. Any Solution to this?

cdob

Jun 21 2008, 06:37 AM

QUOTE (Cyborg_sa @ Jun 21 2008, 04:14 AM)

If I remove -joliet parameter, ISO file is created but KNOPPIX does not work. Any Solution to this?

Add Rock Ridge file extension instead: mkisofs -r

Cyborg_sa

Jun 21 2008, 08:29 AM

QUOTE (cdob @ Jun 21 2008, 07:37 AM)

QUOTE (Cyborg_sa @ Jun 21 2008, 04:14 AM)

If I remove -joliet parameter, ISO file is created but KNOPPIX does not work. Any Solution to this?

Add Rock Ridge file extension instead: mkisofs -r

Done already. This does not help

Cyborg_sa

Jun 21 2008, 08:51 AM

Just found a solution. mkisofs should be used with the following parameters

QUOTE

mkisofs -no-pad -U -J -joliet-long -hide-joliet

As for my DVD structure

QUOTE

mkisofs -N -V "Multiboot-DVD" -b boot/isolinux/isolinux.bin -no-pad -U -J -joliet-long -hide-joliet -d -iso-level 4 -c boot.cat -hide boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o D:\Test.iso D:\Multiboot-DVD

Now everything works fine

jetman

Jun 23 2008, 06:41 AM

QUOTE (Cyborg_sa @ Jun 21 2008, 09:51 AM)

Just found a solution. mkisofs should be used with the following parameters

QUOTE

mkisofs -no-pad -U -J -joliet-long -hide-joliet

As for my DVD structure

QUOTE

mkisofs -N -V "Multiboot-DVD" -b boot/isolinux/isolinux.bin -no-pad -U -J -joliet-long -hide-joliet -d -iso-level 4 -c boot.cat -hide boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o D:\Test.iso D:\Multiboot-DVD

Now everything works fine

Actually, this is my fault. I need to update the intro msg to the topic to include a download site for MKISOFS, that works w/ the initial script I provided. As I've pointed out in later msgs, there are several versions of MKISOFS w/ minor cmd-line incompatibilities.

I would definitely discourage anyone from using RockRidge in conjunction w/ BartPE or XP. No probs w/ Linux, but it always fouled up Windows-based sware on my builds....Jet

jetman

Jun 23 2008, 06:57 AM

QUOTE (rageaddict @ Jun 18 2008, 01:35 PM)

i just downloaded DSL 4.4.1 and managed to multi boot it..

heres how..
1) i extracted everything from dsl-4.4.1.iso to a folder named DSL
2) i copied everything within folder DSL\BOOT\ISOLINUX to folder DSL
3) i copied everything within folder DSL\KNOPPIX to folder DSL
4) i deleted folder DSL\BOOT
5) i deleted DSL\LOST+FOUND

so the folder contents of DSL are...

QUOTE

boot.cat
boot.msg
f2
f3
german.kbd
isolinux.bin
isolinux.cfg
KNOPPIX
linux24
logo.16
minirt24.gz

finally here's the isolinux command i use to call DSL from cdshell.ini

QUOTE

if $lastKey == key[ b ]; then isolinux /SETUP/DSL/linux24 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 xmodule=fbdev initrd=/SETUP/DSL/minirt24.gz nomce noapic quiet knoppix_dir=/SETUP/DSL/ BOOT_IMAGE=knoppix

its all one line... and i made some changes...

1) i kept folder DSL in a folder called SETUP (doesn't matter where you put it. just remember to call perfectly from the cdshell.ini menu)

2) i use the above command to redirect to the following files LINUX24 / MINIRT24.GZ / KNOPPIX.

finally, i set my file system to ISO 9660 and ROCK RIDGE...

Please do not offer or ask for CDSHELL solutions in this thread. Simply bec you're using ISOLINUX as a chainloader under CDSHELL doesn't mean the post is appropriate here. The entire idea behind this thread is to offer a coherent source of solutions for using the latest ISOLINUX to make multiboot CD/DVDs. Regardless of what some mite suggest, ISOLINUX and its utils are very easy to use and are a complete alternative to CDSHELL. There are plenty of other places for soliciting and offering help w/ CDSHELL issues....Jet

midz

Jul 12 2008, 04:47 PM

i'm having a problem and i can't seem to solve it, hopping someone can help.
i'm trying to integrate Backtrack3 (or 2 - it has the same issues) into a multiboot dvd based on jets initial post,
bt3 boots fine until

CODE

*looking for data directory
Fatal error occurred - BT3 data not found.
You are maybe using an unsupported boot device (eg. SCSI or old PCMCIA)
...

i have no ideea why this is happening since bt is based on slax and slax works perfectly in this setup.
dvd directory structure is:

CODE

\dvd\
      boot\
              bt3\
              dsl\
              isolinux\
              slax\
              sysresccd\
      bt3\
      dsl\
      i386\
      slax\
      sysresccd\
      bootsect.bin
      WIN51IP
      WIN51IP.SP2

i386 is bartPE,
config file snippet for bt3:

CODE

LABEL bt3
MENU LABEL Backtrack
KERNEL /boot/bt3/vmlinuz
APPEND vga=0x317 initrd=/boot/bt3/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=kdm

testing done in vmware - virtual cdrom device using ide interface
i have to admit my isolinux skills don't go higher than begginer level so i'm running out of ideeas,
googled it and what i found didn't help me, please help...
midz

Jotnar

Jul 14 2008, 07:34 PM

Add from=/bt3 to your isolinux append line. Make sure you have livecd.sgn in the bt3 folder.

Cheers

Here's some tips for multibooting other distros:

QUOTE

Chris D'Hondt (cmdhondt @ hotmail.com)
Changes to Support Multibooting Linux Live CDs on the Same Disc (14,June 2008)

This assumes that your disc label is "AdminToolkit" and that your linux directory
on the root of your disc is called LINUX. Change ISOLinux kernel and append statements as needed.

Almost all of these changes deal with editing files inside the initrd.
This file is usually a gzipped cpio or a gzipped ext2 image.

Knoppix - use the knoppix_name and knoppix_dir cheatcodes on ISOLinux initrd boot paramaters.

DSL - See Knoppix

Zenwalk - need to change name of livecd.sgn and edit liblinuxlive to change LIVECDSGN and LIVECDNAME variables
from=/LINUX/ZENWALK needs to be added on isolinux append line.
root password is ZenLive.

Fedora - Username is root, no password. initrd0.img is gzipped cpio.
To unpack: $> mkdir /home/user/tmp
$> mv initrd0.img initrd0.gz
$> gunzip initrd0.gz
$> cd tmp
$> cpio -id < ../initrd0
$> mv ../initrd0 ../initrd0_old

needed to change the sections in 'init' where it referenced the LiveOS directory.
ie.. OSMINSQFS, EXT3FS, SQUASHED. You also need to change the lines right above so
the files can be found

To pack:
$> cd /home/user/tmp
$> find . | cpio --create --format='newc' > ../initrd0.img
$> cd ..
$> mv initrd0.img initrd0
$> gzip initrd0
$> mv initrd0.gz initrd0.img

Ubuntu - need to change casper in initrd/scripts
change all $Path/casper to $Path/LINUX/UBUNTU/casper
change $mountpoint/.disk/casper-uuid to $mountpoint/LINUX/UBUNTU/.disk/casper-uuid
change all $Directory/casper to $Directory/LINUX/UBUNTU/casper
See above (Fedora) for cpio extraction and compilation.

Kubuntu - See Ubuntu

Linux Mint - See Ubuntu

OpenSuSE - need to change config.isoclient file to point new location for
openSUSE-10.3.i386*. Also need to change init and linuxrc so
that LIVECD_CONFIG points to config.isoclient in the right place.
See above (Fedora) for cpio extraction and compilation.

Mandriva - needed to modify linuxrc and change LABEL to AdminToolkit
also change /live/media/distrib.sqfs to correct path.

Clonegenius- need to change copy path in init under "Mounting Squashfs filsystem"
ISOLinux append line needs SUBDIR=LINUX/GENTOO added

CloneZilla - add /live_media/LINUX/CLONEZILLA to live_media_path_checklist in
pkg\opt_drbl.tgz\opt\drbl\conf\drbl-ocs.conf
add /live_media/LINUX/CLONEZILLA to possible_path variable in ocs-live.d/s03prep-drbl-clonezilla
add /live_media/LINUX/CLONEZILLA to possible_path variable in S99start-ocs-live in /etc/rcS.d
put changed S99start-ocs-live in the root of initrd
need to change casper in initrd/scripts
change all $Path/casper to $Path/LINUX/CLONEZILLA/casper
change all $Directory/casper to $Directory/LINUX/CLONEZILLA/casper
at the bottom (line right before the brace) create a new line and add
cp S99start-ocs-live "${rootmnt}/etc/rcS.d/"
See above (Fedora) for cpio extraction and compilation.

PCLinuxOS - need to change linuxrc in initrd (ext2 image).
Change $MNTCDROM/$BASEIMG$LOOPSEXT to $MNTCDROM/LINUX/PCLINUXOS/$BASEIMG$LOOPSEXT
Change losetup $DEVLOOP $MNTCDROM/$BASEIMG$LOOPTYPE to losetup $DEVLOOP $MNTCDROM/LINUX/PCLINUXOS/$BASEIMG$LOOPTYPE
Change all $MNTCDROM/livecd.sqfs to $MNTCDROM/LINUX/PCLINUXOS/livecd.sqfs

Kaspersky - In init change ${cdrom_mount_point}${SUBDIR}/kavresc to ${cdrom_mount_point}${SUBDIR}/LINUX/KASPERSKY/kavresc
Gentoo based.

Gentoo - In ISOLinux config change loop=image.squashfs to loop=/LINUX/GENTOO/image.squashfs
In ISOLinux config add SUBDIR=LINUX/GENTOO

Backtrack - In ISOLinux config add from=/LINUX/BACKTRACK

Virtualbox is a good way to test your changes
To get eth0 interface working in VirtualBox, you need the Bridge_Utils package:

$> brctl addbr br0
$> ifconfig eth0 0.0.0.0
$> brctl addif br0 eth0
$> ifconfig br0 192.168.1.2 netmask 255.255.255.0

midz

Jul 15 2008, 04:24 PM

Yeah, my bad, i missed the from= parameter i was using on slax BUT no good
it still doesn't find it's data directory as discribed in my earlier post, i can't understand why
because slax works and the config lines for slax and bt3 are essentially identical as you can see...

CODE

LABEL slax
MENU LABEL ^7  Slax 5
KERNEL /boot/slax/vmlinuz
APPEND vga=769 max_loop=255 initrd=/boot/slax/initrd.gz from=/slax init=linuxrc load_ramdisk=1 prompt_ramdisk=0  ramdisk_size=4444 root=/dev/ram0 rw nopcmcia
-----------
LABEL bt3 
MENU LABEL ^8 BackTrack 3 
KERNEL /boot/bt3/vmlinuz
APPEND vga=0x317 max_loop=255 initrd=/boot/bt3/initrd.gz from=/bt3 init=linuxrc  load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=6666 root=/dev/ram0 rw autoexec=kdm

Also livecd.sgn is in the bt3 folder.
Am i missing something?

Thanks,
midz

Jotnar

Jul 15 2008, 07:25 PM

What's your mkisofs command line?

jetman

Jul 16 2008, 09:45 AM

Midz: I believe BT3 is based on the most rec version (v6) of Tomas M's Linux-Live scripts, so that LIVECD.SGN's location must also change. As I research this issue using my old Super-Discs, I have both Slax-5 and Slax-6 (ie. two diff versions of the Linux-Live scripts) working on a Super-Disc, so it isn't too tough. I seem to recall that the 'from' cmd-line option changed a little bit bet versions. Also review your cmd-line, as this changed from Linux-Live-5 to Linux-Live-6.

What I can say with certainty, is that the structure of the orig source must be replicated for each version of the Linux-Live scripts. Therefore, whatever is in the root of the Slax-5 disc must appear in the \dvd\slax sub-dir, which is where LIVECD.SGN lives. The same is true of BT3 (which should be comparable to Slax-6), so that you should have a \dvd\bt3\boot and \dvd\bt3\slax. \dvd\bt3\slax is probably where LIVECD.SGN lives, assuming the BT crew didn't hack liblinuxlive. HTH....Jet

midz

Jul 16 2008, 09:46 AM

this is the mkisofs command line i'm using

CODE

mkisofs -N -V mb12 -b boot/isolinux/isolinux.bin -d -iso-level 4 -no-emul-boot -boot-load-size 4 -boot-info-table -o mb12.iso \mb

Jotnar

Jul 17 2008, 09:10 AM

@midz
Try this one:

CODE

mkisofs -J -joliet-long -no-iso-translate -N -V mb12 -b boot/isolinux/isolinux.bin -iso-level 4 -no-emul-boot -boot-load-size 4 -boot-info-table -o mb12.iso \mb

@Jetman
I have all my linux live-cds booting from a directory called LINUX on the root of my dvd so I know you can put them in directories other than the default

. The SLAX (5/6) based ones where easy to do since the from= boot parameter tells it where to look for the LIVECD.SGN file first. Otherwise it'll search the whole disc and will try to boot from the directory it finds that file in first, which can end up being the wrong one if you have mutiple SLAX based distros on your disc like I do (SLAX 5 / SLAX 6 / ZenWalk 5 / Backtrack 3).

Cheers

jetman

Jul 18 2008, 01:44 PM

QUOTE (Jotnar @ Jul 17 2008, 10:10 AM)

@midz
Try this one:

@Jetman
I have all my linux live-cds booting from a directory called LINUX on the root of my dvd so I know you can put them in directories other than the default

. The SLAX (5/6) based ones where easy to do since the from= boot parameter tells it where to look for the LIVECD.SGN file first. Otherwise it'll search the whole disc and will try to boot from the directory it finds that file in first, which can end up being the wrong one if you have mutiple SLAX based distros on your disc like I do (SLAX 5 / SLAX 6 / ZenWalk 5 / Backtrack 3).

Cheers

Jotnar: I understood all of that and read your earlier post about hacks to other distros that I haven't touched yet: very good ! My point was that 'from=' changed a little bit, from Linux-Live-5 to 6, but it still helps find LIVECD.SGN. I did my SuperDisc proj w/o hacks to the init ramdisk and I still segmented the distros in their own sub-dirs. Also, I discovered that LL/Slax-5 had several directories in the root, while LL/Slax-6 had two: /boot and /slax. Initially, I made the mistake of breaking out the sub-dirs in /slax, to match the layout of LL/Slax-5. Never worked and I suspect midz did something like that. Also the reason I mentioned the cmd-line boot opts changed. It would never find LIVECD.SGN. So, I have something like:

CODE

\Super-Disc
   killbill\
      base\
      devel\
      modules\
    etc...
  slax-6\
     boot\
     slax\
        base\
        devel\
        modules\
      etc...

I probably could've buried killbill (Slax-5) and slax-6 under another dir level, but otherwise I did my proj w/o mods.

Re: MKISOFS cmd-line opts, I've covered that more than once, but perhaps it's time for another recap in the 1st msg, w/ a pointer to a MKISOFS dload.

I also need to d/l a fresh copy of PCLinuxOS, to try your hack for adding it to a multi-boot disc. Later....Jet

Jotnar

Jul 18 2008, 06:54 PM

Sorry Jet, I misread your post.

Cheers

midz

Jul 22 2008, 11:52 AM

Jet, you were right I was using the same layout for slax6 as for slax5 and as you know it didn't work.
I tried doing it your way with the boot and slax dir under a slax6 dir and it worked with:

CODE

from=/slax6

What did you mean by 'from=' changed a little bit?

Here's the interesting part, BT3 works with the usual layout, boot and data dirs split, BUT using Jotnar's mkisofs command line (Jotnar, can you expand on why this works...), I'm guessing this has something to do with the file system since my initial one used rock ridge while the new one uses joliet?
Funny though i expected BT3 to behave like Slax6, guess i was wrong.

Thanks,
midz

SaGGiO

Aug 4 2008, 08:41 AM

I hope you dont get mad at me... but... could someone upload a basic iso example.
I cant get it working... I need to se a working example... to modify it... Thats how i learn this stuff...

Hope you can help me... i Just need... ISOlinux menu whit only one or 2 items, a bin file loader... such as xp extracted boot image... and thats all... after that i think i would get it working my way...

Thanks...

Bye

jetman

Aug 5 2008, 04:24 PM

QUOTE (midz @ Jul 22 2008, 12:52 PM)

Jet, you were right I was using the same layout for slax6 as for slax5 and as you know it didn't work.
I tried doing it your way with the boot and slax dir under a slax6 dir and it worked with:

CODE

from=/slax6

What did you mean by 'from=' changed a little bit?

If I remembered, I would've told you !

Neustaedter

Aug 13 2008, 10:10 AM

QUOTE (Jotnar @ Jul 14 2008, 07:34 PM)

Add from=/bt3 to your isolinux append line. Make sure you have livecd.sgn in the bt3 folder.

Cheers

Here's some tips for multibooting other distros:

QUOTE

Chris D'Hondt (cmdhondt @ hotmail.com)
Changes to Support Multibooting Linux Live CDs on the Same Disc (14,June 2008)

This assumes that your disc label is "AdminToolkit" and that your linux directory
on the root of your disc is called LINUX. Change ISOLinux kernel and append statements as needed.

Almost all of these changes deal with editing files inside the initrd.
This file is usually a gzipped cpio or a gzipped ext2 image.

Knoppix - use the knoppix_name and knoppix_dir cheatcodes on ISOLinux initrd boot paramaters.

DSL - See Knoppix

Zenwalk - need to change name of livecd.sgn and edit liblinuxlive to change LIVECDSGN and LIVECDNAME variables
from=/LINUX/ZENWALK needs to be added on isolinux append line.
root password is ZenLive.

Fedora - Username is root, no password. initrd0.img is gzipped cpio.
To unpack: $> mkdir /home/user/tmp
$> mv initrd0.img initrd0.gz
$> gunzip initrd0.gz
$> cd tmp
$> cpio -id < ../initrd0
$> mv ../initrd0 ../initrd0_old

needed to change the sections in 'init' where it referenced the LiveOS directory.
ie.. OSMINSQFS, EXT3FS, SQUASHED. You also need to change the lines right above so
the files can be found

To pack:
$> cd /home/user/tmp
$> find . | cpio --create --format='newc' > ../initrd0.img
$> cd ..
$> mv initrd0.img initrd0
$> gzip initrd0
$> mv initrd0.gz initrd0.img

Ubuntu - need to change casper in initrd/scripts
change all $Path/casper to $Path/LINUX/UBUNTU/casper
change $mountpoint/.disk/casper-uuid to $mountpoint/LINUX/UBUNTU/.disk/casper-uuid
change all $Directory/casper to $Directory/LINUX/UBUNTU/casper
See above (Fedora) for cpio extraction and compilation.

Kubuntu - See Ubuntu

Linux Mint - See Ubuntu

OpenSuSE - need to change config.isoclient file to point new location for
openSUSE-10.3.i386*. Also need to change init and linuxrc so
that LIVECD_CONFIG points to config.isoclient in the right place.
See above (Fedora) for cpio extraction and compilation.

Mandriva - needed to modify linuxrc and change LABEL to AdminToolkit
also change /live/media/distrib.sqfs to correct path.

Clonegenius- need to change copy path in init under "Mounting Squashfs filsystem"
ISOLinux append line needs SUBDIR=LINUX/GENTOO added

CloneZilla - add /live_media/LINUX/CLONEZILLA to live_media_path_checklist in
pkg\opt_drbl.tgz\opt\drbl\conf\drbl-ocs.conf
add /live_media/LINUX/CLONEZILLA to possible_path variable in ocs-live.d/s03prep-drbl-clonezilla
add /live_media/LINUX/CLONEZILLA to possible_path variable in S99start-ocs-live in /etc/rcS.d
put changed S99start-ocs-live in the root of initrd
need to change casper in initrd/scripts
change all $Path/casper to $Path/LINUX/CLONEZILLA/casper
change all $Directory/casper to $Directory/LINUX/CLONEZILLA/casper
at the bottom (line right before the brace) create a new line and add
cp S99start-ocs-live "${rootmnt}/etc/rcS.d/"
See above (Fedora) for cpio extraction and compilation.

PCLinuxOS - need to change linuxrc in initrd (ext2 image).
Change $MNTCDROM/$BASEIMG$LOOPSEXT to $MNTCDROM/LINUX/PCLINUXOS/$BASEIMG$LOOPSEXT
Change losetup $DEVLOOP $MNTCDROM/$BASEIMG$LOOPTYPE to losetup $DEVLOOP $MNTCDROM/LINUX/PCLINUXOS/$BASEIMG$LOOPTYPE
Change all $MNTCDROM/livecd.sqfs to $MNTCDROM/LINUX/PCLINUXOS/livecd.sqfs

Kaspersky - In init change ${cdrom_mount_point}${SUBDIR}/kavresc to ${cdrom_mount_point}${SUBDIR}/LINUX/KASPERSKY/kavresc
Gentoo based.

Gentoo - In ISOLinux config change loop=image.squashfs to loop=/LINUX/GENTOO/image.squashfs
In ISOLinux config add SUBDIR=LINUX/GENTOO

Backtrack - In ISOLinux config add from=/LINUX/BACKTRACK

Virtualbox is a good way to test your changes
To get eth0 interface working in VirtualBox, you need the Bridge_Utils package:

$> brctl addbr br0
$> ifconfig eth0 0.0.0.0
$> brctl addif br0 eth0
$> ifconfig br0 192.168.1.2 netmask 255.255.255.0

Hi - I know my question is not quite right positioned here, but anyway....
I followed your instruction to build a multiboot USB-pendrive with ubuntu and pmagic located in subfolders on the stick. I am using syslinux v.3.71 and it works fine with pmagic, but with ubuntu I found no way to get it work. It starts up fine first, but then the boot-process stops on the bootscreen (with the scrollbar scrolling around) with alternating access on the USB-stick and then the CD-drive. I assume that it has something to do with the mountpoint in initrd/scripts/casper, but I have no idea what the stick's mountpoint is - I tried /media/CORSAIR already (regular mountpoint under installed Ubuntu), but that doesn't work. So any hint would be greately appreciated...

Jotnar

Aug 18 2008, 08:28 PM

Try booting it without the "quiet" and "splash" options. (Hit tab at the boot screen when the boot option is selected and then delete them from the options line). That may give more of a hint at where its failing.

Cheers

Israeru

Aug 28 2008, 08:41 AM

Hello I am tryng to make a multiple live cd that bots some distributions, but only Ubuntu Hardy Hedron dont bot, there are the distros, directory structure and my isolinux.cfg:

Knoppix 5.1 live cd -- ok
Fedora 9 live cd (gnome based) -- ok
OpenSUSE 11 with KDE 4.1 -- ok
Mandriva ONE KDE -- ok
Kubuntu Hardy -- don´t boot

Live dvd label: MandrivaOne (for boot mandriva! n_n), firts i use grub for boot the live dvd, and isolinux in a second try

CODE

Directory structure:boot/ -- here are the global menu.lst, in the root the mandriva kernel, in the directories the kernels and initrd of the other distros distros
boot/grub -- grub menu.lst configs files only
boot/grub/mandriva -- only menu.lst
boot/grub/ubuntu -- menu.lst, kernel and initrd
boot/grub/suse -- menu.lst, kernel and initrd
boot/grub/knoppix -- menu.lst, kernel and initrd
boot/grub/fedora -- menu.lst, kernel and initrd.gz
boot/cdrom -- directory for mandriva initrd
casper/ -- here the loopback image for kubuntu, the kernel and initrd
config.isoclient* -- this archive is for the kiwi system of Fedora
isolinux/ -- this isolinux directory is from the mandriva live cd, also i reuse it for tryng boot the dvd using this isolinux :P
KDE-Four-Live-read-only.i686-1.1.0* -- loopback image of SUSE 11
KNOPPIX/ -- for the knoppix image
LiveOS/ -- for the Fedora image
loopbacks/ -- for the mandriva image
preseed/ -- ubuntu files... i don´t know for what :P
ubuntu@ -- link from ubuntu

CODE

default Mandriva One KDE
prompt 1
timeout 40
gfxboot /boot/syslinux/bootlogo
label Mandriva One KDE
kernel /boot/vmlinuz
append initrd=/boot/cdrom/initrd.gz splash=silent vga=788

label SUSE 11 KDE 4.1
kernel /boot/suse/linux
append initrd=/boot/suse/initrd ramdisk_size=512000 ramdisk_blocksize=4096 splash=silent

label Fedora 9
kernel /boot/grub/fedora/vmlinuz0
append initrd=/boot/grub/fedora/initrd0.img rhgb root=CDLABEL=SFD rootfstype=iso9660 ro quiet liveimg

label Knoppix 5.1
kernel /boot/grub/knoppix/linux
append initrd=/boot/grub/knoppix/minirt.gz ramdisk_size=100000 init=/etc/init lang=es apm=power-off vga=791 nomce splash BOOT_IMAGE=knoppix

label Kubuntu Hardy
kernel /casper/vmlinuz
append initrd=/casper/initrd.gz boot=casper bootkbd=es quiet splash

Then i generate the iso image with this command:

genisoimage -V SFD -J -R -D -o sfd.iso -b isolinux/isolinux.bin -c isolinux/boot.catalog -no-emul-boot -boot-load-size 4 -boot-info-table

But ubuntu dont choose the live filesystem, this is the shoot of the error:

http://img46.imageshack.us/img46/8868/errorubuntuog1.png

Help please T_T n_n

killr

Sep 25 2008, 04:59 AM

what about ophcrack XP LiveCD and ophcrack Vista LiveCD and backtrack 3

how can add this

thank you all

kof94

Sep 28 2008, 07:52 AM

@Israeru

Sounds to me like you missed out the .disk hidden directory from the livecd.

@killr

Ophcrack and BackTrack are both based on slax. There's loads of info about Slax around here so I'll leave you to search.

If your using isolinux you wont be able to boot Vista's bootmgr but you do have the choice of using either GRUB4DOS or BCDW instead.

I use BCDW as the launcher from isolinux:

isolinux label

CODE

label vista
  menu label Windows Vista Recovery Console
  kernel /bcdw/loader.bin
  append -

bcdw.ini

CODE

[InitOptions]

[MenuItems]
\boot\bootmgr

[MenuOptions]
MenuDefault = 0
MenuTimer = 1

Jotnar

Oct 3 2008, 01:37 PM

@kof94
You can boot WinPE v2.x from ISOLinux.

Extract the boot sector and boot that from ISOLinux while having BOOTMGR on the root of your disc and the BOOT folder there too. If you don't change the BCD file then you need to have the wim file in a folder called SOURCES that exists on the root of the disc. I changed BCD to point to a wim in the BOOT folder to cut down on the number of folders in my root but it works fine either way. If you want to have a BOOTMGR menu with the correct labels you'll need to use the BOOTMGR file from pre-SP1 VISTA or pre WinPE 2.0. The boot process for VISTA\2008\PE2.X can be summed up like this: BOOTSECTOR -> BOOTMGR -> BOOT\BCD -> SOURCES\BOOT.WIM.

@killr
I think the only difference between the two different Ophcrack discs is the tables. So if you copy all the tables into one of the folders it should find both the Vista and the XP ones. Then you only need to multiboot two discs.

Cheers

kof94

Oct 4 2008, 03:41 AM

I tried what you said to start with but couldn't get it to work. The boot sector just keeps returning something like "Cannot find BOOTMGR".

I'm not really a Vista user either, I just keep a copy of the Vista Recovery Disk to fix other peoples PC's so I don't really have anyway of editing the bootmgr.

I'll give it another go later and get back to you.

jetman

Oct 5 2008, 05:47 AM

QUOTE (kof94 @ Oct 4 2008, 04:41 AM)

I tried what you said to start with but couldn't get it to work. The boot sector just keeps returning something like "Cannot find BOOTMGR".

I'm not really a Vista user to be either, I just keep and copy of the Vista Recovery Disk to fix our peoples PC's so I don't really have anyway of editing the bootmgr.

I'll give it another go later and get back to you.

Kof: Just for the record, have you been keeping up w/ the latest releases (now 3.72) of ISOLINUX ? In rec months, the pkg has been improved for enhanced Windows compatibility. I haven't had a chance to try this myself, but it's (reported to be) pos to load modules like SETUPLDR.BIN, NTLDR, etc now....Jet

kof94

Oct 11 2008, 04:33 PM

Yes and no. I recently decided to update my multi-boot disc so I took advantage of some of the new features but I still can't get the Vista bootmgr to boot.

It's no bother though, bcdw does the job for now and I don't really use Windows much any more apart from at work or other peoples PC's anyway.

cdob

Oct 12 2008, 07:55 AM

Vista boot sector is case sensitive at ISO9660:
use name \BOOT\BOOTMGR, not \boot\bootmgr. And use \SOURCES\BOOT.WIM

Syslinux chain.c32 does chainload NTLDR at media with Master Boot Record.
I've no idea how to use this at DVD.

jetman

Oct 13 2008, 06:12 AM

QUOTE (cdob @ Oct 12 2008, 08:55 AM)

Vista boot sector is case sensitive at ISO9660:
use name \BOOT\BOOTMGR, not \boot\bootmgr. And use \SOURCES\BOOT.WIM

Syslinux chain.c32 does chainload NTLDR at media with Master Boot Record.
I've no idea how to use this at DVD.

One can replace the hd0 param w/ boot, to specifiy the orig boot media, but only w/ SYSLINUX and EXTLINUX. Time to post a question about this on the mail list. I've tried the new CHAIN feature, but the job I wanted to experiment on was short on time, so I had to resort to more conventional measures (ie. install from a stock XP disc.)

Later....Jet

Gremo

Nov 25 2008, 09:22 PM

Hi there! Anyone? Need help with Vista WinPE and Gentoo linux. CD layout:

CODE

isolinux <--- 3.72
BOOT <--- Taken from WinPE
linux
    gentoo
        gentoo
        gentoo.igz
        image.squashfs
SOURCES <--- Taken from WinPE
BOOTMGR <--- Taken from WinPE
EFI <--- Taken from WinPE
vista.bin <--- Extracted with bbie

Neither WinPE or Gentoo boot. Vista gives me "Cannot find BOOTMGR" while Gentoo "Media not found! Could not find CD to boot".

CODE

LABEL -
MENU LABEL Windows Vista SP1 Recovery Console
KERNEL /vista.bin
APPEND -

CODE

LABEL -
MENU LABEL Gentoo Linux 2008.0 Minimal CD
KERNEL /linux/gentoo/gentoo
APPEND root=/dev/ram0 init=/linuxrc dokeymap looptype=squashfs loop=/linux/gentoo/image.squashfs cdroot initrd=/linux/gentoo/gentoo.igz subdir=/linux/gentoo vga=791

jetman

Dec 1 2008, 11:22 PM

QUOTE (Gremo @ Nov 25 2008, 10:22 PM)

Hi there! Anyone? Need help with Vista WinPE and Gentoo linux. CD layout:

CODE

isolinux <--- 3.72
BOOT <--- Taken from WinPE
linux
    gentoo
        gentoo
        gentoo.igz
        image.squashfs
SOURCES <--- Taken from WinPE
BOOTMGR <--- Taken from WinPE
EFI <--- Taken from WinPE
vista.bin <--- Extracted with bbie

<snip>

Check out Jotnar's tips for integrating several Linux distros, for help pertaining to Gentoo. I recently added a Vista Recovery Disc image to one of my SuperDisc projects and there was nothing to it. That is, it's just the boot image (courtesy of BBIE) and the sources sub-dir. I mite also review the MKISOFS cmd-line opts you're using....Jet

gabo2502

Dec 26 2008, 02:02 AM

QUOTE (midz @ Jul 22 2008, 11:52 AM)

Jet, you were right I was using the same layout for slax6 as for slax5 and as you know it didn't work.
I tried doing it your way with the boot and slax dir under a slax6 dir and it worked with:

CODE

from=/slax6

What did you mean by 'from=' changed a little bit?

Here's the interesting part, BT3 works with the usual layout, boot and data dirs split, BUT using Jotnar's mkisofs command line (Jotnar, can you expand on why this works...), I'm guessing this has something to do with the file system since my initial one used rock ridge while the new one uses joliet?
Funny though i expected BT3 to behave like Slax6, guess i was wrong.

Thanks,
midz

I have the same problem with my BT3 live CD, error: Fatal error occurred-BT3 data not found
Maybe you are using an unsupported boot device (eg-SCSI or old PCMCIA).
Workaround: Copy the directory BT3 from your boot device to IDE / SATA disk. eg. Mnt/had/BT3 or C: \ BT3. Then try to boot again.
Please help correct as

Thank you

midz

Dec 30 2008, 04:19 PM

Have you tried using the mkisofs command line Jotnar suggested to me back then? It worked fine for me, you can find it back there, anyway just in case this would be it:

CODE

mkisofs -J -joliet-long -no-iso-translate -N -V mb12 -b boot/isolinux/isolinux.bin -iso-level 4 -no-emul-boot -boot-load-size 4 -boot-info-table -o mb12.iso \mb

Would like to know if this does the trick for you....

midz

gabo2502

Jan 2 2009, 12:03 AM

I did not test well, a question, put where i the command, thanks.

If possible an example thank you very much for your help.

Phylum

Feb 5 2009, 04:17 PM

I'm a *n?x lover but sad to see that there's no Windows app. to simplify this process. Such a shame. We're not a *n?x shop which means I gotta load up a Live CD. In any event, thanks to all who have posted.

Naturally I'm here because I'm doing the same as everyone else: Trying to create a one-stop-shop CD/DVD with various tools. In addition to various distro's of linux (Gentoo, Linux Mint, Ubuntu, BackTrack 3, GParted, RIPLinuX) I'm also trying to get some useful utilities on there a well. Speifically the Offline NT Password & Registry Editor and Maxtor MaxBlast 5. (Yea, there's some overlap, but I won't always be available to guide my co-workers through how to use it the other tools.)

I imagine it won't be too difficult to get the Offline NT Password & Registry Editor working as its based on some flavor of linux so I can deal with a bit of logic, trial & error there. But what about getting Maxblast, or any other non-linux app (like a Windows Install), as an option?

I've not tried any of this yet, but I am in the process of doing so. Big thanks to Jetman & Jotnar for keeping in the spirit of open source and helping others! (http://www.msfn.org/board/index.php?showtopic=94398&st=220&p=780896&#entry780896 - very useful)
A thanks to all those who have been contributing to this is also.