search for: isohdppx

Thomas Schmitt wrote: > I have some problems understanding the details of the program's flow. > > - The code inside PARTITION_SUPPORT is supposed to be inactive with > MBR isohdpfx.bin. It belongs to isohybrid --partok which is equivalent > to MBRs isohdppx*.bin. Debian uses isohdpfx.bin. Yes. isohdpfx.bin is generated from isohdpfx.S in which PARTITION_SUPPORT is not defined. isohdppx.bin us generated from isohdppx.S which #defines PARTITION_SUPPORT to 1 and #includes isohdpfx.S. > - I am quite clueless what the code between "1:" in li...

Thomas Schmitt wrote: > So if we had a MBR which prints the content of the first 512 read bytes > we could tell whether they are block aligned and from which block they > come. Ok. I'll try. Is it the isohdppx or isohdpfx (or both) that is relevant? Meanwhile I have a hacked isohdppx.bin that prints: G if GPT M if MBR <nothing> if no partition info E if EBIOS C if not EBIOS (from "CHS"). For isohdpfx.bin it will print: E if EBIOS C if not EBIOS (from "CHS"). Is that interest...

...e dumping every iso image into its partition space on the USB disk I need to remaster it changing something on its initrd to be able to coexist with other linux distros on the same USB drive, - After that, I build a new remastered iso9660 file with mkisofs or xorriso, - If I use xorriso, I select isohdppx.bin as the MBR file. If I use mkisofs I need to postprocess the image with isohybrid --partok. The menu entry on syslinux.cfg for each partition is as simple as: Konsole output LABEL ZeroShell MENU LABEL ^ZeroShell COM32 boot/syslinux/c32/chain.c32 APPEND guid:xxxxx 5 So, I'm chainloading t...

...> 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 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 Their purpose is explained in the table at http://www.syslinux.org/wiki/index.php?title=Isohybrid#MBR_selection Have a nice day :) Thomas

...annot be written for that, and iso9660 fits the bill. Are examples known ? Up to now i have to stay quite vague in http://www.syslinux.org/wiki/index.php/Isohybrid#Images_prepared_with_--partok "==Images prepared with --partok== ISO images, which were prepared by --partok resp. with MBR isohdppx*.bin, have to be copied to a partition device. E.g. /dev/sdb1 rather than /dev/sdb. Such an ISO partition may then be booted by chainloading or by a suitable MBR at the start of the base disk device. " I hope this is at least not wrong. Whatever, it would not suffice for myself to really c...

...on 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 @@ -21,7 +21,8 @@ include $(MAKEDIR)/embedded.mk all: mbr.bin altmbr.bin gptmbr.bin isohdpfx.bin isohdppx.bin \ mbr_c.bin altmbr_c.bin gptmbr_c.bin isohdpfx_c.bin isohdppx_c.bin \ - mbr_f.bin altmbr_f.bin gptmbr_f.bin isohdpfx_f.bin isohdppx_f.bin + mbr_f.bin altmbr_f.bin gptmbr_f.bin isohdpfx_f.bin isohdppx_f.bin \ + isohdpfv.bin isohdppv.bin %.o: %.S $(CC) $(MAKEDEPS) $(SFLAGS) -Wa,-a=$*.lst -...

Hi, > The ISO will boot successfully (when chainloaded from grub) on 2 and > 3, but not on 5 and 6. Did you try with a boot loader other than GRUB ? Afaik, the MBRs of newly bought USB sticks often contain code which hops on the MBR code of the partition that is marked by the boot flag. At least one could exclude that your problem is in a GRUB peculiarity. Have a nice day :) Thomas

...syslinux itself) with the following files at least (found by git status in the gnu-efi submodule): gnu-efi-3.0/gnuefi/crt0-efi-ia32.o gnu-efi-3.0/lib/libefi.a After removing these and the bios, efi32 and efi64 subdirectories, the build failed ending with the following messages: [...] gcc -Wp,-MT,isohdppx_f.o,-MD,./.isohdppx_f.o.d -m32 -march=i386 -mpreferred-stack-boundary=2 -mincoming-stack-boundary=2 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -Os -fomit-frame-pointer -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables -fno-strict-aliasing -falign-functions=0 -falign-...

