<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <div class="moz-signature">_______________________________ Do you GNU!? <a href="http://www.gnu.org/">Microsoft Free since 2003</a>--the ultimate antivirus protection! </div> Terrell Prudé Jr. wrote: <blockquote cite="mid46D43CFF.6000108@cmosnetworks.com" type="cite"> <pre wrap="">Mel Wade wrote: </pre> <blockquote type="cite"> <pre wrap="">I have some Intel and 3com cards with PXE boot capabilities. I have flashed the cards with the lastest firmware, but get PXE-E20 errors when it tries to boot. I've googled, but can't seem to find a solution.... I have other thin clients booting on the system so I know that part is working. </pre> </blockquote> <pre wrap="">Just did some preliminary Googling, too. From what I read of that error code, the BIOS is returning an error code trying to copy the NIC's boot image into "extended memory" and that this error should "never" (haha) happen. What happens if you take those NIC's and try them in a totally different computer? Any change? The only other possibility that quickly comes to mind is the 15-16MB memory "hole" that some BIOS's allow you to set. This is totally a guess, but maybe that NIC's trying to write into that memory hole, and it can't? I note that the error code speaks of a problem with writing to extended memory. --TP</pre> </blockquote> Another thing I've seen some people report is that the PC's BIOS itself might need updating. I know from experience that buggy BIOS's can be a problem for Dell OptiPlex GX1's when you try to PXE-boot them (recent BIOS versions do fix this). --TP </body> </html>