JP2010225050A - Driver program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an automatic update technique of a custom driver program. <P>SOLUTION: In a setting file 123 of a printer driver unit 120 (printer driver program) of a PC10, a custom flag 124 is previously set which indicates whether or not the printer driver unit 120 is a customized driver. The printer driver unit 120, upon receiving from a user an instruction for performing automatic update of the printer driver program (printer driver unit 120), refers to the custom flag 124, and if the custom flag 124 indicates the customization, makes access to a site (i.e., a site not a default maker site) designated by the user and obtains the printer driver program to perform automatic update. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for updating a driver program, and more particularly, to a technique for updating a driver program for a printing apparatus such as a printer, a copier, or a multifunction peripheral.

  As a function of a driver program installed in a computer such as a PC of a user of a printing apparatus, an automatic update (automatic update) function is known. If this function is used, the user can automatically update the driver program by instructing the driver program to perform automatic updating (for example, by clicking the automatic update button on the interface screen displayed by the driver program). As described above, the update operation of the driver program is easy for the user.

  Further, as a technology related to automatic update, there is a system in which a list of correction information of software operating on a user's computer is notified to the user's computer, and the user updates the software collectively by pressing an execution button (for example, Patent Document 1).

Japanese Patent Laid-Open No. 11-134179

  On the other hand, a driver program customized for a specific organization such as a company (hereinafter referred to as “custom driver” or “individual driver”) may be installed on the user's computer. . In this case, it is inconvenient if the installed custom driver is updated by a driver program (hereinafter, referred to as “standard driver”) that can be downloaded from a manufacturer site on the Internet, for example. Therefore, there is a need to suppress the update from such a custom driver to a standard driver.

  However, with the conventional automatic updating function of the driver program, the user can easily obtain and update the standard driver program from the Internet. Therefore, it is not possible to meet the needs as described above.

  For the above problem, for example, the operation of the automatic update button may be invalidated. In this way, updating from a custom driver to a standard driver can be prohibited.

  However, as described above, when updating a custom driver to another custom driver, it is not possible to meet the need to use the automatic update function.

  Accordingly, an object of the present invention is to provide an automatic update technique for a custom driver program.

  A driver program for causing a computer to solve the above problems to update the driver program of the computer, an input reception step for receiving an instruction for update processing from a user, and whether or not the driver program is a custom product A custom determination step for determining whether or not the product is a custom product with reference to a predetermined custom flag, and connection destination information for acquiring a driver program designated by the user in the input reception step is predetermined. A connection destination determination step for determining whether or not the connection destination information is first connection information, the custom flag indicating that the custom flag is a custom product, and the connection destination information designated by the user is the first connection If it is destination information, a stop step of canceling the update process; To be executed by said computer, characterized in that.

  Here, in the above driver program, when the custom flag indicates a custom product, and the connection destination information specified by the user is not the first connection destination information, the user specifies The acquisition step of accessing the connection destination indicated by the connection destination information and acquiring the driver program may be executed by the computer.

  Further, in the above driver program, the obtaining step obtains a predetermined custom flag indicating whether or not the connection destination driver program is a custom product from the connection destination, and the acquired custom flag is When indicating that it is a custom product, a driver program is acquired, and when the acquired custom flag indicates that it is not a custom product, the user is notified that the connection destination driver program is not a custom product. May be.

  Further, in the above driver program, when the acquisition step receives an instruction to continue the update process by the input reception step after notifying the user that the connection destination driver program is not a custom product. The connection destination driver program may be acquired.

  In addition, any of the above driver programs may be a driver program that controls at least one of a printer, a copier, a multifunction peripheral, and a scanner.

The figure which shows schematic structure of the hardware of PC which is an example of one Embodiment of this invention. The block diagram which shows an example of a function structure of PC. The figure which shows the example of an interface screen for performing automatic update. The figure which shows an example of the setting file which described the custom flag. The figure which shows an example of the driver information file which described the custom flag. The flowchart which shows an example of the automatic update process of a driver.

  Hereinafter, an embodiment of the present invention will be described.

  FIG. 1 is a diagram illustrating a schematic configuration of hardware of a PC 10 which is an example of an embodiment of the present invention.

  As shown in this figure, the PC 10 includes, for example, a CPU 11 that performs various calculations, a RAM 12 that stores programs and data executed by the CPU 11, a ROM 13 that stores programs and data necessary for startup in advance, and an auxiliary device such as a hard disk. A storage device 14, a display device 15 such as an LCD for displaying a user interface screen, an input device 16 such as a keyboard and a mouse, and a media reader that reads information from a portable storage medium such as a CD-ROM 17 and a communication device 18 that communicates with an external device via a network such as a LAN.

  In the present embodiment, there are a plurality of PCs 10 and each is connected to the LAN 40. An internal server 20 and a printer 30 are connected to the LAN 40. The LAN 40 is connected to the Internet 50. An external server 60 is connected to the Internet 50.

  The PC 10 causes the printer 30 to execute printing via the LAN 40. Therefore, a printer driver program (not shown) that controls the printer 30 is installed in the PC 10. Further, the PC 10 accesses the internal server 20 or the external server 60 via the LAN 40 and executes automatic update of the printer driver program.

  The printer 30 executes printing in accordance with the print request transmitted from the PC 10. The printer 30 is, for example, an ink jet color printer. A laser-type page printer may be used.

  The internal server 20 is used to automatically update the printer driver program of the PC 10 to a custom driver program designated by the administrator. That is, the internal server 20 is a server managed by the administrator of the LAN 40 and is designated as an access destination for automatic updating by the user of the PC 10. Therefore, the internal server 20 stores various files (driver information file 21 and driver package file 22) used for automatic updating. The internal server 20 is, for example, a general computer similar to the PC 10.

  The external server 60 is used to automatically update the printer driver program of the PC 10 to the standard driver program. That is, the external server 60 is a server managed by the manufacturer of the printer driver program or the like, and is preset (default setting) as an access destination for automatic update. Therefore, the external server 60 stores various files (driver information file 61 and driver package file 62) used for automatic updating. The external server 60 is, for example, a general computer similar to the PC 10.

  The driver information file (21, 61) is a file in which, for example, version information of the driver program to be updated, information indicating the presence / absence of update, information indicating the storage location of the driver package file (22, 62), and the like are described. . The driver information file (21, 61) is, for example, a file with an extension “.dat”.

  The driver package file (22, 62) is a file including, for example, a driver program to be updated (may be a plurality of program groups), various setting files, and the like. The driver package files (22, 62) are, for example, files with extensions “.exe” and “.msi”.

  When the PC 10 is set to refer to the driver information file (21, 61) when automatically updating the printer driver program, the PC 10 first refers to the driver information file (21, 61) to determine whether or not the driver information file is updated. Information indicating the storage location of the package file (22, 62) is acquired. If there is an update, the driver package file (22, 62) is downloaded from the storage location to update the printer driver program. On the other hand, when the PC 10 is set to refer to the driver package file (22, 62) when automatically updating the printer driver program, the PC 10 downloads the driver package file (22, 62), and the printer driver program Update.

  The system configuration relating to the automatic update of the PC 10 and the printer driver has been described above. However, this configuration is not limited to the above configuration because the main configuration has been described in describing the features of the present invention. In addition, the configuration of a general PC or a system related to automatic update is not excluded.

  FIG. 2 is a block diagram illustrating an example of a functional configuration of the PC 10.

  As shown in the figure, the PC 10 has a printer driver unit 120. Also, it has an OS unit (not shown) and an application unit (not shown).

  The printer driver unit 120 is realized, for example, when the CPU 11 executes a predetermined printer driver program loaded from the auxiliary storage device 14 to the RAM 12. The OS unit and the application unit are realized, for example, by the CPU 11 executing a predetermined OS program or application program loaded from the auxiliary storage device 14 to the RAM 12.

  The printer driver program is downloaded from the internal server 20 or the external server 60 and installed or updated. Of course, the media reader 17 may read and install or update from a storage medium such as a CD-ROM. For example, the OS program and the application program are downloaded from the network and installed or updated. Of course, the media reader 17 may read and install or update from a storage medium such as a CD-ROM.

  The printer driver unit 120 includes a main control unit 121, an update control unit 122, and a setting file 123. The main control unit 121 and the update control unit 122 may be realized by the same file (for example, an .exe file) or may be realized by different files.

  The main control unit 121 includes display control processing for various interface screens of the printer driver, input control processing for user operations via the interface screen, print data generation processing for converting print target data received from the application unit, to print data, Transmission processing for transmitting print data to the printer 30 is performed.

  When the printer driver unit 120 is activated, the main control unit 121 displays on the display device 15 a print setting screen 500 for accepting various print settings, for example, as shown in FIG. In a predetermined area of the screen, an automatic driver update button 510 for receiving a driver automatic update instruction is displayed. The main control unit 121 sets the driver automatic update button 510 to valid (active) so that the user can select it.

  When the selection by the user of the driver automatic update button 510 is accepted, the main control unit 121 displays a connection destination designation screen 600 for accepting designation of a connection destination, for example, as shown in FIG. The connection destination designation screen 600 has a selection field 610 for selecting a preset access destination (for example, the external server 60) for performing automatic update by a standard driver, and access for performing automatic update by a custom driver. A selection field 620 for selecting a destination (for example, the internal server 20), and connection destination information (for example, a URL, including a file name to be referenced) indicating an access destination for automatic update by a custom driver. A connection destination input field 621 for inputting, an OK button 630 for starting automatic update, and the like are provided.

  When the selection by the user of the OK button 630 is accepted, the main control unit 121 instructs the update control unit 122 to print the printer driver from the internal server 20 or the external server 60 based on the information specified on the connection destination designation screen 600. Download the program. The downloaded printer driver program causes the printer driver unit 120 (printer driver program) installed in the PC 10 to be updated.

  The update control unit 122 is activated by the main control unit 121 and uses the custom flag 124 of the setting file 123 to determine a connection destination for acquiring the printer driver program.

  The custom flag 124 is information that is included in the printer driver unit 120 in advance when the printer driver unit 120 (printer driver program) is a custom driver and indicates whether the driver is customized. The custom flag 124 is described in, for example, the setting file 123 included in the driver program.

  That is, the custom flag is included in advance in the driver package program of the custom driver distributed from the manufacturer, and is installed in the PC 10. The value of the custom flag included in the driver package program is set in advance (for example, at the time of manufacture) by the manufacturer depending on whether the driver is custom or standard.

  In the example of FIG. 4, the custom flag 124 “IsCustomized” is described following the description of the driver download information in the setting file 123. The setting value “0x0001” indicates that the driver is customized, and the setting value “0x0000” indicates that the driver is not customized (standard). As the setting file 123, for example, a module name description file can be used.

  The custom flag is also included in advance in the driver information file 21 of the internal server 20. The value of the custom flag is set in advance by the administrator depending on whether the driver is custom or standard. The update control unit 122 refers to the custom flag and determines whether the driver package program to be updated is custom or standard. Note that the custom information is not included in the driver information file 61 of the external server 60 managed by the manufacturer or the like.

  In the example of FIG. 5, the custom flag 211 is described following the description of the information about the driver in the driver information file 21.

  When the custom flag 124 in the setting file 123 indicates custom, the update control unit 122 starts processing for accessing a specified connection destination (for example, the internal server 20). On the other hand, when the custom flag 124 indicates standard, the driver accesses the preset connection destination (for example, the external server 60) and acquires the driver information file 61 and the driver package file 62.

  The above components are classified according to the main processing contents in order to facilitate understanding of the configuration of the PC 10. The present invention is not limited by the way of classification and names of the constituent elements. The configuration of the PC 10 can be classified into more components depending on the processing content. Moreover, it can also classify | categorize so that one component may perform more processes. Further, the processing of each component may be executed by one hardware or may be executed by a plurality of hardware.

  Next, characteristic processing realized by the PC 10 will be described.

  FIG. 6 is a flowchart illustrating an example of the automatic update process. This flow is started when there is an automatic update instruction from the user (for example, when the main control unit 121 accepts the selection by the user of the above-described OK button 630 (FIG. 3B)). That is, the main control unit 121 calls the update control unit 122.

  In S100, the update control unit 122 determines whether the value of the custom flag 124 in the setting file 123 indicates a custom driver or a standard driver. For example, if the custom flag 124 is “0x0000”, the printer driver unit 120 determines that it is a standard driver (S100: standard), and advances the process to S200. On the other hand, if the custom flag 124 is “0x0001”, the printer driver unit 120 determines that it is a custom driver (S100: Custom), and advances the process to S110.

  In S110, the update control unit 122 determines a connection destination. Specifically, the update control unit 122 acquires, from the main control unit 121, information on the connection destination designated by the user using the selection column 610 or the selection column 620 of the connection destination designation screen 600 (FIG. 3B) described above. . If the designated connection destination is a preset connection destination (for example, the external server 60) for automatic updating by the standard driver (S110: manufacturer site), the process proceeds to S170. On the other hand, if the designated connection destination is a connection destination (for example, the internal server 20) for automatic updating by the custom driver (S110: designated site), the process proceeds to S120.

  In S120, the update control unit 122 determines whether the file type specified from the connection destination information designated by the user is a driver information file or a driver package file.

  Specifically, the update control unit 122 acquires connection destination information designated by the user from the main control unit 121 via the connection destination input field 621 of the connection destination designation screen 600 (FIG. 3B) described above. . For example, if the connection destination information is “http: //server/driverupdate/drvupdate.exe”, it is determined that the file type is a driver package file (S120: driver package), and the process proceeds to S150. On the other hand, for example, when the connection destination information is “http: //server/driverupdate/drvinfo.dat”, it is determined that the file type is a driver information file (S120: driver information), and the process proceeds to S130.

  In S130, the update control unit 122 refers to the driver information file. Specifically, the update control unit 122 accesses the connection destination (for example, the internal server 20) indicated by the connection destination information acquired in S120. Then, the driver information file 21 is referred to. Then, the process proceeds to S140.

  In S140, the update control unit 122 acquires the value of the custom flag 211 from the driver information file 21, and determines whether this value indicates a custom driver or a standard driver. If it is determined that the driver package file 22 is a standard driver (S140: standard), the process proceeds to S150. On the other hand, if it is determined that the driver package file 22 is a custom driver (S140: Custom), the process proceeds to S180.

  The determination process in S140 is effective when the user mistakenly specifies a driver program that is not an update target (for example, when a driver other than a custom driver is stored in the internal server 20) as connection destination information. is there. S130 and S140 may be omitted.

  In S150, the update control unit 122 displays a warning message. Specifically, for example, an interface screen that warns that there is a possibility that the driver to be updated is not a custom driver is output to the display device 15. In addition, a button for selecting whether or not to continue the driver update is displayed on the interface screen. Then, the process proceeds to S160.

  The process of S150 is effective when the user mistakenly designates a driver program that is not an update target (for example, when a driver other than a custom driver is stored in the internal server 20) as connection destination information. .

  In S160, the update control unit 122 determines whether or not the driver update is continued. Specifically, a user instruction is received via the interface screen displayed in S150. If an instruction to continue the update is given (S160: Continue), the process proceeds to S180. On the other hand, when an instruction to cancel the update is given (S160: Cancel), the process proceeds to S190. In addition, you may abbreviate | omit the process of S120-S160. In this way, processing can be simplified according to the determination result of S110.

  In S170, the update control unit 122 displays an error message. Specifically, for example, an interface screen indicating that the driver to be updated is not a custom driver and updating cannot be continued is output to the display device 15. Then, the process proceeds to S190. The process may proceed to S160 to determine whether or not the update is continued.

  In S180, the update control unit 122 executes the update by the custom driver. Specifically, when the file type is a driver information file (S120: driver information), the update control unit 122 refers to the driver information file 21 and acquires connection destination information indicating the storage location of the driver package file 22. . Based on the connection destination information, the internal server 20 is accessed and the driver package file 22 is downloaded. Of course, the driver information file 21 may be referred to obtain information indicating the presence / absence of update, and the presence / absence of update may be determined. If there is no update, this flow ends.

  On the other hand, when the file type is a driver package file (S120: driver package), the update control unit 122 accesses the internal server 20 and downloads the driver package file 22 based on the connection destination information.

  The update control unit 122 updates the printer driver unit 120 using the driver package file 22 downloaded as described above. Then, this flow ends.

  In S190, the update control unit 122 ends this flow without performing the update process.

  In S200, the update control unit 122 executes update using a standard driver. Specifically, the update control unit 122 accesses the internal server 20 or the external server 60 based on connection destination information specified by the user. When the driver information file is set as the connection destination information, the driver information file 21 or 61 is referred to, and the connection destination information indicating the storage location of the driver package file 21 or 62 is acquired. Based on the connection destination information, the internal server 20 or the external server 60 is accessed, and the driver package file 22 or 62 is downloaded. Of course, the driver information file 21 or 61 may be referred to obtain information indicating the presence / absence of the update, and the presence / absence of the update may be determined. If there is no update, this flow ends.

  In the present embodiment, the driver package file is set as the connection destination information when the internal server 20 is specified. Therefore, when a driver package file is set as connection destination information, the update control unit 122 accesses the internal server 20 and downloads the driver package file 22 based on the connection destination information.

  The update control unit 122 updates the printer driver unit 120 using the driver package file 62 downloaded as described above. Then, this flow ends.

  Each processing unit in the flow of FIG. 6 is divided according to main processing contents in order to facilitate understanding of the processing of the PC 10. The present invention is not limited by the way of dividing the processing unit or the name. The processing of the PC 10 can be divided into more processing units according to the processing contents. Moreover, it can also divide | segment so that one process unit may contain many processes.

  The embodiment of the present invention has been described above. According to the present embodiment, an automatic update function can be provided also for a custom driver.

  Specifically, in the present embodiment, a flag for identifying whether or not the driver is custom as setting information is included. In the automatic update process, the flag is referred to. With this configuration, when the installed driver is custom, automatic update processing for the custom driver is executed.

  In the present embodiment, the connection destination driver information file designated by the user also includes an identification flag. As a result, the administrator can explicitly specify that the update from the custom driver to the custom driver is executed.

  As described above, according to the present invention, it is possible to provide a driver capable of executing automatic updating as needed even if the driver is individually compatible. Therefore, the convenience of network managers and users of organizations such as companies is further improved.

  The above-described embodiments of the present invention are intended to illustrate the gist and scope of the present invention and are not intended to be limiting. Many alternatives, modifications, and variations will be apparent to those skilled in the art.

  The present invention can also be applied to update of a driver program for a scanner, a copier equipped with a scanner, a multifunction machine, a facsimile machine, and the like.

