>If the devnode’s HwID figures in the database - then I have a strong suspect that Windows will do minimal setup of this devnode early in the boot stage, before the INF-processing service is up.
Depends on what you mean by setup. It just starts the stack with the service indicated in the cddb entry under the device class listed (to get class filters added). That’s it. No real “setup”, the cddb is a minimal bootstrap to the os out of the boot phase and into the real installer once it is up and running
d
-----Original Message-----
From: Maxim S. Shatskih
Sent: Thursday, December 31, 2009 5:13 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] WiX installer - how to know when drivers are installed
>Hmmm… I’d vaguely wondered about that earlier. So I guess until
>Windows sets up the devnodes and figures out that it’s a boot device, it
>doesn’t get in CriticalDeviceDatabase automatically?
It does.
CriticalDeviceDatabase is a primitive map of HwID -> DriverServiceName, which is the INF files replacement for the early boot stages.
If the devnode’s HwID figures in the database - then I have a strong suspect that Windows will do minimal setup of this devnode early in the boot stage, before the INF-processing service is up.
> Time to do some testing!
Yes.
>- Happy New Year everyone!)
To you too 
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
—
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