Damn Small Linux And Bart's Pe On Same Cd, How ca i make this Options

[dwalker0229]

I am trying to add dsl to my bart's pe with bcdw. I get the error, can't find KNOPPIX filesystem i load the boot.img and have the boot.cat and KNOPPIX in a directory called knoppix. Can anyone suggest anything.

[FM_81]

I think, you must not only have a iso-level-4-filesystem on the CD, you must also have RockRidge.
Otherwise: uppercase and lowercase for folder- and filenames is not the same.
MfG FM_81

[dwalker0229]

should i have everythig put into lowercase

[cdob]

Use uppercase and lowercase. Don't uppercase unix files.

PE requires some upercased files, use forum search.

[MrFSL]

Cheers all.
There is alot of confusion amongst many people concerning KNOPPIX disks. I have been building custom KNOPPIX disks for quite awhile now and often see posts with mis-information. So, without making this a tutorial here is some information about KNOPPIX and KNOPPIX/PE Hybrid CD's.

First off:
1) Knoppix CD's DO NOT require RockRidge
2) Lowercase filenames are not needed

Here is why.
1) The KNOPPIX filesystem is all contained in the file called KNOPPIX inside a folder called KNOPPIX on the root of the cd. This file is created by redirecting the output of mkisofs to a file compression utility (Cloop). When the KNOPPIX image is made in mkisofs, RockRidge file extensions are infact used. So when the KNOPPIX image is mounted it has all the rr extensions it needs for the KNOPPIX file system. An example script for building the KNOPPIX file is:

CODE

mkisofs -R /KNOPPIX | create_compressed_fs - 65536 > KNOPPIX

ISOLinux also does not require rr.

2) If you are using ISOLinux to boot your CD (which I suggest) you can note that it does not differentiate between uppercase and lowercase files so that at least gets you CD booted. The small linux kernel that gets loaded which mounts the KNOPPIX image file looks for the file 'KNOPPIX' located in folder on the root CD also called 'KNOPPIX' so you have to make sure you have these things located in the correct place.

So with this being said back to your problem. For starters you can use this script to build your PE/DSL hybrid CD.

CODE

mkisofs.exe -J -N -v -joliet-long -iso-level 4 -force-uppercase -b ISOLINUX/ISOLINUX.BIN -no-emul-boot -boot-info-table -o "./PECD.iso" "./DIR"

(Guarenteed to work!!)

If this doesn't solve your problem then consider the following:
1) More times then not the KNOPPIX file system cannot be found because the KNOPPIX image file itself is corrupt. To guard against this, get a Md5sum of the original KNOPPIX file before you extract it off the DSL disk. Then when you have your PE CD built check the KNOPPIX file against this initial md5sum.
2) Try different CD media. I have found on some computers KNOPPIX does not boot off of CD-RW's.
3) Make sure your ISOLINUX.CFG file is correct

I hope this helps.
**Note that rr will not cause this CD not to boot... it is just is not necessary as some claim. Also note that not all the flags I have included in the above script are necessary either. This is simply the script that I use with my PECD hybrid because of other tools I use on my disk.

[jacky]

Found in an old forums topic
I use this
With UltraIso
create an new iso, put all you're file, and put that in the properties


CD file system :
check joliet and iso 9660

Iso 9660 filename fomat :
check Max (221) and Omit iso 9660 version number

Joliet filename format :
check extended (110)


Jacky

[dwalker0229]

Using ftweak-case.exe

I made all files in my Bartpe directory UPPERCASE
Then made \bootsect.bin and \knoppix\knoppix lowercase.

Then i used mkisofs.exe -J -N -v -joliet-long -iso-level 4 -force-uppercase -b ISOLINUX/ISOLINUX.BIN -no-emul-boot -boot-info-table -o "./PECD.iso" "./DIR"

That did the trick I thank you guys verymuch for helping.

[cdob]

ISO9660:1999 and rock ridge is a working solution in my case.

