Prev: ad-hoc mode and 802.11g as a requirement
Next: mirror driver Win7 mediaplay problem
From: Boby George on 14 Mar 2010 18:28
I have a problem where events gets created properly during driver
installation. But after a reboot IoCreateNotificationEvent fails to
initialize the same set of events. In the driver, DriverEntry function
initializes these events.

Driver is installed with ServiceType=1 and StartType=3. So I would assume
BaseNamedObjects folder will exist during DriverEntry stage.

Driver is a KMDF driver. OS is Windows XP Embedded SP3, operationally
similar to Windows XP Pro SP3.

Another question, does events created using IoCreateNotificationEvents in
BaseNamedObjects folder persist across reboots?

From: Boby George on 14 Mar 2010 19:18
Small correction: Events are created on DeviceAdd entry point.

I also noticed that if I disable the failed driver, and enable it back (from
administrator login), driver seems to load successfully.

Security access in inf file is set as follows:
HKR,,DeviceCharacteristics,0x10001,0x100 ;Use same security checks on
relative opens
HKR,,Security,,"D:P(A;;GA;;;SY)(A;;GA;;;BA)" ;Allow generic all access to
system and built-in Admin.


"Boby George" <bgeorge(a)nospam.cwc.com> wrote in message
news:4B40A797-F65F-4B46-8E7E-CD672FBE35F0(a)microsoft.com...
> I have a problem where events gets created properly during driver
> installation. But after a reboot IoCreateNotificationEvent fails to
> initialize the same set of events. In the driver, DriverEntry function
> initializes these events.
>
> Driver is installed with ServiceType=1 and StartType=3. So I would assume
> BaseNamedObjects folder will exist during DriverEntry stage.
>
> Driver is a KMDF driver. OS is Windows XP Embedded SP3, operationally
> similar to Windows XP Pro SP3.
>
> Another question, does events created using IoCreateNotificationEvents in
> BaseNamedObjects folder persist across reboots?

 | 
Pages: 1
Prev: ad-hoc mode and 802.11g as a requirement
Next: mirror driver Win7 mediaplay problem