LANDD.SYS: Difference between revisions

Latest revision as of 06:07, 12 April 2023

The Communications Manager LAN device driver must be loaded before:

TRNETDD.SYS - IBM Token-Ring device driver
PCNETDD.SYS - IBM PC Network device driver
ETHERDD.SYS - IBM ETHERAND device driver

The device driver provides services for MAC frame protocols.

DEVICE=x:\CMLIB\LANDD.SYS

NOTE: By Jeff Summer: Looking at the driver, it supplies the driver names \dev\LANDD$ and requires another device, \dev\protman$ to work. In my experience, in OS/2 it is strictly used for SNA, be that Anynet (NetBIOS over SNA/APPN) or simple Mainframe connectivity. It is also used to configure Bridges and LAM/CAU equipment. It does allow for some pretty cool stuff, like simple Token Ring utilization figures (a la Ringutil, IBM EWS, useless at full duplex, though) and Token-Ring Diags (last ring code, upstream neighbour, beaconing MAC, Ring Parameter Server reporting.)

@@ Line 1: / Line 1: @@
-LAN Manager's user device driver that provides services for MAC frame protocols.
+The Communications Manager LAN device driver must be loaded before:
- DEVICE=LANDD.SYS
+* [[TRNETDD.SYS]] - IBM Token-Ring device driver
+* [[PCNETDD.SYS]] - IBM PC Network device driver
+* [[ETHERDD.SYS]] - IBM ETHERAND device driver
-'''NOTE:''' By Jeff Summer: Looking at the driver, it supplies the driver names \dev\LANDD$ and requires another device, \dev\protman$ to work. In my experience, in OS/2 it is strictly used for SNA, be that Anynet (Netbios over SNA/APPN) or simple Mainframe connectivity. It is also used to configure Bridges and LAM/CAU equipment. It does allow for some pretty cool stuff, like simple Token Ring utilization figures (a la Ringutil, IBM EWS, useless at full duplex, though) and Token Ring Diags (last ring code, upstream neighbour, beaconing MAC, Ring Parameter Server reporting.)
+The device driver provides services for MAC frame protocols.
+ DEVICE=x:\CMLIB\LANDD.SYS
-{| class="wikitable"
+;NOTE: ''By Jeff Summer:'' Looking at the driver, it supplies the driver names \dev\LANDD$ and requires another device, \dev\protman$ to work. In my experience, in OS/2 it is strictly used for SNA, be that Anynet (NetBIOS over SNA/APPN) or simple Mainframe connectivity. It is also used to configure Bridges and LAM/CAU equipment. It does allow for some pretty cool stuff, like simple Token Ring utilization figures (a la Ringutil, IBM EWS, useless at full duplex, though) and Token-Ring Diags (last ring code, upstream neighbour, beaconing MAC, Ring Parameter Server reporting.)
-|+Platform Support:
-|-
-!OS/2 2.x
-!OS/2 3.0
-!OS/2 4.0
-!OS/2 4.5x
-|-
-|
-|C
-|Yes
-|Yes
-|}
 [[Category:DEVICE Statements]]