4.4.1Selecting the Best Compatible Driver: Verbose Logging
The following example illustrates what the messages that relate to selecting the best compatible driver look like for a Blender device—if the most verbose logging level is set.
@ 10:18:56.718 #V166 Device install function: DIF_SELECTBESTCOMPATDRV.
@ 10:18:56.718 #T149 Executing coinstaller 1 of 1.
@ 10:18:56.734 #V150 Completed coinstaller 1 of 1.
@ 10:18:56.734 #V155 Executing default installer.
@ 10:18:56.734 #I063 Selected driver installs from section [Blender_install-section-name_1.HW] in "e:\windows\inf\Blender_INF_File_Name.inf".
@ 10:18:56.734 #I062 Class GUID of device changed to: {Device_Setup_Class_GUID}.
@ 10:18:56.734 #I060 Set selected driver.
@ 10:18:56.734 #I058 Selected best compatible driver.
@ 10:18:56.734 #V156 Completed default installer.
In the previous example, the #V166 message indicates that SetupAPI initiated the processing of the DIF_SELECTBESTCOMPATDRV request for the device. The #T149 and #V150 messages indicate that a co-installer processed the request, and the #V155 message indicates that the default installer was called to process the request. Next, the #I063 message specifies the installation section in the INF file for the device, and the #I062 message states that the class GUID of the device was changed. The #I160 and #I058 messages indicate that the best compatible driver was selected and, finally, the #156 message indicates that the default installer completed processing the request.
Share with your friends: | 
