Printer Driver Customization Without Certification Loss
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional printer driver customization methods risk canceling certification if even a single byte is altered, leading to unreliable driver messages during installation, making it difficult for users to determine if the issue is due to customization or a different problem.
Innovation Solution
A recording medium with a program that includes a pre-certified file, authentication information, and a default configuration file, which authenticates the file upon installation by comparing generated and stored authentication information, allowing customized configuration data to be registered in a separate storage area without altering the original driver package, thus maintaining certification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If configuration data is written directly into the driver package files, then customization is achieved, but certification is canceled and reliability deteriorates
Solution Approach 1:
The patent segments the driver system into two independent parts: the original certified driver package (maintained unchanged) and a separate configuration data file (where customization is stored). This segmentation allows customization without modifying the certified driver files, thus maintaining both adaptability and reliability.
Solution Approach 2:
The patent introduces an intermediary configuration file that acts as a mediator between user customization needs and the certified driver package. This intermediary stores customized settings and is loaded by the driver at runtime, enabling customization without direct modification of the certified driver files.
2Ease of operation
If the driver package is modified to include customized settings, then ease of operation is improved, but manufacturing precision deteriorates
Solution Approach 1:
The patent performs preliminary action by creating and storing customized configuration data in a separate file before the driver is installed or executed. This pre-configured data is then applied by the driver during operation, avoiding the need to modify the driver package itself and thus preserving manufacturing precision while achieving ease of operation.
Solution Approach 2:
The patent uses copying by creating a separate configuration data file that contains customized settings, which is then referenced and applied by the driver package. Instead of modifying the original driver files, the system copies the necessary configuration information into a dedicated external file, maintaining driver integrity while enabling customization.
3Ease of manufacture
If authentication information is not verified, then ease of manufacture is improved, but reliability worsens
Solution Approach 1:
The patent implements feedback by incorporating an authentication mechanism that verifies the integrity of the configuration data file against the driver package. This verification process ensures that customized configuration data has not been tampered with and is compatible with the driver, maintaining reliability while keeping the customization process straightforward through automated verification.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer-readable recording medium has a program recorded therein. The program includes a pre-certified file to be authenticated, an authentication information file, and a default configuration file. The program is subjected to authentication based on the comparison of authentication information generated from the file to be authenticated and the authentication information of the authentication information file when the program is installed in an information processor. The program instructs a central processing unit to execute the following steps: when a configuration file of a predetermined filename exists in the information processor, registering configuration data written in the configuration file with a first storage area different from a second storage area in which the program is stored; determining whether the configuration data are stored in the first storage area; and when it is determined that the configuration data are stored in the first storage area, reflecting the configuration data in the operation of the program.