Path: utzoo!attcan!uunet!fernwood!asylum!sharon From: sharon@asylum.SF.CA.US (Sharon Fisher) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: General/Philosphical Questions on PC/NOS's Message-ID: <4810@asylum.SF.CA.US> Date: 22 Sep 89 17:08:19 GMT References: <8909211705.AA16247@uhura.cc.rochester.edu> Reply-To: sharon@asylum.UUCP (Sharon Fisher) Organization: The Asylum; Belmont, CA Lines: 31 In article <8909211705.AA16247@uhura.cc.rochester.edu> mead@UHURA.CC.ROCHESTER.EDU (Ted Mead) writes: >2) What exactly is LAN Manager? What was the motivation for it's >development? My understanding is that it is another session through >application layer "standard" with hooks for OS/2. LAN Manager is for OS/2 (and eventually for Unix). The motivation for its development is that it takes advantage of OS/2 features, and so has more features and improved performance over DOS. >3) What is the relationship between SAA and LAN Manager? I see these as >conflicting architectures, yet IBM seems to be touting both? SAA is a much more global thing, composed of several sets of rules, protocols, and recommendations that allow users to develop applications that can be easily ported from one IBM family to another. IBM is not really 'touting' LAN Manager; it's touting OS/2 Extended Edition, a version of OS/2 with built-in communications and database capability. OS/2 EE incorporates some technology from the LAN Manager that IBM licensed from Microsoft. >4) Is there any reason why LAN Manager couldn't run on top of another >OS (UNIX, VMS, VM, MVS, ...)? Or is it tightly tied to OS/2? Work is underway by HP and Microsoft to do a Unix LAN Manager. I am not aware of any other implementations, but I don't know of any reason why there couldn't be. -- "Girl?! Don't you call *me* 'Girl'! I got a foot of cunt, a number two washtub full of tit, and enough hair on my pussy to weave an Indian blanket, and you call me 'Girl'??? paraphrased from "Texas Crude: The How-to on Talkin' Texan," by Ken Weaver.