[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: tftp protocol
It could be either/or.
The way PXE works, it starts out purely as a BIOS thing that searches for a
network server and does a tftp pull for a bootstrap executable. The bootstrap
executable MAY use the PXE BIOS network stack and NIC driver, or may provide
it's own, then pull further executables, file system images, etc. Generally,
that first executable will use the PXE BIOS resources to remain platform
It doesn't hurt to look for BIOS updates and errata just to ensure it is a
vista issue. If the NIC is an on board model, then the PC manuf should have
updated BIOS available. If the NIC is a PCI add on, then the PXE network
extensions are in the BIOS of the NIC card itself. Replacing the NIV card with
another PXE capable brand would suffice, or maybe the NIC card manuf has a
Let us know how you come out.
--- On Tue, 10/13/09, Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:
> From: Patrick Welche <prlw1%cam.ac.uk@localhost>
> Subject: Re: tftp protocol
> To: jscottkasten%yahoo.com@localhost
> Cc: tech-net%netbsd.org@localhost
> Date: Tuesday, October 13, 2009, 7:10 AM
> On Tue, Oct 13, 2009 at 07:02:41AM
> -0700, jscottkasten%yahoo.com@localhost
> > If it is PXE boot, then it's likely a BIOS
> thing. Perhaps you can find
> > a BIOS update for the hardware?
> I think it is more likely to be one of the "Windows AIK"
> files. One of
> pxeboot.n12, bootmgr.exe, boot.sdi - the trouble happens
> while the .wim
> file is being transfered - I assume that it is one of them
> that is making
> the read request?
Main Index |
Thread Index |