Setting information update method and device driver

The method and device driver automatically update per-user printer settings based on standard settings during driver updates, addressing the inefficiency of manual specification and enhancing administrative ease.

JP7582011B2Active Publication Date: 2024-11-13OKI ELECTRIC INDUSTRY CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2021052883
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-03-26
Publication Date
2024-11-13
Estimated Expiration
2041-03-26

AI Technical Summary

Technical Problem

Existing methods require administrators to manually specify whether to update user-specific printer settings when updating printer drivers, making it difficult to reflect standard setting changes in per-user information efficiently.

Method used

A method and device driver that automatically updates per-user setting information based on standard setting information during driver updates, ensuring version consistency and allowing administrators to manage updates without additional screens.

Benefits of technology

Facilitates easy reflection of standard setting updates in user-specific settings, eliminating the need for manual specification and reducing administrative effort.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007582011000001
    Figure 0007582011000001
  • Figure 0007582011000002
    Figure 0007582011000002
  • Figure 0007582011000003
    Figure 0007582011000003
Patent Text Reader

Abstract

To easily reflect an update of standard setting information on per-user basis setting information.SOLUTION: There is provided a setting information update method of updating setting information of a device driver. The setting information includes standard setting information indicating an initial setting value and per-user basis setting information indicating a setting value designated by a user. The setting information update method includes a setting information updating step of updating the per-user basis setting information based on the standard setting information if the per-user basis setting information exists separately from the standard setting information when the device driver handles the setting information.SELECTED DRAWING: Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a setting information updating method and a device driver. [Background technology]

[0002] Device drivers are installed on a PC so that devices connected to the PC can be controlled by the operating system (for example, Windows (registered trademark), hereafter referred to as the OS). In a PC on which a printer driver, for example, is installed as a device driver, a logical printer based on that printer driver is created by the OS, and that logical printer can be selected as the print output destination in an application. The OS holds setting information indicating various printer settings as information about the logical printer, and makes it possible to print out based on that setting information.

[0003] Logical printer setting information (i.e. printer driver setting information) includes setting information that indicates the standard settings (referred to here as standard setting information) and setting information that indicates the settings for each user logged in to the OS (referred to here as per-user setting information). Of these, the standard setting information is created and maintained by the OS when the printer driver is installed on the PC. In other words, the standard setting information is setting information that indicates the initial setting values ​​(default setting values) of the logical printer. On the other hand, per-user setting information is created and maintained by the OS when a logged-in user specifies and saves setting values ​​on the driver setting screen or the like. In other words, per-user setting information is setting information that indicates the setting values ​​specified by the user.

[0004] The printer driver is designed to return the stored setting information in response to a request for setting information from an application, allowing the application to perform print output based on the setting information.

[0005] Incidentally, when only standard setting information is held as the setting information of the printer driver (logical printer) (i.e., per-user setting information has not yet been created), the printer driver returns the held standard setting information in response to a setting information inquiry from an application. On the other hand, when both standard setting information and per-user setting information are held as the setting information of the printer driver (logical printer) (i.e., per-user setting information has already been created), the printer driver returns the per-user setting information of the held standard setting information and per-user setting information in response to a setting information inquiry from an application.

[0006] In this way, when both standard setting information and per-user setting information are held, the printer driver gives priority to the per-user setting information and returns it to the application.

[0007] On the other hand, there are cases where the printer driver is updated on the PC in order to update the contents of the setting information (i.e., the setting values), etc. In this case, when the printer driver is updated, only the standard setting information is updated, and the setting information for each user is not updated.

[0008] For this reason, if per-user setting information has already been created, the contents of the setting information (i.e., the contents of the per-user setting information) cannot be updated even if the printer driver is updated.

[0009] In the past, a method was proposed in which an administrator is allowed to specify on a dedicated settings screen whether or not to reflect updates to the setting values ​​for each setting item in the standard setting information in the per-user setting information, and for setting items that are specified to be reflected, when the setting value is updated in the standard setting information, the updates to the setting values ​​are also reflected in the per-user setting information for each user (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0010] [Patent Document 1] JP 2007-122137 A Summary of the Invention [Problem to be solved by the invention]

[0011] However, with conventional methods, an administrator had to take the trouble of preparing a dedicated settings screen and specify whether or not to reflect updates to the setting values ​​for each setting item in the standard setting information in the per-user setting information, making it difficult to say that updates to the standard setting information could be easily reflected in the per-user setting information.

[0012] The present invention has been made in consideration of the above points, and aims to propose a setting information updating method and a device driver that can easily reflect updates to standard setting information in per-user setting information. [Means for solving the problem]

[0013] The setting information update method of the present invention is a setting information update method for updating setting information of a device driver, the setting information including standard setting information indicating initial setting values ​​and per-user setting information indicating setting values ​​designated by a user, The standard setting information is updated when the device driver is updated, When the device driver handles the setting information, the user setting information exists separately from the standard setting information. And the version of the user-specific setting information is different from the version of the standard setting information. In this case, The setting information update unit Update the user-specific setting information based on the standard setting information and matching the version of the per-user setting information with the version of the standard setting information. It also has a setting information updating step.

[0014] The device driver of the present invention is a device driver that is installed in a computer, and the setting information of the device driver includes standard setting information indicating initial setting values ​​and per-user setting information indicating setting values ​​designated by a user, The standard setting information is updated when the device driver is updated, When the device driver handles the setting information, the user setting information exists separately from the standard setting information. And the version of the user-specific setting information is different from the version of the standard setting information.When the user-specific setting information is updated based on the standard setting information, and matching the version of the per-user setting information with the version of the standard setting information. The processing is executed by the computer.

[0015] In this way, if per-user setting information exists at the time the device driver handles the setting information, the per-user setting information is automatically updated based on the standard setting information. This makes it possible to reflect updates to the standard setting information in the per-user setting information without the need to prepare a dedicated setting screen or for the administrator to specify whether or not to reflect updates to the setting values ​​for each setting item in the standard setting information in the per-user setting information. Effect of the Invention

[0016] The present invention can realize a setting information updating method and a device driver that can easily reflect updates to standard setting information in per-user setting information. [Brief description of the drawings]

[0017] [Figure 1] 1 is a diagram showing an overall configuration of a computer system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram showing the configuration of a DEVMODE according to the first embodiment. [Diagram 3] 2 is a block diagram showing a functional configuration of a UI module according to the first embodiment. FIG. [Figure 4] FIG. 13 is a diagram showing the configuration of a confirmation dialog according to the first embodiment. [Diagram 5] 5 is a flowchart showing the operation of a UI module according to the first embodiment. [Figure 6] FIG. 11 is a diagram illustrating an example of updating a DEVMODE according to the first embodiment. [Figure 7] FIG. 11 is a block diagram showing a functional configuration of a UI module according to a second embodiment. [Figure 8] 10 is a flowchart showing the operation of a UI module when updating a printer driver according to the second embodiment. [Figure 9] 13 is a flowchart showing an operation of a UI module when a DEVMODE is requested from an application according to the second embodiment. [Figure 10] FIG. 11 is a diagram illustrating an example of updating the DEVMODE according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, modes for carrying out the invention (hereinafter referred to as embodiments) will be described in detail with reference to the drawings.

