Customize isolinux.cfg DVD 4.0 ; reburn fails

Copied all files from DVD bittorrent download (boots and runs fine) to root file named DVD.

Replaced /boot/isolinux/isolinux.cfg with customized copy to enable fast boot, lang=us, and myconfig=scan.

Ran mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 -boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -hide-rr-moved -o KNOPPIX40.iso /root/DVD.

Opened k3b and selected KNOPPIX40.iso. The md5 sum check stopped at 48%.

I ran the burn anyhow on DVD r/w. The result was a 48% burn, the boot sequence ended up with large X in center screen and no KDE activity in the rom ensued.

It seems half of the KNOPPIX/KNOPPIX files failed to burn.

The mkisofs total was 4119MB and the properties readout was 4318263616.

Is there a need for a new mkisofs for DVD burns? Two knoppix files are provided in the DVD, one is a normal type and the other is Unionfs related.

I suggest the Unionfs related file is not recognized by the mkisofs routine above.

Please advise corrective action!

Hi,

Does this method of customising work for you with a CD Version 3.6 or 3.8?

I have customized the 3.8.2 isolinux.cfg using the described mkisofs routine successfully.

Failed two attempts using older k3b. Upgraded to version 0.12-2.

Tried to reburn and failed to burn the full nine yards, about half of the DVD is present on the disc. Same display results.

The downloaded DVD is nearly fully burned on the dusc.

The md5 check stops displaying the progress of md5 check at 48% but finishes the check after waiting for some time.

The mkisofs routine reports 4119MB, and k3b reports burning 4GB during the burn.

The DVD properties is listed as 4 318 323 127, 709files, 9 subfolders on the burned DVD +r/w. (Lies!!)

The process did not burn 4GB on the disc.

Problem was two-pronged. Lost myconfig in HDD and re-stated options in isolinux.cfg.

The system reaches the "X" display normally but then switches to the KDE install init. With the DVD not fully burned, no KDE init occurred.

The DVD was re-burned with a new mkisofs run and the disc is now "maxi" burned with a new myconfig generated in the HDD. It is operating normally.

It is probable that , if the HDD data is missing, or applies to another kernel, that the "X" display will appear.

The cheat code for myconfig appeared on the boot sequence but the data never reached the program, hence the "X" display.

All is well!!!