PnP Driver Installer Reference Manual - Thesycon Systemsoftware ...

More documents

Recommendations

Info

2 Operation 2.4.2 Silent Uninstallation Command Line Parameters Parameter Description /SU The setup silently uninstalls the currently installed version, if there is any. Example: setup.exe /SU Exit codes Status Code Description Solution 0 The uninstallation finished success- - fully. "Successfully" means that the uninstallation is done as well as possible. The uninstaller may detect that the existing installation is corrupt (e.g., because the user deleted some installed files). This may prevent the uninstaller from performing all required steps or may even prevent the whole uninstallation in the worst case. Since neither the user nor any calling application can resolve such problems no error code is returned. 100 Uninstallation aborted: Another Inform the user to close all open hardware PnP installation process is currently installation wizards. If currently no wizard running on the system. is open the system probably is performing some installation steps in the background. Just wait some time. Then run setup again. 101 Uninstallation finished successfully, but a restart is required for completion. Reboot the system. 102 Uninstallation aborted: The current operating system is not supported by the uninstaller. Inform the user and abort. 103 Uninstallation aborted: Unexpected Inform the user and abort. The uninstaller error. creates a log file in the user’s temp directory. This file may help to analyze the 104 Uninstallation aborted: The current user has no administrator privileges which are required to proceed. problem. Inform the user and abort. 12 PnP Driver Installer Reference Manual
109 Uninstallation aborted: Invalid 111 command line parameters. Uninstallation aborted: The in- 123 staller/uninstaller is already running. Uninstallation aborted: setup.ini is not present or is corrupt. 126 Uninstallation aborted: Running this version of the setup application requires activation of the Demo Mode by means of the corresponding "Demo Mode Control Panel". 2.5 Signing Driver Packages 2 Operation Call the uninstaller with correct command line parameters. The user has to finish the running (un-) installation at first. Provide a correct setup.ini file. This code is only returned in the demo edition of the setup which is not delivered to the end user. It has not to be handled by a calling application. If the setup is executed in non-silent mode the information is displayed by a message box. Otherwise only an error entry is written to the log file of the setup in the user’s temp directory. A driver package consists of driver files (.sys), installation files (.inf) and further optional files (e.g. DLLs). To sign a driver package a catalog file (.cat) is created in the first step. This catalog file contains a hash value of each file belonging to the driver package. In the next step the catalog file is signed by means of a certificate. Either the signature is obtained from a WHQL submission (i.e. a submission to the Windows Hardware Quality Labs program of Microsoft) or by means of a vendor certificate (Authenticode). A WHQL submission is more expensive and a time-consuming process while a vendor signature can be created within seconds after you achieved a valid certificate from a certificate authority (CA). For further information please contact Thesycon. Note: Vendor signatures do not have any noteworthy impact on driver installations before Windows Vista. To enjoy the advantages of a signed driver package under Windows 2000, XP and corresponding server systems a WHQL signature has to be used instead. A signature may be required for the following reason: • Windows setup dialogs can be suppressed, i.e. it is possible to install a driver completely silent (with administrator privileges). • Windows Vista 64-bit and later 64-bit operating systems require signed driver packages (or at least signed driver files). Otherwise the drivers can be installed but are never loaded by the system. • Windows provides built-in drivers that may be compatible in some cases with the device to install (see section 4). Built-in drivers are always WHQL signed. Windows always prefer signed drivers when selecting the appropriate driver for a device. To solve this the driver package should be signed. Note: Before Windows 7 WHQL signed drivers are preferred over vendor-signed drivers according to the default system settings. PnP Driver Installer Reference Manual 13
Page 1: PnP Driver Installer A Customizable
Page 5 and 6: 1 Introduction 1 Introduction The P
Page 7 and 8: 2 Operation 2.1 Driver Installation
Page 9 and 10: When using this mode the following
Page 11: 126 Setup aborted: Running this ver
Page 15 and 16: 3 Customization The flag 0x00000004
Page 17 and 18: CopyFiles 3 Customization Common fi
Page 19 and 20: SubDir 3 Customization Sub-folder o
Page 21 and 22: 3 Customization the files have to b
Page 23 and 24: 3 Customization Under Windows 8 (64

PnP Driver Installer Reference Manual - Thesycon Systemsoftware ...

Create successful ePaper yourself

Delete template?

Save as template?