Sometimes where SetupCopyOemInf was used, an INF file contained hard-coded relative paths back to the CD drive or driver install point to provide links to additional nondriver software. Because the driver package is copied to the driver store before the driver is installed, the “installed from” location is always the driver store, not the original media or any other install point. Any assumptions about relative paths must be removed.
Using setup.exe to install print drivers by using any methods other than simply calling the INF file is not recommended. If this use is necessary, some problems with User Account Control can occur.
One of the most visible security features of Windows Vista is User Account Control. By default, all users, including administrators, run as standard users and elevate their privilege to full administrator only when necessary. Installing a new print driver requires elevated privilege unless that driver is signed by a trusted signatory. When a user installs a driver from an INF file, Windows detects that this is a privileged operation and allows the user to elevate his or her privilege level. Setup applications, however, must use an application manifest to indicate that the application requires administrative rights to run correctly. More details of this can be found in the paper titled Printer Installation in Windows Vista.
|
