| Note
For more information on the UpdateDriverForPlugAndPlayDevices function, see “UpdateDriverForPlugAndPlayDevices” in the Windows DDK documentation.
4.1.1Initiating Driver Installation: Verbose Logging
The following example illustrates what the initiating-driver-installation subsection looks like for a Blender device—if the most verbose logging level is set.
[2003/02/18 10:18:56 568.2675 Driver Install]
#-019 Searching for hardware ID(s): Blender_Hardware_ID
#-199 Executing "E:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
@ 10:18:56.437 #V017 Enumerating files "E:\WINDOWS\inf".
@ 10:18:56.437 #V392 Using INF cache "E:\WINDOWS\inf\INFCACHE.1".
@ 10:18:56.437 #V073 Cache: Excluding INF "accessor.inf".
You can check entries of this type to determine if Setup excludes an INF file.
@ 10:18:56.437 #V073 Cache: Excluding INF "activeds.inf".
@ 10:18:56.437 #V073 Cache: Excluding INF "agtinst.inf".
@ 10:18:56.437 #V073 Cache: Excluding INF "apcompat.inf".
…
@ 10:18:56.609 #T075 Enumerating files: Directory pass completed.
In the previous example, the #V017 through #T075 messages are associated with finding the INF files that match the device.
Share with your friends: | 
