Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!husc6!spdcc!ftp!jbvb
From: jbvb@ftp.COM (James Van Bokkelen)
Newsgroups: comp.dcom.lans
Subject: Re: LanManager Questions
Summary: DOS LAN Manager is MS/Net descendant
Message-ID: <687@ftp.COM>
Date: 23 Jun 89 13:36:32 GMT
References: <127000005@tippy>
Organization: FTP Software Inc., Cambridge, MA
Lines: 24

In article <127000005@tippy>, wvanbeek@tippy.uucp writes:
> 
> Does anyone have any personal experience with Microsoft's LanManager
> in the contect of a replacement for Novell.  A little information.
> ....
> The questions that I have are (1) what about DOS client RAM requirements,
> (2) services available, (3) any severe anomolies?

DOS LAN Manager is a direct descendant of MS/Net, uses the same SMB
protocol, and makes the same class of calls to a NETBIOS of some sort.
The major difference I know of is that it is loaded via the Protocol
Manager defined under the 3Com/Microsoft NDIS spec.  I would expect
that RAM requirements and features would closely resemble those of
MS/Net, but I don't know for sure (we don't use it in-house).  3Com's
3+/Open is an example of an OEM version of it, using an XNS transport
layer.  The major problem with the versions I've seen so far is the
Protocol Manager, which doesn't.  It is supposed to allow more than
one protocol stack (e.g XNS and TCP/IP) to share a single NDIS driver
and a single interface card, but at the moment it only works for one
stack at a time.

-- 
James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901