-->
A digitally-signed catalog file (.cat) can be used as a digital signature for an arbitrary collection of files. A catalog file contains a collection of cryptographic hashes, or thumbprints. Each thumbprint corresponds to a file that is included in the collection.
Invented for life: we want our products to spark enthusiasm, improve quality of life, and help conserve natural resources.
- Medium: Bosch Security Systems, Inc. Strongly recommends you take the action(s) described below. Low: Advisory. SecurComm Modems. RPS 1.0 Issue RPS might occasionally call and connect to a Bosch Security Systems, Inc. Control panel by using a SecurComm or StarComm modem, then drop the connection.
- Web site created using create-react-app.
- 4e) USB Dongle Driver Update: If an Allegiant USB Security Dongle will be connected to a PC running an older version of the Allegiant LTC 8059 Master Control Software or Allegiant LTC 8850 GUI software, a USB driver must first be installed on the PC. Download the file from the link below, and save it in a temporary location.
Plug and Play (PnP) device installation recognizes the signed catalog file of a driver package as the digital signature for the driver package, where each thumbprint in the catalog file corresponds to a file that is installed by the driver package. Regardless of the intended operating system, cryptographic technology is used to digitally-sign the catalog file.
PnP device installation considers the digital signature of a driver package to be invalid if any file in the driver package is altered after the driver package was signed. Such files include the INF file, the catalog file, and all files that are copied by INF CopyFiles directives. For example, even a single-byte change to correct a misspelling invalidates the digital signature. If the digital signature is invalid, you must either resubmit the driver package to the Windows Hardware Quality Labs (WHQL) for a new signature or generate a new Authenticode signature for the driver package.
Similarly, changes to a device's hardware or firmware require a revised device ID value so that the system can detect the updated device and install the correct driver. Because the revised device ID value must appear in the INF file, you must either resubmit the package to WHQL for a new signature or generate a new Authenticode signature for the driver package. You must do this even if the driver binaries do not change.
The CatalogFile directive in the INF Version section of the driver's INF file specifies the name of the catalog file for the driver package. During driver installation, the operating system uses the CatalogFile directive to identify and validate the catalog file. The system copies the catalog file to the %SystemRoot%CatRoot directory and the INF file to the %SystemRoot%Inf directory.
Guidelines for Catalog Files
Starting with Windows 2000, if the driver package installs the same binaries on all versions of Windows, the INF file can contain a single, undecorated CatalogFile directive. However, if the package installs different binaries for different versions of Windows, the INF file should contain decorated CatalogFile directives. For more information about the CatalogFile directive, see INF Version Section.
Download Bosch Security Driver Manual
If you have more than one driver package, you should create a separate catalog file for each driver package and give each catalog file a unique file name. Two unrelated driver packages cannot share a single catalog file. However, a single driver package that serves multiple devices requires only one catalog file.