You would probably need something to load your driver, but obviously USB function drivers are temporary and only there when the physical device is attached. Likewise KS drivers that are attached to USB and other removable devices.
I know how to make a root-enumerated KS driver, but it if course tends to stay around. Possibly there is some technique for making a load-on-demand KS driver that isn’t associated with hardware.
Loren
----- Original Message -----
From: Mathieu Routhier
To: Windows System Software Devs Interest List
Sent: Wednesday, July 14, 2004 8:16 AM
Subject: RE: [ntdev] Temporary Device Object
This is interesting. I’m a bit familiar to bus drivers (I developed one myself) and this makes sense.
The problem with this is I don’t want to have a driver loaded permanently, which is what this bus driver would do. Also, I’m interested in creating only one instance of that driver, never more. Choosing a bus architecture seems a bit exaggerated in this case.
Does the system provide a way to create a device object temporarily, just like a bus driver would do? Isn’t the root-enumerator a bus driver?
Mat
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, July 14, 2004 10:54 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Temporary Device Object
See the toaster sample driver. Basically you are describing bus driver functionality. The bus driver and its device object are permanent, the devices enumerated by the bus driver are under your software’s control.
=====================
Mark Roddy
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Wednesday, July 14, 2004 10:49 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Temporary Device Object
What hardware will your driver emulate? Storage? Network? Human input? or what another kind?
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: Mathieu Routhier
To: Windows System Software Devs Interest List
Sent: Wednesday, July 14, 2004 6:40 PM
Subject: [ntdev] Temporary Device Object
Greetings,
I’m interested in developing a virtual driver, one that does not control hardware. It would load temporarily, only for the time it is required. Are there other options for loading that driver than using calls to SetupApi (using a similar approach to the install command of devcon)?
Using the SetupApi approach, the device object is permanent and is created again after a crash/reboot. How can I tell the system I want it only temporarily and that the device object should not be automatically created again after a reboot?
Thanks In Advance,
Mat
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to xxxxx@lists.osr.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@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.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@encentrus.com
To unsubscribe send a blank email to xxxxx@lists.osr.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@earthlink.net
To unsubscribe send a blank email to xxxxx@lists.osr.com