search for: ibsig

I have just pushed out Syslinux 3.81-pre10. This fixes some pretty serious bugs, including the fact that, apparently, isohybrid didn't work at all in CBIOS mode. Unfortunately it means that the isohybrid handover protocol has changed, and so a new isolinux.bin isn't compatible with an old isohybrid or vice versa (as a result, the magic number has changed.) -hpa

I have addressed all the issues that I know about (including, hopefully, the isohybrid version dependence...). I would like to release this this week so please let me know as soon as possible if this version is "go". -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Op 2014-06-20 om 15:56 schreef Ady: > > The Perl variant, isohybrid.in, seems to be getting left behind > regarding several patches. I don't recall whether there is at least > some mention in the isohybrid docs about the existence of 2 variants > included in Syslinux (and that is in addition to other isohybrid > methods outside Syslinux). Is there any reference? >

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

...ybrid is that it bears as first El Torito boot image the isolinux.bin BIOS boot image from a SYSLINUX release which is modern enough to also offer the isohybrid tool. The tools check this and eventually complain: http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.in if ($ibsig ne "\xfb\xc0\x78\x70") { die "$0: $file: bootloader does not have a isolinux.bin hybrid signature.". "Note that isolinux-debug.bin does not support hybrid booting.\n"; } http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.c...

> I proposed -h 252 -s 63 because it yields the largest > possible cylinder size which is divisible by 4 (i.e. > the byte count is divisible by 512*4 = 2048). > -h 240 -s 63 would fulfill this constraint, too. > Size limits are 252*63*1024*512 = 8,323,596,288 > resp. 240*63*1024*512 = 7,927,234,560 bytes. > > > The workaround cannot be temporal, because the

...Torito boot image the > isolinux.bin BIOS boot image from a SYSLINUX release which > is modern enough to also offer the isohybrid tool. > > The tools check this and eventually complain: > > http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.in > if ($ibsig ne "\xfb\xc0\x78\x70") { > die "$0: $file: bootloader does not have a isolinux.bin hybrid signature.". > "Note that isolinux-debug.bin does not support hybrid booting.\n"; > } > > http://git.kernel.org/cgit/boot/syslinux/syslinux.git/t...

Hi, Ady wrote: > Let's not forget that the goal usually is to select CHS values so that > the resulting (optical and/or other) media would boot correctly in as > many systems as possible Agreed. But we now have a report about failure of 255x63 on a popular pseudo-hardware, when the ISO is presented as DVD-ROM. (Probably there is no complaint when it gets presented as hard disk.)