[0019] 1. First embodiment [1-1. Overall configuration of computer system] 1 shows the overall configuration of a computer system 1 according to the first embodiment. The computer system 1 is made up of a host computer 10 and a printer 50 connected to the host computer 10. Note that the host computer 10 and the printer 50 may be directly connected by a cable, for example, or may be connected via a network such as a wired LAN or wireless LAN.

[0020] Next, the software configuration of the host computer 10 will be described with reference to Fig. 1. The host computer 10 has general hardware such as a CPU, memory, storage device, and various interfaces, and the CPU reads out a program stored in the storage device into the memory and executes it to build the software configuration shown in Fig. 1.

[0021] That is, an OS 11 and an application 12 are running on a host computer 10. In this embodiment, it is assumed that the OS 11 is Windows (registered trademark). The OS 11 has user accounts 13 for multiple users to log in. As an example, it is assumed here that the OS 11 has a user account 13A for user A, a user account 13B for user B, and a user account 13C for user C.

[0022] Furthermore, a printer driver 14 is installed in the host computer 10 so that the printer 50 can be controlled by the OS 11. The printer driver 14 is made up of a UI module 15 and a rendering module 16. In the host computer 10, a logical printer based on the printer driver 14 is created by the OS 11, and this logical printer can be selected as a print output destination on the application 12.

[0023] Furthermore, the OS 11 holds setting information indicating various settings of the printer 50 as logical printer information, and is capable of print output based on this setting information. Note that the logical printer setting information (i.e., the setting information of the printer driver 14) includes a "standard setting" DEVMODE 17 as standard setting information, and a "per user" DEVMODE 18 as per user setting information.

[0024] The "standard settings" DEVMODE 17 is setting information that is created and held by the OS 11 when the printer driver 14 is installed, and is setting information that indicates the initial settings (default setting values) of the logical printer. This "standard settings" DEVMODE 17 is held by the printer spooler service 19 of the OS 11.

[0025] On the other hand, the "per-user" DEVMODE 18 is setting information indicating settings for each user, and is created by the OS 11 when a logged-in user performs an operation to specify and save setting values ​​on a driver setting screen or the like, and is stored in association with the user account 13 of that user. For this reason, the "per-user" DEVMODE 18 does not exist for users who have not performed an operation to specify and save setting values.

[0026] In the example shown in Fig. 1, for users A and B, the operation of specifying and saving setting values ​​has been performed, and therefore "per-user" DEVMODEs 18A and 18B are held in association with the respective user accounts 13A and 13B. On the other hand, for user C, the operation of specifying and saving setting values ​​has not been performed, and therefore "per-user" DEVMODE 18 is not held.

[0027] In this way, the OS 11 holds one “standard setting” DEVMODE 17 and “per-user” DEVMODEs 18 (18A, 18B) for each user as setting information (DEVMODE) for a logical printer based on the printer driver 14.

[0028] 2 shows the configurations of the "standard settings" DEVMODE 17 and the "per-user" DEVMODE 18. The "standard settings" DEVMODE 17 and the "per-user" DEVMODE 18 have the same configuration, and each is made up of a basic DEVMODE area 30 and an extended DEVMODE area 31.

[0029] The basic DEVMODE area 30 mainly includes setting values ​​corresponding to functions commonly provided in general printers, such as paper size, paper feed location, and whether or not double-sided printing is enabled.

[0030] In contrast, the extended DEVMODE area 31 mainly contains setting values ​​corresponding to unique functions (such as model-specific functions) other than the functions commonly provided in general printers. Specifically, it contains setting values ​​indicating the presence or absence of toner save, color adjustment values, etc. In addition, the extended DEVMODE area 31 contains an initial value version indicating the version of the DEVMODE as a setting value. This initial value version will be described in detail later.

[0031] Returning to FIG. 1, the application 12 performs printing processing by the printer driver 14 via a DDI (Device Driver Interface) 20, which is part of the OS 11. At this time, the application 12 uses a DocumentProperties function 21 included in the DDI 20 to make a print setting request (i.e., a DEVMODE request) to a UI module 15 of the printer driver 14. The application 12 also performs drawing processing on a rendering module 16 of the printer driver 14 to give print output instructions (instructions to create and transmit print data) to the printer 50.

[0032] When print settings are requested by the application 12, the UI module 15 of the printer driver 14 responds by returning either the "standard settings" DEVMODE 17 or the "per-user" DEVMODE 18. At this time, if a "per-user" DEVMODE 18 has not yet been created for the logged-in user, the UI module 15 returns the "standard settings" DEVMODE 17. On the other hand, if a "per-user" DEVMODE 18 has already been created for the logged-in user, the UI module 15 returns the "per-user" DEVMODE 18.

[0033] In this way, in the case of a user for whom a "per-user" DEVMODE 18 has already been created, the UI module 15 of the printer driver 14 returns the "per-user" DEVMODE 18 to the application 12 with priority.

[0034] Incidentally, in order to update the settings (i.e., default setting values) of the "standard settings" DEVMODE 17, the printer driver 14 may be updated on the host computer 10. Here, when updating only the printer driver 14 without deleting the logical printer, only the "standard settings" DEVMODE 17 is updated (i.e., upgraded), and the "per-user" DEVMODE 18 is not updated.

[0035] In other words, for a user for whom a "per-user" DEVMODE 18 has already been created, when updating the printer driver 14, the updates to the "standard settings" DEVMODE 17 cannot be reflected in the "per-user" DEVMODE 18.

[0036] Therefore, in this embodiment, when the "standard settings" DEVMODE 17 is updated (upgraded) by updating the printer driver 14, the UI module 15 of the printer driver 14 reflects the updated contents of the "standard settings" DEVMODE 17 in the "per-user" DEVMODE 18 when print settings are requested by the application 12, and then returns the "per-user" DEVMODE 18 to the application 12.

[0037] That is, in this embodiment, the UI module 15 of the printer driver 14 has a function for reflecting the update contents of the “standard setting” DEVMODE 17 in the “per user” DEVMODE 18 .

[0038] 3 shows the functional configuration of the UI module 15 of the printer driver 14. The UI module 15 has a DEVMODE selection processing unit 40, an initial value version acquisition / determination unit 41, and a "per user" DEVMODE update processing unit 42. The UI module 15 also holds a driver initial value DEVMODE 43 that is the basis of the "standard setting" DEVMODE 17. When the printer driver 14 is updated, the setting contents of the driver initial value DEVMODE 43 included in the new version of the printer driver 14 are overwritten onto the "standard setting" DEVMODE 17, thereby updating (upgrading) the "standard setting" DEVMODE 17.

