search for: torito

Hi, i downloaded http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso Inspection by xorriso-1.3.8: xorriso -indev slint64-14.1_syslinux.6.03.iso \ -report_el_torito plain \ -report_system_area plain yields El Torito catalog : 46 1 El Torito cat path : /isolinux/isolinux.boot El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El Torito boot img : 1 BIOS y none 0x0000 0x00 4 22645 El Torito boot i...

Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El Torito boot img : 1 BIOS y none 0x0000 0x00 4 767 El Torito boot img : 2 UEFI y none 0x0000 0x00 2880...

Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso

On 10/11/2014 10:46, Thomas Schmitt wrote: > Hi, > > i downloaded > http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso > > Inspection by xorriso-1.3.8: > > xorriso -indev slint64-14.1_syslinux.6.03.iso \ > -report_el_torito plain \ > -report_system_area plain > > yields > > El Torito catalog : 46 1 > El Torito cat path : /isolinux/isolinux.boot > El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA > El Torito boot img : 1 BIOS y none 0x00...

> EFI from CD/DVD/BD has a soft size limit of 32 MB for its > System Partition. > That's due to the format of El Torito Boot Catalog which > counts the 512-bytes blocks by a 16-bit unsigned integer. @Thomas, If you would be so kind, would you please remind me (us)... Is this "32MiB" a limitation related to the UEFI specs in any way? Or is it relevant for BIOS (non-EFI) too? Is this limitation rela...

