Xref: utzoo comp.unix.sysv386:4566 comp.unix.xenix.sco:1585 comp.dcom.lans:7153
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tiamat!jim
From: jim@tiamat.fsc.com (Jim O'Connor)
Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco,comp.dcom.lans
Subject: Re: Lan Manager/X
Message-ID: <788@tiamat.fsc.com>
Date: 4 Feb 91 16:22:40 GMT
References: <783@tiamat.fsc.com> <1991Jan27.220253.24498@actrix.gen.nz> <1393@pdxgate.UUCP>
Followup-To: comp.unix.sysv386,comp.unix.xenix.sco,comp.dcom.lans
Organization: Ahlstrom Filtration - Chattanooga,TN
Lines: 20

In article <1393@pdxgate.UUCP>, dmatlock@eecs.cs.pdx.edu (Delbert Matlock) writes:
> What's the word on interoperability between HP-LM/X, SCO-LM/X, and Microsoft
> LAN Manager (1.1 & 2.0)?  In particular, what will be the deal with protocol
> support?  3Com's NBP protocol easily allows for 521K of available memory on
> DOS workstations, so it would be nice to someday see something along the lines
> of an NBP protocol in LM/X.  With 3Com's recent change in direction I don't 
> know if this will ever be available now.

The docs for HP-LM/X said that you could use 3Com clients with it only after
3Com introduced a TCP/IP stack for their DOS client software (which was
supposedly in progress at the time - and is definitely available, since HP's
DOS client software uses it).  HP also sells an OS/2 server package which
has TCP/IP capabilities, so you can have HP-UX LM/X servers and OS/2 LM
servers talk to the same clients.

I haven't heard anything about SCO or Microsoft LM/X, but my guess is that
they'll also use TCP/IP, thus requiring TCP/IP capability in the DOS clients.
------------- 
James B. O'Connor			jim@tiamat.fsc.com
Ahlstrom Filtration, Inc.		615/821-4022 x. 651