[0039] The DEVMODE selection processing unit 40 is a processing unit of the DrvDocumentPropertySheets function 44 which serves as a receiving port on the printer driver 14 side for the DDI 20, and selects either the "standard settings" DEVMODE 17 or the "per-user" DEVMODE 18 as the DEVMODE to be returned using the DrvDocumentPropertySheets function 44 in response to a print setting request from the application 12. Specifically, the DEVMODE selection processing unit 40 selects the "standard settings" DEVMODE 17 if the "per-user" DEVMODE 18 for the logged-in user has not yet been created, and selects the "per-user" DEVMODE 18 if the "per-user" DEVMODE 18 for the logged-in user has already been created.

[0040] The initial value version acquisition / determination unit 41 determines whether there is a difference between the driver definition initial value version included in the driver initial value DEVMODE 43 and the initial value version included in the "per user" DEVMODE 18. The driver definition initial value version included in the driver initial value DEVMODE 43 indicates the initial value version of the "standard setting" DEVMODE 17 held by the printer spooler service 19.

[0041] In other words, if the driver definition initial value version included in the driver initial value DEVMODE 43 matches the initial value version included in the "per-user" DEVMODE 18, it means that the versions of the "standard setting" DEVMODE 17 and the "per-user" DEVMODE 18 match. On the other hand, if the driver definition initial value version included in the driver initial value DEVMODE 43 does not match the initial value version included in the "per-user" DEVMODE 18, it means that the versions of the "standard setting" DEVMODE 17 and the "per-user" DEVMODE 18 do not match, that is, the "standard setting" DEVMODE 17 has been updated (upgraded) by updating the printer driver 14, but the update has not yet been reflected in the "per-user" DEVMODE 18.

[0042] If a "per-user" DEVMODE 18 has already been created for the logged-in user and the initial value version acquisition / determination unit 41 determines that the driver definition initial value version contained in the driver initial value DEVMODE 43 (i.e., the initial value version of the "standard setting" DEVMODE 17) does not match the initial value version contained in the "per-user" DEVMODE 18, the "per-user" DEVMODE update processing unit 42 updates the "per-user" DEVMODE 18 based on the settings of the driver initial value DEVMODE 43 (i.e., based on the settings of the "standard setting" DEVMODE 17). This causes the update contents of the "standard setting" DEVMODE 17 to be reflected in the "per-user" DEVMODE 18.

[0043] In addition, the “per-user” DEVMODE update processing unit 42 also has the function of a confirmation dialog display unit 45 that displays a confirmation dialog on a display unit (not shown) to notify the user when updating the “per-user” DEVMODE 18 (i.e., overwriting and updating the print settings).

[0044] 4 shows the configuration of the confirmation dialog 46 displayed by the confirmation dialog display unit 45. The confirmation dialog 46 displays a message Ms1 notifying the user that the default setting values ​​(i.e., the "standard settings" DEVMODE 17) have been updated as a result of updating the printer driver 14, and asking whether or not to reflect the updates in the saved setting values ​​(i.e., the "per user" DEVMODE 18), as well as an OK button Bt1 and a cancel button Bt2.

[0045] When the OK button Bt1 in the confirmation dialog 46 is pressed, the "per-user" DEVMODE update processing unit 42 terminates the display of the confirmation dialog 46 and executes processing to reflect the update contents of the "standard settings" DEVMODE 17 in the "per-user" DEVMODE 18. In contrast, when the cancel button Bt2 in the confirmation dialog 46 is pressed, the "per-user" DEVMODE update processing unit 42 terminates the display of the confirmation dialog 46 without reflecting the update contents of the "standard settings" DEVMODE 17 in the "per-user" DEVMODE 18.

[0046] Furthermore, when the Cancel button Bt2 is pressed, the "per-user" DEVMODE update processing unit 42 only executes the process of updating the initial value version of the "per-user" DEVMODE 18 with the driver defined initial value version of the driver initial value DEVMODE 43 (i.e. the initial value version of the "standard settings" DEVMODE 17). As a result, when the Cancel button Bt2 is pressed, the initial value version of the "standard settings" DEVMODE 17 and the initial value version of the "per-user" DEVMODE 18 will match, and thereafter the confirmation dialog 46 will not be displayed until the printer driver 14 is updated again. The software configuration of the host computer 10 is as described above.

[0047] [1-2. Host computer operation] Next, the operation of the host computer 10 when the UI module 15 of the printer driver 14 receives a request for print settings (i.e., DEVMODE) by the application 12 calling the DocumentProperties function 21 of the DDI 20 will be described in detail with reference to the flowchart shown in Fig. 5. This operation is performed by the UI module 15 of the printer driver 14.

[0048] First, when the application 12 running on the user account 13A of the logged-in user performs printing, it calls the DocumentProperties function 21 of the DDI 20 to reflect the current print settings in the print job. By calling the DocumentProperties function 21, the DEVMODE selection processing unit 40 of the UI module 15 of the printer driver 14 starts processing the DrvDocumentPropertySheets function 44, and the process proceeds to step SP1.

[0049] In step SP1, the DEVMODE selection processing unit 40 of the UI module 15 attempts to acquire the “per-user” DEVMODE 18 of the logged-in user by using the GetPrinterAPI, which is an API of the OS 11.

[0050] In the following step SP2, the DEVMODE selection processing unit 40 determines whether or not acquisition of the "per-user" DEVMODE 18 was successful. If acquisition of the "per-user" DEVMODE 18 has failed because the "per-user" DEVMODE 18 has not yet been created, the DEVMODE selection processing unit 40 obtains a negative result in step SP2, moves to step SP12, selects the "standard settings" DEVMODE 17, and returns this to the application 12, thereby ending the series of operations.

[0051] On the other hand, if the acquisition of the "per-user" DEVMODE 18 is successful because the "per-user" DEVMODE 18 has already been created, the DEVMODE selection processing unit 40 obtains a negative result in step SP2 and proceeds to step SP3.

[0052] In step SP3, the initial value version acquisition / determination unit 41 of the UI module 15 acquires the initial value version from the acquired "per user" DEVMODE 18, and proceeds to step SP4.

[0053] In step SP4, the initial value version acquisition / determination unit 41 acquires the driver definition initial value version (that is, the initial value version of the "standard setting" DEVMODE 17) from the driver initial value DEVMODE 43 of the printer driver 14, and proceeds to step SP5.

[0054] In step SP5, the initial value version acquisition and judgment unit 41 compares the initial value version of the "per-user" DEVMODE 18 with the driver-defined initial value version of the driver initial value DEVMODE 43, and judges whether they match. Here, if the initial value version of the "per-user" DEVMODE 18 matches the driver-defined initial value version of the driver initial value DEVMODE 43, this means that the versions of the "standard setting" DEVMODE 17 and the "per-user" DEVMODE 18 match. In this case, the initial value version acquisition and judgment unit 41 obtains a positive result in step SP5, and proceeds to step SP9. In step SP9, the DEVMODE selection processing unit 40 selects the "per-user" DEVMODE 18, returns it to the application 12, and ends the series of operations.

[0055] On the other hand, if the initial value version of the "per-user" DEVMODE 18 does not match the driver definition initial value version of the driver initial value DEVMODE 43, this means that the versions of the "standard setting" DEVMODE 17 and the "per-user" DEVMODE 18 do not match, that is, the "standard setting" DEVMODE 17 has been updated (upgraded) by updating the printer driver 14, but the update contents have not yet been reflected in the "per-user" DEVMODE 18. In this case, the initial value version acquisition / determination unit 41 obtains a negative result in step SP5 and proceeds to step SP6.

