Jake covered the first step of this process - getting the PnP Manager to
load your driver - earlier today:
“If your desire is for the BIOS to trigger the loading of a driver,
that’s trivial. Add a node in the ACPI BIOS with the PnP ID for your
driver. The PnP manager will pick it up (with help from the ACPI
driver) and load whatever driver your INF specifies.”
After that, the specifics of the driver your inf specifies depends on
what you wish to emulate.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mickey Lane
Sent: Thursday, August 30, 2007 18:03
To: Windows System Software Devs Interest List
Subject: [ntdev] Virtual PnP Device Driver or…
Hi,
I need to create a driver to emulate a device that does not physically
exist. If it did exist, it would be a PnP device and the PnP Manager
would kick things off in response to the introduction of the device to
some bus.
It appears that you can’t arbitrarily load a PnP driver and telling the
PnP Manager to do it for you is a lot less than obvious.
Should I write a PnP driver (AddDevice, StartDevice, Power, etc) and
look for a way to fake out the manager -or- write something that creates
the DeviceObject (and everything else) in the DriverEntry routine? If
the latter and I specify FILE_DEVICE_SMARTCARD or FILE_DEVICE_TAPE
(etc), will it co-exist and function with similar devices that do
physically exist and are supported via the PnP mechanism?
Regards,
Mickey.
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