...64 Suffix="_syslinux.6.03" ( cd $SLINT mkisofs -o /tmp/slint${SFX}-${VERSION}${Suffix}.iso \ -rational-rock -J -A 'Slint hybrid installer ISO' \ -hide-rr-moved \ -v -d -N \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -b isolinux/isolinux.bin \ -c isolinux/isolinux.boot \ -eltorito-alt-boot -no-emul-boot -eltorito-platform 0xEF \ -eltorito-boot isolinux/efiboot.img \ -V 'Slint installer' . \ 2>>$TMP/log.txt ) ( cd /tmp md5sum slint${SFX}-${VERSION}${Suffix}.iso > slint${SFX}-${VERSION}${Suffix}.iso.md5 ) chown `stat -c %U:%G ${ROOT}` /tmp/slint${SFX}-${VE...

...mg \ > -isohybrid-gpt-basdat \ I tried that and got this, which is what was expected I think: xorriso 1.3.8 : RockRidge filesystem manipulator, libburnia project. xorriso : NOTE : Loading ISO image tree from LBA 0 xorriso : UPDATE : 34 nodes read in 1 seconds xorriso : NOTE : Detected El-Torito boot information which currently is set to be discarded Drive current: -indev '/tmp/slint64-14.1.iso' Media current: stdio file, overwriteable Media status : is written , is appendable Boot record : El Torito , MBR isohybrid cyl-align-on GPT APM Media summary: 1 session, 38912 data blocks...

...re even UEFI Macs which do not boot if GPT is present. See answer by Colin Watson in: http://askubuntu.com/questions/37999/what-is-different-about-the-mac-iso-image For the others, the most mac-ish ISOs are probably those of Fedora: - isolinux.bin ISOLINUX boot image for BIOS reachable by EL Torito and MBR code - efiboot.img FAT filesystem image for UEFI reachable by El Torito, MBR partition, GPT partition, APM partition - macboot.img HFS(Plus ?) filesystem image for some Macs reachable by El Torito, MBR partition, GPT partition, APM partition As one can see from the flaws, created by...

Hi, Ady wrote: > Is this "32MiB" a limitation related to the UEFI specs in any way? Or > is it relevant for BIOS (non-EFI) too? It comes from El Torito specs which are referred to by UEFI 2.4 specs. In EL Torito 1.0, Figures 3 and 5, "Sector Count" is a 2-byte "Word". So it can count up to 65535. Sector count gives the number of "virtual/emulated sectors". Paragraph 1.5. defines "Virtual Sector" as "200...

...oof instructions to build one ? I may have asked this already years ago. The long intervals between the discussions of this topic do not help me with keeping track. Whatever, now i have quite usable qemu-system-x86_64 and OVMF.fd of Debian 8. So i could pack a partition image into an ISO as EFI El Torito image and look whether it gives some signs of life as virtual CD-ROM. > At this point, some reader could interpret Peter's words as if this > situation could actually be successfully achieved. I explicitely asked him for clarification. Ping ? > I hope the current status would be...

hello i hope this is on topic here... i really need help and i'm guessing one of you will know the answer. i am trying to write software (open source) to work with cd images. the only thing i'm having trouble with is no-emulation 'el torito' boot records. i can't find any place where it sais how big the boot image is. bytes 8-0B of the initial/default entry say where to find it but how can i read it if i don't know the length? so my question is, what am i missing? i am intimately familiar with ecma119 (iso9660), jolie...

...aborting : -abort_on 'FAILURE' encountered 'FAILURE So the efi-boot option is not known. >In any case i would be interested to see what xorriso reports >about the boot equipment of your already existing ISO > > $xorriso -indev ...path.to.ISO... \ > -report_el_torito plain \ > -report_system_area plain \ > -print '' \ > -print '===== Proposed bootability options with -as mkisofs :' \ > -print '' \ > -report_el_torito as_mkisofs \ > -print '' >From a...

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

...ed to work with UEFI unless the > firmware emulates BIOS. What particular UEFI firmware did you use ? > > > and with qemu as hard disk on uefi but not on bios. > > That's even more astounding. The UEFI would have to look into the ISO 9660 > filesystem or interpret the El Torito boot info prepared for BIOS. I think that "in qemu as hard disk" means that he is not booting it as CD-ROM, so no iso9660 in this case; but I could be misinterpreting the words. > > > > isohybrid: core.iso: unexpected boot catalogue parameters > > That's b...

..."original" is the debian source package. > The "real" genisoimage (and any reincarnation of > it) might never work with Syslinux; who knows? It works fine for BIOS purposes, assisted by a run of isohybrid, if desired. The Debian version has no means to express other El Torito Platform Ids than number 0 ("80x86" as of El Torito 1.0). This is done by using option -b. > I cannot see any good reason to keep testing (Syslinux) with > "genisoimage". Bruno obviously uses genisoimage from Fedora or RedHat, which has options -e and -efi-boot. The ou...

...System Partition. The boot success with UEFI and -cdrom must have other reasons. I suspect the BIOS emulation of the firmware. About SYSLINUX EFI: Do we really have confirmed examples where SYSLINUX EFI software works from qemu DVD-ROM ? Decisive test would be to make an ISO which offers no El Torito boot image for BIOS, but only an EFI System Partition image as El Torito boot image for Platform Id 0xef. In that partiton image there would have to be SYSLINUX stuff - not GRUB or a directly bootable kernel. Why i doubt: When it comes to reading data, there should be no perceivable difference be...

> Hi, > > Ady wrote: > > Is this "32MiB" a limitation related to the UEFI specs in any way? Or > > is it relevant for BIOS (non-EFI) too? > > It comes from El Torito specs which are referred to by UEFI 2.4 > specs. In EL Torito 1.0, Figures 3 and 5, "Sector Count" is a 2-byte > "Word". So it can count up to 65535. > Sector count gives the number of "virtual/emulated sectors". > Paragraph 1.5. defines "Virtual Secto...

...my collection.) It boots to "Slint installer for Slackware64-14.1" by: qemu-system-x86_64 -enable-kvm -m 2048 \ -bios /usr/share/ovmf/OVMF.fd \ -hda slint64-14.1_syslinux.6.03.img So i make it passenger in an ISO where it is marked as EFI El Torito boot image: xorriso -as mkisofs -v -o slint64-14.1_syslinux.6.03_in.iso \ -e slint64-14.1_syslinux.6.03.img -no-emul-boot \ slint64-14.1_syslinux.6.03.img which yields this sparse boot equipment: El Torito catalog : 33 1 El Torito cat path : /boot.catalog El Torito...

Hi folks, I'm new to the list so forgive me if this topic has already been explained in great detail. I'm trying to understand how an image gets booted from an EL-TORITO compabatible CD-ROM, so I have some general questions: 1) Is there a limit of how big the boot image can be? In the Initial/Default entry I see a "Sector Count" which is only a word long in length. Does that mean I can only load boot binary (isolinux.bin) that is FFFF many sectors (a...

Hi, My problem is not uncommun, I have an old machine I'd like to use as a linux internet FW. The Bios is old and does not let me boot from an el torito bootable CD( 1998 PC) The CD's OK on other machines, boots fine Is there any way to get . isolinux on floppy, . when PC read floppy, isolinux tell it to boot from the /dev/hdc device, all bootfiles are in /isolinux on the CD (SENTRY-FIREWALL CD) I have looked around the net but didn...