Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!AI.AI.MIT.EDU!PAP4
From: PAP4@AI.AI.MIT.EDU ("Philip A. Prindeville")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: 3COM 3c503 (Etherlink II) -- info needed.
Message-ID: <289267.871121.PAP4@AI.AI.MIT.EDU>
Date: Sat, 21-Nov-87 01:50:45 EST
Article-I.D.: AI.289267.871121.PAP4
Posted: Sat Nov 21 01:50:45 1987
Date-Received: Sun, 22-Nov-87 22:56:20 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16


    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 s