Re: multiple UNDI NICs in VMWare ESX 3.5 cause gPXEDHCP to fail on 1st NIC
Michael Brown <[email protected]>
| Newsgroups | gmane.network.etherboot.user |
|---|---|
| Message-ID | <[email protected]> |
On Thursday 06 August 2009 17:49:23 Bill Lortz wrote: > I'd like some clarification on the difference between building a image > with .kpxe vs .pxe as an extension. I have been building the other > chainloaded gPXE images for the PCNET32 and E1000 drivers with a .pxe > extension. .kpxe is "keep PXE". If you're intending to use the PXE stack that was used to load gPXE, you probably want a .kpxe image. If you're intending to replace the PXE stack that was used to load gPXE, you probably want a .pxe image. In practice, this means that you use bin/undionly.kpxe and bin/anything-except-undionly.pxe Michael ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july