G
Guest
Guest
Archived from groups: microsoft.public.development.device.drivers,microsoft.public.win32.programmer.kernel,microsoft.public.windowsxp.device_driver.dev (More info?)
Hi
I have a legacy kernel driver, that uses the a COM port (serial.sys). Its
works OK and application can acces it as they schould.
Now I would like to make the driver know, if the system is restarting or
shutting down. To get this information, it must be a PnP driver. Is that
right ?
I then have to add a XXXAddDevice and a XXXDispatchPnp major function in my
DriverEntry. XXXAddDevice now has to performe some of hte task done by
DriverEntry, e.g. creating symbolic link etc.
But the driver has no actual HW device attached to it, so its a software
only device driver, so i guess it schould be software enumerated by the PnP.
I whant the driver to be started by the system somewhere in the boot phase
(After the serial driver has been started), just like the legacy version do.
Do I need to add something in the registry to do this ?
If I try to start my driver manualy, after boot up is done, my XXXUnload is
called just after DriverEntry is finished, with following message in the
system log:
"The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it. " ID event: 7000
So my XXXAddDevice never gets called.
How do I get the PnP to start this driver and accept, that there is no
device associated with it ?
Thomas
Hi
I have a legacy kernel driver, that uses the a COM port (serial.sys). Its
works OK and application can acces it as they schould.
Now I would like to make the driver know, if the system is restarting or
shutting down. To get this information, it must be a PnP driver. Is that
right ?
I then have to add a XXXAddDevice and a XXXDispatchPnp major function in my
DriverEntry. XXXAddDevice now has to performe some of hte task done by
DriverEntry, e.g. creating symbolic link etc.
But the driver has no actual HW device attached to it, so its a software
only device driver, so i guess it schould be software enumerated by the PnP.
I whant the driver to be started by the system somewhere in the boot phase
(After the serial driver has been started), just like the legacy version do.
Do I need to add something in the registry to do this ?
If I try to start my driver manualy, after boot up is done, my XXXUnload is
called just after DriverEntry is finished, with following message in the
system log:
"The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it. " ID event: 7000
So my XXXAddDevice never gets called.
How do I get the PnP to start this driver and accept, that there is no
device associated with it ?
Thomas