search for: isohdp

From: MartinS <ams at ludd.ltu.se> isohdp[fp]v.S which says E or C if EBIOS or CBIOS is used. isohdppv.S also says G or M if a GPT or MBR partition is detected. Signed-off-by: MartinS <ams at ludd.ltu.se> --- Comments? diff --git a/mbr/Makefile b/mbr/Makefile index be2bded..7095396 100644 --- a/mbr/Makefile +++ b/mbr/Makefile @@ -...

Hi, Martin Str|mberg wrote: > And given that space in isohdpfx is very limited (432 bytes) perhaps > the right thing might be to not have that xor in there. > But then better safe than sorry, and given that there is space _now_, > why not? I still agree. But while answering Ady's questions i get to a question of my own: Do all six fixed isohd...

...+($file, $maxsize) = @ARGV; + +if (!defined($file) or $file == "--help" or $file == "-h") { + $usage = <<"END_USAGE"; +Usage: $0 file [maxsize] +If maxsize is not given it will be guessed based on filename: + - 440 bytes for mbr and gptmbr; + - 432 bytes for isohdp; + - 439 bytes for altmbr. +END_USAGE + die $usage; +} if (!defined($maxsize)) { # Defaults based on the filename if ($file =~ /^mbr[^0-9a-z]/) { - $maxsize = $padsize = 440; + $maxsize = 440; } elsif ($file =~ /^gptmbr[^0-9a-z]/) { - $maxsize = $padsize = 440; + $maxsize = 44...

...> +if (!defined($file) or $file == "--help" or $file == "-h") { > + $usage = <<"END_USAGE"; > +Usage: $0 file [maxsize] > +If maxsize is not given it will be guessed based on filename: > + - 440 bytes for mbr and gptmbr; > + - 432 bytes for isohdp; > + - 439 bytes for altmbr. > +END_USAGE > + die $usage; > +} > > if (!defined($maxsize)) { > # Defaults based on the filename > if ($file =~ /^mbr[^0-9a-z]/) { > - $maxsize = $padsize = 440; > + $maxsize = 440; > } elsif ($file =~ /^gptmb...

...> +if (!defined($file) or $file == "--help" or $file == "-h") { > + $usage = <<"END_USAGE"; > +Usage: $0 file [maxsize] > +If maxsize is not given it will be guessed based on filename: > + - 440 bytes for mbr and gptmbr; > + - 432 bytes for isohdp; > + - 439 bytes for altmbr. > +END_USAGE > + die $usage; > +} > > if (!defined($maxsize)) { > # Defaults based on the filename > if ($file =~ /^mbr[^0-9a-z]/) { > - $maxsize = $padsize = 440; > + $maxsize = 440; > } elsif ($file =~ /^gptmbr[^0-9...

Hi, i have implemented in xorriso the equivalents of isohybrid.c options --mac and --uefi. There remains the question how to ensure that the submitted MBR is prepared for the 32 byte mock-up of an APM Block0. I see in git of may 2012 that all mbr/isohdp[fp]x*.bin begin by 33 ed 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 Can i safely refuse on MBR templates which do not bear that signature without inflicting injustice on future isohybrid MBRs ? (I will also accept...

> 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

On Sun, Mar 26, 2017 at 10:13:28PM +0200, Thomas Schmitt via Syslinux wrote: > Do all six fixed isohdp*.bin variations still fit into 432 bytes ? > > mbr/Makefile builds among other MBRs: > isohdpfx.bin isohdppx.bin isohdpfx_c.bin isohdppx_c.bin > isohdpfx_f.bin isohdppx_f.bin Yes. I make my changes in my syslinux git clone. All of the above is build from isohdpfx.S with different...

..."APM". ---------------------------------------------------------------- Known Variants up to now: - isohybrid.in -> isohybrid.pl from SYSLINUX, no EFI/GPT support - isohybrid.c -> isohybrid from SYSLINUX - libisofs/make_isohybrid_mbr.c from libburnia, needs isohdp[fp]x*.bin -> libisofs, xorriso from SYSLINUX - isohybrid.sh from SliTaz, no EFI/GPT support - iso2exe.c -> isohybrid.exe from SliTaz, no EFI/GPT support ---------------------------------------------------------------- If somebo...

...res suffer from bugs, which obviously do not hamper booting of Fedora ISOs. http://download.fedoraproject.org/pub/fedora/linux/releases/20/Live/x86_64/Fedora-Live-Desktop-x86_64-20-1.iso Debian, Ubuntu, and Archlinux ISOs with EFI support are made with isohybrid from xorriso/libisofs using "isohdp[fp]x*.bin" MBRs from the SYSLINUX installation. intrigeri: > Would it help if someone with the needed > Perl skills stepped up and volunteered to maintain the Perl version, > at least to port bugfixes from the C version? I am willing to explain what is unclear about above options....

> Hi, > > i wrote: > > > I think it still has good reason to exist. > > Ady wrote: > > Would you please clarify what do you mean with "it"? > > "It" was the code part about > > xor %cx, %cx /* Clear EBIOS flag. */ > > which Martin mentioned as "can be ignored" in the the text which i > quoted

...and not about ISOs made with isohybrid options --partok -ctrlhd0 --forcehd0. > which would be the step-by-step instructions for users of other > isohybrid images? Copy at most 432 bytes to the start of USB stick or ISO image file: iso=/dev/sdc or iso=image.iso dd conv=notrunc if=isohdpfx.bin.170324 bs=1 count=432 of="$iso" > Would they differ according to some/any parameter? We do not yet have downloadable binaries of the other five isohdp* variants as listed in http://www.syslinux.org/wiki/index.php?title=Isohybrid#MBR_selection with --partok -ctrlhd0 --force...

...early stage software has to be offered to the intended boot firmware. More or less the overall topic of SYSLINUX et.al. > As one of Didier's questions suggests, the _alternative_ methods seem > to be not clear enough. I am pondering about a translation table from isohybrid options to isohdp[fp]x*.bin and the terminology in the Mbr article. (Three terminologies for the same thing. Sometimes, choice is bad.) > > I showed three of the variants: isohybrid.pl, isohybrid.c, xorriso. > > The other two are not clear enough to me. > Do you mean from Slitaz? Yep. The .sh scr...

...; tree before running these commands. With this in mind, here are my remarks: _Unde PC-BIOS you write: The ISO 9660 production program xorriso can enhance its results by isohybrid, if an MBR template file from the local SYSLINUX installation is provided. The names of these files match the pattern isohdpfx*.bin and are to find in SYSLINUX directory ./mbr or installed as e.g. /usr/lib/syslinux/isohdpfx.bin. But in ./mbr (Syslinnux-407) I find three files isohdpfx{,_c,_f}f.bin so whare are their respective differences and/or use cases? _When you write just before the UEFI title: The result needs no...

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

...o the intended boot firmware. > More or less the overall topic of SYSLINUX et.al. > > > > As one of Didier's questions suggests, the _alternative_ methods seem > > to be not clear enough. > > I am pondering about a translation table from isohybrid options > to isohdp[fp]x*.bin and the terminology in the Mbr article. > (Three terminologies for the same thing. Sometimes, choice is bad.) > > > > > I showed three of the variants: isohybrid.pl, isohybrid.c, xorriso. > > > The other two are not clear enough to me. > > > Do you...

Hi, 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 very end of the image 5: Change all fseek(3) to fseeko(3) 6: Introduce option --mbr and make isohybrid.c compilable standalone If the form needs adjustments,

Hi all, We're using the classic boot BIOS syslinux successfully for many years, but meanwhile it's getting harder to buy hardware the still supports this boot mode. The option for us would be syslinux EFI boot. To avoid too many changes we would like to generate an image for our different hardware parts that supports both - classic BIOS boot and (U)EFI boot. This would allow us to leave

Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one partition

...html -O - | tail -n 388 | head -n 362 | perl -p -e 's/\&quot;/"/g' | perl -p -e 's/&lt;/</g' | perl -p -e 's/\&gt;/>/g' > mbr/martins_mbr.S 2017-03-21 13:18:36 dpchrist at hd-tracy ~/src/syslinux/syslinux-6.03+dfsg+dpchrist $ perl -pi -e 's/(isohdp\[fp\]x)/($1|martins_mbr)/' mbr/checksize.pl 2017-03-21 13:33:55 dpchrist at hd-tracy ~/src/syslinux/syslinux-6.03+dfsg+dpchrist $ make ... 2017-03-21 13:35:26 dpchrist at hd-tracy ~/src/syslinux/syslinux-6.03+dfsg+dpchrist $ ll bios/mbr/martins_mbr.bin -rw-r--r-- 1 dpchrist dpchrist 432 201...