Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!mercury.twg.com!ljm
From: ljm@mercury.twg.com
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Use of Wollongong Win/TCP for DOS with AT&T StarLan 10 NAU
Message-ID: <9009191456.aa23603@Mercury.TWG.COM>
Date: 20 Sep 90 02:13:24 GMT
References: <SCEF0003@wsuvm1.csc.wsu.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 22


>Does anyone know whether the Wollongong Win/TCP for DOS software
>product will work with AT&T StarLAN 10 Network Access Unit or with
>the StarLan-10 EN100 Network Access Unit?...

>AT&T markets products which have the Wollongong copyright, but they
>may have purchased the source and made it work with their hardware.

AT&T markets our WIN/TCP for their UNIX machines, this is a very
different product (and source base) than our WIN/TCP for DOS.

>Wollongong is not sure if it will work.  They say that if the boards
>are NDIS compatable, then it will work.  Any experience or suggestions?

NDIS drivers definately exist and are tested for the StarLAN boards as
AT&T's Stargroup software is LAN Manager based.  Or, as Russ Nelson
suggested, you can use the Clarkson University StarLAN packet driver.

enjoy,
leo j mclaughlin iii
Manager of Microcomputer Networking
ljm@twg.com