Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!udel!gatech!hubcap!ncrcae!ncr-sd!sceard!mrm
From: mrm@sceard.Sceard.COM (M.R.Murphy)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Bootp and 3C501
Message-ID: <953@sceard.Sceard.COM>
Date: 10 Oct 89 15:39:13 GMT
References: <8910092133.AAsunic17654@sunic.sunet.se>
Reply-To: mrm@Sceard.COM (M.R.Murphy)
Organization: Sceard Systems, Inc.  San Marcos, CA  92069
Lines: 16

In article <8910092133.AAsunic17654@sunic.sunet.se> xjeldc@GEMINI.LDC.LU.SE (Jan Engvald LDC) writes:
[description of BOOTP problem with 3C501 deleted for brevity, the soul of wit]
>The reason for this behaviour was that I updated the bootptab file after
>each installation. For the first test bootp didn't have the ethernet address
>in RAM memory, so it had to read the updated file (takes a short while).
>From then on, all answers for that address was from RAM memory, and thus
>were fast and got lost in the 3C501.
>
>In summury: Use a modern Ethernet card (3C503, WD8003, NI5210, or the like).
>                                             
Or remove the update of the bootptab file after each installation. Or put a
delay in the server software so that existing hardware will continue to work.
Emphasis on "server" comes to mind:-)
--
Mike Murphy  Sceard Systems, Inc.  544 South Pacific St. San Marcos, CA  92069
mrm@Sceard.COM        {hp-sdd,nosc,ucsd,uunet}!sceard!mrm      +1 619 471 0655