Troubleshooting Device Installation with the Setupapi log File




старонка6/11
Дата канвертавання22.04.2016
Памер227 Kb.
1   2   3   4   5   6   7   8   9   10   11

4.9Registering and Reloading Co-Installers


During the registering-and-reloading stage of driver installation, SetupAPI logs messages that are associated with a DIF_REGISTER_COINSTALLERS request. The class installers and class co-installers process this request to register any new device co-installers and to reload all the co-installers. The following example illustrates what the log-file subsection that is associated with this stage looks like for an Oven device, if the default logging level is set.

#-166 Device install function: DIF_REGISTER_COINSTALLERS.

#I056 Coinstallers registered
In the previous example, the #-166 message indicates that SetupAPI initiated the processing of the DIF_REGISTER_COINSTALLERS request, while the #I056 message indicates that the installers successfully registered the new co-installers and that SetupAPI reloaded all the co-installers.

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.



4.10Installing Device Interfaces


During the installing-device-interfaces stage of driver installation, SetupAPI logs messages that are associated with a DIF_INSTALLINTERFACES request. The following example illustrates what the log-file subsection that is associated with this stage looks like for an Oven device, if the default logging level is set.

#-166 Device install function: DIF_INSTALLINTERFACES.

#-011 Installing section [Oven_install-section-name.Interfaces] from "c:\windows\inf\Oven_INF_File_Name_2.inf".

#I054 Interfaces installed


In the previous example, the #-166 message indicates that SetupAPI initiated the processing of the DIF_INSTALLINTERFACES request, and the #I054 message indicates that the device interfaces were installed.

4.10.1Installing Device Interfaces: Verbose Logging


The following example illustrates what the installing-device-interfaces subsection in a SetupAPI log file looks like for a Blender device—if the most verbose logging level is set.

@ 10:18:24.187 #V166 Device install function: DIF_INSTALLINTERFACES.

@ 10:18:24.187 #T152 Executing class installer.

@ 10:18:24.187 #V153 Completed class installer.

@ 10:18:24.187 #V155 Executing default installer.

@ 10:18:24.187 #V005 Opened the PNF file of "e:\windows\inf\Blender_INF_File_Name.inf" (Language = 0409).

@ 10:18:24.187 #V011 Installing section [Blender_install-section-name.Interfaces] from "e:\windows\inf\Blender_INF_File_Name.inf".

@ 10:18:24.187 #I054 Interfaces installed.

@ 10:18:24.203 #V156 Completed default installer.
In the previous example, the #V166 message indicates that SetupAPI initiated the processing of the DIF_INSTALLINTERFACES request, the #V011 message specifies the INF section that installed the device interface, and the remaining messages indicate that the installers processed the request.

4.11Installing the Device


During the installing-the-device stage of driver installation, SetupAPI logs messages that are associated with a DIF_INSTALLDEVICE request. The following example illustrates what the log-file subsection that is associated with this stage looks like for an Oven device, if the default logging level is set.

#-166 Device install function: DIF_INSTALLDEVICE.

#I123 Doing full install of "Oven_Device_Instance_ID_2".

#I121 Device install of "Oven_Device_Instance_ID_2" finished successfully.


In the previous example, the #-166 message indicates that SetupAPI initiated the processing of the DIF_INSTALLDEVICE request, and the #I121 message reports that SetupAPI successfully installed the device.

4.11.1Installing the Device: Verbose Logging


The examples in this section illustrate what the installing-the-device messages in a SetupAPI log file looks like for a Blender device—if the most verbose logging level is set.

The following messages are those associated with executing the class installer, writing basic logical configurations, setting registry values, and adding the Blender service:

@ 10:18:24.218 #V166 Device install function: DIF_INSTALLDEVICE.

@ 10:18:24.218 #T152 Executing class installer.

@ 10:18:24.234 #T200 Install Device: Begin.

@ 10:18:24.234 #I123 Doing full install of "Blender_Device_Instance_ID".

@ 10:18:24.250 #V005 Opened the PNF file of…

@ 10:18:24.250 #T209 Install Device: Writing BASIC Logical Configurations.

@ 10:18:24.250 #T211 Install Device: Changing registry settings as specified by the INF(s).

@ 10:18:24.250 #T212 Install Device: Writing driver specific registry settings.

@ 10:18:24.250 #T213 Install Device: Installing required Windows services.

#-035 Processing service Add/Delete section [Blender_install-section-name.Services].

@ 10:18:24.640 #V282 Add Service: Modified existing service "Blender".

@ 10:18:24.656 #T214 Install Device: Writing driver descriptive registry settings.


In the previous example, the #V166 message indicates that SetupAPI initiated the processing of the DIF_INSTALLDEVICE request. The #T152 through #V005 messages are associated with the start of the installation by the class installer. The #T209 message reports the time that SetupAPI checked for those hardware resources specified by any LogConfig directive in the INF file. In this case, no resources were logged, so none were in specified in the INF file. The #T211 and #T212 messages show that the class installer set some registry values. Finally, the #T213, #-035, #V282, and #T214 messages outline the changing of the existing Blender service.

If an installer changes an existing service, SetupAPI must restart all the devices that depend on that service. Furthermore, if any device vetoes a restart, a reboot is required. For example, the following messages illustrate removing and restarting the devices that depend on the Blender service:

@ 10:18:24.656 #T398 Install Device: Removing device "Blender_Device_Instance_ID" sub-tree.

@ 10:18:24.718 #T399 Install Device: Removing device "Blender_Device_Instance_ID" sub-tree completed.

@ 10:18:24.734 #T398 Install Device: Removing device "Some_Device_Instance_ID" sub-tree.

@ 10:18:24.781 #T399 Install Device: Removing device "Some_Device_Instance_ID" sub-tree completed.

@ 10:18:24.937 #T396 Install Device: Restarting device "Blender_Device_Instance_ID".



@ 10:18:24.968 #T397 Install Device: Restarting device "Blender_Device_Instance_ID" completed.

@ 10:18:24.968 #T396 Install Device: Restarting device "Some_Device_Instance_ID".

@ 10:18:24.984 #T397 Install Device: Restarting device "Some_Device_Instance_ID" completed.
In the previous example, the #T398 and #T399 messages show that a device was removed, and the #T396 and #T397 messages show that a device was restarted.
If SetupAPI restarts all the devices without a reboot, the class installer completes the DIF_INSTALLDEVICE request, as shown by the following messages:

@ 10:18:25.000 #T396 Install Device: Restarting device "Some_Device_Instance_ID".

@ 10:18:25.000 #T397 Install Device: Restarting device "Some_Device_Instance_ID" completed.

@ 10:18:25.015 #I121 Device install of "Some_Device_Instance_ID" finished successfully.

@ 10:18:25.015 #T201 Install Device: End.

@ 10:18:25.015 #V153 Completed class installer.


In the previous example, the #I121, #T201, and #V153 messages indicate that the device installation successfully completed without a reboot.

If a device restart requires a reboot, SetupAPI logs messages that are similar to the following:

@ 10:18:25.000 #W100 Query-removal during install of "Blender_Device_Instance_ID" was vetoed by "Some_Device_Instance_ID" (veto type 1: PNP_VetoLegacyDevice).

@ 10:18:25.000 #W104 Device "Blender_Device_Instance_ID" required reboot: Query remove failed (install) CfgMgr32 returned: 0x17: CR_REMOVE_VETOED.


The messages indicating that rebooting is required are discussed in more detail later in this paper.
1   2   3   4   5   6   7   8   9   10   11


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка