In order to add a driver to a packaging project, users go to the Drivers view of the Visual Designer mode.
|
Note: Using the New Driver wizard from the Visual Designer View assumes that the driver data is not a part of the current package and that it is supposed to be imported as a part of driver creation. If you already have a component having necessary data and a valid KeyPath that points to the .inf file, then use the Component View inside the Advanced Designer, which allows a fine control over the existing components. |
With a click on the Create new... button, the New Driver wizard is invoked.
Work your way through the steps of the wizard to define all required properties for the new item.
At any time, using the Next or Back buttons, which are displayed at the bottom of the wizard dialog, allows to navigate within the already processed steps.
To exit the wizard without creating a new object, use the Cancel button, also located at the bottom of the wizard dialog.
Step 1: INF File
INF file
Use the browse button at the right-hand side of the INF file path info field to browse for the required driver file.
Select the INF file and click Open to use it as driver data source.
|
Note: The system browser dialog is by default opened with a type restriction, allowing to select INF files (*.inf) only. However, it is possible to add driver files of other types here as well once the file type filter is set to All files (*.*). Even though RayPack allows to do that, it is recommended for experts use only. The mechanisms of the driver wizard are optimized for inf-based drivers, and may deliver unexpected results for other driver types. |
Target platform
The target platform may be changed for drivers that are added to packaging projects with a 32-bit target platform. As soon as a package has a global target platform with a 64-bit architecture, this option is activated by default and read-only.
|
Note: It is highly recommended to keep the target platform of the driver object and the target platform of the packaging project itself closely aligned. If there are reasons to set them to different values, these circumstances should be validated and documented carefully. |
Click Next to proceed.
Step 2: Supporting Files
Automatically Determined Supporting Files
When a driver file is added, RayPack automatically reads the dependencies determined per INF file. If there is readable information about required *.sys, *.cat, *.drv, or *.dll files, this automatism adds them to the packaging project as files that depend on the newly created driver object.
Manually Add Supporting Files
If there are additional files known to be required for the driver to operate, users may add them manually. To do so, the Add button above the list of already added supporting files has to be clicked. A system browser dialog is displayed, enabling the user to select any *.sys, *.cat, *.drv, or *.dll file, and add it to the list of supporting files by clicking on the Open button.
Each new file is added to the end of the list of already added supporting files. Please be aware that the supporting files will be added to the packaging project exactly as given in the list of supporting files. Restrictions regarding required installation orders have to be meet by adding them in the correct order. Later re-adjustments are error-prone and should be avoided.
Remove Supporting Files
If a file should not be installed along with the new driver object, but has been added to the list of supporting files either manually or automatically, users have the option to remove them from that list. To do so, users select one or more files from within the list, and click on the Remove button above the list area. The Remove button is inactive as long as no file has been selected, but becomes available as soon as at least one file is currently selected.
The selected files will be removed from the list - immediately and without any intermediate confirm step.
Create Separate Components for Supporting Files
According to Best Practices, it is recommended to create a component per supporting file of a driver. These files are typically executables, which should be key path of their very own component. The checkbox for automated component creation is active by default in order to allow effortless Best Practice compliance.
Step 3: Options
Create the Add / Remove Programs entry for a driver package
If this checkbox is active, the driver will be visible within the ARP dialog of the packages target system. In order to provide transparency on the target system, it is recommended to do so.
Show the Connect Device dialog on install
It is possible to suppress the Connect Device dialog by deactivating this checkbox. If it is left active (as it is per default), the installing user will be ordered to connect a matching Plug and Play device at package run-time if the device recognition has not detected a matching device yet.
Always overwrite existing driver
If a similar driver is already present on the target system, the new driver brought along within the package will not be installed automatically. To force the installation in such a situation, this option needs to be activated manually.
Remove the binaries from system folder when the driver is being uninstalled (not recommended)
It is part of Best Practice to keep files that have been created at specific system folders during package installation, even beyond the package uninstallation. If other (vital) parts of the target device rely on these system files, their removal could cause severe harm. Therefore, it is recommended to keep this checkbox inactive. Please double-check the necessity of removing system folder files before it is actually activated.
Allow the installation of unsigned / incomplete drivers
It is not common to allow the installation of unsigned or incomplete driver packages on a device. However, there may be circumstances where it is required to do so. Activating this checkbox overrules standard system settings, which would suppress the installation of usually unfit driver packages. Please double-check the necessity of allowing this type of resource installation before this checkbox is actually activated.
Step 4: Summary
Use the summary page to check the correctness of the driver properties that were defined during the previous wizard steps.
•If all properties are set as required, click Process to finally create the driver item.
•If changes are due, click Back until the wizard step with the incorrect property definition(s) is displayed and make modifications as required.
Please note that changes in an early step may lead to different defaults or options in any later step. Therefore, please verify that all steps contain the desired settings whilst NEXTing to the summary page again.
Step 5: Finished
Once the new driver has been created, the wizard can be closed by using the Finish button at its lower right corner. The Drivers view is updated, and the list of existing items contains the newly created object at the lowest position of the installation order.