similar to: Good news booting with isolinux

Hi, I'm trying to create a bootable CD, and so far I have had limited success. On the first CD I created, isolinux worked, but I think I had a kernel without the necessary initrd support compiled in, so the boot failed. Now I can't even re-create that success. At the moment the CD's I'm burning (3 so far) do not even show the display file. I used isolinux-debug.bin for the

Hi, > makehybrid \ > -o isos/muaaa.iso temp/ \ > -eltorito-boot temp/isolinux/isolinux.bin \ > -no-emul-boot \ > -iso -joliet -boot-load-size 4 \ > -default-volume-name "Custom Installer" \ > -eltorito-platform temp/isolinux/boot.cat > ... > [at boot time:] > Image checksum error, sorry I guess it is the Boot Information Table feature

Hello List, I have used isolinux for years without problems. Recently I decided to upgrade from 3.09 to 3.11. Every CD I create can be read on my Vectra (Pentium 3) and all other Pentium 3 boxes, but all my Pentium 4 boxes will not boot (they ignore the CD and boot from hard disk). The bochs VM will boot the CDs fine just like the Pentium 3 machines. I have tried 3.09 (which worked

till last week everything was fine, our cds with isolinux and created with mklinux worked fine. but suddenly our build system fails, the cds don't boot anymore, or more precisely: they do boot in vmware and on several new machines we have, but on lots of other, older machines they suddenly stopped working. we didn't change our scripts, and syslinux and mkisofs is still the same version

[cross-posted to nntp://comp.os.linux.setup, sorry] Dear Everyone, I'm writing this message merely to publish this information somewhere visible, so that others can find it when debugging a linux-based bootable CD compilation setup... For many months now, I've been using cdrtools 2.0 with isolinux 2.04 to create bootable Linux CD's. I know there are newer versions of both

Hello! I'm trying to boot with a remastered Knoppix 3.4 CD. I burned it with debugging and I get the following output: isolinux: Starting up, DL = 9F isolinux: Loaded spec packet OK, drive = 9F isolinux: Loading main image from LBA = DEADBEF0 isolinux: Sectors to load = D5B7 isolinux: Disk error BE, AX = 42F0, drive 9F A don't understand everything in it and I can't find enough

Hello, I want to modify isolinux.cfg of a given, bootable iso (of Linux CentOs installation) according to my needs. The things is : I copy the contents of that iso to a different directory. I modify the isolinux.cfg according to my needs. Then what? I had of course googled for it. I had tried afterwards: mkisofs -o centos1.iso -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-i But

Hello, i'm just curious, why the -boot-load-size 4 for mkisofs with isolinux.bin is needed. I searched the list archive and found nothing and found nothing anywhere else. Since the isolinux.bin is much bigger than 4 * 512 byte, I'd suspect, it wont get completely loaded. With -boot-load-size 4, mkisofs reports: Size of boot image is 4 sectors -> No emulation Without it, mkisofs

Hello, I'm Jacques living in France. I have a problem when I use isolinux. I'm working on a multiboot cdrom so I make many "mkisofs" for testing. The problem is that when I modify the "isolinux.cfg" file and then build my image with mkisofs it's the previous configuration of my "isolinux.cfg" which appears on my screen (I run the .iso file with qemu...)

i tried to make a bootable CD with isolinux,but met some problem. the error is as follows. i don't know what cause the problem. anyone met the same problem? thanks for help. ===================================================================================== mkisofs 1.13 (i686-pc-linux-gnu) Scanning . Scanning ./boot Scanning ./isolinux Scanning ./isolinux/help Excluded by match:

I'm using islonix to build my own 'el torito cd bootable'. I use mkisofs : "mkisofs -o c:\temp\toto.iso -r -J -V "toto" -v -no-emul-boot -boot-load-size 4 -boot-info-table -b isolinux/isolinux.bin -c isolinux/isolinux.boot -sort src\isolinux\iso.sort -A "toto" data" When i put only 1-12 files on data/ the cd boot. But when i put many more files on

Hi, we are the developers of an alternative to mkisofs: program xorriso from libburnia-project.org . The current development cycle is about support for creating bootable CDs, DVDs, BDs. So we look for testers and for advise about ISOLINUX specifics. The example from the ISOLINUX wiki is supposed to work if you replace "mkisofs" by "xorriso -as mkisofs". I.e: xorriso -as

H, Ady wrote: > A_ The default checksum included in the tested isolinux.bin (offset 20, > 4-bytes-long) is the "correct" one (as oppose to the current situation, > since version 4.00). That's good news. > F_ In the tested isolinux.bin file, there are two additional bytes that > I found to be changed/affected by some ISO-building tools (e.g. > mkisofs), at

Greetings, I have been using isolinux with Microsoft's cdimage.exe for my Utility / Preinstallation cds. I just upgraded from 3.36 to 3.55 and found it to be non functional. I didn't use the -debug version, it just hangs at the version banner. I went through several previous versions, and it appears that 3.50-pre23 is the last working version. I didn't see anything between that

> Hi, > > i think i found a suspect in lzo/prepcore.c and it would indeed be a > wrong range of checksumming (speculative congratulations to Ady). Thank you Thomas for your replies and for looking into this issue. My part on the initial investigation that triggered this email thread is relatively small. Others deserve much more credit. I was/am providing not just my own report,

Hi, MartinS wrote: > Is it the isohdppx or isohdpfx (or both) that is relevant? The file /.disk/mkisofs in the ISO tells that option -isohybrid-mbr syslinux/usr/lib/ISOLINUX/isohdpfx.bin was used. (This file is a Debian specialty.) I guess you can see at the first bytes of the ISO that the partition interpreter code is not there. > For isohdpfx.bin it will print: > E if EBIOS >

I'm having a problem booting Slackware 10.1 boot CD's as well as an isolinux image of my own. The system is a VIA Epia M10000 and the drive is an AOpen ISU-8424E CD/DVD writer. If I use a Toshiba CD-RW/DVD-ROM Drive SD-R2612 in place of the AOpen DVD writer, the cd boots fine and everything works as expected. What's the best course for further debugging of this problem? The only

I am trying to PXE boot an ISO image using ISOLINUX. I am starting small just trying to get anything working but seem to be having problems. I followed the instructions on the isolinux page (http://syslinux.zytor.com/iso.php) but still cannot get it to work. I can get the ISO image to try to load but then it stops at the booting message. Any help would be greatly appreciated. Here is

Hi All, I've got a simple isolinux cd loading a floppy image via memdisk, that boots reliably on 14 of 15 platforms, but intermittently hangs on one and, unfortunately, I can't substitute the platform. The behavior is weird. If I cold boot the system with the CD already in the drive, it *usually* boots to completion. Warm boots are hit-or-miss. If there's any drive door action

Hi, i think i found a suspect in lzo/prepcore.c and it would indeed be a wrong range of checksumming (speculative congratulations to Ady). Looking at http://repo.or.cz/syslinux.git/blob/0d82b71304d596d80f3c4520f9dcf90048ca50b7:/lzo/prepcore.c it seems that this change in line 374 could yield correct checksums: unsigned int ptr; - for (ptr = 64; ptr < offset; ptr += 4) +