LANDD.SYS: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
DEVICE=LANDD.SYS | DEVICE=LANDD.SYS | ||
'''NOTE:''' By Jeff | '''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.) | ||
{| class="wikitable" | {| class="wikitable" | ||
|+Platform Support: | |||
|- | |- | ||
!OS/2 2.x | !OS/2 2.x | ||
Revision as of 15:50, 2 March 2018
LAN Manager's user device driver that provides services for MAC frame protocols.
DEVICE=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.)
| OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x |
|---|---|---|---|
| C | Yes | Yes |