search for: eltorito

Hi, > Unfortunately I get the error message: > isohybrid: slint64-14.1.iso: unable to find mac efi image This is probably due to El Torito Platform id "Mac" in -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ -eltorito-boot isolinux/macboot.img \ This caused in the image http://slint.fr/misc/MacBoot/slint64-14.1.iso platform id 1 with the third image. (I would have expected 2 from reading El Torito specs: 0=x86 , 1=PowerPC , 2=Mac. Shrug.) Regardle...

HI, In http://slint.fr/misc/MacBoot/ you'll find all context information. All files referenced here are stored there. Long story short: once dd-ed on an USB stick the ISO image can boot on a BIOS or EFI machine, but I want it to be able to boot on most x86_64 Macs with an EFI firmware. Unfortunately I get the error message: isohybrid: slint64-14.1.iso: unable to find mac efi image The

Good day to all. Since we've adopted Gary Tong's and Bart Lagerweij's ElTorito.sys (now modified by H. Peter Anvin and tiny changes from myself), I'd appreciate if anyone with more El Torito experience might criticize my comments below and advise as to how they might be wrong. Some of it is off-topic GRUB4DOS detail; safe to ignore. A bit of history: FDUBCD ("F...

...ck the resulting ISO image. Perhaps Didier can update his current version of mkisofs and retry with his current scripts/receipts. According to the subject of this email thread, we are talking about a "mac efi" anyway, so the platform ID should not be zero, nor 1, nor 2, and the '-eltorito-alt-boot -no-emul-boot -eltorito-platform Mac' is being misused. Regards, Ady.

...e for each firmware. I think they should be created only once (under the main txt/html/ directory), just as the rest of the documentation is. In that case, the <respective_firmware>/txt/html/ subdirectories should not even be created. _ The bios/dosutil/ directory contains copybs.com and eltorito.sys, while the efi32/ and efi64/ don't, which is expected. OTOH, mdiskchk.com is being created under the main dosutil/ directory. I think that 'mdiskchk.com' should be created under the bios/dosutil/ subdirectory, just as copybs.com and eltorito.sys are. I am unsure whether 'do...

...erhaps Didier can update his current version of mkisofs and retry > > with his current scripts/receipts. > > I will upgrade the cdrtools package from 3.01a17 to 3.01a24 in the > coming days and see what I come up with. If I understand well, I should > check that even with "-eltorito-platform Mac" in the mkiosfs command, > isohybrid doesn't complain any more, right? No. The "eltorito-platform Mac" option is meant for (old-ish) "Mac" hardware with BIOS firmware. If you want to boot current "Mac" hardware, which is using (some variant...

...ulting ISO image. > Perhaps Didier can update his current version of mkisofs and retry > with his current scripts/receipts. I will upgrade the cdrtools package from 3.01a17 to 3.01a24 in the coming days and see what I come up with. If I understand well, I should check that even with "-eltorito-platform Mac" in the mkiosfs command, isohybrid doesn't complain any more, right? If that works I could suggest to Parick Volkerding to upgrade the cdrtools Slackware package in Slackware-current (upcoming Slackware release). About mixing with Syslinux 6.03-pre19 (or newer) as suggested...

...beyond) 4GB of memory? Say you'd have 8/16GBGB and want 4GB available to the user so might as well use the other 4/12GB for MEMDISK. Or max 4GB due to 32bit memory/disk limitations in the module (or processor) ? * Is there a way to detect a system was booted (in non-emulation mode) through ELTORITO spec? MDISKCHK can detect the used loader(s), provided an instance of MEMDISK is found. Booting a CD, then chaining to floppy/HD from isolinux.cfg means not loading MEMDISK though. Basicly, I'd like to detect if ELTORITO.SYS should be loaded instead of awaiting its loading succes/failure. *...

Hi, I am trying to build a custom installer for a popular linux distro on MacOS. Here is how: makehybrid \ -o isos/muaaa.iso temp/ \ -eltorito-boot temp/isolinux/isolinux.bin \ -no-emul-boot \ -iso -joliet -boot-load-size 4 \ -default-volume-name "Custom Installer" \ -eltorito-platform temp/isolinux/boot.cat This happens when I boot up the new image: http://cl.ly/image/2p2p3H0F0t0z My question would be: where does sys...

...just as the rest of the documentation is. > > In that case, the <respective_firmware>/txt/html/ subdirectories > > should not even be created. Proper dep rules are the key. Building under only bios/ is a quick fix. > > _ The bios/dosutil/ directory contains copybs.com and eltorito.sys, > > while the efi32/ and efi64/ don't, which is expected. OTOH, > > mdiskchk.com is being created under the main dosutil/ directory. I > > think that 'mdiskchk.com' should be created under the bios/dosutil/ > > subdirectory, just as copybs.com and eltorito.s...