[0056] In step SP6, the "per-user" DEVMODE update processing unit 42 causes the confirmation dialog display unit 45 to display the confirmation dialog 46 on the display unit, and proceeds to step SP7. In step SP7, the "per-user" DEVMODE update processing unit 42 determines whether or not the OK button Bt1 on the confirmation dialog 46 has been pressed. If the OK button Bt1 has been pressed, the "per-user" DEVMODE update processing unit 42 obtains a positive result in step SP7, and proceeds to step SP8.

[0057] In step SP8, the "per-user" DEVMODE update processing unit 42 overwrites and updates the "per-user" DEVMODE 18 using the SetPrinterAPI, an API of OS 11, based on the setting contents of the driver initial value DEVMODE 43. Specifically, based on the setting contents of the driver initial value DEVMODE 43, the setting contents of the "per-user" DEVMODE 18 are updated so as to be identical to the setting contents of the "standard setting" DEVMODE 17. As a result, the update contents of the "standard setting" DEVMODE 17 are reflected in the "per-user" DEVMODE 18. At this time, the initial value version of the "per-user" DEVMODE 18 becomes identical to the initial value version of the "standard setting" DEVMODE 17.

[0058] In the next step SP9, the DEVMODE selection processing unit 40 selects the "per user" DEVMODE 18 and returns it to the application 12, thereby completing the series of operations.

[0059] On the other hand, if the cancel button Bt2 in the confirmation dialog 46 is pressed, the "per-user" DEVMODE update processing unit 42 obtains a negative result in step SP7 and proceeds to step SP10. In step SP10, the "per-user" DEVMODE update processing unit 42 copies the "per-user" DEVMODE 18 to a memory area, and overwrites the initial value version of the "per-user" DEVMODE 18 in the memory area with the driver-defined initial value version of the driver initial value DEVMODE 43 (i.e., the initial value version of the "standard setting" DEVMODE 17). Furthermore, in the following step SP11, the "per-user" DEVMODE update processing unit 42 overwrites and updates the "per-user" DEVMODE 18 held in the OS 11 with the "per-user" DEVMODE 18 whose initial value version has been overwritten by the SetPrinterAPI. As a result, the initial value version of the "per-user" DEVMODE 18 becomes consistent with the initial value version of the "standard setting" DEVMODE 17.

[0060] In the next step SP9, the DEVMODE selection processing unit 40 selects the "per user" DEVMODE 18 and returns it to the application 12, thus completing the series of operations. The above is the operation of the UI module 15 of the printer driver 14 when the application 12 calls the DocumentProperties function 21 of the DDI 20 to request print settings (i.e., the DEVMODE).

[0061] In the above-described series of operations, only the "per-user" DEVMODE 18 of the logged-in user is updated, and the "per-user" DEVMODE 18 of other users is not updated. The "per-user" DEVMODE 18 of other users is updated by performing the above-described series of operations when the other users log in.

[0062] Here, how the DEVMODE is updated by the series of operations described above will be briefly explained using an example shown in FIG.

[0063] The example shown in FIG. 6 shows a case where the setting value for double-sided printing included in the “standard settings” DEVMODE 17 has been updated from “none” to “long-edge binding” due to an update of the printer driver 14.

[0064] Here, if the "per-user" DEVMODE 18 for the logged-in user has not yet been created (i.e., has not been saved), the DEVMODE returned from the printer driver 14 to the application 12 will be the updated "standard settings" DEVMODE 17 (i.e., the "standard settings" DEVMODE 17 of the new version). In this regard, the same results will be obtained whether the above-mentioned series of operations is not performed (conventional) or is performed (this embodiment).

[0065] In contrast, if a "per-user" DEVMODE 18 has already been created for the logged-in user (i.e., if it has been saved), the DEVMODE returned from the printer driver 14 to the application 12 will be the "per-user" DEVMODE 18, but the settings of the "per-user" DEVMODE 18 differ depending on whether the above-mentioned series of operations is not performed (conventional method) or whether the above-mentioned series of operations is performed (this embodiment).

[0066] In the "per user" DEVMODE 18, it is assumed that the setting value for double-sided printing is designated by the user as "short edge binding", for example.

[0067] Here, if the above-described series of operations is not performed (as in the past), updates to the "standard settings" DEVMODE 17 are not reflected in the "per-user" DEVMODE 18, and therefore even though the double-sided printing setting value has been updated from "none" to "long edge binding" in the "standard settings" DEVMODE 17, the double-sided printing setting value remains "short edge binding" in the "per-user" DEVMODE 18, and this "per-user" DEVMODE 18 is returned to the application 12.

[0068] On the other hand, when the above-mentioned series of operations is performed (this embodiment), the update contents of the "standard settings" DEVMODE 17 are reflected in the "per-user" DEVMODE 18, so that as the double-sided printing setting value in the "standard settings" DEVMODE 17 is updated from "none" to "long-edge binding", the double-sided printing setting value in the "per-user" DEVMODE 18 is also updated from "short-edge binding" to "long-edge binding", and the updated "per-user" DEVMODE 18 is returned to the application 12.

[0069] In this embodiment, all of the settings in the "standard settings" DEVMODE 17 are copied to the "per-user" DEVMODE 18, so for example, the paper size setting value in the "standard settings" DEVMODE 17 is not updated when the "standard settings" DEVMODE 17 is upgraded (i.e., it remains at "A4"), but is reflected in the "per-user" DEVMODE 18.

[0070] [1-3. Summary and Effects] As described above, in the first embodiment, the setting information of the printer driver 14 held by the OS 11 of the host computer 10 includes a "standard setting" DEVMODE 17 as standard setting information indicating initial setting values, and a "per-user" DEVMODE 18 as per-user setting information indicating setting values ​​specified by the user. When a DEVMODE is requested from an application 12, if a "per-user" DEVMODE 18 is held in addition to the "standard setting" DEVMODE 17, the "per-user" DEVMODE update processing unit 42, which serves as a setting information update unit of the printer driver 14, updates the "per-user" DEVMODE 18 based on the "standard setting" DEVMODE 17 (specifically, based on the driver initial value DEVMODE 43 on which the "standard setting" DEVMODE 17 is based), and returns the updated "per-user" DEVMODE 18 to the application 12.

[0071] In other words, when a DEVMODE is requested by an application 12, if the "per-user" DEVMODE 18 of the logged-in user is held and the initial value version of the "per-user" DEVMODE 18 differs from the initial value version of the "standard setting" DEVMODE 17 (specifically, the driver-defined initial value version of the driver initial value DEVMODE 43), the "per-user" DEVMODE update processing unit 42 overwrites and updates each corresponding setting value of the "per-user" DEVMODE 18 of the logged-in user with each setting value of the "standard setting" DEVMODE 17.