Of course, there are another solutions. But I know this and can speak about.

If I disable RockRidge, I get:
Can't find KNOPPIX filesystem, sorry.
Dropping you to a (very limited) shell.

I don't use joliet filesystem. Joliet dosn't support needed file name length in my case: non english BartPE.

There is one possibility, don't include long filenames in joliet tree: -hide-joliet i386
But I don't like that solution.

mkisofs.exe -o image.iso -iso-level 4 -output-charset cp850 -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -hide boot.catalog -graft-points -duplicates-once -sort pe_sort.txt bartpe knoppix xp rampe

Isolinux.cfg
# Knoppix 3.7
LABEL knoppix
KERNEL linux24
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 xmodule=vesa initrd=minirt24.gz nomce quiet BOOT_IMAGE=knoppix

The boot image /KNOPPIX/KNOPPIX does exist.

Isolinux boot small linux kernel. Small linux kernel can't detect knoppix image.

How does small linux kernel detect knoppix image?
-does it use ISO9660, ignoring file case
-or ISO9660, file case importand
-or use joliet filesystem
-or use rock ridge filesystem

[FM_81]

ISO9660:1999 and rock ridge is a working solution in my case.

Absolutely correct, I can only confirm this!
If the kernel and the initrd (in your case the minirt24.gz) has been booted, then will be the big compressed KNOPPIX-image loaded. Only RockRidge will implement the permissions on CD, like linux needs.
You need this also, if your booted KNOPPIX will access other files from CD (e.g. virus-signatures), and you wish to copy them to the KNOPPIX-ramdisk. If you have not RockRidge, may be you get problems with permissions; other solution in that case: patch the KNOPPIX-file itself.

But may be, in some cases you don't need RockRidge!

MfG FM_81

[MrFSL]

@cdob

CODE

mkisofs.exe -o image.iso -iso-level 4 -output-charset cp850 -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -hide boot.catalog -graft-points -duplicates-once -sort pe_sort.txt bartpe knoppix xp rampe

No -force-uppercase ?

How does small linux kernel detect knoppix image?
-does it use ISO9660, ignoring file case
-or ISO9660, file case importand
-or use joliet filesystem
-or use rock ridge filesystem

Definately does not use rock ridge because I (like others) do not use rock ridge and have no problems booting. Furthermore, I can't imagine it using Joliet. Seems like it would make sense to use ISO9660 but as far as ignoring file case goes, on every KNOPPIX distro I have ever seen they are uppercase, and I have never tried to lowercase them. Interesting what would happen if I did! Perhaps next build I will try this.

Finally concerning my use of joliet filenames.... as stated in my post, my build script is NOT solely to get KNOPPIX running but also to get KNOPPIX running with several other tools that I use which require Joliet (hybrid). I did not try to give the impressions that Joliet filenames where necessary, only that RR are not. Furthermore it must be stressed that the error "KNOPPIX Filesystem could not be found" is a generic message that does not mean necessarily that it cannot find the /KNOPPIX/KNOPPIX file, but it can also mean other things such as the /KNOPPIX/KNOPPIX file is corrupt.


Cheers!

[cdob]

@MrFSL

Yes, no -force-uppercase. Some BartPE files are uppercased before at hard disk.

A existing knoppix distro use ISO9660, joliet and rock ridge.

BartPE use ISO9660:1999.

Most likely knoppix kernel use ISO9660 to detect /KNOPPIX/KNOPPIX.

Maybe knoppix kernel don't understand ISO9660:1999 and use a fallback file system.
A fallback file system can be joliet or rock ridge.

I can't boot knoppix using only ISO9660:1999 file system.
Maybe I make an additional error.

If I use same source files, same DVD-RW and add rock ridge, then knoppix boot.
I guess, my /KNOPPIX/KNOPPIX is not corrupt.

[MrFSL]

@cdob

Sorry did not mean to sound like a prig. I would agree whole-heartedly that your /KNOPPIX/KNOPPIX is not corrupt.

