similar to: EDD error RE: Re: SYSLINUX 2.12-pre7 released

I have an application/program which shows 'bios EDD error' when using Isolinux (with either loading an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver,

>The way the El Torito CD-ROM is going to look like to the program, is >that it looks like an additional hard disk which a very high drive >number (typically 9Fh or so); MS-DOS will normally ignore this since it >asks the BIOS how many drives there are and ignores the rest. >Does the error message come from UDMA2.SYS or...? > -hpa yes, it comes from UDMA2.SYS, it does a

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cdrom ->

I'm running into some issues with regard to isolinux and memdisk, and am not sure where to ask/look in the best way possible. These are DOS-related issues. So here goes: * Can MEMDISK map a imagefile (compressed? harddisk?) to more than (and/or 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

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

Hi, i'm possibly not the best source of general SYSLINUX knowledge, as my interest in it is only with my xorriso hat on. (As you can see in the SYSLINUX wiki, xorriso can do the isohybridization without the need for the isohybrid program.) Fulalas Caos wrote: > I tried this: > mkisofs -o "$ISONAME" -v -l -J -joliet-long -R -D -A "$CDLABEL" \ > -V

>No, but you can write a comboot/com32 module to do it if you wish. I meant for syslinux.exe/com (the installer). that BIOS issue is now handled in the driver the author wrote. Unfortunately I can't find another cdrom which boots but lets me access A: to really demonstrate it's the BIOS which is doing this. Every non-emulation cdrom either uses isolinux (even ReactOS bootloader) or

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

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:

> Hi, > > Ady wrote: > > cdrtools.sourceforge.net/private/man/cdrtools-3.01axx/mkisofs.8.html > > Mac Boot entries for the Apple Mac platform. > > Interesting feature. But the El Torito specs of Phoenix and > IBM of 1994 state that "Mac" would be Platform Id 2. > http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf > Page

I posted this on the bugzilla page but I figured that on the mailing list it would get more attention. Please see http://bugzilla.syslinux.org/show_bug.cgi?id=49 for a description of my current issue. -- Thank you, Fernando Reyes GPG BDD75DD7 Mission Accomplish, Inc. http://missionaccomplish.com Email:design at missionaccomplish.com Tel: 7187100008 Cell: 3479275477

> Hi, > > Pascal wrote: > > mkisofs -o core.iso -b boot/core.img -c boot/boot.cat -hard-disk-boot core/ > > my iso image is ok with qemu on bios and uefi, > > Astounding. As CD-ROM this is not supposed 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

Hi all, I have merged Tim's patches to the mboot loader, and have pushed it out as 3.20-pre7. I guess I'm going to actually have to make a 3.20 here soon... -hpa

Hi all, I am at the end of my wits, after a day and a half of mucking around with this :) My intention was to take a multi-boot DVD - of the style you get with an MSDN subscription - and burn an individual installer to disc. How to do this? My theory was to take the files for the installation CD, add isolinux, add a bootsector, and away I go. Unfortunately it doesn't seem this easy. So I

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

hello every body, I'm trying to build an isohybrid image based on syslinux able to boot on bios and uefi with optical disk or usb key. I've build a 16Mb hard disk image (core.img) with necessary parts for bios (legacy bootable partition, protective mbr, gptmbr.bin & syslinux installation) and for uefi (gpt, esp, /efi/boot/bootx64.efi & syslinux files). my hard disk image is ok -

> Hi, > > > I don't understand why you say "*But* the El Torito...". I don't see > > a difference with what the mkisofs manual says. > > The manual announces "Mac" for Apple Mac. > The program obviously writes Platform Id 1 in this case. > The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac". > In the sum this

when you say """ Unfortunately, syslinux.efi v.6.03 is not capable of booting optical """, you talk about isolinux.bin ? because my iso image with a "good" alternate eltorito boot image (eg. "uefi ready") is booting with qemu (qemu -cdrom core.iso -bios uefi.fd) and is also booting in hard disk mode (qemu -hda core.iso -bios uefi.fd). Le mercredi

> Hello, > > Gene Cumm said on Thu, Oct 22, 2015 at 06:39:44PM -0400: > >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

> Hi, > > Ady wrote: > > This could be misinterpreted by some users as: "if > > you want to build an isohybrid image, then you cannot use > > 'syslinux.efi'". This would be incorrect. > > I don't know whether syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed