JP2008158660A - Installer creation device, installer creation method, and installer creation program - Google Patents

Abstract

Provided is an installer creation device capable of taking over the settings of an existing device driver even when an OS is reinstalled.
The installer creating apparatus obtains the device driver setting information stored in the HDD (step S301) and the device driver based on the information of the INF file corresponding to the acquired device driver. A generation unit (step S304) for generating a new INF file used by the installation application when installing, and acquiring file information included in the device driver, and adding the acquired file information to the new INF file And changing means (step S304) for changing the device driver, and collecting means for collecting the device driver files and copying them to a predetermined area based on the file information added by the changing means.
[Selection] Figure 3

Description

  The present invention relates to an installer creation apparatus, an installer creation method, and an installer creation program for creating an installer for a device driver such as a printer driver.

  2. Description of the Related Art Conventionally, peripheral devices such as printers are widely used by being shared by many users. In this case, a printer server is installed on the network, and the printer server manages information necessary for each client computer to use the printer, such as authority settings and security settings for each client computer. Yes.

  By the way, as the number of client computers increases, the load on the printer server increases, so it becomes necessary to increase the number of printer servers or to make the printer server more functional.

  In that case, the administrator records the setting information of the printer driver in the existing printer server as a reference setting as a memo or the like. Thereafter, a printer driver installer for the printer server to be added or changed is prepared, and the installer is activated to install a new printer driver. Then, the standard setting of the existing printer driver recorded with a memo or the like is reflected on the new installed printer driver.

  It is complicated and troublesome for an administrator to perform the above-mentioned work manually. Also, considering that the standard settings of existing printer servers are reflected to a plurality of printer servers, the work must be performed for the number of printer servers, which further increases the load.

Therefore, a technique for matching the setting of a newly installed printer driver when updating the printer driver with the standard setting of an existing printer driver is disclosed (see Patent Document 1).
JP 2006-107476 A

  The above-mentioned patent document 1 takes over the device settings of a printer driver that has already been installed when the printer driver is updated, but cannot be applied, for example, when the OS is reinstalled. This is because when the OS is reinstalled, the printer driver set up to that point is cleared.

  Accordingly, the present invention provides an installer creation apparatus, an installer creation method, and an installer creation program for creating an installer that can take over the settings of an existing device driver even when the OS is reinstalled. With the goal.

  In order to achieve the above object, an installer creating apparatus according to claim 1 is an apparatus for creating an installer of a device driver, and setting information for acquiring device driver setting information stored in a predetermined storage area. An acquisition unit; and a definition file generation unit that generates a new definition file used by an installation application when installing the device driver based on information of a definition file corresponding to the device driver acquired by the setting information acquisition unit; A definition file changing unit that acquires predetermined file information included in the device driver, adds the acquired file information to the new definition file and changes the file, and a file added by the definition file changing unit Based on the information, the device driver file Condensed, characterized in that it comprises a collection means for copying in a predetermined area.

  The installer creation method according to claim 6 is a method of creating a device driver installer, a setting information acquisition step of acquiring device driver setting information stored in a predetermined storage area, and the setting information acquisition A definition file generating step for generating a new definition file to be used by an installation application when installing the device driver based on the information of the definition file corresponding to the device driver acquired in the step, and a predetermined included in the device driver A definition file changing step for changing the file by adding the acquired file information to the new definition file, and based on the file information added in the definition file step, Collect files and place Characterized in that it comprises a collecting step of copying the area, the.

  An installer creation program according to claim 11 is a program for causing a computer to execute a process for creating a device driver installer, and obtains device driver setting information stored in a predetermined storage area. And a definition file generation module that generates a new definition file used by an installation application when installing the device driver based on the information of the definition file corresponding to the device driver acquired by the setting information acquisition module; A definition file change module that acquires predetermined file information included in a device driver, adds the acquired file information to the new definition file and changes the file, and file information added by the definition file module Based on the collected device driver files, a collection module for copying in a predetermined area, to execute the computer, and wherein.

  According to the present invention, even when the OS is reinstalled, the existing device driver settings can be taken over by executing the installer created after the OS is reinstalled.

  Hereinafter, an example of an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a configuration diagram of a network system including a printer server which is an example of an embodiment of the present invention.

  As shown in FIG. 1, in this system, a printer server 101, information processing apparatuses 102-1 and 102-2, and printers 103-1 and 103-2 are connected to each other via a network 104. Here, in this embodiment, the printer server 101 functions as the installer creation apparatus of the present invention.

  Document data created by the information processing apparatuses 102-1 and 102-2 is output from the printers 103-1 to 103-3 in a predetermined storage area (for example, the HDD 204 or the like: see FIG. 2) of the printer server 101. The printer driver necessary for this is stored. The printer server 101 also monitors the status of each of the printers 103-1 to 103-3.

  Further, the printer server 101 manages access right setting information indicating what functions can be used for the printers 103-1 to 103-3 for each user who uses the information processing apparatuses 102-1 and 102-2. is doing. Further, the printer server 101 also manages security information and the like when the information processing apparatuses 102-1 and 102-2 transmit data to the printers 103-1 to 103-3.

  The information processing apparatuses 102-1 and 102-2 (hereinafter referred to as the information processing apparatus 102) convert data created by a predetermined application into print data using a printer driver on the printer server 101, and Output to -1 to 103-3.

  The printers 103-1, 103-2, and 103-3 have a function of printing print data transmitted from the printer server 101 and the information processing apparatus 102.

  Next, the hardware configuration of the printer server 101 will be described with reference to FIG. In FIG. 2, the hardware configuration of the printer server 101 will be described, but it is assumed that the information processing apparatus 102 has the same hardware configuration.

  As shown in FIG. 2, the printer server 101 includes a CPU 201, a RAM 202, a ROM 203, an HDD (hard disk drive) 204, and a network I / F (interface) 205 as hardware.

  The printer server 101 also includes a recording medium drive 206, a keyboard 207, a mouse 208, a video I / F 209, a display device 210, and an external device I / F 211 as hardware. These hardwares are connected to each other via a system bus 212.

  The CPU 201 uses the programs and data stored in the RAM 202 and ROM 203 to control the entire printer server 101 and executes each process performed by the printer server 101.

  The RAM 202 has an area for temporarily storing programs and data loaded from the HDD 204 and a work area used by the CPU 201 to execute various processes. The ROM 203 stores various programs such as a computer boot program and BIOS.

  The HDD 204 stores an OS (operating system), programs for causing the CPU 201 to execute each process performed by the printer server 101, and various data, which are read out to the RAM 202 as required by the control of the CPU 201. Executed.

  A network I / F 205 is used to connect to the network 104, and data communication can be performed with an external device via the network I / F 205. The recording medium drive 206 functions as a drive such as a CD-ROM, CD-R / RW, DVD-ROM, DVD-R / RW, and DVD-RAM. The keyboard 207 and the mouse 208 function as an input unit that can input various instructions to the CPU 201.

  A display device 210 is connected to the video I / F 209. The display device 210 includes a CRT, a liquid crystal display device, and the like, and has a function of displaying information such as characters and images on a display screen based on a signal transmitted via the video I / F 209.

  The external device I / F 211 is a port for connecting a peripheral device, and data can be transmitted / received to / from the peripheral device via the external device I / F 211. The external device I / F 211 can be configured by various interfaces such as SCSI, USB, IEEE1394, and usually includes a plurality of external devices I / F.

  The connection form with the peripheral device may be wired / wireless. Of course, it is possible to connect to the printers 103-1 to 103-3 via the external device I / F 211.

  Next, an installer creation process performed by the CPU 201 of the printer server 101 will be described with reference to FIG.

  In this process, the settings of the printer driver installed in the printer server 101 are applied as they are to other computers (printer server and the like) as they are (if the OS of the printer server 101 is reinstalled, the printer server after the OS is installed) A printer driver installer (to be directly applied to the server 101) is created.

  The following description is given assuming that the OS of the printer server is Windows (registered trademark) 2000, Windows (registered trademark) XP, or Windows (registered trademark) Server 2003.

  Hereinafter, an installer creation process in Windows (registered trademark) will be described.

  First, the CPU 201 of the printer server 101 acquires already installed printer driver information (step S301).

  FIG. 9 is a diagram illustrating an example of printer driver information, and the printer driver information is stored in the HDD 204 of the printer server 101.

  In FIG. 9, “printer name” is data indicating the name of the printer. “Driver name” is data indicating the type of printer driver used in the printer. “Port name” is data indicating the port to which the printer is connected. “Version” is data indicating the version of the printer driver. “Alternative OS” indicates for which OS an alternative driver is installed in the printer server 101 for the printer.

  An alternative driver can be set for each printer driver, and a printer driver for another OS is also copied to the shared printer server, and the printer driver is installed via the network 104 when the client is connected. This is a function of the OS.

  Returning to FIG. 3, a printer for adding a printer driver to the created installer is selected from printers that can create print data using the printer driver already installed in the printer server 101 (step S302). In this case, for example, as shown in FIG. 7, a dialog box is displayed on the display device 210, and the CPU 201 detects the printer in accordance with an instruction from the input unit by the user using the printer server 101 via the dialog box. Will choose.

  FIG. 7 is a diagram illustrating an example of a printer selection screen for adding a printer driver to the installer.

  In FIG. 7, a radio button in the column “Select Printer to Add Driver to Installer” is a control for selecting the type of printer to be displayed in the printer display area below the radio button.

  When “Display all existing printers” is selected, all printers that can be used by the printer driver installed in the printer server 101 are displayed in the printer display area.

  When “display currently connected printer” is selected, only the printer driver of the printer currently connected to the printer server 101 is displayed. For example, although a printer driver is installed in the printer server, such a selection is possible in order not to display a printer that is actually not used due to a failure or a model change.

  When “printer information file” is selected, the printer information file is selected and the printer recorded in the printer information file is displayed in the printer display area so as to be selectable.

  By selecting the printers displayed in this printer display area (multiple selection is possible), the user can instruct the CPU 201 to select a printer for adding a printer driver to the installer. When the “OK” button is pressed, an installer creation process is performed.

  In this dialog box, it is possible to select a security setting as well as a printer. The security setting represents printer access permission, and user / group access permission can be assigned to each printer. The radio button in the “security setting method” column is a control for selecting the type of security information file to be created. Based on the setting here, a security information file creation process, which will be described later, is performed.

  Returning to FIG. 3, after selecting the printer to add the printer driver to the installer, the CPU 201 determines whether or not an installer creation instruction has been received by pressing the “OK” button in FIG. 7 (step S303). If an installer creation instruction has not been received (NO in step S303), the selection process in step S302 is continued. If it is determined that a creation instruction has been received (YES in step S303), driver folder creation processing in step S304 is performed. Details of the driver folder creation processing will be described later with reference to FIG.

  Then, the driver folder creation processing in step S304 is repeated for all the printers selected in step S302 (until YES is determined in step S305).

  Thereafter, a printer information file for the selected printer is created (step S306). The printer information file here is a file in which existing setting information is described for each printer. For example, it refers to a file in which items of a print setting dialog that is an OS function such as print orientation and page layout, and printer property dialog items that are an OS function such as location and comment are registered.

  Then, a security information file creation process is performed (step S307). At this time, a security information file corresponding to the security setting set on the printer selection screen shown in FIG. 7 is created.

  Thereafter, an installation information file is created (step S308). The installation information file is, for example, as shown in FIG. 12, and is a file used as an ini file when the printer driver is installed.

  FIG. 12 is a diagram illustrating an example of the installation information file.

  In FIG. 12, the [INFO] section can describe (items related to the entire installer, excluding printers to be installed and printer information), and can specify, for example, a security information file.

  In the [InstallPrinter] section, names of printers corresponding to printer drivers installed using the installation information file are listed. In this case, printers named local printer-A, local printer-B, and network printer-C are created on the computer when the printer driver is installed using the installation information file.

  Subsequent [Local Printer-A], [Local Printer-B], and [Network Printer-C] sections include “driver name” and “port name” for the printers listed in the [InstallPrinter] section, respectively. , “Version”, “INF for basic OS” (name of INF file for basic OS), “INF for alternative OS” (name of INF file for alternative OS: “,”) ), “Printer setting” (name of printer setting file), and the like.

  The installer is completed by storing the file created by this processing in a predetermined folder.

  The above is the installer creation process performed by the CPU 201 of the print server 101.

  As a result of the above processing, an installer as shown in FIG. 8 is created. This installer includes an installer application (existing), installation information (created in step S308 in FIG. 3), security information (created in step S307 in FIG. 3), printer setting information (created in step S306 in FIG. 3), and FIG. The basic OS driver folder and the alternative OS driver folder created in step S304.

  Next, the driver folder creation process in step S304 of FIG. 3 will be described in detail with reference to FIG. FIG. 4 is a flowchart for explaining an example of the driver folder creation process in step S304 of FIG.

  First, an INF file (setup information definition file) of a printer driver included in the installer is acquired (step S401). In Windows (registered trademark) XP, the INF file is copied to C: \ Windows (registered trademark) \ INF when the driver is installed. Therefore, the INF file corresponding to the selected printer is acquired from the folder. Become.

  Here, the configuration of the INF file will be described with reference to FIG.

  FIG. 11 is a diagram illustrating an example of an INF file of a printer driver of Windows (registered trademark) XP.

  In FIG. 11, “Version” section A describes the outline of the INF file and describes information such as the provider and the driver version.

  In the “Manufacturer” section B, information on a target manufacturer and the like is described.

  In “Model” section C, a target driver is described, and information such as a driver name, an “Install” section name described later, and a hardware ID is described. In this section, a plurality of driver names can be set. In this case, an “Install” section D described later corresponding to each driver name is described.

  The “Install” section D describes what kind of work is to be performed in the installation. The “Data” section name (DataSection value) described later corresponding to the “Install” section ([PR1000]) is described. Information such as “FileList” section name (indicated by the value of CopyFiles), which will be described later, is described.

  In the “Data” section E, information such as the names of the Driver file, the Config file, and the Help file is described.

  In the “FileList” section F, information on driver file names used in the printer driver installer whose CopyFiles value in the “Install” section is the name of this section is described.

  In the “Destination Directors” section G, copy destination information of driver files used by the installer for each “FileList” section is described.

  The “Strings” section H describes replacement information of characters enclosed in “%” among items related to the entire INF file.

  If acquisition of the INF file has failed (NO in step S402), an error is displayed (step S414), and this process ends.

  On the other hand, if the acquisition of the INF file is successful (YES in step S402), the printer driver version is determined (step S403). This is determined based on the value of “DriverVer” in “Version” section A in FIG.

  After that, it is determined whether or not the version of the basic OS INF file (INF file created by the installer creating apparatus of the present invention) has already been created (step S404). If it is determined that it has not been created yet (NO in step S404), a basic OS INF file for the driver of the version is created (step S405).

  In the basic OS INF file created in this step, first, the information of “Version” section A and “Manufacturer” section B in FIG. 11 is copied from the INF file acquired in step S401.

  If YES in step S404 (the basic OS INF file has already been created) and if the basic OS INF file creation process in step S405 is completed, the basic OS INF file editing process is performed (step S406). . Details of the editing process in step S406 will be described later with reference to FIG.

  Thereafter, the driver file necessary for the printer driver is copied to the designated folder (step S407). The driver file is copied to C: \ Windows (registered trademark) \ System32 \ spool \ Drivers \ W32X86 \ 3 in Windows (registered trademark) XP when installing the printer driver. Become. If a driver file with the same name and a new update date has already been copied to the specified folder, that file is not copied. The above is the process for creating the driver folder for the basic OS.

  Thereafter, it is determined whether there is an alternative OS setting in the printer driver used to create print data for the printer being processed (step S408). This determination is made based on whether there is data in the alternative OS column of the printer driver information in FIG.

  If NO is determined in step S408, the installation file creation process for the selected printer being processed is terminated.

  If YES is determined in step S408, it is determined whether an alternative OS INF file (an INF file created by the installer creating apparatus of the present invention) has already been created (step S409).

  Since the alternative OS INF file is created for each alternative OS, it is determined here whether the alternative OS INF files for all the alternative OSs set in the printer have been created.

  If it is determined that alternative OS INF files for all alternative OSs have not been created (NO in step S409), an alternative OS INF file for an alternative OS that has not yet been created is created (step S410).

  In the alternative OS INF file created in this step, the information of the “Version” section A in FIG. 11 is first copied from the INF file acquired in step S401.

  After the process of step S410 is completed, or when YES is determined in step S409, the alternative OS INF file is edited for each alternative OS (step S411). Details of the editing process in step S411 will be described later with reference to FIG.

  Thereafter, the driver file necessary for the printer driver for the alternative OS is copied to the designated folder (step S412). When installing an alternative printer driver, the Windows XP (Windows) 98 / Me alternative printer driver for Windows (registered trademark) XP is C: \ Windows (registered trademark) \ System32 \ spool \ Drivers \ Win40 \ 0, Windows Since the alternative printer driver for (registered trademark) NT is copied to C: \ Windows (registered trademark) \ System32 \ spool \ Drivers \ W32X86 \ 2, the driver file is obtained from the folder.

  If a driver file with the same name and a new update date has already been copied to the specified folder, the file is not copied. With this process, a substitute OS driver folder for each substitute OS is created.

  Then, the processes in steps S411 and S412 are repeated until the process is completed for all alternative OSs (YES in step S413).

  The above is the details of the driver folder creation processing in step S304 in FIG.

  Next, details of the editing process of the basic OS INF file in step S406 of FIG. 4 will be described with reference to FIG.

  First, the CPU 201 determines whether or not information on the printer driver used in the selected printer in FIG. 7 has already been described in the basic OS INF file to be edited.

  In the case of a Windows (registered trademark) INF file, a section with a name of a key value 2001 surrounded by ““ ”and“ ”in the“ Manufacture ”section B in the INF file of FIG. Check if the name of the driver is included.

  If the driver name is already included, it is determined that the driver name has already been described. If it is determined that the driver name has already been described (YES in step S501), the process ends.

  If it is determined that it is not described in step S501 (NO in step S501), driver information of the printer driver is added to the basic OS INF file (step S502).

  Specifically, the setting information of the printer driver in the section with the name surrounded by ““ ”and“ ”in the“ Manufacture ”section B of the existing INF file in FIG. 11 is used for the basic OS. Copy to INF file. In addition, if the “Manufacture” section B and the section in which the setting information of the printer driver is to be described have not yet been created, such information is also created.

  Thereafter, based on the value of the driver information (2002 in FIG. 11), the setting value of the “Install” section (for example, the “PR1000” section in FIG. 11) is copied from the existing INF file to the basic OS INF file, thereby “Install”. Section information (for example, D in FIG. 11) is added (step S503).

  Then, by copying the section in the existing INF file having the same name as the value of the “DataSection” key in the “Install” section (for example, the D “PR1000” section in FIG. 11) to the basic OS INF file being edited, “Data” section information is added (step S504).

  Then, the “FileList” section information is added by copying the section in the existing INF file having the same name as the value of the “CopyFiles” key in the “Install” section to the basic OS INF file being edited (step S505).

  The basic OS INF file editing process has been described above. Although not shown in FIG. 5, after adding information about all printer drivers to the basic OS INF file, for example, information on the [Destination Directors] section and information on the [Strings] section are also added at this time. Become.

  Next, details of the editing process of the alternative OS INF file in step S411 of FIG. 4 will be described with reference to FIG.

  First, the CPU 201 determines whether or not information on the printer driver used in the selected printer has already been described in the alternative OS INF file to be edited.

  In the case of a Windows (registered trademark) INF file, in the section tag with the name of the key value (2001 in FIG. 11) surrounded by ““ ”and“ ”” in the “Manufacture” section in the INF file If the driver name is already included, it is determined that the driver name has already been described. If it is determined that the description has been made (YES in step S601), the process ends.

  If it is determined that it is not described in step S601 (NO in step S601), the driver information of the printer driver is added to the alternative OS INF file (step S602).

  Specifically, the setting information of the printer driver in the section with the name surrounded by ““ ”and“ ”” in the “Manufacture” section of the existing INF file is copied to the alternative OS INF file To do. In addition, if a “Manufacture” section or a section in which setting information of the printer driver is to be described has not yet been created, the information is also created.

  Then, based on the value of the driver information (for example, 2002 in FIG. 11), the setting value of the “Install” section (for example, the “PR1000” section in FIG. 11) is copied from the existing INF file to the alternative OS INF file. “Install” section information (for example, D in FIG. 11) is added (step S603).

  As for the values to be added to the [DataFile] key and the [LanguageMonitor] key, in Windows (registered trademark) XP, the registry HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Print \ Environments \ Windows (registered trademark) NTx86 \ Drivers \ Version Since the information is stored in the [Data File] value [Monitor] value of the key indicated by -2 \ friendly name (driver name), it is obtained from the registry and described.

  Thereafter, the section in the existing INF file having the same name as the value of the “DataSection” key in the driver section (for example, the D “PR1000” section in FIG. 11) is copied to the INF file for the alternative OS being edited. Information is added (step S604).

  In Windows (registered trademark) XP, the value to be added to the [DriverFile] key, [ConfigFile] key, and [HelpFile] key is HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Print \ Environments \ Windows (registered trademark) NTx86 \ in the registry. Information is stored in the [Driver] value, [Configuration File] value, and [Help File] value of the key indicated by Drivers \ Version-2 \ friendly name (driver name). And will be described.

  Then, the copy file section information is added by copying the section in the existing INF file having the same name as the value of the “CopyFiles” key in the driver section to the alternative OS INF file being edited (step S605).

  In Windows (registered trademark) XP, the value to be added to the [DriverFile] key is HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Print \ Environments \ Windows (registered trademark) NTx86 \ Drivers \ Version-2 \ friendly name (driver) Since the information is stored in the value of [Dependent Files] of the key indicated by (Name), it is acquired from the registry and described.

  The above processing is performed for all alternative OSs set in the printer driver being processed, and when editing of all alternative OS INF files is completed, this processing ends.

  Although not described in FIG. 6, after information about all printer drivers is added to the basic OS INF file, for example, information on the “Destination Directors” section and information on the “Strings” section are also added at this time. Become.

  The “Destination Dir” section is not copied as it is, but the respective values are changed based on the Destination Dir correspondence information shown in FIG.

  The above is the editing process of the alternative OS INF file.

  As is apparent from the above description, in this embodiment, based on a device driver already stored in the printer server 101, the environment of the device driver set in the printer server 101 is changed to another printer server or OS. It is possible to create a device driver installer for migrating to the printer server 101 after re-installation. Then, by executing the device driver created according to the present invention, the printer driver is installed in a form reflecting the existing settings.

  In addition, this invention is not limited to what was illustrated to the said embodiment, In the range which does not deviate from the summary of this invention, it can change suitably.

  The object of the present invention is achieved by executing the following processing. That is, a storage medium that records a program code of software that realizes the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus is stored in the storage medium. This is the process of reading the code.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code and the storage medium storing the program code constitute the present invention.

  Moreover, the following can be used as a storage medium for supplying the program code. For example, floppy (registered trademark) disk, hard disk, magneto-optical disk, CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD + RW, magnetic tape, nonvolatile memory card, ROM or the like. Alternatively, the program code may be downloaded via a network.

  Further, the present invention includes a case where the function of the above-described embodiment is realized by executing the program code read by the computer. In addition, an OS (operating system) running on the computer performs part or all of the actual processing based on an instruction of the program code, and the functions of the above-described embodiments are realized by the processing. Is also included.

  Furthermore, a case where the functions of the above-described embodiment are realized by the following processing is also included in the present invention. That is, the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, based on the instruction of the program code, the CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing.

1 is a configuration diagram of a network system including a printer server (installer creation apparatus) as an example of an embodiment of the present invention. FIG. 3 is a block diagram for explaining a hardware configuration of a printer server. FIG. 10 is a flowchart for explaining an example of an installer creation process by the printer server. FIG. 4 is a flowchart for explaining an example of a driver folder creation process in step S304 of FIG. FIG. 5 is a flowchart for explaining an example of a basic OS INF file editing process in step S406 of FIG. 4; FIG. 5 is a flowchart for explaining an example of editing processing of an alternative OS INF file in step S411 of FIG. 4; FIG. 6 is a diagram illustrating an example of a printer selection screen for adding a printer driver to an installer. FIG. 4 is an image diagram of an installer created by the installer creation process of FIG. 3. 6 is a diagram illustrating an example of printer driver information. FIG. It is a figure which shows DistinationDir corresponding | compatible information. It is a figure which shows an example of an INF file. It is a figure which shows an example of an installation information file.

Explanation of symbols

101 Printer server (installation creation device)
102 Information processing apparatus 103 Printer 201 CPU
202 RAM
203 ROM
204 HDD
205 Network I / F
206 Recording medium drive 207 Keyboard 208 Mouse 209 Video I / F
210 Display device 211 External device 212 System bus

