Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ames!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrcae!cs-col!vause From: vause@cs-col.Columbia.NCR.COM (Sam Vause, NCR Corporate Customer Services) Newsgroups: comp.sys.ncr Subject: Re: Streams and TLI (again, sorry) Message-ID: <1990Mar22.193114.7405@cs-col.Columbia.NCR.COM> Date: 22 Mar 90 19:31:14 GMT References: <3018@uwm.edu> Reply-To: vause@cs-col.Columbia.NCR.COM (PUT YOUR NAME HERE) Organization: Corporate Customer Services NCR E&M Columbia, SC Lines: 30 In article <3018@uwm.edu> andrew@csd4.csd.uwm.edu (Andy Biewer) writes: >This article refers to Streams and TLI on a Tower running SysVR3. > >I posted earlier about this topic, and got many excellent >replies, thanks. However, in looking through my systems /dev >directory, I find nothing that looks anything close to a network >clone (as someone put it), such as /dev/net, or /dev/tcp, >/dev/ip, /dev/osi_cots, etc... This poses serious problems in >using t_open, although the manual pages say, "SUPPORT STATUS: >Supported". Could it be possible that this was never implemented >on this system? And, if so, how would one go about installing >it? Well, the only way that I know of is for you to install a copy of the WIN-TCP/IP LAN Networking product. It does install the TLI interfaces. At first glance, this arrangement may seem to be slightly unusual. However, the intent was to allow the TLI code to be maintained by the network development groups that actually used it for products; therefore, it was removed from the OS distribution. --sam +---------------------------------------------------------------+ |Sam Vause, NCR Corporation, Customer Services - TOWER Support | |3325 Platt Springs Road, West Columbia, SC 29169 (803) 791-6953| | vause@cs-col.Columbia.NCR.COM | | ...!uunet!ncrlnk!ncrcae!cs-col!vause | | ...!ucbvax!sdcsvax!ncr-sd!ncrcae!cs-col!vause | +---------------------------------------------------------------+