Xref: utzoo comp.dcom.lans:1283 comp.sys.dec:643 comp.periphs:912 misc.wanted:2166
Path: utzoo!mnetor!uunet!husc6!purdue!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.dcom.lans,comp.sys.dec,comp.periphs,misc.wanted
Subject: Re: TCP/IP board for the BI bus?
Message-ID: <11278@mimsy.UUCP>
Date: 29 Apr 88 11:25:31 GMT
References: <876@pilchuck.Data-IO.COM> <465@tsc.dec.com>
Distribution: na
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 28

>In article <876@pilchuck.Data-IO.COM> tim@Data-IO.COM (The Daemon's Slave)
>writes:
>>   Does anyone know  of anybody that  has a TCP/IP  board, much like  the
>> Excelan product, that will work on the BI bus and is available today?

In article <465@tsc.dec.com> pete@tsc.dec.com (Pete Schmitt) writes:
>Digital's DEBNA will share TCP/IP and DECnet and has been available for
>some time

He said `like the Excelan product': a board with the TCP/IP code
*on the board*.  The DEBNA relies on the host for this.

And now that I have your attention ... WHERE does one get the
documentation for the BI Vax Port Network Interface?  I have the
register bits for the DEBNT, but still cannot use the two I have,
because I have no idea how to make them do anything useful.  All I know
how to do is point them to memory.  What goes in the memory?  And WHY
is buying documentation for DEC's hardware products from DEC so blasted
difficult?!  If you want to sell hardware, how about letting us know
how to program it, too?

DEC has come a long way from the original PDP series, and in the
matter of documentation, for the worse.  Just try buying MSCP
documentation (QP905-GZ, or whatever it is):  `Oops, we can't sell
that to you.'  `Why not?'  `Because it might be useful.'  Arrh.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris