Xref: utzoo comp.protocols.tcp-ip.ibmpc:6077 comp.dcom.lans:8293
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!mips!pacbell.com!tandem!netcomsv!jbreeden
From: jbreeden@netcom.COM (John Breeden)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.dcom.lans
Subject: Re: LAN MANAGER Questions.
Message-ID: <1991Jun4.184540.12360@netcom.COM>
Date: 4 Jun 91 18:45:40 GMT
References: <1991May29.062359.29481@brolga.cc.uq.oz.au> <1991May29.151027.27342@ohsu.edu> <30582@hydra.gatech.EDU>
Organization: Netcom - Somewhere in the S.F. Bay Area
Lines: 42

In article <30582@hydra.gatech.EDU> qseclrb@prism.gatech.EDU (BOB BAGGERMAN) writes:
>Now the real reason I replied to this article (sorry, I always get carried 
>away).  I understand that DEC Pathworks 4.0 is based on LanMan 2.0 code.
>I think it is not a full LM 2.0 implementation but it has been implied that
>if the TCP/IP transport is chosen for both the VMS side and the PC side then
>LanMan 2.0 client can connect to VMS Pathworks 4.0 server.  I have not tried
>this but would love to hear from anyone who has.  I like the LanMan product
>and think for larger LANs it has some strong features.  It should be 
>interesting to see how the market responds to LM 2.0 especially the Unix
>ports of LM 2.0 which are now showing up.  I wonder if anything can slow
>the Novell juggernaut. 

Close. Acually DEC's Pathworks supports two different servers. The PathWorks
server for VMS is the same server that they used for PCSA (MS Network over
DECNet), so in that respect PathWorks is the same as PCSA when viewed from
services provided from a VMS/VAX box (MS Network over DECNet - resource
security only, no support for mailslots and named pipes (the 'stuff Lan
Man layers on top of SMB).

DEC also sells PathWorks for OS/2. This IS Lan Man 2.0 with DECnet as a 
transport. It also seems to imply that you could take the PathWorks/OS2
DECNet transport driver (decnet.os2?) and run it on an MS Lan Man server
giving you PathWorks via MS Lan Man (which is prob. the same as DEC's
OS/2 PathWorks - ie: they just repackage MS's Lan Man with a DECNet
transport.

The NDIS driver that DEC ships with PathWorks is an NDIS to DLL driver
(dll.dos & dll.os2). DECnet's transport runs on top of the dll driver.
It also means that you can run the OLD PCSA 'stuff on top of this
driver (PCSA over NDIS). The only gotcha you need to watch out for is
dll.dos and dll.os2 make the "optional" ndis "change hardware address"
call - not all NDIS MAC drivers support it at this time.

This was the state of PathWorks as of Networld Boston and comes from the
DEC engineers.
-- 
 John Robert Breeden, 
    jbreeden@netcom.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden
 -------------------------------------------------------------------
 "The nice thing about standards is that you have so many to choose 
  from. If you don't like any of them, you just wait for next year's 
  model."