Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!erb1!wittmann From: wittmann@erb1.engr.wisc.edu (art wittmann) Newsgroups: comp.dcom.lans Subject: Re: Please boycott Xircom Message-ID: <269@erb1.engr.wisc.edu> Date: 8 Oct 90 17:37:06 GMT References: <1990Sep26.145651.24708@daver.bungi.com> <1990Sep28.192413.21255@ism.isc.com> <27414@usc.edu> Reply-To: wittmann@erb1.UUCP (art wittmann) Organization: Computer Aided Engineering Center-University of Wisconsin-Madison Lines: 30 In article <27414@usc.edu> dra@neuro.usc.edu (Diane Annala) writes: >In article nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) writes: ># >#You can bet your bippy I'm going to go over your "independently developed" >#packet driver with a fine-toothed comb. > >Of course, Xircom could include a provision in their copyright notice >forbidding nelson@image.clarkson.edu from disassembling, decompiling, >or otherwise going over the new packet driver with a fine toothed comb. I doubt Russ will take my word for this, but I do know the folks that wrote the replacement driver for Xircom. The company that did the work (as far as I understand) is Persoft here in Madison. They've been using the generic FTP spec, but not Mr. Nelson's shell. Although I'm less sure of this, I believe they also wrote the Dlink driver. They've written drivers for a number of other boards as well. I understand that they perform quite well. I bring it up only to hopefully save Russ the time of checking over the new Xircom driver. I in no way feel that what Xircom did was appropriate. Respecting the intellectual property of others is a fundamental precept in this biz. Art =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Art Wittmann Phone: (608) 263-1748 Network Manager Email: wittmann@engr.wisc.edu Computer Aided Engineering Center or: wittmann@cae.wisc.edu University of Wisconsin, Madison