Error customising Knoppix 3.7

[Saint0453]

The commands look OK. But the problem with the mkisofs command, which itself is reporting, that it can't find boot file "boot/isolinux.bin". So, the only possibility I can think out is a typing mistake or the file isolinux.bin may be corrupt. Try to replace boot directory with the boot directory of original CD and tell the progresss.

It looks like it was a typing mistake, i can't beleive it... after the error i even checked the typing but i left out the isolinux folder in /boot/isolinux/isolinux.bin and skimming over it i must have missed the mistake.

I am going to try to burn the iso today and add a file to it to see if it still does the checksum, i will report back later




........I made the iso file and then used an iso modifying program to remove a couple of readme files to test the checksum. I made a cd with the new iso and when i booted with the new iso it still gave me the checksums error.

So I went through and looked to see if there were any md5sums files in in the /mnt/hda1/knx direcotires and I found one in:
/mnt/hda1/knx/master/KNOPPIX/ md5sums

I am not sure if this has any meaning or not.

Thanks.

[raj1478]

So I went through and looked to see if there were any md5sums files in in the /mnt/hda1/knx direcotires and I found one in:
/mnt/hda1/knx/master/KNOPPIX/ md5sums

I am not sure if this has any meaning or not.

Thanks.

Yes, this is the checksum file. I had asked you to remove it before making the iso.
First remove it then make iso. Why are you using iso modifying program to modify the iso.? Just make changes to the master folder and make iso.

After removing the "md5sums" file, you should not get any cheksum errors...

Post the results...

[Saint0453]

Alright, cool, I will try that, though will not be untill monday

I thought that by leaving out the step:
rm -f KNOPPIX/md5sums; find -type f -not-name md5sums -not -name boot.cat -not -name isolinux.bin -exec md5sum '{}' \; >> KNOPPIX/md5sums

the checksum would not be included. All that I do is delete that file before making the iso, there is not anything that is going to call that file and when it is missing it will error out?

Thanks, I will give it a try.

[Saint0453]

After removing the md5sums file and recompiling using the mkisofs -pad -l -r -J etc... comand I still received an error when I later removed some files from the iso.

(Looking back all I did was "rm md5sums". At the time I was not "chroot" into the copied KNOPPIX. Does this make a difference?

Why are you using iso modifying program to modify the iso.? Just make changes to the master folder and make iso.

I am using ISO magic (the iso modifying program) so that I can make the cd a duel / tripple boot cd. Is is the program that adds the menu to boot to the different "operating" systems on the CD.

[raj1478]

I am using ISO magic (the iso modifying program) so that I can make the cd a duel / tripple boot cd. Is is the program that adds the menu to boot to the different "operating" systems on the CD.

Can you elaborate your process, what exactly are you doing after remastering knoppix? What kind of dual/triple booting you are trying?

[Saint0453]

I am using ISO magic (the iso modifying program) so that I can make the cd a duel / tripple boot cd. Is is the program that adds the menu to boot to the different "operating" systems on the CD.

Can you elaborate your process, what exactly are you doing after remastering knoppix? What kind of dual/triple booting you are trying?

I am trying to either get a dual boot of knoppix and helix (if you do not know helix is, it is a forensic costomization of knoppis http://www.e-fense.com/helix/index2.html ) or a tripple boot of knoppix / helix / dos (for ghost and snapback utilities).

I am trying to use this dual/tripple boot cd/dvd at work to make forensic backups and recoveries of hard drives. Using preferably helix, snapback if it fails, to backup the drive; then using knoppix to restore this image, if necessary, to a different hard drive. It would be advantagious for me to have all these bootable tools on one cd/dvd.

After remastering knoppix, and helix I use "ISO Magic" to pull the boot images off the ISO images. I also pull the boot image off of my bootable snapback cd. This being done I can add each ISO to the new CD image within "ISO Magic" and point each boot image to its appropiate ISO. "ISO Magic" then creates a dual / tripple boot cd/dvd with a menu allowing you to select either the helix, knoppix or snapback boot image to boot from. Snapback boots fine, but if I try to boot from knoppix I get the checksum error because the cd/dvd contents have changed.

What is causing it to call the checksum? Idealy I would just like to stop it from doing this checksum verification.

If this is not possible is there a way to create a new checksum once the dual/triple boot cd/dvd is created?

Thanks.

[raj1478]

Hi,
From your description it appears that you are removing boot.img file from the iso or using a copy of boot.img in your CD outside the iso. (Am I right?). Perhaps this tempering with iso file is causing the problem. If yes, then I think you don't need to make your knoppix iso bootable. Just delete the lines "-b KNOPPIX/boot.img -c KNOPPIX/boot.img" from the iso creation command (don't include the md5sums file, delete it if you have created it again) and create the iso. Copy the boot.img file to dos partition and go ahead with the process of creating the bootable CD.


Another thing you can try is to look for help in iso-magic to see if there is an option of creating checksum from within the program. If yes let it compute the checksums for your iso.

I hope I have understood your problem in a right way. Tell me the progress. Good luck..!

[Saint0453]

when I try to make the iso using the command:

mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 -boot-info-table -hide-rr-moved
-o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master

I get the following error:
"Segmentation Fault"

Do you know what would cause this?

I believe what "ISO Magic" does it create a new boot.img using the old one and renames it to 1.img, 2.img, etc. and references these instead of the original boot.img depending on which boot option you choose (helix, knoppix, snapback).

I am not sure if it deletes the old boot.img files or just ignores them while referencing the new ones.

Also, I am not sure I completely understand what you want me to try. You want me to copy the boot.img file to the dos partition and then make the boot CD? I am not sure about this step.

Thanks.

[raj1478]

mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 -boot-info-table -hide-rr-moved
-o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master

I'm sorry, my fault. I gave the suggestion using my experience of 3.4. I've no experience of 3.6 or 3.7 yet. But I can see the options "-no-emul-boot -boot-load-size 4 -boot-info-table". These options are related to making a bootable CD. Delete them too and then retry.

Also, I am not sure I completely understand what you want me to try. You want me to copy the boot.img file to the dos partition and then make the boot CD? I am not sure about this step.

What I want is as follows: -
1. Create an iso using the file with modifications above.
2. Copy your boot.img (and of course your knoppix iso) of knoppix from remaster directory to a DOS partition.
3. When your software asks for boot.img (or boot image) give it the path of the boot.img you copied to your DOS partition.
4. Don't modify the newly created iso with the software.
5. Look for help or any option in your software for creating or verifying checksum.
6. If available, recomputer checksums (through your software) of the contents you are trying to put in your CD (the iso images and boot files etc.)

Tell the progress.

[Saint0453]

I created the non-bootable iso image and then used "ISO Magic" to create the dual boot cd, using the boot image from the original knoppix CD.

I receive the following error:
No-Emulation type image (raw)
0000080000000001
ISO linux 2.04 (debian, 2003-06-05) isolinux: Image checksum error, sorry...

Boot Failed.



To me it looks like the checksum is being called in the boot.bin file and when it can't find the checksum file or the checksum is incorrect it fails.

Is there a way to modify this boot.bin file and remove the part where it checks for the checksum if this is what is occuring?

Note: The "ISO Magic" program does not have a way to create a verifying checksum.

Thanks.