similar to: isohybrid patch

Hello all, Past few days I was working on porting the isohybrid perl script to c. (-> https://fedorahosted.org/fedora-engineering-services/ticket/15) The first patch towards the same is attached with this mail. And the same could also be accessed from: http://pjp.dgplug.org/tools/syslinux-3.86-isohybrid.patch I would really appreciate it if somebody could have a look at it and let me know

??? Hi, Recently it was brought to notice by Mr Steffen(snwint at suse.de) that ---- > syslinux 4 comes with a C-rewrite of isohybrid. Unfortunately the option > parsing has changed: it no longer accepts hex numbers (0x...). Was this > intentional or can we have the old behaviour back (say, changing > sscanf(%u) -> sscanf(%i))? > I've made the changes to the current git

I'll file a ticket once fedorahosted is back online. The request is to port the isohybrid script, in the syslinux package, from perl to C (and of course submit it upstream). This would let syslinux drop its dependency on perl, which would save considerable space. $ wc -l git/syslinux/utils/isohybrid.in 258 git/syslinux/utils/isohybrid.in As this is doing some simple structure unpacking

Hi, Just checking, if there are any updates about testing of the isohybrid.c patch at -> http://pjp.dgplug.org/tools/syslinux-3.86-isohybrid.patch.10 Is there anything I can do to help test it? Thank you. --- Regards -P J P PS: Please don't send me html/attachment/Fwd mails

?? Hi, Could someone please have a look at this? -> http://syslinux.zytor.com/archives/2011-June/016649.html ? Thank you. --- Regards -Prasad PS: Please don't send me html/attachment/Fwd mails

Hello Recently while playing with bigger iso images (>2G) looks like isohybrid from syslinux-4.02 fails. Sometimes tunning heads/sectors (-h/-s) works, because no padding is needed depending of size of the image. Some debug info provided, if more info is needed please just ask. # isohybrid -v pandereta-2010.09.13-i686.iso catalogue offset: 326 ve[0]: 1, cs: 1 ve[1]: 0, cs: 1 ve[2]: 25927,

Hi, Miller, Shao: > I am enjoying this discussion Me not. I feel quite misunderstood. hpa: > Actually, I would prefer if you removed this in its current form. Ok. Will do. If any viable solution emerges, please let me know. Have a nice day :) Thomas

On 02/10/14 07:41, Thomas Schmitt wrote: > Hi, > > email at missionaccomplish.com wrote: >> We been trying to boot the image in vbox using efi emulation but it >> complains about kernel not supporting handover. > If it complains about a kernel then it should be past El Torito > or GPT. The job of xorriso is to point BIOS and EFI to their > boot images. Everything else

Hi, > All the "isohybrid.exe" I know of are based on the Perl variant. I just got one from http://www.filewatcher.com/m/isohybrid.exe.39568-0.html Its strings seem not to stem from isohybrid.pl. Digging in slitaz source brought a shell script (that would be variant #5 then): http://hg.slitaz.org/wok/file/313b384e2a06/syslinux/stuff/tools/isohybrid.sh But isohybrid.exe must

Hi, > Not being compatible with EFI/GPT is already a problem for the Perl > variant. The relation of both is: isohybrid.in/.pl is being left behind. http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/Makefile has: SCRIPT_TARGETS += isohybrid.pl # about to be obsoleted isohybrid.c replaces it feature-wise and adds new features. Only those new features contain the bugs,

The worst sin of isohybrid.c was to compose GPT partition names by 8-bit characters and to memcpy() them as if they were 16 bit wide. GPT names are encoded as UTF-16LE. It is trivial to create this encoding from 7-bit ASCII. This change introduces two byte arrays with the desired UTF-16LE names which replace the string constants "ISOHybrid ISO" and "ISOHybrid". ---

We been trying to boot the image in vbox using efi emulation but it complains about kernel not supporting handover. Anyways, I will take your advice and get back to you tomorrow. I think we might be getting close to a successful boot on Mac OSX hardware and any other UEFI capable hardware. Thanks for your help and tomorrow I should come with more data to debug. P.S the latest fedora ISO seems

Hi, Ady: > _ Wiki should use more user-friendly language and "less deep" > technical information. I tried to stay at the surface of isohybrid. (Didier already asked for more depth about expert options.) > _ In the Syslinux wiki, "PC-BIOS" should rather be called plain > "BIOS". I understand there are other "BIOS" for other hardware. But

On 01/11/2013 18:40, Didier Spaier wrote: > On 01/11/2013 05:36, Ady wrote: >> >>> That is with syslinux 4.05 on Slackware-14.0: >>> >>> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >>> catalogue offset: 561 >>> ve[0]: 1, cs: 1 >>> ve[1]: 0, cs: 1 >>> ve[2]: 0, cs: 1 >>> ve[3]: 0, cs: 1 >>>

Hi, email at missionaccomplish.com wrote: > We been trying to boot the image in vbox using efi emulation but it > complains about kernel not supporting handover. If it complains about a kernel then it should be past El Torito or GPT. The job of xorriso is to point BIOS and EFI to their boot images. Everything else is in the scope of the boot images resp. the operating system that shall

No #if. On May 12, 2014 6:26:18 PM PDT, Kang Kai <Kai.Kang at windriver.com> wrote: >On 2014?05?12? 22:38, H. Peter Anvin wrote: >> That is because it needs to use fseeko() and use off_t. > >Do you mean it does need a patch for isohybrid.c. And the patch looks >like: > >#if _FILE_OFFSET_BITS == 64 > fseeko(...) >#else > fseek(...) > >

Hi, Ady: > Since both included variants are currently different, and both > variants have problems I am not aware of problems of the perl version. It is just lacking the newer features which support EFI/GPT and Mac/APM. The known bugs of isohybrid.c are with those newer features. http://www.syslinux.org/archives/2012-May/017843.html

Hi, Ady wrote: > Hmm, but dd'ing isohybrid images is so simple...! > You have the freedom to waste your time. But dd-ing is the reason why isohybrid exists. Matthew Garrett extended the BIOS hard disk use case to UEFI in 2011 and 2012. hpa signed it off and committed it. See

Hi, i wrote: > > Not only MBR writing but also reading of the Primary Volume Descriptor > > and of the El Torito catalog by isohybrid.c are currently prone to > > unwanted CR-insertion. Miscalculations can be caused by this. I have to correct myself: Carriage Return characters (byte value 13 = 0x0d) are not at risk to be inserted, but rather to be removed if they happen to be

When call isohybrid with option '-u', it overflows on a 32 bits host. It seeks to 512 bytes before the end of the image to install gpt header. If the size of image is larger than LONG_MAX, it overflows fseek() and cause error: isohybrid: image-x86-64-20140505110100.iso: seek error - 8: Invalid argument Replace fseek with fseeko to fix this issue. Signed-off-by: Kai Kang <kai.kang at