[0072] In this way, in the first embodiment, it is possible to reflect updates to the "standard settings" DEVMODE 17 for each user in the "per-user" DEVMODE 18, without the need to prepare a dedicated setting screen or for the administrator to specify whether or not updates to the setting values ​​for each setting item of the "standard settings" DEVMODE 17 should be reflected in the "per-user" DEVMODE 18. Thus, in the first embodiment, updates to the "standard settings" DEVMODE 17 can be easily reflected in the "per-user" DEVMODE 18.

[0073] Furthermore, in the first embodiment, before the "per-user" DEVMODE update processing unit 42 updates the "per-user" DEVMODE 18, the confirmation dialog display unit 45 displays a confirmation dialog 46 on a display unit (not shown), and when an operation to permit updating of the "per-user" DEVMODE 18 is performed on the confirmation dialog 46 (pressing the OK button Bt1), the "per-user" DEVMODE 18 is updated based on the "standard settings" DEVMODE 17. At this time, the initial value version of the "per-user" DEVMODE 18 is overwritten and updated with the initial value version of the "standard settings" DEVMODE 17.

[0074] On the other hand, if an operation is performed on the confirmation dialog 46 to not allow the update of the “per-user” DEVMODE 18 (pressing the Cancel button Bt2), the “per-user” DEVMODE update processing unit 42 overwrites and updates only the initial value version of the “per-user” DEVMODE 18 with the initial value version of the “standard setting” DEVMODE 17.

[0075] By doing this, in the first embodiment, each user can select whether or not to reflect updates to the "standard setting" DEVMODE 17 in the "per user" DEVMODE 18, and the "per user" DEVMODE 18 can be updated for each user, or used as is without updating. Also, if a user performs an operation in the confirmation dialog 46 to not allow updates to the "per user" DEVMODE 18, the confirmation dialog 46 will not be displayed thereafter while the user is logged in until the printer driver 14 is updated, making it possible to avoid a situation in which the confirmation dialog 46 is displayed multiple times each time printing is performed with the application 12.

[0076] 2. Second embodiment Next, a second embodiment will be described. This second embodiment is different from the first embodiment in the method of reflecting updates to the "standard settings" DEVMODE 17 in the "per-user" DEVMODE 18. Specifically, in the first embodiment, all of the setting contents of the "standard settings" DEVMODE 17 are copied to the "per-user" DEVMODE 18. In other words, in the first embodiment, each setting value of the updated "standard settings" DEVMODE 17 matches each setting value of the updated "per-user" DEVMODE 18.

[0077] In contrast, in the second embodiment, among the setting values ​​(i.e., the default setting values) included in the "standard setting" DEVMODE 17, only the setting values ​​that are updated when the "standard setting" DEVMODE 17 is upgraded are reflected in the "per-user" DEVMODE 18.

[0078] In this second embodiment, the functional configuration of the UI module 15 of the printer driver 14 is different from that of the first embodiment, but the other configurations are the same as those of the first embodiment. Therefore, the functional configuration of the UI module 15 will be described first. In the following description, the UI module 15 of the second embodiment will be referred to as UI module 15X to distinguish it from the first embodiment.

[0079] [2-1. Functional configuration of UI module] 7 shows the functional configuration of the UI module 15X. In addition to the configuration of the UI module 15 of the first embodiment, the UI module 15X has a previous version "standard setting" DEVMODE acquisition unit 100, a mask data creation processing unit 101, and a mask data / DEVMODE merge processing unit 102. Furthermore, the UI module 15X holds DEVMODE mask data 103 (described later) created by the mask data creation processing unit 101.

[0080] The previous version "standard settings" DEVMODE acquisition unit 100 acquires the previous version "standard settings" DEVMODE 17 when updating the printer driver 14 (i.e., when upgrading the "standard settings" DEVMODE 17). Note that the previous version "standard settings" DEVMODE 17 is still held by the printer spooler service 19 and can be acquired immediately after installation of the new version of the printer driver 14 has begun.

[0081] The mask data creation processing unit 101 creates DEVMODE mask data 103. Specifically, the mask data creation processing unit 101 creates DEVMODE mask data 103 that indicates which setting values ​​of the "standard settings" DEVMODE 17 of the new version have been updated from the "standard settings" DEVMODE 17 of the previous version. In other words, the DEVMODE mask data 103 is data that indicates which setting values ​​of the "standard settings" DEVMODE 17 have been updated by updating the printer driver 14.

[0082] The mask data / DEVMODE merge processing unit 102 merges the DEVMODE mask data 103 created by the mask data creation processing unit 101, the "standard settings" DEVMODE 17 updated by updating the printer driver 14 (i.e., the new version of the "standard settings" DEVMODE 17), and the "per-user" DEVMODE 18. The merging method will be described in detail later, but by merging the DEVMODE mask data 103, the "standard settings" DEVMODE 17 updated by updating the printer driver 14, and the "per-user" DEVMODE 18, it becomes possible to reflect, among the setting values ​​of the "standard settings" DEVMODE 17, only those setting values ​​updated by updating the printer driver 14, in the "per-user" DEVMODE 18. The functional configuration of the UI module 15X is as described above.

[0083] [2-2. Host computer operation] Next, the operation of the host computer 10 will be described in order, including the operation when updating the printer driver 14 (i.e., installing a new version of the printer driver 14) and the operation when, after updating the printer driver 14, the UI module 15X receives a request for print settings (i.e., DEVMODE) from the application 12 by calling the DocumentProperties function 21 of the DDI 20.

[0084] First, the operation when updating the printer driver 14 (i.e., installing a new version of the printer driver 14) will be described with reference to the flowchart shown in Fig. 8. Note that this operation is performed by the UI module 15X of the new version of the printer driver 14.

[0085] When updating printer driver 14 (that is, when installing a new version of printer driver 14), UI module 15X of the new version of printer driver 14 is requested by OS 11 to use the “standard settings” DEVMODE 17 of the new version.

[0086] Here, in step SP100 immediately before the UI module 15X returns the driver initial value DEVMODE43 as the “standard setting” DEVMODE17 of the new version, the previous version “standard setting” DEVMODE acquisition unit 100 acquires the previous version’s “standard setting” DEVMODE17 from the printer spooler service 19.

[0087] In the next step SP101, the mask data creation processing unit 101 sets the leading addresses for the driver initial value DEVMODE43, the “standard setting” DEVMODE17 of the previous version, and the DEVMODE mask data 103, respectively.

[0088] Here, the driver initial value DEVMODE43 and the previous version's "standard settings" DEVMODE17 have a common structure in which, for example, N setting values ​​are arranged in a predetermined order, and each setting value is represented by, for example, 8 bits (1 byte). Therefore, by setting a top address for each of the driver initial value DEVMODE43 and the previous version's "standard settings" DEVMODE17, each setting value of the driver initial value DEVMODE43 and each setting value of the previous version's "standard settings" DEVMODE17 are associated with each other by the number of bytes from the top address.