I wonder... do you use ISOLinux to boot Knoppix or do you use MEMDISK + Image file to boot?

Also, when I asked about "-force-upppercase" I should have been more specific and asked "Is your /KNOPPIX/KNOPPIX uppercase all the way through?"

My comment about corrupt /KNOPPIX/KNOPPIX I meant to address to the forum and not to you in particular. There are several posts both here and at http://www.knoppix.net where people complain about missing file system in KNOPPIX and it is not the case that the file is not there nor undetectible but rather unreadable or unmountable for one reason or the other.

Lastly, perhaps the small linux boot kernel does require Joliet or RR. I have not ever built without Joilet so I would not know. Thank you for all your posts. Just note that my intention in this thread is to inform people that adding RR is not required absolutly, because often the next post is "I addded RR and it still doesn't work now what?"

[cdob]

I'm using IsoLinux 3.02 and don't use another boot manager in addition.

There is a uppercased file /KNOPPIX/KNOPPIX at CD/DVD.

I agree with you: Knoppix dosn't require rock ridge absolutely.

I used Knoppix 3.7 and created three CD-RW:

plain ISO9660:
-Kernel 2.4.27 dosn't detect KNOPPIX image
-Kernel 2.6.9 dosn't detect KNOPPIX image

ISO9660 and -joliet-long:
-Kernel 2.4.27 does detect KNOPPIX image
-Kernel 2.6.9 does detect KNOPPIX image

ISO9660 and rock ridge:
-Kernel 2.4.27 does detect KNOPPIX image
-Kernel 2.6.9 does detect KNOPPIX image

I'm surprised: plain ISO9660 dosn't work.

Lastly, perhaps the small linux boot kernel does require Joliet or RR.

Yes, that's true.

[MrFSL]

@cdob

Ah your testing is quite prompt and informative.

My final question is... where do you find the time! (Ha Ha!)

Anyways this is an answer for others on the forums. From now on I will tell people to enable either J or RR depending on their needs.

I'm surprised: plain ISO9660 dosn't work.

Me too. You'd think it would right?

Thanx again cdob for doing the work for us!

[sanbarrow]

Hi all

mkisofs.exe -iso-level 4 -force-uppercase  -volid ""Sanbarrow"" -A SANBARROW/MKISOFS -sysid ""Win32"" -R -b %_bootfile% -no-emul-boot -boot-load-size 4 -hide %_bootfile% -hide boot.catalog -o %_outiso% %_source%

this works for me to have BartPE, Knoppix and OpenBSD on one disk.

@MrFSL
I tried to add Knoppix-std and DSL by renaming the DSL-knoppix-image and changing the cfg in the boot-floppy-image but failed to boot DSL afterwards.
Is there a way to have two or more Linuxversions that all use the name KNOPPIX/KNOPPIX ?

[MrFSL]

@sanbarrow
My question is... why would you want to?

What does DSL linux have that STD doesn't. If you just want it to start up with the different GUI then you can do that from the command line when booting.

[sanbarrow]

I want to use the 'inram' feature of DSL - Knoppix-secure is a little bit to large for that ;-)

[dwalker0229]

to me it seems like the problem has to deal with it being case sesitive, ive used rr, 9660:1999 9660 and joliet the only time it dosent work is if it is in caps as long as it is in lower case it seems to find the fs just fine

[Fordiman]

The correct command for making a hybrid KNX-type/Win32-type CD is:

mkisofs -no-pad -U -J -joliet-long -hide-joliet -iso-level 4 -b isolinux/isolinux.bin -c boot.cat -hide boot.cat -no-emul-boot -boot-load-size 4 -o [myiso.iso] [isodir]

