This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFEDA5.2CA50624 Content-Type: text/plain; charset="iso-8859-1" On Fri, 14 Jul 2000, Alan Garrison wrote: >>With the NIC problem I've been having, I was trying to >>come up with an alternate solution (short of replacing >>the $25 Tulip-based card with a $75 3com). I assume > >Gack! $35 Intel Inbusiness adaptor is what I'd suggest :) (not >the digital chips manuf'ed by Intel either) My favorites are the 3coms.. I've got a bunch of 3c509s and 590/905's. The PNP ISA versions are software programmable so I can always work around conflicts without dealing with jumpers or buggy PNP BIOSes. That, and you can find the 509s for around $5 ea. ------_=_NextPart_001_01BFEDA5.2CA50624 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">RE: Prolly a silly question, but... On Fri, 14 Jul 2000, Alan Garrison wrote:
>>With the NIC problem I've been having, I was = trying to
>>come up with an alternate solution (short of = replacing
>>the $25 Tulip-based card with a $75 = 3com). I assume
>
>Gack! $35 Intel Inbusiness adaptor is what = I'd suggest :) (not >the digital chips manuf'ed by Intel = either)My = favorites are the 3coms.. I've got a bunch of 3c509s and = 590/905's. The PNP ISA versions are software programmable so I = can always work around conflicts without dealing with jumpers or buggy = PNP BIOSes. That, and you can find the 509s for around $5 = ea.
------_=_NextPart_001_01BFEDA5.2CA50624--