Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!netsys!lamc!wet!epsilon From: epsilon@wet.UUCP (Eric P. Scott) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: 3Com 3C523 lockup problem with PS II 70/80's. Summary: 3+ wanting the Ethernet interface all to itself? Message-ID: <440@wet.UUCP> Date: 18 Aug 89 10:12:45 GMT References: <1989Aug16.222938.608@geology.wisc.edu> Reply-To: epsilon@wet.UUCP (Eric P. Scott) Organization: Wetware Diversions, San Francisco Lines: 20 In article <1989Aug16.222938.608@geology.wisc.edu> ben@geology.wisc.edu (Ben Abernathy) writes: >The computers lockup and require rebooting especially when using >the NSCA V2.2 telnet program. We are using the 3Com eth523.sys driver >and DOS 3.3 and DOS 4.01. Is 3Com software going to coexist with NCSA? Here's my fantasy: a 3+ driver that "looks like" a FTP 1.08 packet driver--I don't want to run 3+ over a standard packet driver, I want a driver that makes 3+Share happy, but will pass IP, ARP, RARP and trailer types to anything that wants them. It has to be free, and freely redistributable. I don't have access to 3+ technical documentation, and yes, I've been told to flush 3Com in favor of Novell. I need support for 3C501, 3C503, 3C505, and 3C523. I understand that PC-NFS will coexist with 3+; if so, how did Sun pull this off? Geoff? -=EPS=-