[0089] On the other hand, the DEVMODE mask data 103 has a structure in which N one-byte mask values, each of which indicates whether the setting value of the driver initial value DEVMODE43 matches or differs from the setting value of the "standard setting" DEVMODE17 of the previous version, are arranged, the same number as the number of setting values ​​of the driver initial value DEVMODE43 and the "standard setting" DEVMODE17 of the previous version. Therefore, by setting a top address for the DEVMODE mask data 103, the setting values ​​of the driver initial value DEVMODE43, the setting values ​​of the "standard setting" DEVMODE17 of the previous version, and the mask values ​​of the DEVMODE mask data 103 are associated with each other by the number of bytes from the top address.

[0090] Note that each mask value of the DEVMODE mask data 103 is "FF" if the setting value of the driver initial value DEVMODE43 matches the setting value of the "standard setting" DEVMODE17 of the previous version, and is "00" if they differ. However, at this point, the setting value of the driver initial value DEVMODE43 has not yet been compared with the setting value of the "standard setting" DEVMODE17 of the previous version, so all mask values ​​are "-" (null).

[0091] In the following step SP102, the mask data creation processing unit 101 compares the current address value of the driver initial value DEVMODE43 (i.e., the nth setting value (1≦n≦N)) with the current address value of the previous version's "standard setting" DEVMODE17 (i.e., the nth setting value (1≦n≦N)), and determines whether they match.

[0092] Here, if the value of the current address of the driver initial value DEVMODE43 is different from the value of the current address of the "standard setting" DEVMODE17 of the previous version, this means that the n-th setting value of the driver initial value DEVMODE43 is different from the n-th setting value of the "standard setting" DEVMODE17 of the previous version. In this case, the mask data creation processing unit 101 obtains a negative result in step SP102, proceeds to step SP103, sets the current address value of the DEVMODE mask data 103 (i.e., the n-th mask value (1≦n≦N)) to "00", and proceeds to step SP105. Note that the initial value version of the driver initial value DEVMODE43 (i.e., the initial value version of the "standard setting" DEVMODE17 of the new version) and the initial value version of the "standard setting" DEVMODE17 of the previous version are necessarily different, so the mask value for the initial value version may be fixed to "00", for example.

[0093] On the other hand, if the current address value of the driver initial value DEVMODE 43 matches the current address value of the previous version's "standard setting" DEVMODE 17, this means that the nth setting value of the driver initial value DEVMODE 43 matches the nth setting value of the previous version's "standard setting" DEVMODE 17. In this case, the mask data creation processing unit 101 obtains a positive result in step SP102, proceeds to step SP104, sets the current address value of the DEVMODE mask data 103 (i.e., the nth mask value (1≦n≦N)) to "FF", and proceeds to step SP105.

[0094] In step SP105, the mask data creation processing unit 101 adds one byte to the addresses of the driver initial value DEVMODE43, the previous version's "standard setting" DEVMODE17, and the DEVMODE mask data 103 (i.e., sets n=n+1 and moves to the next setting value), and then proceeds to step SP106.

[0095] In step SP106, the mask data creation processing unit 101 judges whether or not the current addresses of the driver initial value DEVMODE43, the previous version's "standard setting" DEVMODE17, and the DEVMODE mask data 103 have exceeded the final addresses. If the current addresses have not exceeded the final addresses, this means that there are setting values ​​that have not yet been compared in the driver initial value DEVMODE43 and the previous version's "standard setting" DEVMODE17. In this case, the mask data creation processing unit 101 obtains a negative result in step SP106, returns to step SP102, and continues comparing the setting values.

[0096] On the other hand, if the current addresses of the driver initial value DEVMODE43, the "standard setting" DEVMODE17 of the previous version, and the DEVMODE mask data 103 exceed the final addresses, this means that all of the setting values ​​of the driver initial value DEVMODE43 and the "standard setting" DEVMODE17 of the previous version have been compared, and the DEVMODE mask data 103 has been completed. In this case, the mask data creation processing unit 101 obtains a positive result in step SP106, proceeds to step SP107, and holds the completed DEVMODE mask data 103.

[0097] In the next step SP108, the DEVMODE selection processing unit 40 returns the driver initial value DEVMODE 43 to the OS 11 as the "standard setting" DEVMODE 17 of the new version, and ends the series of operations. The operations when updating the printer driver 14 (i.e., installing a new version of the printer driver 14) are as described above.

[0098] In this way, when updating the printer driver 14, the mask data creation processing unit 101 of the UI module 15X compares each setting value of the driver initial value DEVMODE43 that is the basis of the new version's "standard settings" DEVMODE17 with each setting value of the previous version's "standard settings" DEVMODE17, and creates DEVMODE mask data 103 that indicates which setting values ​​of the new version's "standard settings" DEVMODE17 have been updated from the previous version's "standard settings" DEVMODE17.

[0099] Next, the operation when the UI module 15X receives a request for print settings (i.e., DEVMODE) from the application 12 by calling the DocumentProperties function 21 of the DDI 20 after updating the printer driver 14 will be described using the flowchart shown in Fig. 9. Note that the operation shown in Fig. 9 is obtained by replacing the processing of step SP8 (i.e., the processing after the OK button Bt1 is pressed in the confirmation dialog 46) of the operation shown in Fig. 5 described in the first embodiment with the processing of steps SP200, SP201, and SP202. Therefore, the processing of steps SP200, SP201, and SP202 will be mainly described here.

[0100] As a result of the processing of steps SP1 to SP7, the UI module 15X determines that the initial version of the “per-user” DEVMODE 18 of the logged-in user is different from the initial version of the “standard setting” DEVMODE 17, and therefore causes a confirmation dialog 46 to be displayed on the display unit to prompt the user to select whether or not to update the “per-user” DEVMODE 18, and determines that the OK button Bt1 on the confirmation dialog 46 has been pressed by the user.

[0101] At this time, the UI module 15X obtains a positive result in step SP7, and proceeds to step SP200. In step SP200, the mask data / DEVMODE merge processing unit 102 of the UI module 15X copies the "per user" DEVMODE 18 to the memory area.

[0102] In the next step SP201, the mask data / DEVMODE merge processing unit 102 merges in the memory area the DEVMODE mask data 103 created and stored when the printer driver 14 is updated, the driver initial value DEVMODE43 that is the basis of the "standard setting" DEVMODE17 updated (upgraded) by updating the printer driver 14, and the "per-user" DEVMODE18, and creates the merged result as a new "per-user" DEVMODE18.

[0103] Specifically, each setting value of the driver initial value DEVMODE 43 is A, each mask value of the DEVMODE mask data 103 is B, and each setting value of the "per-user" DEVMODE 18 is C, and an Aor(BandC) calculation is performed for each setting value, and the result of the calculation is set as the new C (i.e., each setting value of the "per-user" DEVMODE 18). In the following step SP202, the "per-user" DEVMODE update processing unit 42 overwrites and updates the "per-user" DEVMODE 18 held in the OS 11 with the new "per-user" DEVMODE 18 by using the SetPrinterAPI.

