Xref: utzoo comp.unix.i386:3661 comp.protocols.tcp-ip.ibmpc:2590 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!image.soe.clarkson.edu!news From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.unix.i386,comp.protocols.tcp-ip.ibmpc Subject: Re: Probs with WIN/TCP for 386 Streams on AT&T V/386 3.2.2 (LONG) Message-ID: Date: 22 Mar 90 04:53:18 GMT References: <3642@infmx.UUCP> <12706@ulysses.att.com> <3665@infmx.UUCP> Sender: news@sun.soe.clarkson.edu Reply-To: nelson@clutx.clarkson.edu Distribution: na Organization: Clarkson University, Potsdam NY Lines: 16 In-reply-to: aland@infmx.UUCP's message of 21 Mar 90 09:25:49 GMT In article <3665@infmx.UUCP> aland@infmx.UUCP (Dr. Scump) writes: As an alternative, does anybody know of any 16-bit ethernet cards that are supported by both Wollongong and Sun PC-NFS? It would be great if the AT&T cards worked with PC-NFS, but they don't, so I'm stuck. (Or, if the WD8003E can work with other available interrupts). You may wish to use the AT&T driver in the upcoming release 6.x of the packet drivers, along with Geoff's packet driver support for PC-NFS. Release 6.x will be out by the end of March... -russ -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) Russ.Nelson@$315.268.6667 Violence never solves problems, it just changes them into more subtle problems