...yslinux-6.04-pre1-BROKEN/utils/Makefile 2016-03-04 17:24:16.387537657 +0100 @@ -28,17 +28,17 @@ ASIS = $(addprefix $(SRC)/,keytab-lilo TARGETS = $(C_TARGETS) $(SCRIPT_TARGETS) -ISOHDPFX = $(addprefix $(OBJ)/,../mbr/isohdpfx.bin ../mbr/isohdpfx_f.bin \ - ../mbr/isohdpfx_c.bin \ - ../mbr/isohdppx.bin ../mbr/isohdppx_f.bin ../mbr/isohdppx_c.bin) +ISOHDPFX = $(addprefix $(OBJ)/,../bios/mbr/isohdpfx.bin ../bios/mbr/isohdpfx_f.bin \ + ../bios/mbr/isohdpfx_c.bin \ + ../bios/mbr/isohdppx.bin ../bios/mbr/isohdppx_f.bin ../bios/mbr/isohdppx_c.bin) all: $(TARGETS) %.o: %.c $(CC) $(UMAK...

Hi, do we have bystanders who can read x86 assembler code or know easy-to-grasp reference docs? (I left machine code programming when i gave up using my VIC-20.) The MBR template isohdppx.bin stems from http://git.zytor.com/syslinux/syslinux.git/tree/mbr/isohdpfx.S with macro PARTITION_SUPPORT defined. One can see the error message text in there: bad_signature: call error .ascii "isolinux.bin missing or corrupt.\r\n" It seems to be reached only if the seen isolinux....

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 #defines active. Building them runs a check with checksize.pl that fails if they go beyond what's defined in checksiz...

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

Thomas Schmitt wrote: > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... ... > The diagnostic MBR should only use 432 bytes because at

...yslinux.git > > These changes fixed my issues (aside from the concurrency issue which > 2-3 passes solves for me). Now this shows me something I haven't ever seen. Build continuing in the background after the main process exits? wferi at lant:~/syslinux/genec$ make [...] gcc -Wp,-MT,isohdppx_f.o,-MD,./.isohdppx_f.o.d -m32 -march=i386 -mpreferred-stack-boundary=2 -mincoming-stack-boundary=2 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -Os -fomit-frame-pointer -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables -fno-strict-aliasing -falign-functions=0 -falign-...

Hi, The internal Gnu-EFI build gives me grief: * efi/check-gnu-efi.sh: uses realpath, which is not available on my Debian wheezy system. I now use readlink -f, but wonder if it's needed at all. * efi/build-gnu-efi.sh: uses realpath, like above, and also pushd/popd, which is not built into a standard Bourne shell invoked by #!/bin/sh. Again I wonder what's the point of it, as

Hi, i am trying to document the MBR selection by isohybrid option --partok. I assume it is related to "altmbr.bin" as described in http://www.syslinux.org/wiki/index.php/Mbr But there i read "altmbr.bin [...] boots from a partition with fixed number, see below." The "see below" probably refers to "The altmbr.bin (all 3 variants) is only 439 bytes long, -- one

> 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

On Fri, Jan 10, 2014 at 2:53 AM, Ferenc Wagner <wferi at niif.hu> wrote: > Gene Cumm <gene.cumm at gmail.com> writes: > >> On Sat, Jan 4, 2014 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Tue, Dec 17, 2013 at 8:39 AM, Ferenc Wagner <wferi at niif.hu> wrote: >>> >>>> * make spotless still fails after working around

...as reserved (core already does alignment) (Gene Cumm). * MEMDISK: Additional disk probe checks and debug output (Shao Miller, Gene Cumm). * gpxe: add gpxelinuxk.0, based off of undionly.kpxe + new script (Gene Cumm). * isohybrid: install the isohdpfx*.bin/isohdppx*.bin files to make isohybrid images in one step with GNU xorriso. * PXELINUX: disable a hack that would make localboot work on some machines, but break just about as many. Some machines which worked with "localboot 0" in previous versions may...

...mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25 dosutil/copybs.com 1 432 Sep 23 23:51 mbr/isohdpfx.bin 1 432 Sep 23 23:51 mbr/isohdpfx_c.bin 1 432 Sep 23 23:51 mbr/isohdpfx_f.bin 1 432 Sep 23 23:51 mbr/isohdppx.bin 1 432 Sep 23 23:51 mbr/isohdppx_c.bin 1 432 Sep 23 23:51 mbr/isohdppx_f.bin 1 439 Sep 23 23:51 mbr/altmbr.bin 1 439 Sep 23 23:51 mbr/altmbr_c.bin 1 439 Sep 23 23:51 mbr/altmbr_f.bin 1 440 Sep 23 23:51 mbr/gptmbr.bin 1 440 Sep 23 23:51 mbr/gptmbr_c.bin 1 440 Sep 23 23:51...