Additionally, you should write a perl or PHP script to uppercase the I386 directory and its immediate contents (not subdirs) contents (as you'll be booting from a filesystem that has Joliet extensions, and as such will preserve filename case. You don't want that during boot, as the boot-chain is case sensitive, unlike the rest of Windows.

The core iso9660 kernel driver (the one that's included in DSL/KNX using the 2.4.x kernel) does NOT like Joliet. So hide it, and knoppix doesn't knotice. The -N is critical for Knoppix, as the iso9660 driver will throw a fit with the newer iso level, but only if it notices. Since the files DSL and KNX use to load their compressed root do not use any of the iso level 4 extensions, it doesn't need to know they're being used by Bart/Win32.

You shouldn't use -force-uppercase in this event, as Knoppix will NOT like that. (This is pragmatic. KNX will seem to start all hunky-dory, but will continue trying to search for the KNOPPIX image and never find it, dropping you to a HIGHLY limited console.)

I generally hide boot.cat, as it's a pretty useless file to have, and it clutters up whatever directory you put it in with a file that merely looks important. Keep in mind that it's generated when you make the ISO, so you don't need to have one.

I stick isolinux in /isolinux, rather than /boot/isolinux, as it saves 2k. Not much, but I went to the school of Every Byte Counts.

To get a hybrid disc up and running, you need a copy of your WinXP boot sector. Run BBIE and move Image1.bin to isolinux/bartpe.bin. Point isolinux to it like so:

CODE

title bartpe
kernel bartpe.bin

For KNX/DSL, you can just copy the isolinux sections of interest (usually DEFAULT) from the isolinux provided on your DSL/KNX disc.

Also, I would suggest grabbing the memtest kernel off the interweb. If you're going to have a multiboot disc, there are certain utilities you just SHOULD have on it. memtest is one of 'em. The Offline NT Registry and Password Editor is another (search for ntpasswd). I have a tweaked 2.88M version of my Partition Magic boot floppies on there using memdisk as well.

As an example, my multiboot template disc is about 10M in size and contains those tools, as well as a version of FreeDOS with NTFS4DOS, CDROM, sound and mouse drivers with maxllf and your basic dos utilities, and a copy of Tom's RTBT for those "I NEED AN ADMIN CONSOLE NOW" times. I have a template batch file for building the disc, so I don't EVER need to fight with mkisofs again.

So yeah. Use my tips, and make yourself up a template. Never, ever be caught without your basic utilities again.

Additional tips:
To place multiple Win32-type boots on a CD:

• Rename your I386 folder to something else that is arbitrary, but four uppercase characters. In this case, we'll use BART.
• use edit /64 and replace "I386" with "BART" in the following files:
  • BART/SETUPLDR.BIN
  • BART/TXTSETUP.SIF
  • isolinux/bartpe.bin

That's all the needs done there.

To place multiple DSL/KNX/Other Knoppix derivitive on one CD.

• Rename the offending KNOPPIX folders to something else (in this case DSL)
• Rename the kernels from each linux to something appropriate for their owner (IE: knoppix's linux24->knx24.knl (kernel), minirt24.gz-> knx24.ird (init ramdrive); dsl's to dsl.knl & dsl.ird)
• In the append line pertaining to DSL in your isolinu.cfg, add KNOPPIX_DIR=DSL (alternatively, you can just rename the KNOPPIX image to DSL and use the KNOPPIX_NAME parameter. This is all handled by a script called linuxrc guarded within minirt.gz, and is not an actual kernel parameter.

[teletom]

Hello!

analogue to Fordiman i am using this
mkisofs -r -hide-rr-moved -U -iso-level 4 -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -hide "isolinux.bin" -hide boot.catalog -o [myiso.iso] [isodir]

Father more:
-sort sort.txt
-volid "BartPE"
-b "bootsect.bin"
-hide "bootsect.bin"

Works excellent on multiboot CDs (DVDs) with BartPE, Dos, Acronis linux and DSL Knoppix.

Fordiman's command line has 168 chars,
my command line has 162 chars.

Why should be my command line false?

My command line saves 6 bytes in comparison with Fordiman's command line. "Not much, but I went to the school of Every Byte Counts."

Regards,
Teletom