Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!decwrl!acornrc!asylum!romkey
From: romkey@asylum.UUCP (John Romkey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: new 3Com 3C505 card
Keywords: 3C505, device driver, PCIP
Message-ID: <951@asylum.UUCP>
Date: 5 Oct 88 07:35:48 GMT
References: <12996@cisunx.UUCP>
Reply-To: romkey@asylum.UUCP (John Romkey)
Organization: The Asylum; Belmont, CA
Lines: 25

In article <12996@cisunx.UUCP> dpl@cisunx.UUCP (David P. Lithgow) writes:
>	I have a 3Com 3C505 PC bus-to-ethernet adapter, which is the
>follow-on product to the venerable 3C501.

The 3C505 is actually almost as venerable as the 3C501. It was
intended not as a follow-on product but as an entry into a slightly
different market. The 3C505 is a smart board with an 80186 on it, and
you can download code to it or use it as a dumb board. It tends to run
like a dog (with one leg). It's a pain to use as either a smart or
dumb board, so there aren't lots of pieces of software that support
it. The only TCP/IP implementations for it that I can think of offhand
are NRC's Fusion and FTP Software's PC/TCP.

If you want *real* new 3COM boards, check out the 3C503 (real
successor to the 3C501) and 3C523 (Microchannel board). You can
probably get lower prices, better performance and wider software
support from the Western Digital WD8003 and Micom-Interlan NI5210,
though.
			- john romkey
UUCP: romkey@asylum.uucp		ARPA: romkey@xx.lcs.mit.edu
 ...!ames!acornrc!asylum!romkey		Telephone: (415) 594-9268