4.9.1Registering and Reloading Co-Installers: Verbose Logging
The following example illustrates what the registering-and-reloading subsection in a SetupAPI log file looks like for a Blender device—if the most verbose logging level is set.
@ 10:18:24.156 #V166 Device install function: DIF_REGISTER_COINSTALLERS.
@ 10:18:24.156 #T152 Executing class installer.
@ 10:18:24.156 #V153 Completed class installer.
@ 10:18:24.156 #V155 Executing default installer.
@ 10:18:24.156 #V005 Opened the PNF file of "e:\windows\inf\Blender_INF_File_Name.inf" (Language = 0409).
@ 10:18:24.156 #I056 Coinstallers registered.
@ 10:18:24.156 #V156 Completed default installer.
In the previous example, the #V166 message indicates that SetupAPI initiated the processing of the DIF_REGISTER_COINSTALLERS request. The remaining messages indicate that the installers registered the new co-installers and that SetupAPI reloaded all the co-installers. The #V005 message also contains the name of the INF file.
Note
Do not attempt to update a co-installer that is currently in use with another version of the co-installer that has the same name. For information about how to correctly update co-installers, see the “Updating Driver Files” section in the Windows DDK documentation.
Share with your friends: | 
