search for: _soft_

...t;emulation" methods/types (01/02/03)? Is this limitation also valid / relevant for the first/default entry in the Boot Catalog? Or is it only relevant for the second+ entries (i.e. the non-default entries in the boot catalog)? Would you please clarify the meaning of your qualifier, "_soft_ size limit"? TIA, Ady.

...Is this limitation also valid / relevant for the first/default entry in > the Boot Catalog? All entries which describe a boot image have that field of 2 bytes. (There are also header entries which describe catalog sections.) > Would you please clarify the meaning of your qualifier, "_soft_ size > limit"? The option to write size 0 or 1 is a fallback, which gives up the goal to exactly mark the end of the EFI System Partition. So i consider it preferrable to be able to express the true partition size, which is possible only with FAT images below 32 MiB. Whether the "up...

> Hello, > > Ady via Syslinux said on Mon, Apr 06, 2015 at 09:57:02PM +0300: > >Can 'syslinux.efi' v.6.03 boot some media formatted with ISO9660? > > Not at this time, no. > > It took me quite some time to find that :-( Google didn't really help. > > I'd like to get a bit more details on this issue: > > 1/ Using syslinux.efi for PXE

...levant for the first/default entry in > > the Boot Catalog? > > All entries which describe a boot image have that field of 2 bytes. > (There are also header entries which describe catalog sections.) > > > > Would you please clarify the meaning of your qualifier, "_soft_ size > > limit"? > > The option to write size 0 or 1 is a fallback, which gives up > the goal to exactly mark the end of the EFI System Partition. > So i consider it preferrable to be able to express the true > partition size, which is possible only with FAT images below...