Claims (15)

A device that creates a device driver installer,
Setting information acquisition means for acquiring device driver setting information stored in a predetermined storage area;
Definition file generation means for generating a new definition file used by an installation application when installing the device driver based on the information of the definition file corresponding to the device driver acquired by the setting information acquisition means;
Definition file changing means for acquiring predetermined file information included in the device driver, adding the acquired file information to the new definition file, and changing the file;
An installer creation apparatus comprising: a collection unit that collects the file of the device driver based on the file information added by the definition file changing unit and copies the file to a predetermined area. A selection operation means capable of selecting and operating a device driver included in the installer from a plurality of device drivers acquired by the setting information acquisition means;
Receiving means for receiving selection information of the device driver selected by the selection operation means,
The definition file generating means generates the new definition file based on information of a definition file corresponding to the device driver received by the receiving means;
The installer creating apparatus according to claim 1. Security information acquisition means for acquiring security information of the device driver stored in the predetermined storage area;
The installer creation apparatus according to claim 1, further comprising: a security information file generation unit that generates a new security information file based on the security information acquired by the security information acquisition unit. The device driver stored in the predetermined storage area includes an alternative device driver.
The installer creation apparatus as described in any one of Claims 1-3 characterized by the above-mentioned. The definition file changing means adds directory information for recording the alternative device driver to the new definition file during the installation process by the installer application.
The installer creation apparatus according to claim 4. A method of creating a device driver installer,
A setting information acquisition step of acquiring device driver setting information stored in a predetermined storage area;
A definition file generation step for generating a new definition file to be used by the installation application when installing the device driver based on the information of the definition file corresponding to the device driver acquired in the setting information acquisition step;
A predetermined file information included in the device driver, a definition file changing step of changing the file by adding the acquired file information to the new definition file; and
And a collecting step of collecting the device driver files based on the file information added in the definition file step and copying them to a predetermined area. A reception step of receiving selection information of a device driver selected from a plurality of device drivers acquired in the setting information acquisition step;
The definition file generation step generates the new definition file based on information on a definition file corresponding to the device driver received in the reception step.
The installer creation method according to claim 6. A security information acquisition step of acquiring security information of the device driver stored in the predetermined storage area;
The installer creation method according to claim 6, further comprising: a security information file generation step that generates a new security information file based on the security information acquired in the security information acquisition step. The device driver stored in the predetermined storage area includes an alternative device driver.
The installer creation method according to any one of claims 6 to 8. The definition file changing step adds directory information for recording the alternative device driver to the new definition file during the installation process by the installer application.
The installer creation method according to claim 9. A program that causes a computer to execute a process for creating a device driver installer,
A setting information acquisition module for acquiring device driver setting information stored in a predetermined storage area;
A definition file generation module that generates a new definition file to be used by an installation application when installing the device driver based on the information of the definition file corresponding to the device driver acquired by the setting information acquisition module;
A predetermined file information included in the device driver, a definition file change module for changing the file by adding the acquired file information to the new definition file;
Collecting the device driver file based on the file information added in the definition file module, and causing the computer to execute a collection module that copies the file to a predetermined area;
An installer creation program characterized by that. A reception module for receiving selection information of a device driver selected from a plurality of device drivers acquired by the setting information acquisition module;
The definition file generation module generates the new definition file based on information on a definition file corresponding to a device driver received by the reception module.
The installer creation program according to claim 11. A security information acquisition module for acquiring security information of the device driver stored in the predetermined storage area;
The installer creation program according to claim 11, further comprising: a security information file generation module that generates a new security information file based on the security information acquired by the security information acquisition module. The device driver stored in the predetermined storage area includes an alternative device driver.
The installer creation program according to any one of claims 11 to 13. The definition file change module adds directory information for recording the alternative device driver to the new definition file during the installation process by the installer application.
The installer creation program according to claim 14.

Images