pickens%ics@SDCSVAX.UCSD.EDU.UUCP (11/18/87)
I'm in the process of rewriting the CMU PC/IP 3c501 code
for the newer 3c503 card.
I would appreciate any pointers to information on any of the
following:
<1> Existing PC/IP code ("srclib/3com") for the 3c503.
<2> Technical (programming) documentation on both the 3c501
& 3c503. Or on the primary chips on these cards.
<3> Any prior discussion on this mailing list about the
differences between the two boards.
You can reach me by replying to this message
("pickens@sdics.ucsd.edu") or by calling me
collect (after 9:30am PST).
Thanks!
Larry West
CliniComp International (clinical computer systems)
619-456-0361romkey@ftp.UUCP (John Romkey) (11/19/87)
The 3C503 uses the National Semiconductor DP8390 Ethernet controller chip; the 3C501 uses something completely different - it's been long enough that I can't remember what the chip is even called. I think it's the LANCE chip. I try to forget as much about writing my 3C501 driver as I can. If you send me your US Mail address I can send you a document about programming the 3C501, but it won't help any in dealing with the 3C503. The two boards are completely different. You can get specs on the DP8390 from your local National distributor, but you'll need more than that to program the 3C503. You may be able to get technical specs on the 3C503 from your 3COM rep, under non-disclosure. FTP Software has a 3C503 version of PC/TCP (our commercial PC/IP) in beta test now, and if the stuff we got from 3COM isn't under non-disclosure, I can give you a copy of that, too. I don't know of any 3C503 drivers that are available as part of the publically available PC/IP. - john romkey ftp software
jac@UMD5.UMD.EDU.UUCP (11/19/87)
3Com's vector interface is to be published soon. The "vectorized" version of their 3+ system is not expected until end 1Q '88. One would have to wait until then to co-reside with 3+. Until that time, 3Com does have a subset spec called 3L. One can write to this specification in order to support the 3c503, 3c523 and TokenLink cards. This specification and the 3L libraries for the above mentioned cards are currently available (3c523 library may be available shortly). On the original question (programming the 3c503) the following may be of interest: The board uses the National Semiconductor DP839x chipset, see the "Advanced Peripherals, IEEE 802.3, Local Area Network Guide" by National. Interface to the PC bus is through a 3Com gate array, see them for programming info. /joe ------------------------------ Joseph A. Cimmino, Jr. University of Maryland, Systems jac@umd5.umd.edu 1+ 301 454 2946 PC/IP Group cimminoj@umdd.bitnet Bertolt Brecht: You made your bed, so you lie in it.
jbvb@ftp.UUCP (James Van Bokkelen) (11/19/87)
I have a driver I wrote myself in beta test. I am not deeply impressed with the "3L" interface: 1. It has a lot of bells and whistles I didn't need. 2. If you want to use it out of the box, you have to live with the fact that it is designed for a TSR LAN program, and tries to parse command-line arguments on startup. 3. It is all 3Com copyrighted code, even though they supply source. If permission to redistribute it is available, I haven't seen it. 4. It doesn't buy you hardware-independence at the .EXE level - you have to link in a specific driver for one board or another. We are eagerly awaiting the "vector" interface, but the spec hasn't appeared, even under non-disclosure. The 8390 chip has some bugs, which show up in some other cards at high data rates, or only at Starlan clock speeds. Possibly because of the gate array, these bugs show up full-blown during normal use of the 3C503. My advice to the punter is: Reset it thoroughly every time it does something suspicious, and start with a production card (the sticker on it had better not say "IE6PTYP..."). I have actually seen a programming manual for the 3C501, but it is a true fossil, having been given to MIT back when the original PCIP was being developed. I believe that current versions are not at all easy to obtain, nor have I seen a "3L" for the Etherlink. James B. VanBokkelen FTP Software Inc.
PAP4@AI.AI.MIT.EDU ("Philip A. Prindeville") (11/21/87)
You can get specs on the DP8390 from your local National distributor,
but you'll need more than that to program the 3C503. You may be able
to get technical specs on the 3C503 from your 3COM rep, under
non-disclosure. FTP Software has a 3C503 version of PC/TCP (our
commercial PC/IP) in beta test now, and if the stuff we got from 3COM
isn't under non-disclosure, I can give you a copy of that, too.
It's not at all apparent to me why an interface manufacturer would not
want to disclose how to program their interfaces: the hardware
that sells the most is usually the that has the most software available.
Now unless 3com is in the software biz, what are they up to? It's nuts.
Maybe I'm missing something obvious...
OUT LL spickens%ics@SDCSVAX.UCSD.EDU (Larry West {619-456-0361} courtesy of Karen Pickens) (11/23/87)
| It's not at all apparent to me why an interface manufacturer would not | want to disclose how to program their interfaces: the hardware | that sells the most is usually the that has the most software available. | Now unless 3com is in the software biz, what are they up to? It's nuts. | | Maybe I'm missing something obvious... | | -Philip I think the key is that 3Com is selling a "Developer's Kit" for writing software for the 3c503. This includes assembly code for {some part of?} their "Link Level Library" interface, a technical manual, and 5 hours of consultation. The assembly code is well-commented, but of course suffers from all the problems of assembly code. And what I've seen was incomplete and aimed for a "MINDS/XNS" implementation. But what I saw is 6 months out of date, so take that with a grain of salt. Oh, the price is $995. As far as I could find out, there was no way to buy just the technical manual. But then I made only a dozen phone calls to 3com, so if you're not as impatient as me, you might be able to get more help. Larry West CliniComp International temporarily: pickens@sdics.ucsd.edu 619-456-0361
hlison@bbn.com (Herb Lison) (04/11/88)
I'm interested in using the public domain TCP/IP software developed at the National Center for SuperComputing Applications. I've been unable to contact people at the center via mail, so perhaps people on this board might know if the package contains a driver for the 3COM 3C503 Ethernet board, also known as the Etherlink II. Has anyone developed a driver for this board, compatible with the NCSA software? Thanks in advance. Herb Lison