Path: utzoo!attcan!uunet!image.soe.clarkson.edu!news From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: 386 UNIX tcp/ip connections to existing ethernets: examples desired Message-ID: Date: 22 Feb 90 16:41:05 GMT References: <3380@infmx.UUCP> <13318@cbnewsd.ATT.COM> Sender: news@sun.soe.clarkson.edu Reply-To: nelson@clutx.clarkson.edu Distribution: na Organization: Clarkson University, Potsdam NY Lines: 30 In-reply-to: cage@cbnewsd.ATT.COM's message of 21 Feb 90 16:07:53 GMT In article <13318@cbnewsd.ATT.COM> cage@cbnewsd.ATT.COM (charles.gerlach) writes: The AT&T Enhanced WIN/386 product supports AT&T's EN100 board along with the StarLAN 1 and StarLAN 10 NAU boards. Both 15-pin drop cable and BNC thin coax connections are available on the EN100. The NAU's are 1 and 10 MB twisted-pair boards respectively. Support for these boards is available only in the Enhanced WIN/386 package provided by AT&T. ... Through the generous donation of two StarLAN 10 NAU boards to Clarkson University, I'm writing a packet driver for them. And, if their documentation is to be belived, and I interpret it correctly, the packet driver will work on all the AT&T Ethernet and StarLAN boards, including their fiber optic thingamugizzie. Some people have disparaged the Clarkson packet drivers as being unreliable. Well, I can't make a driver reliable unless I have the hardware for it in house. If you are a hardware manufacturer, I encourage you to donate a pair of boards to Clarkson (care of myself). If you are a customer, I encourage you to contact manufacturers about the availability of packet drivers. Hardware manufacturers need you to tell them what software they need to make available. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) Russ.Nelson@$315.268.6667 Violence never solves problems, it just changes them into more subtle problems