Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!rex!ukma!usenet.ins.cwru.edu!eagle!news
From: xxseub@osprey.lerc.nasa.gov (Steven Eubanks)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: NDIS spec.
Keywords: NDIS, Ungermann-Bass
Message-ID: <1990Dec12.095614@osprey.lerc.nasa.gov>
Date: 12 Dec 90 15:16:50 GMT
References: <9012102013.AA10764@ftp.com> <18484@hydra.gatech.EDU>
Sender: news@eagle.lerc.nasa.gov (News Admin)
Reply-To: xxseub@osprey.lerc.nasa.gov (Steven Eubanks)
Organization: NASA Lewis Research Center
Lines: 32

In article <18484@hydra.gatech.EDU>, ce1zzes@prism.gatech.EDU (Eric
Sheppard) writes:
|> 
|> I'd like to add that Ungermann-Bass' last quote on the
|> yet-to-be-released
|> NDIS driver for their NIU (not NIC) cards is $395 for the TCP stack
|> version.  
. . .
|> We can't get non-UB cards to work with the UB-net software, we can't
|> get 
|> NIU cards to run NFS.  What a waste!
|>

Just a point of clarification:  I suspect that the $395 is for UB's TCP 
implementation (TCP for NDIS) which will run over their ($50) NDIS driver.  
You could purchase the UB NDIS driver for $50 and then go purchase
some other vendor's NDIS compliant TCP protocol stack which includes NFS, at 
that vendor's price.  That's the only way I've successfully run NFS on a
UB NIU.

The only advantage I could see in using 'TCP for NDIS' would be to preserve any
UB applications requiring their protocol stack by running 'TCP for NDIS'
over some
other vendor's NDIS compliant card/driver.  Theoretically speaking, of
course. :-)

Steve
-- 
Steven W. Eubanks,  EDS/LIMS			NASA Lewis Research Center
Internet:xxseub@osprey.lerc.nasa.gov		21000 Brookpark Rd. 
(216)433-8498					Cleveland, OH  44135
Disclaimer:  Opinions like mileage, may vary.