Displaying 2 results from an estimated 2 matches for "com32_imag".
Did you mean:
com32_image
2014 Apr 23
2
*.c32 for efi64 and efi32?
...have
*.c32 for the COMBOOT files of BIOS,
*.e32 for the COMBOOT files of EFI32
*.e64 for the COMBOOT files of EFI64
As now the ldlinux file of syslinux 6.0x has, i.e.
ldlinux.c32: BIOS
ldlinux.e32: EFI IA32
ldlinux.e64: EFI X64
Because from the doc:
http://www.syslinux.org/wiki/index.php/SYSLINUX#COM32_image
it mentions:
.c32 COM32 image (32-bit COMBOOT)
Then it makes sense the *.c32 is for 32-bit. With EFI64, shall we have
different name for that?
With the different suffixes for 3 different architectures, we can put
all the COMBOOT files in the same tftp/ftp/http dir. Then these 2 issues
could be...
2014 Apr 23
0
*.c32 for efi64 and efi32?
...OMBOOT files of EFI64
> As now the ldlinux file of syslinux 6.0x has, i.e.
> ldlinux.c32: BIOS
> ldlinux.e32: EFI IA32
> ldlinux.e64: EFI X64
I recall a discussion on this but having difficulty finding it.
> Because from the doc:
> http://www.syslinux.org/wiki/index.php/SYSLINUX#COM32_image
> it mentions:
> .c32 COM32 image (32-bit COMBOOT)
> Then it makes sense the *.c32 is for 32-bit. With EFI64, shall we have different name for that?
> With the different suffixes for 3 different architectures, we can put all the COMBOOT files in the same tftp/ftp/http dir. T...