search for: jorver

...me syntax and protocol? Or is there a "lsyslinux.efi" equiv? I'm sure Gene or Ady will know the answer. > Also why was I calling it PXE 3? Well the cards say they are version 3 when you look at the network analyzer and this is from the EFI SPEC. > > "Type (1), Ma > jorVer (1), MinorVer (1) > Type is a one byte field that i > dentifies the network > interface that > will be used by the downloaded program. Type is followed by two > one byte version number fields, MajorVer and MinorVer. > Type > UNDI (1) = 0x01 > Versions > WfM-1.1a 16-bit UN...

...ng them using wimboot from ipxe (that works still with PXELinux) - only I only got it working so far with tftp that makes no difference ;) Also why was I calling it PXE 3? Well the cards say they are version 3 when you look at the network analyzer and this is from the EFI SPEC. "Type (1), Ma jorVer (1), MinorVer (1) Type is a one byte field that i dentifies the network interface that will be used by the downloaded program. Type is followed by two one byte version number fields, MajorVer and MinorVer. Type UNDI (1) = 0x01 Versions WfM-1.1a 16-bit UNDI: MajorVer = 0x02. MinorVer = 0x00 PXE-2.0...

On Mon, Dec 29, 2014 at 04:15:56AM -0800, Patrick Masotta wrote: > On Mon, Dec 29, 2014 at 08:47:54AM +0100, Luke Ledgerd wrote: > > I think I'd like to ask for a feature request to allow pxechn.c32 > > to work with EFI too and to have the ability for PXELinux to have a > > ROOT path variable (kind of like gpxelinux.0) that can either have > > HTTP or TFTP urls.