Installing MSDLC on Windows for Workgroup Version 3.11 (110059)


The information in this article applies to:

  • Microsoft LAN Manager 2.1
  • Microsoft LAN Manager 2.2
  • Microsoft Windows for Workgroups 3.11
This article was previously published under Q110059


SUMMARY

After you install MSDLC on Windows for Workgroups version 3.11, the following error message may appear during the startup process:
Protocol Manager could not be opened.
DLC Load failure.

MORE INFORMATION

MSDLC is an NDIS2-compliant protocol, which requires Protocol Manager in the memory before it can bind to the NDIS MAC (Medium Access Control) driver. If MSDLC doesn't find the Protocol Manager in the memory, the above error message appears.

In the AUTOEXEC.BAT make sure that Net Initialize or Net Init command comes before the MSDLC. Net Init command basically loads the Protocol Manager in the memory. The following is a sample AUTOEXEC.BAT that shows the correct load order: 
   C:\wfw311\net init
   C:\wfw31\msdlc
   C:\WFW31\net start
Or, do a NET START NETBIND before MSDLC.EXE and leave out the NET START: 
   C:\wfw311\net init
   C:\wfw311\net start netbind
   C:\wfw311\msdlc

REFERENCES

Windows for Workgroups Resource Kit
Modification Type:MajorLast Reviewed:10/23/2003
Keywords:KB110059
©2003 Microsoft Corporation. All rights reserved.