Hello,
I?m trying to install MSFT?s ndisprot example on win8. DriverEntry completes, but BindAdapter is never called.
Running sc query shows the service is running:
SERVICE_NAME: ndisprot
TYPE : 1 KERNEL_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
But the ACPI entry shows a problem:
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
StateHistory[12] = Unknown State (0x0)
StateHistory[11] = Unknown State (0x0)
StateHistory[10] = Unknown State (0x0)
StateHistory[09] = Unknown State (0x0)
StateHistory[08] = Unknown State (0x0)
StateHistory[07] = Unknown State (0x0)
StateHistory[06] = Unknown State (0x0)
StateHistory[05] = Unknown State (0x0)
StateHistory[04] = Unknown State (0x0)
StateHistory[03] = Unknown State (0x0)
StateHistory[02] = Unknown State (0x0)
StateHistory[01] = Unknown State (0x0)
Flags (0x00002030) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_PROBLEM
CapabilityFlags (0x00000080) SilentInstall
Problem = CM_PROB_NOT_CONFIGURED
From what I?ve found on MSDN, that means the driver failed to install, but driver entry is getting called…
Anyone know how to approach this issue?
Is this a 64-bit Win8? If so, was the driver signed?
If the driver appears in the Network Control Panel for at least one adapter,
but is not running, then this often means a signing issue.
Thomas F. Divine
http://www.pcausa.com
From:
Sent: Wednesday, June 27, 2012 5:20 PM
To: “Windows System Software Devs Interest List”
Subject: [ntdev] NDIS Protocol Driver on Win8
> Hello,
>
> I?m trying to install MSFT?s ndisprot example on win8. DriverEntry
> completes, but BindAdapter is never called.
>
> Running sc query shows the service is running:
> SERVICE_NAME: ndisprot
> TYPE : 1 KERNEL_DRIVER
> STATE : 4 RUNNING
> (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
> WIN32_EXIT_CODE : 0 (0x0)
> SERVICE_EXIT_CODE : 0 (0x0)
> CHECKPOINT : 0x0
> WAIT_HINT : 0x0
>
> But the ACPI entry shows a problem:
> State = DeviceNodeInitialized (0x302)
> Previous State = DeviceNodeUninitialized (0x301)
> StateHistory[00] = DeviceNodeUninitialized (0x301)
> StateHistory[19] = Unknown State (0x0)
> StateHistory[18] = Unknown State (0x0)
> StateHistory[17] = Unknown State (0x0)
> StateHistory[16] = Unknown State (0x0)
> StateHistory[15] = Unknown State (0x0)
> StateHistory[14] = Unknown State (0x0)
> StateHistory[13] = Unknown State (0x0)
> StateHistory[12] = Unknown State (0x0)
> StateHistory[11] = Unknown State (0x0)
> StateHistory[10] = Unknown State (0x0)
> StateHistory[09] = Unknown State (0x0)
> StateHistory[08] = Unknown State (0x0)
> StateHistory[07] = Unknown State (0x0)
> StateHistory[06] = Unknown State (0x0)
> StateHistory[05] = Unknown State (0x0)
> StateHistory[04] = Unknown State (0x0)
> StateHistory[03] = Unknown State (0x0)
> StateHistory[02] = Unknown State (0x0)
> StateHistory[01] = Unknown State (0x0)
> Flags (0x00002030) DNF_ENUMERATED, DNF_IDS_QUERIED,
> DNF_HAS_PROBLEM
> CapabilityFlags (0x00000080) SilentInstall
> Problem = CM_PROB_NOT_CONFIGURED
>
> From what I?ve found on MSDN, that means the driver failed to install, but
> driver entry is getting called…
>
> Anyone know how to approach this issue?
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
No, 32-bit, and the driver is signed.
It’s not showing up for any adapters.
Anything helpful in the Windows\INF\setupapi logs?
Thomas
From:
Sent: Wednesday, June 27, 2012 6:12 PM
To: “Windows System Software Devs Interest List”
Subject: RE:[ntdev] NDIS Protocol Driver on Win8
> No, 32-bit, and the driver is signed.
> It’s not showing up for any adapters.
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
I don’t see any log files there. Maybe it’s turned off?
I compared the registry entries with those for NDISUIO and noticed my driver is missing some (such as WdfMajorVersion and WdfMinorVersion) which I think should get added during installation.
Installation is clearly failing (CM_PROB_NOT_CONFIGURED problem), and I’m guessing this is in turn causing the other issues, but I’m not sure what’s going wrong with install.