1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Boot Problem: Error loading device driver MDISHLP.SYS

Discussion in 'Legacy Windows' started by Welt, 2003/08/28.

Thread Status:
Not open for further replies.
  1. 2003/08/28
    Welt

    Welt Inactive Thread Starter

    Joined:
    2002/02/19
    Messages:
    196
    Likes Received:
    0
    Hello

    If I've already posted the following message, I ask your indulgence. I wrote it. I thought I'd posted it but I cannot find it anywhere. Regardless, here goes:

    A friend of mine has a Dell 800 MHz system with Win 98SE loaded and has encountered a boot up problem which is foreign to me.

    As her computer boots, the following messages are displayed:

    QUOTE:

    Invalid value for binding specified.

    Error loading device driver
    MDISHLP.SYS

    Error 7323
    One or more transport drivers failed to load.

    UNQUOTE:

    Windows continues to load.

    I have the identical OS and can find no trace of the file MDISHLP.SYS on my machine. The best I can do on the Internet leads me to believe it may be a `foreign' file [foreign to Win 98 that is] and may in fact be a Unix file: from where I don't know.

    What is meant by `invalid binding'?

    Can any member shed light on the above? Could it have gotten there via a virus, trojan or pirate ware? Ad-Aware doesn't detect it.

    I'm mystified.

    Thank you.
     
    Welt,
    #1
  2. 2003/08/28
    irdreed

    irdreed Inactive

    Joined:
    2002/09/27
    Messages:
    541
    Likes Received:
    0
    Welt,

    It appears that an error is in the TCP/IP protocol configuration.

    Check the Bindings Tab that lists the network protocols that are bound to the Dial-Up-Adapter. The check box beside any protocol that you don't need, to connect to the dial-up-server, should be deactivated.

    It may be necessary to reinstall and reconfigure the the TCP/IP Protocol.

    See:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;q138789

    Hope this helps.
     

  3. to hide this advert.

  4. 2003/08/28
    goddez1

    goddez1 Inactive

    Joined:
    2002/01/12
    Messages:
    2,975
    Likes Received:
    49
    In addition to the above.............
    Error 7323: Error loading network device driver ndishlp.sys:

    This might be caused by an improperly installed network driver or the failure of a proper removal when the computer does not have a network card installed.

    Also see these and use your best judgment for appropriateness:

    http://groups.yahoo.com/group/24hrsupporthelpdesk/message/12123?source=1

    http://www.experts-exchange.com/Operating_Systems/Win98/Q_20421501.html

    http://forums.techguy.org/t107127/s292af45053d395c21473b522f83fd4a0.html

    ==============
    Bear in mind that when dealing with network components {installs/uninstalls} you will have to have the win98 CD or the cab files stored on the harddrive. The CD will be asked for!
     
    Last edited: 2003/08/28
  5. 2003/08/29
    irdreed

    irdreed Inactive

    Joined:
    2002/09/27
    Messages:
    541
    Likes Received:
    0
    Welt,

    Please Clarify, Is it :
    Or as goddez1 states:
    If its's NDIS, then it is a Network Driver Interface Specification Driver.
    See this KBA Article By MS:
    http://support.microsoft.com/defaul...port/kb/articles/Q243/1/99.ASP&NoWebContent=1
    At the bottom of their page is a Driver to Download.

    Please Post Back. Hope this helps.
     
    Last edited: 2003/08/29
  6. 2003/08/29
    Welt

    Welt Inactive Thread Starter

    Joined:
    2002/02/19
    Messages:
    196
    Likes Received:
    0
    ERROR CORRECTION

    Hi irdreed

    I was misinformed. It really was:

    `Error loading network device driver ndishlp.sys'
    `Error 7323'

    When I learned this, I asked for/ received/ and remarked out a line in Autoexec.bat file and all now is well.

    The revision I made and which worked, read as:

    REM C:\windows\net start

    On behalf of my friend and myself, thanks to all who responded.
     
    Welt,
    #5
  7. 2003/08/29
    goddez1

    goddez1 Inactive

    Joined:
    2002/01/12
    Messages:
    2,975
    Likes Received:
    49
    I figured it was ndishlp.sys since this error was found umpteen times on a search and a reference to mdishlp was nowhere to be found. Since "N" and "M" are neighbors on the keyboard, I assumed a typo was made.

    Guess this was good assumption on my part.

    Thanks for the update, your welcome and I'm glad this problem was worked out.
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.