Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!ucsfcgl!cca.ucsf.edu!wet!epsilon
From: epsilon@wet.UUCP (Eric P. Scott)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: 3+Share + Packet Driver may not be "the way to go" but
Summary: Welcome to Academia
Message-ID: <471@wet.UUCP>
Date: 22 Aug 89 19:13:39 GMT
References: <1989Aug16.222938.608@geology.wisc.edu> <440@wet.UUCP> <728@east.East.Sun.COM>
Reply-To: epsilon@wet.UUCP (Eric P. Scott)
Organization: Wetware Diversions, San Francisco
Lines: 12

In article <728@east.East.Sun.COM> geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>                                                                In theory
>one could write such a driver as you describe, but you should be aware that
>according to 3Com NDIS is the way to go.

I'm not disputing this.  The fact is that we have 3+Share now,
and we're not going to yank it this close to the Fall term.
The mandate is to "just make it work."  Kludgy solutions are
fine--we'll only need this for a few months.  But we need it
soon.  Technical documentation?  What technical documentation?
I'm ready to disassemble the code.
					-=EPS=-