Announcement

Collapse
No announcement yet.

Can't initialize the NDIS network card device driver

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Can't initialize the NDIS network card device driver

    Can't initialize the NDIS network card device driver.
    Possible reasons are
    1) The user doesn'thave administrative rights. Login as the administrator.
    2) Service pack 4 or higher is not installed (Only an issue in Windows 2000)


    I have administrator privilages
    Windows XP Pro SP 2

    Latest version of wireless mon

    WirelessMonTestLog

    0.000s - DEBUG: Starting...
    0.000s - DEBUG: WirelessMon V2 Build: 1002
    0.000s - Debug: OS 5.1.2600.2 (2.0)
    0.010s - DEBUG: New Instance of WLAN802_11 class initialized successfully
    0.010s - DEBUG: Service control manager opened
    0.010s - DEBUG: Network Driver Interface service opened
    0.040s - DEBUG: Network Driver Interface service failed to start, 1058, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    0.050s - DEBUG: Network Card Service failed to start, 0, The operation completed successfully.

    0.050s - UpdateHexConst - numHexs: 1 - imgwidth: 0 - imgHeight: 0
    0.150s - DEBUG: Tab Control has been created successfully
    0.150s - DEBUG: Windows major version: 5 windows minor version:1
    0.160s - DEBUG PERF: Found perf functions in DLL
    0.170s - DEBUG: Graphic has been Initialized successfully
    0.201s - InitCounter start
    0.231s - DEBUG: All strings IBM High Rate Wireless LAN PC Card - Packet Scheduler Miniport
    0.231s - DEBUG: IBM High Rate Wireless LAN PC Card - Packet Scheduler Miniport
    0.241s - DEBUG: Intel[R] PRO_Wireless LAN 2100 3B Mini PCI Adapter - Packet Scheduler Miniport
    0.241s - DEBUG: Realtek RTL8139 Family PCI Fast Ethernet NIC - Packet Scheduler Miniport
    0.241s - DEBUG: MS TCP Loopback interface
    0.241s - InitCounter finish
    0.251s - DEBUG: Begin to Enumerate Devices



  • #2
    Can you download the current release and try it. The current release is as of today is V2.0 build 1011, (released 26 March 2007)

    Comment


    • #3
      Same results

      Downloaded the current version & got the same results

      Comment


      • #4
        Was the log the same? Just to be clear. Did it actually crash (as per the subject of your post) or did it say that it can't initialize your NDIS network card device driver, then exit (without a crash)?

        If it did really crash, what did you see. e.g. a blue screen, the PC rebooted, a message like access violation?

        What wireless hardware do you have? Do you have the latest device drivers for it?

        Comment


        • #5
          same results

          Software crashes with same error, here is the debug log from the most current version.

          I have an IBM High Rate Wireless LAN Card 128-bit encryption.
          Orinoco Gold equivilant, in addition there is a Intel Pro wireless 2100 3B Mini PCI


          0.000s - DEBUG: Starting...
          0.000s - DEBUG: WirelessMon V2 Build: 1002
          0.000s - Debug: OS 5.1.2600.2 (2.0)
          0.010s - DEBUG: New Instance of WLAN802_11 class initialized successfully
          0.010s - DEBUG: Service control manager opened
          0.010s - DEBUG: Network Driver Interface service opened
          0.040s - DEBUG: Network Driver Interface service failed to start, 1058, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

          0.050s - DEBUG: Network Card Service failed to start, 0, The operation completed successfully.

          0.050s - UpdateHexConst - numHexs: 1 - imgwidth: 0 - imgHeight: 0
          0.150s - DEBUG: Tab Control has been created successfully
          0.150s - DEBUG: Windows major version: 5 windows minor version:1
          0.160s - DEBUG PERF: Found perf functions in DLL
          0.170s - DEBUG: Graphic has been Initialized successfully
          0.201s - InitCounter start
          0.231s - DEBUG: All strings IBM High Rate Wireless LAN PC Card - Packet Scheduler Miniport
          0.231s - DEBUG: IBM High Rate Wireless LAN PC Card - Packet Scheduler Miniport
          0.241s - DEBUG: Intel[R] PRO_Wireless LAN 2100 3B Mini PCI Adapter - Packet Scheduler Miniport
          0.241s - DEBUG: Realtek RTL8139 Family PCI Fast Ethernet NIC - Packet Scheduler Miniport
          0.241s - DEBUG: MS TCP Loopback interface
          0.241s - InitCounter finish
          0.251s - DEBUG: Begin to Enumerate Devices
          0.020s - DEBUG: Starting...
          0.030s - DEBUG: WirelessMon V2 Build: 1011
          0.030s - Debug: OS 5.1.2600.2 (2.0)
          0.030s - DEBUG: New Instance of WLAN802_11 class initialized successfully
          0.030s - DEBUG: Service control manager opened
          0.030s - DEBUG: Network Driver Interface service opened
          0.050s - DEBUG: Network Driver Interface service failed to start, 1058, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

          0.050s - DEBUG: Network Card Service failed to start, 0, The operation completed successfully.

          0.050s - DEBUG: InitDialog start
          0.050s - UpdateHexConst - numHexs: 1 - imgwidth: 0 - imgHeight: 0
          0.570s - DEBUG: Tab Control has been created successfully
          0.590s - DEBUG PERF: Found perf functions in DLL
          0.600s - DEBUG: Graphic has been Initialized successfully
          0.610s - InitCounter start
          2.023s - Initialised memory2.023s - DEBUG: GetComputerName TOUGHBOOK
          2.053s - DEBUG: All strings IBM High Rate Wireless LAN PC Card - Packet Scheduler Miniport
          2.063s - DEBUG: IBM High Rate Wireless LAN PC Card - Packet Scheduler Miniport
          2.073s - DEBUG: Intel[R] PRO_Wireless LAN 2100 3B Mini PCI Adapter - Packet Scheduler Miniport
          2.083s - DEBUG: Realtek RTL8139 Family PCI Fast Ethernet NIC - Packet Scheduler Miniport
          2.083s - DEBUG: MS TCP Loopback interface
          2.093s - InitCounter finish
          2.103s - DEBUG: SetWindowPos
          2.103s - DEBUG: ListView_GetColumn
          2.113s - DEBUG: ListView_SetColumn
          2.113s - DEBUG: loop ListView_SetColumn
          2.113s - DEBUG: InitDialog finish
          2.123s - DEBUG: check mini mode
          2.133s - DEBUG: get user details
          2.143s - DEBUG: check edition
          2.153s - DEBUG: WelcomeDlg WM_INITDIALOG
          2.163s - DEBUG: WelcomeDlg WM_INITDIALOG end
          8.382s - DEBUG: WelcomeDlg IDCONTINUEON
          8.382s - em != NULL && ky != NULL
          8.382s - DEBUG: WelcomeDlg res true
          8.402s - DEBUG: SetupStart start
          8.402s - DEBUG: WLAN802_11->InitInstance

          Comment


          • #6
            same results

            Newest drivers, yes.

            Comment


            • #7
              The problem doesn't look like a crash, the log shows a normal start up, except it just looks like you have a problem starting the NDIS Windows service.

              First of all are you running any other wireless tools?

              Can you go to the control panel under admin tools and have a look at the service, "Wireless Zero Configuration". If you right click on this service, can you stop, then start it wuthout error?

              Comment


              • #8
                Wireless tools running

                Currently running is Intel ProSet version 7.1.4.7

                Windows Zero wireless service can be stopped & started without errors

                Comment


                • #9
                  Preferred Card

                  I would like the software to use the IBM/Orinoco Card as it has external antenna capabilities

                  Comment


                  • #10
                    Wrong Answer

                    The Zero Wireless service will not start.

                    Zero Wireless error 1068 the dependancy service or group failed to start.

                    Comment


                    • #11
                      removed & reinstalled Intel network drivers & got the same results

                      Comment


                      • #12
                        The Wireless Zero Configuation (WZC) service is part of the Windows O/S and not part of our software. But our software does make use of the same underlying NDIS device driver.

                        On a normal Window XP install you can stop and start this service at will. You should not get any errors when you try to start it. So there is something not right about your system, or some other software is blocking the normal operation of this service.

                        WZC depends on two other operating system functions.
                        1) The NDIS Usermode I/O protocol and the 2) the RPC remote procedure call (RPC) service. The problem is most likely with the NDIS driver (Ndisuio.sys). But as to exactly what the problem is with your system I don't know.

                        Comment


                        • #13
                          Ndis

                          Netstubmler seems to work with either card, in the setup for it is seeems to use the NDIS driver & is able to function, How do I remove & reinstall NDIS so that I can use your software. I am using Intel PRO Set software for managing the connections, could this be part of the problem ?

                          If so other than removing the software, how can this be resolved ?

                          Comment


                          • #14
                            Can you temporarily uninstall the Intel PRO Set software software and reboot. At least to see if this is the problem.

                            Comment


                            • #15
                              There is a walk through for a similar problem when trying to enable internet connection sharing and getting the same error, http://support.microsoft.com/default...b;en-us;827328. You could try following these steps and ensure the Wireless Zero Configuration and Remote Procedure Call options are checked.

                              Comment

                              Working...
                              X