However, this method also has the following disadvantages: Also, additional or optional applications, which are not on the distribution medium, can be downloaded from the Internet. In this way, updates to the driver package and device-specific applications can be synchronized. This occurs through the finish-install actions supplied by the package's co-installer. The user can be prompted during driver package updates to update the device-specific applications. The device-specific applications are installed elsewhere on the user's hard drive. Only the driver package is copied to the driver store. For more information about digital signatures, see Driver Signing. The device installation application and associated installation files do not have to be digitally signed. Only the driver package must be digitally signed. For more information about and AutoRun and AutoRun-enabled applications, see Creating an AutoRun-Enabled Application. Independent hardware vendors (IHVs) can easily use this method to an existing AutoRun-compatible distribution medium by adding one or more INF HardwareId directives to the Autorun.inf file. This method has the following advantages:
If the wizard finds a match, it invokes the AutoRun-enabled device installation application to install the driver package and device-specific applications. When the user plugs in the device, the Found New Hardware Wizard parses this file, and looks for an INF HardwareId directive that matches the device that is being installed.
In this method, the device installation application on the distribution medium is launched as part of the processing of the Autorun.inf file. This method relies on the INF HardwareId directive, which is supported in Windows Vista and later versions of Windows. This method builds upon existing software-first installation methods to create a hardware-first installation scenario.
0 kommentar(er)