[0104] In this way, the "per-user" DEVMODE update processing unit 42 merges the DEVMODE mask data 103, the driver initial value DEVMODE 43, and the "per-user" DEVMODE 18 using the mask data / DEVMODE merge processing unit 102, thereby overwriting and updating the corresponding setting values ​​of the per-user "DEVMODE 18" with setting values ​​of the driver initial value DEVMODE 43 whose corresponding mask value is "00" (i.e., default setting values ​​updated when the "standard setting" DEVMODE 17 is upgraded). In this way, of the setting values ​​of the "standard setting" DEVMODE 17, only the default setting values ​​updated when the "standard setting" DEVMODE 17 is upgraded are reflected in the per-user "DEVMODE 18".

[0105] In the next step SP9, the DEVMODE selection processing unit 40 selects the "per user" DEVMODE 18 and returns it to the application 12, thereby completing the series of operations. The above is the operation of the UI module 15X of the printer driver 14 when the application 12 calls the DocumentProperties function 21 of the DDI 20 to request print settings (i.e., a DEVMODE).

[0106] Here, how the DEVMODE is updated by the series of operations described above will be briefly explained using an example shown in FIG.

[0107] The example shown in FIG. 10 shows a case where the setting value for double-sided printing in the “standard setting” DEVMODE 17 is updated from “none” to “long-edge binding” due to an update of the printer driver 14.

[0108] Here, if the "per-user" DEVMODE 18 for the logged-in user has not yet been created (i.e., has not been saved), the DEVMODE returned from the printer driver 14 to the application 12 will be the updated "standard settings" DEVMODE 17 (i.e., the "standard settings" DEVMODE 17 of the new version). This is the same as in the first embodiment.

[0109] In contrast, if a "per-user" DEVMODE 18 has already been created for the logged-in user (i.e., if it has been saved), the DEVMODE returned from the printer driver 14 to the application 12 will be the "per-user" DEVMODE 18, but the settings of the "per-user" DEVMODE 18 differ depending on whether the above-mentioned series of operations is not performed (conventional method) or whether the above-mentioned series of operations is performed (this embodiment).

[0110] In the "per user" DEVMODE 18, it is assumed that the user has specified, for example, the setting value of the paper size to be "A3" and the setting value of the double-sided printing to be "short edge binding".

[0111] Here, if the above-described series of operations is not performed (as in the past), updates to the "standard settings" DEVMODE 17 are not reflected in the "per-user" DEVMODE 18, and therefore even though the double-sided printing setting value has been updated from "none" to "long edge binding" in the "standard settings" DEVMODE 17, the double-sided printing setting value remains "short edge binding" in the "per-user" DEVMODE 18, and this "per-user" DEVMODE 18 is returned to the application 12.

[0112] On the other hand, when the above-described series of operations is performed (this embodiment), the updates to the "standard settings" DEVMODE 17 are reflected in the "per-user" DEVMODE 18, so that as the double-sided printing setting value in the "standard settings" DEVMODE 17 is updated from "none" to "long edge binding", the double-sided printing setting value in the "per-user" DEVMODE 18 is also updated from "short edge binding" to "long edge binding", and the updated "per-user" DEVMODE 18 is returned to the application 12.

[0113] Incidentally, in the first embodiment, all of the setting contents of the "standard settings" DEVMODE 17 are copied to the "per-user" DEVMODE 18, so that among the setting values ​​of the "standard settings" DEVMODE 17, even setting values ​​that have not been updated when the "standard settings" DEVMODE 17 is upgraded (for example, the default setting value of paper size "A4") are also reflected in the "per-user" DEVMODE 18.

[0114] For this reason, depending on the user, after updating the "per user" DEVMODE18, it may be necessary to perform operations such as changing the paper size setting from "A4" to "A3" again.

[0115] Therefore, in this embodiment, among the setting values ​​of the "standard setting" DEVMODE 17, only the setting values ​​updated when the "standard setting" DEVMODE 17 is upgraded are reflected in the "per user" DEVMODE 18.

[0116] By doing this, as shown in Figure 10, of the setting values ​​of the "standard settings" DEVMODE 17, only the setting values ​​that were updated when the "standard settings" DEVMODE 17 was upgraded (for example, the default setting value for double-sided printing, "long edge binding") are reflected in the "per-user" DEVMODE 18, and setting values ​​that were not updated when the "standard settings" DEVMODE 17 was upgraded (for example, the default setting value for paper size, "A4") are not reflected in the "per-user" DEVMODE 18 (i.e., they remain at "A3").

[0117] This arrangement minimizes the need for the user to change the paper size setting from "A4" to "A3" again after updating the "per-user" DEVMODE 18, thereby improving convenience.

[0118] [2-3. Summary and Effects] As described above, in the second embodiment, when the "per-user" DEVMODE update processing unit 42 of the UI module 15X receives a request for a DEVMODE from an application 12, if the "per-user" DEVMODE 18 of the logged-in user is held and the initial value version of the "per-user" DEVMODE 18 is different from the initial value version of the "standard setting" DEVMODE 17 (specifically, the driver-defined initial value version of the driver initial value DEVMODE 43), the "per-user" DEVMODE update processing unit 42 overwrites and updates the corresponding setting value of the "per-user" DEVMODE 18 with the setting value that was updated when the "standard setting" DEVMODE 17 was upgraded.

[0119] In other words, the "per-user" DEVMODE update processing unit 42 merges DEVMODE mask data 103 indicating the setting values ​​of the "standard settings" DEVMODE 17 that were updated when the "standard settings" DEVMODE 17 was upgraded, which was created by the mask data creation processing unit 101 as a mask data creation unit, with the new version's "standard settings" DEVMODE 17 (specifically, the driver initial value DEVMODE 43), and the "per-user" DEVMODE 18 using the mask data / DEVMODE merge processing unit 102 as a merge processing unit, thereby overwriting and updating the corresponding setting values ​​of the "per-user" DEVMODE 18 with the setting values ​​of the "standard settings" DEVMODE 17 that were updated when the "standard settings" DEVMODE 17 was upgraded.

[0120] In this way, in the second embodiment, as in the first embodiment, it is possible to reflect updates to the "standard settings" DEVMODE 17 in the "per-user" DEVMODE 18 for each user, without the need to prepare a dedicated settings screen or for the administrator to specify whether or not updates to the setting values ​​for each setting item of the "standard settings" DEVMODE 17 should be reflected in the "per-user" DEVMODE 18.

[0121] Furthermore, in the second embodiment, setting values ​​that were not updated when the "standard setting" DEVMODE 17 was upgraded are not reflected in the "per-user" DEVMODE 18, so that the user is spared the trouble of having to reset changed setting values ​​to the settings before the change after updating the "per-user" DEVMODE 18, thereby improving convenience.

[0122] 3. Other embodiments [3-1. Another embodiment 1] In the first embodiment described above, the setting values ​​of the "standard setting" DEVMODE 17 overwrite and update the corresponding setting values ​​of the "per-user" DEVMODE 18. In the second embodiment, the setting values ​​of the "standard setting" DEVMODE 17 that are updated at the time of a version upgrade update the corresponding setting values ​​of the "per-user" DEVMODE 18. Here, the user may be allowed to select whether to update the "per-user" DEVMODE 18 by the method of the first embodiment or the method of the second embodiment, and the "per-user" DEVMODE update processing unit 42 may update the "per-user" DEVMODE 18 by the method selected by the user.

