When I install my miniport driver on my PC the DriverEntry is called but the
Initialize function is never called and my DriverEntry return SUCCESS. Why
the Initialize function is never called ?
Thanks.
Did you successfully attach to the ndiswrapper and
register as a miniport? If yes, then use WinDbg to
dump the devnode of the device to see the state
history.
The init handler is called in the context of
MN_START_DEVICE.
–
Calvin Guan (Windows DDK MVP)
Staff SW Engineer NetXtreme MINIPORT
Broadcom Corp. Irvine, CA
www.broadcom.com
— Francky wrote:
> When I install my miniport driver on my PC the
> DriverEntry is called but the
> Initialize function is never called and my
> DriverEntry return SUCCESS. Why
> the Initialize function is never called ?
>
> Thanks.
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.ca
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Can you give me just a short resume how to get the state history ?
Thanks
“Calvin Guan” wrote in message news:xxxxx@ntdev…
> Did you successfully attach to the ndiswrapper and
> register as a miniport? If yes, then use WinDbg to
> dump the devnode of the device to see the state
> history.
>
> The init handler is called in the context of
> MN_START_DEVICE.
>
> –
> Calvin Guan (Windows DDK MVP)
> Staff SW Engineer NetXtreme MINIPORT
> Broadcom Corp. Irvine, CA
> www.broadcom.com
>
> — Francky wrote:
>
> > When I install my miniport driver on my PC the
> > DriverEntry is called but the
> > Initialize function is never called and my
> > DriverEntry return SUCCESS. Why
> > the Initialize function is never called ?
> >
> > Thanks.
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as:
> > xxxxx@yahoo.ca
> > To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
Look at the !devnode command in the WinDBG documentation.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Francky” wrote in message news:xxxxx@ntdev…
> Can you give me just a short resume how to get the state history ?
>
> Thanks
>
> “Calvin Guan” wrote in message news:xxxxx@ntdev…
>> Did you successfully attach to the ndiswrapper and
>> register as a miniport? If yes, then use WinDbg to
>> dump the devnode of the device to see the state
>> history.
>>
>> The init handler is called in the context of
>> MN_START_DEVICE.
>>
>> –
>> Calvin Guan (Windows DDK MVP)
>> Staff SW Engineer NetXtreme MINIPORT
>> Broadcom Corp. Irvine, CA
>> www.broadcom.com
>>
>> — Francky wrote:
>>
>> > When I install my miniport driver on my PC the
>> > DriverEntry is called but the
>> > Initialize function is never called and my
>> > DriverEntry return SUCCESS. Why
>> > the Initialize function is never called ?
>> >
>> > Thanks.
>> >
>> >
>> >
>> > —
>> > Questions? First check the Kernel Driver FAQ at
>> > http://www.osronline.com/article.cfm?id=256
>> >
>> > You are currently subscribed to ntdev as:
>> > xxxxx@yahoo.ca
>> > To unsubscribe send a blank email to
>> > xxxxx@lists.osr.com
>> >
>>
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>>
>
>
>
Could you help me to see the meaning of that :
DevNode 0x81330dd0 for PDO 0x813316a0
Parent 0x817ba460 Sibling 0x81182ca8 Child 0000000000
InstancePath is “ROOT\NET\0000”
ServiceName is “E100B”
State = DeviceNodeRemoved (0x312)
Previous State = DeviceNodeStartCompletion (0x306)
StateHistory[08] = DeviceNodeStartCompletion (0x306)
StateHistory[07] = DeviceNodeAwaitingQueuedRemoval (0x30f)
StateHistory[06] = DeviceNodeStartCompletion (0x306)
StateHistory[05] = DeviceNodeResourcesAssigned (0x304)
StateHistory[04] = DeviceNodeDriversAdded (0x303)
StateHistory[03] = DeviceNodeInitialized (0x302)
StateHistory[02] = DeviceNodeUninitialized (0x301)
StateHistory[01] = DeviceNodeInitialized (0x302)
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)
Flags (0x00002131) DNF_MADEUP, DNF_ENUMERATED,
DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED,
DNF_HAS_PROBLEM
Problem = CM_PROB_FAILED_START
Failure Status 0000000000
“Francky” wrote in message news:xxxxx@ntdev…
> When I install my miniport driver on my PC the DriverEntry is called but the
> Initialize function is never called and my DriverEntry return SUCCESS. Why
> the Initialize function is never called ?
>
> Thanks.
>
>
>
> InstancePath is “ROOT\NET\0000”
ServiceName is “E100B”
The instance path is wrong. I’m assuming you’re using
the intel 10/100 PCI card, eh? It shouldn’t be root
enumerated. How do you install the driver? Did you
actually plug in an NIC into you system?
The devnode for a PCI card should look like this:
kd> !devnode 0x812dd3a0
DevNode 0x812dd3a0 for PDO 0x812dd640
Parent 0x8134d4f8 Sibling 0000000000 Child
0000000000
InstancePath is
“PCI\VEN_14E4&DEV_1677&SUBSYS_128810CF&REV_01\4&1d332a10&0&00E0”
ServiceName is “b57w2k”
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion
(0x30d)
StateHistory[13] = DeviceNodeEnumerateCompletion
(0x30d)
StateHistory[12] = DeviceNodeStarted (0x308)
StateHistory[11] = DeviceNodeEnumerateCompletion
(0x30d)
StateHistory[10] = DeviceNodeStarted (0x308)
StateHistory[09] = DeviceNodeStartPostWork (0x307)
StateHistory[08] = DeviceNodeStartCompletion (0x306)
StateHistory[07] = DeviceNodeResourcesAssigned
(0x304)
StateHistory[06] = DeviceNodeDriversAdded (0x303)
StateHistory[05] = DeviceNodeInitialized (0x302)
StateHistory[04] = DeviceNodeUninitialized (0x301)
StateHistory[03] = DeviceNodeRemoved (0x312)
StateHistory[02] = DeviceNodeQueryRemoved (0x310)
StateHistory[01] = DeviceNodeStarted (0x308)
StateHistory[00] = DeviceNodeEnumerateCompletion
(0x30d)
StateHistory[19] = DeviceNodeStarted (0x308)
StateHistory[18] = DeviceNodeEnumerateCompletion
(0x30d)
StateHistory[17] = DeviceNodeStarted (0x308)
StateHistory[16] = DeviceNodeStartPostWork (0x307)
StateHistory[15] = DeviceNodeStartCompletion (0x306)
StateHistory[14] = DeviceNodeResourcesAssigned
(0x304)
Flags (0x00000030) DNF_ENUMERATED, DNF_IDS_QUERIED
CapabilityFlags (0x00002000) WakeFromD3
–
Calvin Guan (Windows DDK MVP)
Staff SW Engineer NetXtreme MINIPORT
Broadcom Corp. Irvine, CA
www.broadcom.com
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Yes i have an Intel card on my PC. I install the driver from the Add/remove
hardware.
Is it possible that something is wrong in my Inf file ? My Inf file is based
from the Inf file for the NDIS miniport in the DDK.
Thanks for your help.
“Calvin Guan” wrote in message news:xxxxx@ntdev…
>> InstancePath is “ROOT\NET\0000”
>>
>> ServiceName is “E100B”
>
> The instance path is wrong. I’m assuming you’re using
> the intel 10/100 PCI card, eh? It shouldn’t be root
> enumerated. How do you install the driver? Did you
> actually plug in an NIC into you system?
>
> The devnode for a PCI card should look like this:
>
>
> kd> !devnode 0x812dd3a0
> DevNode 0x812dd3a0 for PDO 0x812dd640
> Parent 0x8134d4f8 Sibling 0000000000 Child
> 0000000000
> InstancePath is
> “PCI\VEN_14E4&DEV_1677&SUBSYS_128810CF&REV_01\4&1d332a10&0&00E0”
> ServiceName is “b57w2k”
> State = DeviceNodeStarted (0x308)
> Previous State = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[13] = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[12] = DeviceNodeStarted (0x308)
> StateHistory[11] = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[10] = DeviceNodeStarted (0x308)
> StateHistory[09] = DeviceNodeStartPostWork (0x307)
> StateHistory[08] = DeviceNodeStartCompletion (0x306)
> StateHistory[07] = DeviceNodeResourcesAssigned
> (0x304)
> StateHistory[06] = DeviceNodeDriversAdded (0x303)
> StateHistory[05] = DeviceNodeInitialized (0x302)
> StateHistory[04] = DeviceNodeUninitialized (0x301)
> StateHistory[03] = DeviceNodeRemoved (0x312)
> StateHistory[02] = DeviceNodeQueryRemoved (0x310)
> StateHistory[01] = DeviceNodeStarted (0x308)
> StateHistory[00] = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[19] = DeviceNodeStarted (0x308)
> StateHistory[18] = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[17] = DeviceNodeStarted (0x308)
> StateHistory[16] = DeviceNodeStartPostWork (0x307)
> StateHistory[15] = DeviceNodeStartCompletion (0x306)
> StateHistory[14] = DeviceNodeResourcesAssigned
> (0x304)
> Flags (0x00000030) DNF_ENUMERATED, DNF_IDS_QUERIED
> CapabilityFlags (0x00002000) WakeFromD3
>
> –
> Calvin Guan (Windows DDK MVP)
> Staff SW Engineer NetXtreme MINIPORT
> Broadcom Corp. Irvine, CA
> www.broadcom.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
I had another driver installed for the same network card. Can it be cause
of the problem ?
“Calvin Guan” wrote in message news:xxxxx@ntdev…
>> InstancePath is “ROOT\NET\0000”
>>
>> ServiceName is “E100B”
>
> The instance path is wrong. I’m assuming you’re using
> the intel 10/100 PCI card, eh? It shouldn’t be root
> enumerated. How do you install the driver? Did you
> actually plug in an NIC into you system?
>
> The devnode for a PCI card should look like this:
>
>
> kd> !devnode 0x812dd3a0
> DevNode 0x812dd3a0 for PDO 0x812dd640
> Parent 0x8134d4f8 Sibling 0000000000 Child
> 0000000000
> InstancePath is
> “PCI\VEN_14E4&DEV_1677&SUBSYS_128810CF&REV_01\4&1d332a10&0&00E0”
> ServiceName is “b57w2k”
> State = DeviceNodeStarted (0x308)
> Previous State = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[13] = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[12] = DeviceNodeStarted (0x308)
> StateHistory[11] = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[10] = DeviceNodeStarted (0x308)
> StateHistory[09] = DeviceNodeStartPostWork (0x307)
> StateHistory[08] = DeviceNodeStartCompletion (0x306)
> StateHistory[07] = DeviceNodeResourcesAssigned
> (0x304)
> StateHistory[06] = DeviceNodeDriversAdded (0x303)
> StateHistory[05] = DeviceNodeInitialized (0x302)
> StateHistory[04] = DeviceNodeUninitialized (0x301)
> StateHistory[03] = DeviceNodeRemoved (0x312)
> StateHistory[02] = DeviceNodeQueryRemoved (0x310)
> StateHistory[01] = DeviceNodeStarted (0x308)
> StateHistory[00] = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[19] = DeviceNodeStarted (0x308)
> StateHistory[18] = DeviceNodeEnumerateCompletion
> (0x30d)
> StateHistory[17] = DeviceNodeStarted (0x308)
> StateHistory[16] = DeviceNodeStartPostWork (0x307)
> StateHistory[15] = DeviceNodeStartCompletion (0x306)
> StateHistory[14] = DeviceNodeResourcesAssigned
> (0x304)
> Flags (0x00000030) DNF_ENUMERATED, DNF_IDS_QUERIED
> CapabilityFlags (0x00002000) WakeFromD3
>
> –
> Calvin Guan (Windows DDK MVP)
> Staff SW Engineer NetXtreme MINIPORT
> Broadcom Corp. Irvine, CA
> www.broadcom.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
I think OS should have installed the IN-THE-BOX driver
for the NIC. What you need to do is perform an “Update
Driver” by right clicking the INTEL NIC in device
manager, provide your INF when asked instead of the
default one.
If the OS doesn’t install IN-THE-BOX driver for the
nic (that’s weird), you will see your device in device
manager with a yellow question mark, then install the
sample driver for it.
BTW, does your company do NDIS driver development? I’m
not aware of any Canadian company doing this.
HTH,
Calvin Guan (Windows DDK MVP)
Staff SW Engineer NetXtreme MINIPORT
Broadcom Corp. Irvine, CA
www.broadcom.com
— OSR Online wrote:
> Yes i have an Intel card on my PC. I install the
> driver from the Add/remove
> hardware.
> Is it possible that something is wrong in my Inf
> file ? My Inf file is based
> from the Inf file for the NDIS miniport in the DDK.
>
> Thanks for your help.
>
> “Calvin Guan” wrote in message
> news:xxxxx@ntdev…
> >> InstancePath is “ROOT\NET\0000”
> >>
> >> ServiceName is “E100B”
> >
> > The instance path is wrong. I’m assuming you’re
> using
> > the intel 10/100 PCI card, eh? It shouldn’t be
> root
> > enumerated. How do you install the driver? Did you
> > actually plug in an NIC into you system?
> >
> > The devnode for a PCI card should look like this:
> >
> >
> > kd> !devnode 0x812dd3a0
> > DevNode 0x812dd3a0 for PDO 0x812dd640
> > Parent 0x8134d4f8 Sibling 0000000000 Child
> > 0000000000
> > InstancePath is
> >
>
“PCI\VEN_14E4&DEV_1677&SUBSYS_128810CF&REV_01\4&1d332a10&0&00E0”
> > ServiceName is “b57w2k”
> > State = DeviceNodeStarted (0x308)
> > Previous State = DeviceNodeEnumerateCompletion
> > (0x30d)
> > StateHistory[13] = DeviceNodeEnumerateCompletion
> > (0x30d)
> > StateHistory[12] = DeviceNodeStarted (0x308)
> > StateHistory[11] = DeviceNodeEnumerateCompletion
> > (0x30d)
> > StateHistory[10] = DeviceNodeStarted (0x308)
> > StateHistory[09] = DeviceNodeStartPostWork
> (0x307)
> > StateHistory[08] = DeviceNodeStartCompletion
> (0x306)
> > StateHistory[07] = DeviceNodeResourcesAssigned
> > (0x304)
> > StateHistory[06] = DeviceNodeDriversAdded (0x303)
> > StateHistory[05] = DeviceNodeInitialized (0x302)
> > StateHistory[04] = DeviceNodeUninitialized
> (0x301)
> > StateHistory[03] = DeviceNodeRemoved (0x312)
> > StateHistory[02] = DeviceNodeQueryRemoved (0x310)
> > StateHistory[01] = DeviceNodeStarted (0x308)
> > StateHistory[00] = DeviceNodeEnumerateCompletion
> > (0x30d)
> > StateHistory[19] = DeviceNodeStarted (0x308)
> > StateHistory[18] = DeviceNodeEnumerateCompletion
> > (0x30d)
> > StateHistory[17] = DeviceNodeStarted (0x308)
> > StateHistory[16] = DeviceNodeStartPostWork
> (0x307)
> > StateHistory[15] = DeviceNodeStartCompletion
> (0x306)
> > StateHistory[14] = DeviceNodeResourcesAssigned
> > (0x304)
> > Flags (0x00000030) DNF_ENUMERATED,
> DNF_IDS_QUERIED
> > CapabilityFlags (0x00002000) WakeFromD3
> >
> > –
> > Calvin Guan (Windows DDK MVP)
> > Staff SW Engineer NetXtreme MINIPORT
> > Broadcom Corp. Irvine, CA
> > www.broadcom.com
> >
> >
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.ca
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
“Calvin Guan” wrote in message news:xxxxx@ntdev…
>I think OS should have installed the IN-THE-BOX driver
> for the NIC. What you need to do is perform an “Update
> Driver” by right clicking the INTEL NIC in device
> manager, provide your INF when asked instead of the
> default one.
>
> If the OS doesn’t install IN-THE-BOX driver for the
> nic (that’s weird), you will see your device in device
> manager with a yellow question mark, then install the
> sample driver for it.
>
Lately I’ve been tinkering with the various versions of the DDK E100BEX
sample driver. Calvin’t right, the OS will have already installed the in-box
Intel PRO/100 driver.
To install the sample driver go to the Device Manager, the Update Driver.
You must choose to install from a specific location, then “Don’t Search” and
finally browse to your INF file.
If you haven’t made any breaking changes to the baseline sample it should
come to life without any problem.
Should do the trick.
Thomas F. Divine, Windows DDK MVP
http://www.rawether.net