...-omit-version-number \ -relaxed-filenames -allow-lowercase \ -volid "${LABEL}" \ -appid "${APPLICATION}" \ -publisher "${PUBLISHER}" \ -preparer "prepared by mkmiso" \ -eltorito-boot isolinux/isolinux.bin \ -eltorito-catalog isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -isohybrid-mbr "${work_dir}/iso/isolinux/isohdpfx.bin" \ ${_iso_efi_boot_args} \ -output "${imgname}&...

> Hi, > > > Unfortunately I get the error message: > > isohybrid: slint64-14.1.iso: unable to find mac efi image > > This is probably due to El Torito Platform id "Mac" in > > -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ > -eltorito-boot isolinux/macboot.img \ > > This caused in the image > http://slint.fr/misc/MacBoot/slint64-14.1.iso > platform id 1 with the third image. (I would have expected 2 > from reading El Torito specs: 0=x86 , 1=Powe...

...with GPT and a FAT ESP (and legacy "MBR"), which then can be used to boot either/both BIOS systems or UEFI systems. The possibility to perform #B/#C/#D/#E (in addition to #A) depends on the content of the isohybrid image and the parameters used by mkisofs (or equivalent). One hint: -eltorito-alt-boot -no-emul-boot -eltorito-platform 0xEF \ -eltorito-boot EFI/BOOT/BOOTX64.EFI (not "-eltorito-boot isolinux/efiboot.img", which is not used by Syslinux). where BOOTX64.EFI comes from (a.k.a. "is a simple copy of"): syslinux-6.03/efi64/efi/syslinux.efi. I am not goin...

.../micro/pc-stuff/freedos/files/distributions/beta9sr1/fdos1440.img That's nice to boot cdroms. There's no way to boot ISOs (yet?). A Linux floppy with kernel+initrd should be able to mount an ISO or ZISOFS file (Knoppix does this for example) To my knowledge, no one has extracted SBM's eltorito stack yet. It would have been usefull as payload for a project like LinuxBIOS for example, especially now that they have VGA BIOS working properly. Welcome to an opensource BIOS :) To promote a FreeDOS component a bit more: the SYS program, also maintained by that same member, is able to transfer...

I just merged a version of the eltorito.sys sources, reconstructed by Eric Auer to match the 1.4 binary and then converted to NASM by NoMySo, to the Syslinux repository; I would greatly appreciate if people would test it to make sure it didn't break in conversion. -hpa

...function: 1. Support the DL=0x7F "terminate all" parameter 2. Only respond to DL=0x7F or DL=our particular emulated drive number This prevents tools like Bart Lagerweij's El Torito tools from receiving false positives when probing all drive numbers. --- eltorito: Include drive 0xFF in scan Although drive 0xFF could yield a false positive as the El Torito booted-from drive number, some users of GRUB4DOS actually use this drive number, so we should include it in our scan. --- - Shao Miller [1] http://git.zytor.com/?p=users/sha0/sys...

Hi, On 11/11/2014 02:55, Ady wrote: > Again, dd'ing your isohybrid image onto your (virtual or real) drive > will fail to boot in EFI mode. Your "syslinux.efi-based" > "/isolinux/efiboot.img" will not be capable of booting. This is one > of the steps that corresponds to grub2, not to whichever other EFI > bootloader you use (e.g. syslinux.efi). So,

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks (as the DOS kernel enumerates them) or using the NOPASSANY parameter for MEMDISK. Different...

On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 > confs) stored on a iso9660 media by genisoimage and its > -eltorito-alt-boot -efi-boot $imagefile -no-emul-boot option doesn't > work. I get a red screen with debug info (attached). However, I'm not > trying to access anything outside of the FAT32 FS. I thought it > wouldn't be related to iso9660 in that use case. (I use wirtual media &gt...

...ber \ > -relaxed-filenames -allow-lowercase \ > -volid "${LABEL}" \ > -appid "${APPLICATION}" \ > -publisher "${PUBLISHER}" \ > -preparer "prepared by mkmiso" \ > -eltorito-boot isolinux/isolinux.bin \ > -eltorito-catalog isolinux/boot.cat \ > -no-emul-boot -boot-load-size 4 -boot-info-table \ > -isohybrid-mbr "${work_dir}/iso/isolinux/isohdpfx.bin" \ > ${_iso_efi_boot_args} \ >...