[0123] Specifically, for example, it is possible to select whether to update the "per user" DEVMODE 18 using the method of the first embodiment or the method of the second embodiment on the confirmation dialog 46, or to select on a driver setting screen (not shown). Note that, since it is not known whether the user will select the method of the first embodiment or the method of the second embodiment, DEVMODE mask data 103 is created and stored when the printer driver 14 is updated.

[0124] [3-2. Other embodiment 2] Also, in the second embodiment described above, the DEVMODE mask data 103(B), the driver initial value DEVMODE43(A) that is the basis of the "standard setting" DEVMODE17, and the "per-user" DEVMODE18(C) are merged by the calculation of Aor(BandC), so that the corresponding setting values ​​of the "per-user" DEVMODE18 are overwritten and updated with the setting values ​​of the "standard setting" DEVMODE17 that have been updated by updating the printer driver 14. This is not restrictive, and the "per-user" DEVMODE18 may be updated using other calculation methods as long as similar results are obtained.

[0125] [3-3. Other embodiment 3] Furthermore, in the first and second embodiments described above, when a DEVMODE is requested by an application 12, if a "per-user" DEVMODE 18 is held separately from the "standard setting" DEVMODE 17, the "per-user" DEVMODE 18 is updated based on the "standard setting" DEVMODE 17 (specifically, based on the driver initial value DEVMODE 43 that is the basis of the "standard setting" DEVMODE 17) by the "per-user" DEVMODE update processing unit 42 of the printer driver 14. This is not limiting, and in short, it is sufficient that the "per-user" DEVMODE 18 is updated based on the "standard setting" DEVMODE 17 when the printer driver 14 handles a DEVMODE for the first time after installation (for example, when the printer driver 14 uses it itself or provides it to an external device) for some reason.

[0126] Furthermore, without being limited to this, the "per-user" DEVMODE update processing unit 42 of the printer driver 14 may be provided in a program other than the printer driver 14 (for example, an installer for the printer driver 14, or a module that can be called from the printer driver 14 that is installed together with the printer driver 14), and the "per-user" DEVMODE update processing unit 42 provided in that program may update the "per-user" DEVMODE 18.

[0127] [3-4. Other embodiment 4] Furthermore, in the first and second embodiments described above, the present invention is applied to the printer driver 14 as a setting information update program, but the present invention is not limited to this and may be applied to device drivers other than the printer driver 14. Specifically, a device driver in which standard setting information indicating initial setting values ​​and per-user setting information indicating setting values ​​specified by the user are prepared is preferable, and the present invention can be applied to various device drivers, such as a graphic driver for controlling a graphic board, an audio driver for controlling audio devices such as a DAC (D / A converter) and a speaker, and a device driver for controlling an image device such as a multifunction printer, a scanner, or a camera.

[0128] [3-5. Other embodiment 5] Furthermore, the present invention is not limited to the above-described embodiments, and the scope of application of the present invention extends to embodiments in which some or all of the above-described embodiments are combined in any manner, or in which some of the embodiments are extracted. [Industrial Applicability]

[0129] The present invention can be widely used in device drivers installed in PCs and the like. [Explanation of symbols]

[0130] 1...computer system, 10...host computer, 11...OS, 12...application, 13...user account, 14...printer driver, 15, 15X...UI module, 17..."standard settings" DEVMODE, 18..."per user" DEVMODE, 40...DEVMODE selection processing unit, 41...initial value version acquisition / determination unit, 42..."per user" DEVMODE update processing unit, 43...driver initial value DEVMODE, 45...confirmation dialog display unit, 46...confirmation dialog, 100...previous version "standard settings" DEVMODE acquisition unit, 101...mask data creation processing unit, 102...mask data / DEVMODE merge processing unit, 103...DEVMODE mask data.

Claims

1. A method for updating setting information of a device driver, The setting information includes standard setting information indicating initial setting values ​​and user setting information indicating setting values ​​designated by a user, The standard setting information is updated when the device driver is updated, When the device driver handles the setting information, if the per-user setting information exists separately from the standard setting information and the version of the per-user setting information differs from the version of the standard setting information, a setting information update unit updates the per-user setting information based on the standard setting information and includes a setting information update step of matching the version of the per-user setting information to the version of the standard setting information. A setting information updating method comprising:

2. In the setting information update step, when the device driver is requested to provide the setting information, if the per-user setting information exists separately from the standard setting information and the version of the per-user setting information is different from the version of the standard setting information, the setting information update unit updates the per-user setting information based on the standard setting information and causes the version of the per-user setting information to match the version of the standard setting information; The setting information update unit further includes a setting information return step of returning the updated setting information for each user to a request source.

2. The setting information updating method according to claim 1.

3. The method further includes a confirmation dialog display step of causing a confirmation dialog display unit of the device driver to display on a display unit a confirmation dialog for confirming whether or not the per-user setting information may be updated, In the setting information updating step, if an operation to permit updating of the per-user setting information is performed on the confirmation dialog displayed in the confirmation dialog displaying step, a process is executed to update the per-user setting information based on the standard setting information and to make the version of the per-user setting information coincide with the version of the standard setting information, and if an operation to not permit updating of the per-user setting information is performed on the confirmation dialog, only a process to make the version of the per-user setting information coincide with the version of the standard setting information is executed.

2. The setting information updating method according to claim 1.

4. In the setting information updating step, the setting information updating unit updates each corresponding setting value of the per-user setting information with each initial setting value of the standard setting information.

4. The setting information updating method according to claim 1 or 3.

5. In the setting information updating step, the setting information updating unit updates the corresponding setting value of the per-user setting information with a setting value that has been updated by upgrading the standard setting information, among the initial setting values ​​of the standard setting information.

4. The setting information updating method according to claim 1 or 3.

6. The method further includes a mask data creating step of, when updating the standard setting information, creating mask data indicating which of the setting values ​​of the standard setting information have been updated by a mask data creating unit; In the setting information update step, the setting information update unit causes a merge processing unit to merge the standard setting information, the per-user setting information, and the mask data, thereby updating corresponding setting values ​​of the per-user setting information with setting values ​​updated by upgrading the standard setting information among the initial setting values ​​of the standard setting information.

6. The setting information updating method according to claim 5.

7. A device driver that is installed on a computer The setting information of the device driver includes standard setting information indicating initial setting values ​​and per-user setting information indicating setting values ​​designated by a user, The standard setting information is updated when the device driver is updated, When the device driver handles the setting information, if the per-user setting information exists separately from the standard setting information and the version of the per-user setting information differs from the version of the standard setting information, the computer is caused to execute a process of updating the per-user setting information based on the standard setting information and matching the version of the per-user setting information to the version of the standard setting information. A device driver characterized by:

8. When the standard setting information is updated, the computer is caused to execute a process of creating mask data indicating which of the setting values ​​of the standard setting information have been updated.

8. The device driver according to claim 7.

Citation Information

Patent Citations

  • Setting information synchronization system for printer driver

    JP2007122137A

  • Information processing apparatus, printing control program, printing device and printing system

    JP2012089003A