ODIHLP.EXE Load Error Messages

 Last reviewed: November 21, 1994
Article ID: Q108700
The information in this article applies to:
  • Microsoft Windows for Workgroups version 3.11

SYMPTOMS

This article lists error messages generated by ODIHLP.EXE when it is loaded out of sequence.

  • The ODIHLP.EXE may produce the following error message if it is loaded before the link support layer (LSL.COM): 

          ERROR:  cannot load LSL
      ODI/NDIS3 Mapper:  Initialization failure
      Press any key to continue

  • The ODIHLP.EXE file may produce the following error message if it is loaded after LSL.COM and before the multiple link interface driver (MLID): 

          ERROR:  not bound to any boards
      ODI/NDIS3 Mapper:  Initialization failure
      Press any key to continue

In both the above scenarios, when you start Windows for Workgroups 3.11, a text-based and a Windows-based error message appear:

The following text-based error message appears when the SYSTEM.INI file is read: 

      ERROR:      MSODISUP failed to load.
      ODIHLP.EXE must be loaded before starting Windows,
      ODIHLP.EXE should be loaded in AUTOEXEC.BAT after LSL.COM
      Cannot load a device that is specified in SYSTEM.INI.

      The performance of Windows should not be affected without this file.
      C:\WINDOWS\SYSTEM\MSODISUP.386
      Press a key to continue
The Windows-based STOP error message that appears is: 

      Networking functionality will not be available. Your network adapter
      or protocols may not be configured properly. Run Network Setup to
      check adapter and protocol settings.

RESOLUTION

To avoid these errors, ODIHLP.EXE must be loaded after LSL.COM and the MLID.

MORE INFORMATION

ODIHLP.EXE is the real-mode component that allows LSL to complete its binding process in real mode (similar to NDISHLP.SYS). This file hooks all the real-mode entry points so that MSODISUP.386 can use this information when working in protected mode.

ODIHLP.EXE acts as a default stack for all frame types (that is, ODIHLP accepts any packet that is of one of the frame types listed in the NET.CFG file.

KBCategory: kbnetwork kberrmsg kb3rdparty
KBSubcategory: wfw wfwg
Additional reference words: 3.11

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 21, 1994
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.