similar to: isohybrid has 2 variants

I'm going to get the hang of this mailing list eventually. Apologies for any duplicate emails.. >Ian Bannerman: >> While I did know the .exe variant was not official / untrusted, >Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Not really. I had never found a convincing source for it and had seen previous list entries like this

Op 2014-06-21 om 21:19 schreef intrigeri: > Hi, > > Ian Bannerman wrote (21 Jun 2014 15:49:51 GMT) : > > One advantage of the Perl one for me is that I can run it on Windows. > > We at Tails rely on isohybrid.pl for installing on OSX: > https://tails.boum.org/doc/first_steps/installation/manual/mac/ > > Of course, this does not mean that the current syslinux team

Hi, at [Tails] we're in the process of shipping hybrid ISO images by default again. We're using `isohybrid -h 255 -s 63' to do that (thanks to the advice we got on this mailing-list a few months ago!). And then, we've discovered that sometimes, isohybrid produces ISO images whose size is not a multiple of 2048 bytes. Who cares? ... may you ask. Well, apparently, VirtualBox does:

Hi, Ian Bannerman: > I did not know the Perl version did not support the EFI/Mac changes. Comparing the help texts of http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.c and http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.in shows that the latter lacks: -u --uefi Build EFI bootable image -m --mac Add AFP table support

Hi, Ian Bannerman wrote (21 Jun 2014 15:49:51 GMT) : > One advantage of the Perl one for me is that I can run it on Windows. We at Tails rely on isohybrid.pl for installing on OSX: https://tails.boum.org/doc/first_steps/installation/manual/mac/ Of course, this does not mean that the current syslinux team owes us to maintain it forever :) Would it help if someone with the needed Perl skills

> Hi, > > at [Tails] we're in the process of shipping hybrid ISO images by > default again. We're using `isohybrid -h 255 -s 63' to do that (thanks > to the advice we got on this mailing-list a few months ago!). > > And then, we've discovered that sometimes, isohybrid produces ISO > images whose size is not a multiple of 2048 bytes. > > Who cares?

>Although there are some "isohybrid.exe" around, there is no official support for them and they are also outdated. >The Syslinux mailing list already includes several emails about issues in the included isohybrid variants. I think that deleting either of them would be a mistake. At least users such as Ian might benefit from both being included. >Ideally, the Perl variant

[I was dropped from cc in the initial response but I'd appreciate if you could keep it this time around since I'm not subscribed to this list. Thanks!] Ady wrote: > I do not know the exact complete procedure that the TAILS team is using > to build the original ISO image, and how it is transformed into an > isohybrid image (there are multiple tools for each, sometimes >

Hi, [ouch, it take me a year? thank you all for this very interesting thread that I'm going to finish reading now.] Pete Batard via Syslinux: > I'll skip the EFI part of tails (that uses grub/EFI) to talk only > about the BIOS/Syslinux part. JFTR Tails uses GRUB only for 32-bit UEFI. We use syslinux for BIOS and 64-bit UEFI. > So, one thing Rufus will need to do is find a

Op 2014-06-23 om 20:09 schreef syslinux-bot for H. Peter Anvin: > Commit-ID: f9dad5340bcefe34d860e991e8743be01a4d6c3c > Gitweb: http://www.syslinux.org/commit/f9dad5340bcefe34d860e991e8743be01a4d6c3c > Author: H. Peter Anvin <hpa at zytor.com> > AuthorDate: Mon, 23 Jun 2014 20:06:51 -0700 > Committer: H. Peter Anvin <hpa at zytor.com> > CommitDate: Mon, 23

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

It is "APM" Apple Partition Map, not "AFP" Apple Filing Protocol Reported-by: Thomas Schmitt <scdbackup at gmx.net> --- utils/isohybrid.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/isohybrid.c b/utils/isohybrid.c index 05afd29..15f63fc 100644 --- a/utils/isohybrid.c +++ b/utils/isohybrid.c @@ -236,7 +236,7 @@ printh(void) printf(FMT,

Op 2014-06-22 om 22:31 schreef Geert Stappers: > Op 2014-06-22 om 21:02 schreef Thomas Schmitt: > > > > following will be 6 patch proposals for isohybrid.c > > > > 1: Encode GPT partition names as UTF-16LE > > 2: Correct blocking factor in APM partition block counts > > 3: Correct end block address of first GPT partition > > 4: Write GPT backup to the

Hi, since the Tails ISO grew from ~900MB to ~1.1GB, we see this warning when running isohybrid on it: isohybrid: Warning: more than 1024 cylinders: 1045 isohybrid: Not all BIOSes will be able to boot this device I guess that's fully expected. And, as expected, we get boot failure reports from users. So, my question is: is there a "known optimal" combination of isohybrid

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, > > 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 there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

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.)

My first attempt ro enable the short options for --uefi, --mac, --mbr was faulty. Here is the second try. This change enables the options -u, -m, -b as promised by the help text. --- isohybrid.c.006_opt_mbr_standalone 2014-06-22 20:10:49.000000000 +0200 +++ isohybrid.c.007_short_opts_umb 2014-06-23 19:52:59.000000000 +0200 @@ -262,7 +262,7 @@ check_option(int argc, char *argv[]) char *err =

> 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