10: PC, 11: CPU, 12: RAM, 13: ROM, 14: auxiliary storage device, 15: display device, 16: input device, 17: media reading device, 18: communication device, 20: internal server, 21: Driver information file, 22: Driver package file, 30: Printer, 40: LAN, 50: Internet, 60: External server, 61: Driver information file, 62: Driver package file, 120: Printer driver unit, 121: Main control unit 122: Update control unit, 123: Setting file, 124: Custom flag, 211: Custom flag, 500: Print setting screen, 510: Automatic driver update button, 600: Connection destination designation screen, 610: Selection field, 620: Selection Column, 621: connection destination input column, 630: OK button,

Claims (5)

A driver program that causes a computer to update the driver program for the computer,
An input reception step for receiving an instruction for update processing from the user;
A custom determination step for determining whether or not the driver program is a custom product by referring to a predetermined custom flag indicating whether or not the driver program is a custom product;
A connection destination determination step for determining whether or not the connection destination information for acquiring the driver program designated by the user in the input reception step is predetermined first connection destination information;
When the custom flag indicates that the product is a custom product and the connection destination information specified by the user is the first connection destination information, a stop step of stopping the update process is performed on the computer. To execute,
A driver program characterized by that. The driver program according to claim 1,
If the custom flag indicates a custom product and the connection destination information specified by the user is not the first connection destination information, the connection destination indicated by the connection destination information specified by the user is accessed. And causing the computer to execute an acquisition step of acquiring a driver program.
A driver program characterized by that. The driver program according to claim 2,
The obtaining step includes
A predetermined custom flag indicating whether or not the connection destination driver program is a custom product is acquired from the connection destination;
If the acquired custom flag indicates that it is a custom product, get the driver program,
When the acquired custom flag indicates that the product is not a custom product, the user is notified that the connection destination driver program is not a custom product.
A driver program characterized by that. The driver program according to claim 3,
The obtaining step includes
After notifying the user that the connection destination driver program is not a custom product, when receiving an instruction to continue the update process in the input reception step, obtaining the connection destination driver program;
A driver program characterized by that.   The driver program according to claim 1, wherein the driver program controls at least one of a printer, a copier, a multifunction peripheral, and a scanner.

Images