JP4812093B2 - Information processing apparatus, information processing apparatus control method, information processing method, program, and storage medium - Google Patents

Description

  The present invention relates to an information processing technique for customizing a device driver.

  With respect to a print control program (printer driver) for controlling a printing apparatus, there has been a demand for customizing a printer driver for controlling a print processing apparatus to be used according to an environment where a printing system is introduced. In particular, in recent years, with the diversification of installation destinations of printing systems, customer usage patterns have also diversified, and customization requests for printer drivers have been increasing.

  In order to meet this demand, in the printer driver of the conventional print processing apparatus, the default setting value is changed and the user interface (hereinafter simply referred to as “UI”) of the printer driver is used in accordance with the usage mode of the customer. A customization technology (customization system) that enables input control (hereinafter referred to as “Disable processing”) that specifies an item that cannot be changed and does not accept input for the item has been provided.

As the above-described prior art, for example, Patent Document 1 and Patent Document 2 exist.
JP-A-8-278871 JP 2003-208276 A

  However, in the conventional customization system, in order to create an installation set of customized printer drivers, first, a printer driver to be customized is installed in the target OS. In that environment, it is necessary to start a tool for creating an installation set of customized printer drivers.

  Also, even when trying to customize multiple printer drivers in one driver set at the same time, only one (one model) printer driver can be customized at a time. Therefore, when customizing a plurality of printer drivers, it is necessary to first customize one type of printer driver and perform the same customization for the next printer driver driver with respect to the customized driver set.

  This is because the conventional customization tool can be customized only when the driver is once installed in the information processing apparatus. In order to customize another driver, it is necessary to install the other driver and restart the customized driver to customize the driver.

  When an information infrastructure administrator tries to create a customized driver for each printing device in a network environment with multiple types of printing devices, the same customization procedure must be repeated for each type of printing device. I must. For this reason, the burden on the information infrastructure manager is large, and the creation efficiency is not good.

  The present invention has been made in view of the above-described prior art. The purpose is to improve the operability of customization.

  It is another object of the present invention to provide an information processing technique that enables a plurality of printer drivers to be customized in one customization process.

An information processing apparatus according to the present invention is an information processing apparatus that customizes a device driver that controls a printing apparatus by setting properties,
A specifying means for specifying a plurality of device drivers by accepting a user operation ;
Wherein for each of the plurality of device drivers is specified unit identified in accordance with the customization completion instruction inputted after the individual customization operation is performed, the individual properties information for each of the plurality of device drivers, the specific And setting means for creating a single driver set including a plurality of individually customized device drivers by setting each of the plurality of device drivers specified by the means.

  According to the present invention, a plurality of printer drivers can be simultaneously customized by a single customization completion instruction after a printer driver customization operation.

[First embodiment]
DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments of the invention will be described with reference to the accompanying drawings. In the present embodiment, a method for customizing a printer driver of Windows (registered trademark), which is an OS (Operating System) for PC manufactured by Microsoft (registered trademark), will be described as an example.

  FIG. 1 is a block diagram showing a configuration of a print processing system according to an embodiment of the present invention. This print processing system includes an information processing apparatus (hereinafter also referred to as “host computer”) 3000 and a printer 1500 that receives print data from the host computer 3000 and performs printing.

  In the host computer 3000, the CPU 1 comprehensively controls each device connected to the system bus 4 according to a program stored in the RAM 2. The RAM 2 also functions as a main memory, work area, and the like for the CPU 1. The ROM 3 stores various programs and data, and is divided into a font ROM 3a that stores various fonts, a program ROM 3b that stores a boot program, BIOS, and the like, and a data ROM 3c that stores various data.

  A keyboard controller (KBC) 5 controls key input from a keyboard (KB) 9 or a pointing device (mouse) (not shown). A CRT controller (CRTC) 6 controls display on a CRT display (CRT) 10. A disk controller (DKC) 7 controls access to an external memory 11 such as a hard disk. The printer controller (PRTC) 8 is connected to the printer 1500 via the bidirectional interface 21 and performs communication control processing with the printer 1500.

  The external memory 11 is, for example, a hard disk (HD), MO, or floppy (registered trademark) disk (FD). As shown in the figure, an operating system program (hereinafter referred to as OS) 205 and various applications (for example, a document processing application program for performing document processing in which graphics, images, characters, tables and the like are mixed) 201 are stored. In addition to storing the print processing related program 204, the external memory 11 also stores user files, edit files, and the like. The print processing related program 204 is a program for generating print data described using a page description language, and can be used in common for a plurality of printers of the same series. The print processing related program 204 also includes a printer control command generation module (hereinafter referred to as a printer driver) 2041 and a printer driver UI control module 2042.

  An application 201 including a customization tool program according to this embodiment (hereinafter simply referred to as “customization tool”) stored in the external memory 11 is loaded into the RAM 2 and executed by the CPU 1. Further, the CPU 1 executes, for example, an outline font development (rasterization) process on the RAM 2 to enable WYSIWYG (What You See Is What You Get) on the CRT 10. Furthermore, the CPU 1 opens various registered windows based on commands instructed by a mouse cursor (not shown) on the CRT 10 and executes various data processing. When the user executes printing, the user can open a print setting screen (controlled by the printer driver UI control module 2042), and perform settings for the printer driver 2041 including printer settings and print mode selection. .

  Next, the configuration of the printer 1500 will be described. The CPU 12 controls the overall operation of the printer 1500. The RAM 19 functions as a main memory, work area, and the like for the CPU 12, and is also used as an output information expansion area and an environment data storage area. The RAM 19 also includes an NVRAM (Non-volatile RAM) area, and is configured such that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown). The ROM 13 includes a font ROM 13a that stores various fonts, a program ROM 13b that stores a control program executed by the CPU 12, and a data ROM 13c that stores various data. The input unit 18 transmits / receives data to / from the host computer 3000. A printing unit interface (I / F) 16 controls an interface with a printing unit 17 that is a printer engine.

  Access to the external memory 14 is controlled by a memory controller (MC) 20 and includes a hard disk (HD), MO, floppy (registered trademark) disk (FD), IC card, and the like connected as options. Then, font data, an emulation program, form data, and the like are stored. When the external memory 14 such as a hard disk is not connected, information used by the host computer 3000 is stored in the data ROM 13c of the ROM 13. The external memory 14 is not limited to one and may include a plurality of external memories. For example, an external memory storing an optional font card, a program for interpreting a printer control language having a different language system, and the like in addition to the built-in font. You may be comprised so that two or more can be connected.

  The operation unit 1501 is provided with an operation panel that receives an operation by a user, and an operation switch, an LED display, and the like are arranged on the operation panel (not illustrated). Further, an NVRAM (Non-volatile RAM) (not shown) may be provided to store printer mode setting information from the operation panel.

  The CPU 12 outputs an image signal as output information to the printing unit (printer engine) 17 via the printing unit interface 16 based on a control program stored in the program ROM 13 b of the ROM 13. Further, the CPU 12 can perform communication processing with the host computer 3000 via the input unit 18. The CPU 12 is configured to receive print data transmitted from the host computer 3000 and to notify the host computer 3000 of information in the printer 1500 and the like.

  FIG. 2 is a diagram showing a memory map of the RAM 2 in a state where a predetermined application and a print processing related program are activated and programs and data are loaded into the RAM 2 of the host computer 3000.

  As shown in the figure, the RAM 2 is loaded with a BIOS 206, an OS 205, an application 201, a print processing related program 204, and related data 203. Furthermore, a free memory area 202 is also secured. As a result, the application 201 and the print processing related program 204 can be executed. Note that the printer driver UI control module 2042 (FIG. 1) in the print processing related program 204 displays a print setting screen on the CRT 10 in response to a print setting command by the user, and enables settings from the user using KB9 or the like. .

  FIG. 3 is a diagram illustrating a UI of the customization tool. The customization tool is assumed to operate on Windows (registered trademark) 2000 / XP / Server 2003. An example is customization of printer drivers for Windows (registered trademark) 98 / ME, Windows (registered trademark) NT4.0, and Windows (registered trademark) 2000 / XP / Server 2003. Note that the gist of the present invention is not necessarily limited to these OSs. The content of simulating the operation of the API corresponding to the OS by changing the setting of an argument for operating an individual function by a pseudo API (which will be described in detail later) without actually installing a printer driver. It is possible to cope by adding it.

  In FIG. 3, when the user designates “Open” in the menu 301, a dialog (not shown) for designating a folder of a driver set to be customized is displayed, and the storage destination of the driver to be customized is designated. it can. The designated folder is displayed in the display column 302, and the corresponding OS of the designated driver set is displayed in the display column 303.

  When a plurality of printer drivers corresponding to printer models (shown as “printer model” in FIGS. 14 to 16) are stored in one driver set folder, a plurality of printer drivers are created when a customized driver is created. Listed (FIG. 19). The customization tool determines whether customization information (customization data) is set for each printer driver listed, and creates a customization driver corresponding to the printer driver for which customization data is set. This process will be described in detail with reference to step S608 in FIG. 6 and the flowchart in FIG. This process is realized by using the pseudo API, so that the driver can be customized one after another without installing and recognizing the driver to be customized to the operating system and making it operable. It becomes possible. A list of printer drivers is displayed on the list display screen 1900 of FIG. A driver can be customized by selecting each driver, reversing black and white, and pressing buttons 1901 to 1903. By pressing a button 1904, a plurality of drivers customized on the list display screen 1900 are generated. Thus, the customization tool is provided as an installation set including a plurality of customized driver groups by pressing the customize button 1904 once.

  The customized data includes various data. This includes control data for displaying / hiding control of the user interface of the device driver and setting values of the device driver as shown in FIG.

  FIG. 18 is a diagram showing an example of the data structure of the device mode (DEVMODE).

  Here, a state in which paper orientation (dmOrientation), paper size (dmPaperSize), paper width (dmPaperWidth), number of copies (dmCopies), and the like are stored is described. In addition, this DEVMODE data structure is stored in the registry. By reading and writing the DEVMODE data structure stored in this registry, the printer driver 2041 can read the default print setting environment and “favorites” described later and reflect them in the user interface.

  Here, “favorite” is a set of a plurality of print settings of the printer driver 2041. The user can obtain a desired operating environment by designating “favorites” consisting of this group of settings on the user interface of the printer driver 2041. For example, in the case of a user who often uses stamps and staples, a set of these staples and stamp settings is registered as a “favorite”, and by simply selecting this “favorite”, a plurality of settings can be set to desired values. Can be printed. Such data is stored as customization data, which is an example of property information, by the customization tool and written in a GPD file to be described later.

  In the list view 305, an identification display “On” is displayed for the printer model to be customized and the customized information. When the check box 310 is checked, the button 311 is enabled. When the button 311 is pressed, a printer driver UI for customization (FIG. 4) is displayed, and initial values such as print settings (document properties) and device settings (printer properties) can be set.

  When the check box 320 is checked, the button 321 is enabled. When the button 321 is pressed, a UI (FIG. 5) for customizing the control display method on the printer driver UI is displayed, and the control display method on the customization printer driver UI can be set.

  When the setting button 350 is pressed on the UI screen in FIG. 3, the settings related to customization set from the UI screen in FIG. 4 or 5 are held as customization information (customization data) in the application (customization tool). For example, the customization tool holds the customization information in a file (hereinafter referred to as “inf file”) that describes printer driver installation information described later with reference to FIG. Whether the printer driver is already customized or not yet customized can be determined from the identification information. A state in which a plurality of printer drivers are stored in one driver set is shown in FIGS. The customization tool determines the presence or absence of customization information, and customizes the printer driver for which customization information is ready (step S608 in FIG. 6, FIG. 17).

  As shown in FIG. 14, the customization information is held in a format in which a printer model name (printer driver corresponding to the printer model) and customization information are paired. The customization information may be held in the form of FIG. 15 or FIG. In the case of FIG. 15, identification information (“Done” or “Not”) that can identify that customization has been performed is held in combination with the printer model name (printer driver) and customization information.

  In the data holding format shown in FIG. 16, the identification information (for example, “0 clear”) indicating that the data is not customized is held in the data corresponding to the uncustomized printer model name. When the customization tool secures the customization information holding area in the inf file, for the printer model that has not been customized, when the setting button 350 is pressed, the customization information is held instead of the identification information. . The customization tool can determine whether the corresponding printer model is customized based on whether identification information is retained or customization information is retained in the customization information retaining area.

  By pressing the button 330, a dialog (not shown) for designating the creation destination of the customized driver is displayed, and the creation destination of the customized driver can be designated.

  When the user presses the button 340 after performing various settings, a printer driver customized according to the settings is created.

  FIG. 4 shows a printer driver UI (initial setting value customization UI) for initial setting value customization of a printer driver (hereinafter also simply referred to as “driver”) displayed when the button 311 is pressed in the UI of FIG.

  The customization tool functions as a setting unit of the information processing apparatus under the control of the CPU 1. The setting unit is, for example, a setting screen for setting document properties and device properties such as a UI screen shown in FIG. Is displayed on the CRT.

  In the printer driver of Windows (registered trademark) NT4.0 and Windows (registered trademark) 2000 / XP / Server 2003, the document property UI for setting a document and the printer property UI for setting a device are set to 1 at the same time. What is displayed in one UI screen cannot be displayed on a UI screen related to printer driver settings by normal installation. However, the printer driver UI for customization according to the embodiment of the present invention is displayed by the customization tool using the module of the printer driver. A document property UI for setting a document and a printer property UI for setting a device are simultaneously displayed as one UI screen (FIG. 4). In FIG. 4, four types of UIs such as page setting 401, finishing 402, paper feed 403, and print quality 404 can be displayed as the document property UI, and the device setting 405 can be displayed as the printer property UI. is there. Through these UIs (401 to 405), it is possible to set the initial value of the document property and the initial value of the printer property.

  Further, regarding settings that are not to be customized, the UI shown in FIG. 4 is configured not to accept input of settings by the user, for example, by gray-out display as indicated by reference numeral 410.

  FIG. 5 is a diagram illustrating a document property display control setting UI, which is displayed on the CRT 10 of the host computer 3000 when the button 321 is pressed in FIG. In the screen example shown in FIG. 5, display control can be set for five types of page settings 501, finishing 502, paper feed 503, print quality 504, and common 505. The page setting 501, finishing 502, paper feed 503, and print quality 504 can be set for display control corresponding to the document property UI shown in FIG. 4, and the common 505 is common to these display controls. The display control can be set.

  Reference numeral 506 specifically indicates the setting of the control item “Job Operations”, and can specify valid display (display as usual), invalid display (always Disable display), and non-display (Hide display). Similarly, display of the document property UI can be controlled by individually setting valid, invalid, and non-display for other control items. Once you enter these settings, the customization tool writes to the GPD file.

  The customization tool functions as a display control unit of the information processing apparatus under the control of the CPU 1. The display control unit can control effective display, invalid display, or non-display of items in the user interface (UI) based on the set document properties (including control items).

  Next, the basic operation of the customization tool will be described using the flowchart of FIG. In the execution of the basic operation, the customization tool executed by the CPU 1 in the host computer 3000 is the main operation.

  First, in step S601, when the user activates the customization tool, the customization tool is initialized. In step S602, the customization tool displays the UI screen described with reference to FIG. In step S603, when the user designates an installation set of the printer driver to be customized from the UI screen of FIG. 3, in step S604, the designated installation set is checked.

  In the installation set check process, the customization tool makes a determination based on the description contents of a file (inf file) describing printer driver installation information shown in FIG. Based on the description contents of the file describing the installation information (701, 710, 720 in FIG. 7), the OS is compatible with the instructed installation set, or the instructed printer driver is a printer driver corresponding to customization by the customization tool. To determine.

  An information processing apparatus that customizes a device driver (printer driver) that controls a printing apparatus by setting properties (initial value data related to a document property for setting a document and initial value data related to a printer property for setting a device) The property information corresponding to the document property or the device property is set in the multiple device drivers specified by the specific unit in response to the customization instruction for one device driver and the specific unit that identifies multiple device drivers. It is preferable to include a setting unit. In this case, in the information processing apparatus, each unit described above executes processing of each unit by executing the customization tool under the control of the CPU 1.

  Here, FIG. 7 is a diagram illustrating the description content of an inf file describing installation information of the printer driver. This inf file includes module description information (not shown), and based on this module description information, the customization tool can specify the module that is performing the UI processing of the printer driver. In FIG. 7, 700 indicates a part of an inf file for Windows (registered trademark) 98 / ME, 710 indicates a part of an inf file for Windows (registered trademark) NT4.0, and 720 indicates a Windows (registered). (Trademark) A part of inf file for 2000 / XP / Server2003 is shown. If the “Signature” setting 730 in the inf file 700 is a character string resource (“$ CHICAGO $”), the customization tool executed by the CPU 1 determines that the printer driver is for Windows (registered trademark) 98 / ME. To do.

  Also, the customization tool uses Windows (registered) if the “Signature” setting (740, 750) in the inf file (710, 720) is a character string resource (“$ Windows (registered trademark) NT $”). (Trademark) It is determined that the driver is for NT4.0 or Windows (registered trademark) 2000 / XP / Server 2003. Further, in order to narrow down the customization tool, if “NT” is included in the setting character string resource of “DISK1” (760, 770) in the inf file (710, 720), Windows ( (Registered trademark) Judged for NT4.0. If “NT” is not included, it is determined that the product is for Windows (registered trademark) 2000 / XP / Server 2003.

  The printer driver that supports customization includes a character string resource in the inf file to indicate that. For this reason, the customization tool can determine whether the character string resource is included in the inf file of the printer driver when determining whether it is compatible with customization.

  Returning to FIG. 6, if the customization tool determines in step S605 that the printer driver does not support customization (S605-NO), the process proceeds to step S610. Then, error processing is performed, and the process returns to the installation set instruction step (S603) again.

  On the other hand, in the determination in step S605, if the customization tool determines that the printer driver supports customization (S605-YES), the process proceeds to step S606. The customization tool controls the CRTC 6 to display the UI screen described with reference to FIGS. 3 to 5 on the CRT 10 to enable customization of the printer driver.

  The settings input in FIGS. 3 to 5 are the customization data. The customization data is set in a GPD file that is a file that can be read by the printer driver. When the printer driver is installed and set to the operating state, it reads the setting value in the GPD file. Then, the printer driver reflects the customized value in the GPD file to the printer driver. For example, frequently used print setting values (double-sided, 2-in-1 etc.) are preset in the printer driver. By simply installing a customized driver, the printer driver uses frequently used print setting values and customized default values for print settings that are set in the driver when the driver is instructed to return to the state before the operation. Will be set to.

  When an instruction to create a customized driver is issued in step S607, a customized driver creation process is performed in step S608. Here, FIG. 17 is a diagram for explaining the specific processing contents of the processing in step S608, and the flow of processing for customizing a plurality of printer drivers existing in one driver set collectively. It is a flowchart explaining these.

  In the customization driver creation process, the customization tool first copies the customization source installation set to the customization driver creation destination. Thereafter (S1701), the customization tool checks the order of the printer drivers listed in the inf file in order to identify the device driver for setting the customization data. For example, in the case of FIG. 14, the printer model 3, the printer model 7, the printer model 1, and the printer model 2 are used in this order. Then, it is checked whether customized data is set (S1702). The customization tool can determine the setting of the customization data based on the presence or absence of the identification information described with reference to FIGS. 15 and 16. The customization tool may specify a device driver for setting customization data in response to an input of a selection instruction from the outside such as a user. In that case, the user is required to input information described in the INF file, such as the printer driver type and the storage location of the customization data.

  If the customization data is set in the corresponding printer driver (YES in S1703), the process proceeds to step S1704. The customization tool writes customization data to a driver information file (this file is also referred to as “UPD file”) included in the copy destination installation set (S1704), thereby creating a customized driver (S1705). In step S1706, if all the printer drivers listed are not checked (S1706—NO), the process returns to step S1703. Then, it is checked whether customization data is set for the next printer driver (S1703). If set, the customization tool repeatedly performs the process of writing the customization data to the UPD file of the corresponding printer driver. If all the printer drivers listed have been checked (S1706: YES), the flowchart of FIG. 17 is terminated, and the process returns to step S608 of FIG. With the above processing, a customization driver reflecting customization data is created by the customization tool for a plurality of printer drivers present in one driver set.

  An information processing apparatus that customizes a device driver (printer driver) that controls a printing apparatus by setting properties (initial value data related to a document property for setting a document and initial value data related to a printer property for setting a device) The property information corresponding to the document property or the device property is set in the multiple device drivers specified by the specific unit in response to the customization instruction for one device driver and the specific unit that identifies multiple device drivers. And a setting unit. In the information processing apparatus, each unit described above executes processing of each unit by executing a customization tool under the control of the CPU 1.

  Here, FIG. 9 is a diagram illustrating the data format of a driver information file (UPD file), which is one file constituting the printer driver. As shown in the figure, the UPD file includes a header 901, an ID definition 902, and data 903. The ID definition 902 stores a set of an ID of data stored in the data 903 and a storage position (address) of the data. The set is stored as a set corresponding to the number of IDs. In the customization tool according to the present embodiment, the data value corresponding to the ID defined for customization is changed. If the ID of customization data to be used is not defined in the ID definition 902, a new ID corresponding to the customization data is added to the ID definition 902.

  The customized printer driver reads the UPD file in which the customization data is written by the customization tool at the time of installation or first activation. Then, it is implemented so as to read data 903 stored in association with a predetermined ID in the ID definition 902 of the UPD file. For example, it is assumed that an ID indicating “CUSTUMIZED” and an address X as the data storage position are stored in the ID definition 902 in the UPD file created by the customization tool.

  The printer driver that supports customization is mounted in advance so that when ID information indicating “CUSTUMIZED” is stored in the ID definition 902 at the time of completion of installation or initial startup, an address corresponding to the information is read. Therefore, this printer driver reads the address X of the corresponding data from the ID definition when the ID is displayed in the ID definition 902 of the UPD file when the installation is completed or at the first activation. Subsequently, the printer driver further reads the data structure of the device mode, which is actual driver setting data, from the data 903 of the address X. Here, the address X may be an absolute address, or the head address of the data 903 is stored in the header 901 and the offset address from the head address of the data 903 is set in the address X. Good.

  The customization tool functions as a display control unit of the information processing apparatus under the control of the CPU 1. The display control unit refers to the driver information file (UPD file) of the printer driver when the printer driver is activated. The user interface can be displayed on the CRT 10 based on the customization data set in the UPD file.

  In this embodiment, the customization tool uses, as customization data, initial value data relating to document properties for setting a document (data set by 401 to 404 in FIG. 4) and initial values relating to printer properties for setting a device. Data (set by 405 in FIG. 4) and data related to the display method of controls on the UI related to document properties (data set from the UI screen in FIG. 5) are written into the UPD file. The customized printer driver operates based on the customization information by reading the UPD file created by the customization tool when the installation is completed or at the first activation. Thereby, the operating environment of the customized printer driver can be easily constructed.

  Returning to FIG. 6, after the customization driver is created (S608), when the user gives an end instruction (S609), the operation of the customization tool is ended (S611).

  Next, processing for displaying a printer driver customization UI by the customization tool executed by the CPU 1 will be described with reference to the flowchart of FIG. In the execution of this process, it is assumed that the customization tool executed by the CPU 1 in the host computer 3000 is the main operation.

  When the button 311 in FIG. 3 is pressed, the customization tool specifies the module that performs the UI processing of the printer driver based on the module description information included in the inf file. Then, it is loaded into the memory so that it can be called from the customization tool (S801).

  In step S802, the address of the function exported by the printer driver module is acquired (S802). Then, a CSPL structure (not shown), which is a structure for exchanging information between the customization tool and the printer driver that supports customization, is initialized (S803). Various information is stored in the CSPL structure so that UI control of the printer driver is possible even if it is not installed.

  In step S804, a property sheet (customization driver UI) is displayed. At this time, as shown in FIG. 4, the property sheet display function is called so that both property pages are displayed on one UI screen so that the document property and the printer property can be customized at the same time.

  When the customization driver UI is closed by the user, information set in the customization driver UI is held in the CSPL structure. Therefore, the customization tool acquires printer driver information corresponding to the information from the CSPL structure (including the DeviceOption structure and Devmode structure) (S805).

  The customization tool functions as an acquisition unit that acquires printer driver data corresponding to document properties or device properties under the control of the CPU 1. The acquisition unit can acquire printer driver information by holding data related to printer driver settings and exchanging data with a data holding unit (CSPL structure) capable of transferring data. At this time, the acquisition unit causes the data holding unit (CSPL structure) to hold data corresponding to the document property or device property set on the UI screen (FIGS. 3 to 5). Printer driver information corresponding to these properties can be acquired from the data holding unit (CSPL structure) as customization setting information.

  The customization tool writes the contents of the data holding unit into a GPD file described later. When invoked, the printer driver determines whether there is a customized GPD file. When the printer driver determines that there is a customized GPD file, the printer driver reads customized print settings, UI control data, and the like in the customized GPD file. The printer driver is customized.

  That is, the customization tool that functions as a display control unit calls the UI module of the printer driver based on the setting information for customization. The called UI module of the printer driver is displayed on the customization information CRT 10 set via the UI shown in FIGS. 3 to 5 using a pseudo API described later. For example, the CRT 10 displays a customized user interface reflecting the control display control, the default value of the print setting information, and the like.

  As customization setting information, printer property setting information is stored in a DeviceOption structure (not shown), and document property setting information is stored in a Devmode structure (not shown). The customization tool acquires the setting information stored in these as customization setting information.

  Thereafter, in step S806, the module loaded in the memory in the previous step S801 is unloaded, and the display of the customization driver UI is ended (S807).

  This processing flow is slightly different depending on the corresponding OS of the printer driver. For example, Windows (registered trademark) NT4.0 and Windows (registered trademark) 2000 / XP / Server 2003 use an OS mechanism called Common Property SheetUI for displaying the driver UI. Therefore, necessary preprocessing is performed and the Common Property SheetUI function is called. On the other hand, in Windows (registered trademark) 98 / ME, necessary pre-processing is performed, and the Property Sheet function is called to display the UI. However, the basic processing flow is as shown in FIG.

  FIG. 10A is a diagram for explaining calling of a Windows (registered trademark) API (Application Programming Interface) implemented by the printer driver. When the printer driver is installed, in the printer driver UI processing 1010, a Windows (registered trademark) API (simply shown as “API” in the figure) is called 1040 (during normal calling), and customization is supported. When the printer driver is not installed and the call is made from the customization tool, the pseudo Windows (registered trademark) API 1060 (simply shown as “pseudo API” in the drawing) is called (1050), and the correspondence relationship is established. A certain Windows (registered trademark) API process is simulated in a pseudo Windows (registered trademark) API, and the result is returned to the printer driver UI process 1010.

  1030 shown in FIG. 10B is a diagram showing the relationship between the Windows (registered trademark) API and the corresponding pseudo (registered trademark) API name (in the diagram, indicated as “API” and “pseudo API name”, respectively). The correspondence relationship can be set in advance in the printer driver. Normally, a program that controls the user interface of the printer driver calls a Windows (registered trademark) API in response to an input to the driver. In this embodiment, the Windows (registered trademark) API cannot be called in a state where the printer driver is not installed, but the pseudo API can be called.

  In the case of a call from the customization tool, the pseudo Windows (registered trademark) API simulates the processing of the Windows (registered trademark) API and returns the processing to the printer driver UI processing 1010 to the OS. When the printer driver is called as a normal driver UI after being installed, a normal Windows (registered trademark) API 1020 is called and the processing is returned to the printer driver UI processing 1010.

  FIG. 11 is a flowchart for explaining the flow of processing related to calling a pseudo Windows (registered trademark) API (simply referred to as “pseudo API” in the figure). In the execution of this process, it is assumed that the customization tool executed by the CPU 1 in the host computer 3000 is the main operation.

  First, in step S1110, the customization tool receives the address information (hereinafter simply “address”) of the CSPL structure in which the printer handle (argument) included in the argument of the pseudo Windows (registered trademark) API is passed when calling from the customization tool. It is also referred to as “information”. In this determination method, since the top member of the CSPL structure indicates the size of the CSPL structure, the passed printer handle (argument) is referred to as the head address of the CSPL structure, and the CSPL structure is referred to. If it is equal to the size, the printer handle of the argument is determined to be the address of the CSPL structure (S1110-YES). The printer driver UI module stores the processing result, for example, the value of each item of the print setting input through the UI and the designation of the control display in the structure designated by the handle, and ends the processing.

  When the printer handle of the argument is not the address of the CSPL structure (S1110-NO), normal printer driver operation is performed. In this case, the Windows® API (simply indicated as “API” in the figure) is called as it is (S1120), and the process is terminated. The printer driver UI module stores the processing result, for example, the value of each item of the print setting input through the UI and the designation of the control display in the structure designated by the handle, and ends the processing.

  If it is determined in step S1110 that the printer handle of the argument matches the address of the CSPL structure (S1110-YES), the process proceeds to step S1130 to call from the customization tool, that is, the printer driver is not installed. In the state, call the Windows (registered trademark) API. In this case, since the Windows (registered trademark) API cannot be called without the printer driver installed, a process equivalent to the Windows (registered trademark) API is performed by the pseudo Windows (registered trademark) API (S1130). The process result is returned to the printer driver UI process 1010, and the process ends.

  Through the above processing, the customization tool functions as a selection unit of the information processing apparatus under the control of the CPU 1. The selection unit uses an application program interface (Windows (registered trademark) API or pseudo Windows (registered)) to be used (to be called) based on address information (start address) held in the data holding unit (CSPL structure). Trademark) API).

  FIG. 12 is a flowchart showing a processing flow when a CSPL_GetVersionEx () function (see 1040 in FIG. 10B) is called from the printer driver as an example of the pseudo Windows (registered trademark) API. In executing this process, the printer driver UI is called by the customization tool executed by the CPU 1 in the host computer 3000, and further the CSPL_GetVersionEx () function is called. The Windows (registered trademark) API simulated by this function is Windows (registered trademark) GetVersionEx () (see Table 1030 in FIG. 10B), and this Windows (registered trademark) API is running on the host computer. A process of returning information related to the OS version to the process 1010 on the printer driver UI side is performed.

  First, in step S1210, the CSPL_GetVersionEx () function determines whether the printer handle that is an argument of the function is the address of the CSPL structure that is passed at the time of calling. This determination method is the same as the determination method described in step S1110 of FIG. If it is not the address of the CSPL structure (S1210-NO), the process proceeds to step S1220, and the GetVersionEx () function 1040, which is a Windows (registered trademark) API that operates as a normal printer driver, is called (S1220). Exit.

  On the other hand, if it is determined in step S1210 that the function argument matches the address of the CSPL structure (S1210—YES), the process proceeds to step S1230, and the printer driver stored in the CSPL structure is supported. Based on the OS information to be executed, the GetVersionEx () function process is simulated (a process equivalent to the GetVersionEx () function process is executed) (S 1230). In step S1230, the CSPL_GetVersionEx () function returns the same processing result as the GetVersionEx () function to the printer driver UI module. The same applies to other functions.

  For example, the application program interface (pseudo Windows (registered trademark) API) that is called in response to the document property or device property set from the UI screen of FIGS. Processes the printer driver for properties in a pseudo manner (executes processing equivalent to that of Windows (registered trademark) API).

  After the process of step S1230 or step S1220, the process of the flowchart of FIG.

  Thereby, for example, when the processing related to the UI control of the driver module of Windows (registered trademark) 98 / ME is performed by a call from the customization tool, the OS that is actually operating is the Windows supported by the customization tool. (Registered Trademark) 2000 / XP / Server 2003, but the CSPL structure contains information that Windows (registered trademark) 98 / ME is supported as an OS supported by the driver module. As a result, a value of “Windows (registered trademark) ME” is returned so that the UI control processing of the driver module of Windows (registered trademark) 98 / ME does not fail.

  That is, the target of customization is a printer driver of Windows (registered trademark) 98 / ME and driver information (for example, an INF file and a driver user interface module). In this embodiment, the customization tool corresponds to Windows (registered trademark) 2000 / XP / Server 2003, and the environment in which the customization tool is executed is controlled by one of these OSs. Since the CSPL structure is initialized in step S803 of FIG. 8, for example, information indicating that it is Windows (registered trademark) 98 / ME is written in the CSPL structure as data indicating the version of the OS. As a result, the CSPL structure includes information (OS version information) that the OS supported by the driver module is Windows (registered trademark) 98 / ME. In step S1230, the CSPL_GetVersionEx () function accesses the OS version information of the CSPL structure, and returns a value of “Windows (registered trademark) ME” to the call source printer driver UI module.

  The same applies to other pseudo Windows (registered trademark) APIs, and since the printer driver is not actually installed, inconvenience occurs in the UI control of the driver module by calling the Windows (registered trademark) API. Even if it happens, the operation of the Windows (registered trademark) API can be virtually reflected in the UI control by simulating the processing of the Windows (registered trademark) API by the processing in the pseudo function (pseudo API). Is possible.

  Although not explicitly shown, the printer driver of Windows (registered trademark) 98 / ME is originally a module that operates in a 16-bit environment. Therefore, the UI processing is also performed in a 16-bit environment. However, the printer driver of Windows (registered trademark) 98 / ME that is the target of this embodiment uses a OS mechanism called thunk-up for UI processing over 16-bit environment in the UI processing, and the 32-bit environment. The UI is actually processed. For this reason, from the customization tool of this embodiment, a UI processing function that operates in a 32-bit environment that performs actual UI processing can be called to display and control the UI of Windows (registered trademark) 98 / ME. It can be done relatively easily.

  That is, the customization tool acquires properties including print settings. Then, the customization tool registers the device driver in the operating system so as to be operable. That is, the device driver can read the properties including the print settings acquired by the customization tool without registering and installing in the registry area managed by the operating system using the authority of the operating system administrator. In addition, the device driver can be set. At the time of the setting, the device driver is stored in the user area of the file system managed by the operating system.

  Properties are stored in a UPD file by the customization tool. The created UPD file constitutes an installation set together with a printer driver to be customized, a printer driver UI module, and an inf file. The created installation set is distributed to client computers via a recording medium or a communication medium. The installer executes the installation according to the description of the inf file. The installer copies the value corresponding to each setting item read from the UPD file as the value of the corresponding item in the devmode structure or deviceOption structure. The printer driver and the printer driver UI module operate by referring to the value of each item stored in the devmode structure or deviceOption structure.

  The above-described processing is executed by a customization tool that is an example of an application program. The customization tool further responds to the device driver on behalf of the operating system for input of information via the device driver.

  And since there is a pseudo proxy response of this customization tool, the device driver recognizes the response from the application as a response from the operating system without falling into error processing, and then performs setting processing by input from the user To continue.

  Further, the customization tool is configured by a pseudo API for the printer driver. Furthermore, the customization tool can set properties including the print settings for device drivers for a plurality of types of operating systems (for example, Windows (registered trademark) NT, Windows (registered trademark) 95).

  The customization tool can set information related to print settings acquired by the customization tool with a single instruction for a plurality of device drivers.

  The pseudo API in the present embodiment causes the device driver to have an illusion that the device driver is installed in an operating state by imitating the operating environment of the device driver. If the customization tool does not respond to the device driver in a pseudo manner, the device driver shifts to error processing. Thereby, the customization process by the customization tool can be continued without installing the device driver.

  FIG. 13 is a flowchart for explaining the flow of UI control processing regarding printer driver property settings corresponding to customization. In the execution of this processing, it is assumed that the customization tool executed by the CPU 1 in the host computer 3000 is the main operation. In the procedure of FIG. 13, the pseudo API function shown in FIG. 11 and FIG. 12 is called, and property sheet display, parameter acquisition, and setting value input are realized.

  First, in step S1300, when a UI control instruction is input, the customization tool is activated. In step S1310, UI initialization processing is performed. If the customization information related to UI display is in the driver information file shown in FIG. 9 in step S1320 (S1320—YES), the process proceeds to step S1330. The display control (Disable control, Hide control) on the UI is reflected in the instruction, and a user operation standby state is set (S1340). On the other hand, if there is no driver information file (S1320-NO), the process of step S1330 is skipped, and a user operation standby state is set (S1340).

  Then, it waits until a user's operation is performed (S1340). When the operation for closing the UI is performed (S1350-YES), the UI processing is terminated (S1370). When the operation is for another operation (S1350-NO), UI control corresponding to the user operation is performed. (S1360), the process returns to step S1320.

  The property information input from the UI is saved again in the printer driver information file (UPD file) via the CSPL structure. At this time, the customization code 350 of FIG. 3 is stored in the printer driver information file together with a predetermined identification code.

  Accordingly, the customization data related to the control display method instructed in FIG. 5 is held in the driver information file shown in FIG. 9, so that UI control can be displayed according to the customization data.

  In this embodiment, customization information is written in a driver information file called a UPD file. However, as long as the printer driver can refer to the file and can be analyzed, the form is limited to the UPD file. is not. Accordingly, in Longhorn, which is the next Windows (registered trademark), a GPD file is standard as a driver information file for a printer driver. However, customization information may be incorporated in this file.

  According to the present embodiment, a plurality of printer drivers can be simultaneously customized by a single customization completion instruction after the printer driver customization operation.

  Even if the printer driver is for an OS that does not support customization, a customized driver reflecting the customization desired by the user can be created.

  Further, since customization of the initial setting value of the printer driver can be performed using a UI equivalent to the UI of the printer driver, the initial setting operation for customization can be easily performed. By reflecting the contents of customization set using such UI and controlling the effective display, invalid display, and non-display of display items, the user's work efficiency and the convenience of operation can be improved. Become.

  The customized driver has the same configuration as an installation set of uncustomized drivers. It can also operate as a customized driver in a so-called Point & Print environment in Longhorn, which is a product of Microsoft (registered trademark), Windows (registered trademark) operating system, or the next OS. Thereby, the versatility of the customized driver can be improved.

[Other embodiments]
Needless to say, the object of the present invention can also be achieved by supplying a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus. Needless to say, this can also be achieved by the computer (or CPU or MPU) of the system or apparatus reading and executing the program code stored in the storage medium.

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

  As a storage medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a nonvolatile memory card, a ROM, or the like can be used.

  Further, the functions of the above-described embodiment are realized by executing the program code read by the computer. In addition, an OS (operating system) running on a computer performs part or all of actual processing based on an instruction of a program code, and the above-described embodiment is realized by the processing. Needless to say.

  When the present invention is applied to the above-described storage medium, the storage medium stores program codes corresponding to the flowcharts described above (FIGS. 6, 8, 11 to 13, and 17). Become.

1 is a block diagram illustrating a configuration of a print processing system according to an embodiment of the present invention. 3 is a diagram illustrating a memory map of the RAM 2 in a state where a predetermined application and a print processing related program are activated and programs and data are loaded into the RAM 2 of the host computer 3000. FIG. It is a figure which illustrates UI of a customization tool. 6 is a diagram illustrating a printer driver UI for initial setting value customization. FIG. It is a figure which illustrates document property display control setting UI. It is a flowchart explaining the flow of a process of the basic operation | movement in a customization tool. FIG. 6 is a diagram exemplifying description contents of an inf file that describes printer driver installation information. 10 is a flowchart illustrating a flow of processing for displaying a printer driver customization UI. FIG. 4 is a diagram for explaining a data format of a UPD file constituting a printer driver. It is a figure explaining the call of the application program interface (API) which the printer driver is mounted. It is a figure which shows the relationship between pseudo API corresponding to API. It is a flowchart explaining the flow of a process regarding the call of pseudo | simulated Windows (trademark) API. It is a flowchart which shows the flow of a process in the case of calling a CSPL_GetVersionEx () function as an example of pseudo | simulated Windows (trademark) API. 10 is a flowchart for explaining a UI control processing flow regarding printer driver property settings corresponding to customization. It is a figure explaining the holding | maintenance format of customization information. It is a figure explaining the holding | maintenance format of customization information. It is a figure explaining the holding | maintenance format of customization information. FIG. 6 is a flowchart for explaining a flow of processing for collectively performing customization for a plurality of printer drivers existing in one driver set. FIG. It is a figure which shows an example of the customization data of a device driver. It is a figure which illustrates UI of the tool which customizes multiple drivers.

Claims (24)

An information processing device that customizes a device driver that controls a printing device by setting properties,
A specifying means for specifying a plurality of device drivers by accepting a user operation ;
Wherein for each of the plurality of device drivers is specified unit identified in accordance with the customization completion instruction inputted after the individual customization operation is performed, the individual properties information for each of the plurality of device drivers, the specific An information processing apparatus comprising: setting means for creating a single driver set including a plurality of individually customized device drivers by setting each of the plurality of device drivers specified by the means.   2. The setting unit according to claim 1, wherein the setting unit determines whether property information for the plurality of device drivers is set, and writes the property information to an information file when the property information is set. Information processing device.   The information processing apparatus according to claim 1, further comprising: a display control unit that causes a display unit to display a customized user interface based on data corresponding to the set property information.   The information processing apparatus according to claim 3, wherein the display control unit controls effective display, invalid display, or non-display of items in the user interface based on property information set by the setting unit. .   5. The information processing according to claim 4, wherein the display control unit displays the user interface based on property information obtained by referring to an information file of the device driver when the device driver is activated. apparatus.   The plurality of device drivers respectively correspond to a plurality of models and are included in the same device driver set, and the setting means includes a property in the information file readable by the plurality of device drivers. The information processing apparatus according to claim 2, wherein information is written.   2. The specification unit reads a device driver list or model from data stored in a memory of an information processing apparatus, and the setting unit specifies a device driver for setting property information. The information processing apparatus described in 1.   The information processing apparatus according to claim 1, wherein the specifying unit specifies a device driver for the setting unit to set property information in accordance with an external selection instruction. A method of controlling an information processing apparatus that customizes a device driver that controls a printing apparatus by setting properties,
A specifying step in which the specifying unit of the information processing apparatus specifies a plurality of device drivers by accepting a user operation ;
Setting means of the information processing apparatus, wherein for each of the plurality of device drivers specified step has been specified, in accordance with the customized input completion indication after individual customization operation is performed, each of the plurality of device drivers s individual property information for, by setting each of the plurality of device drivers the specific process is identified, it and a setting step of creating a single set of drivers that includes a plurality of device drivers that are customized individually A control method characterized by the above.   10. The setting step determines whether property information for the plurality of device drivers is set, and writes the property information to an information file when the property information is set. Control method. The display control unit of the information processing apparatus further includes a display control step of causing the display unit to display a customized user interface based on data corresponding to the set property information. Control method.   The control method according to claim 11, wherein the display control step controls effective display, invalid display, or non-display of items in the user interface based on the property information set by the setting step.   13. The control method according to claim 12, wherein the display control step displays the user interface based on property information obtained by referring to an information file of the device driver when the device driver is activated. .   The plurality of device drivers respectively correspond to a plurality of models and are included in the same device driver set, and the setting step includes a property in the information file readable by the plurality of device drivers. The control method according to claim 10, wherein information is written.   10. The specifying step reads a device driver list or model from data stored in a memory of an information processing apparatus, and the setting step specifies a device driver for setting property information. The control method described in 1.   The control method according to claim 9, wherein the specifying step specifies a device driver for the property information to be set by the setting step in accordance with an external selection instruction. A device driver for controlling the printing apparatus, a computer readable storage medium storing a control program for the control method to be executed by a computer of the information processing apparatus of an information processing apparatus for customizing the setting of property, the control method ,
A specifying step in which the specifying unit of the information processing apparatus specifies a plurality of device drivers by accepting a user operation ;
Setting means of the information processing apparatus, wherein for each of the plurality of device drivers specified step has been specified, in accordance with the customized input completion indication after individual customization operation is performed, each of the plurality of device drivers s individual property information for, by setting each of the plurality of device drivers the specific process is identified, it and a setting step of creating a single set of drivers that includes a plurality of device drivers that are customized individually A storage medium characterized by the above. An information processing apparatus for creating a driver set for installing a plurality of device drivers,
A specifying means for specifying a plurality of device drivers to be customized by accepting a user operation ;
The specific means by pairs to each of the plurality of device drivers specified, to customize print settings, and a setting means for setting property information by individual customizing operation,
The information processing apparatus characterized by comprising a generating means for generating a single set of drivers that includes a plurality of device drivers that are customized individually by setting the property information by said setting means.   19. The information processing apparatus according to claim 18, wherein the specifying unit specifies a plurality of device drivers using driver information read in advance in a customization program. The information processing apparatus according to claim 19 , wherein the driver information is information used when installing a plurality of device drivers having property information set by the setting unit. An information processing method in an information processing apparatus for creating a driver set for installing a plurality of device drivers,
A specifying step of specifying a plurality of device drivers to be customized by accepting a user operation by the specifying means of the information processing apparatus ;
Setting means of the information processing apparatus, the specific step by pairs to each of the plurality of device drivers specified, to customize print settings, a setting step of setting property information by individual customizing operation,
Creating means of the information processing apparatus is characterized by having a generation step of generating a single set of drivers that includes a plurality of device drivers that are customized individually by setting the property information by said setting step Information processing method.   The information processing method according to claim 21, wherein the specifying step specifies a plurality of device drivers using driver information read in advance in a customization program. 23. The information processing method according to claim 22 , wherein the driver information is information used when installing a plurality of device drivers having property information set in the setting step. A program for causing a computer to execute an information processing method of the information processing apparatus in an information processing apparatus for creating a driver set for installing a plurality of device drivers, said information processing method,
A specifying step of specifying a plurality of device drivers to be customized by accepting a user operation by the specifying means of the information processing apparatus ;
Setting means of the information processing apparatus, the specific step by pairs to each of the plurality of device drivers specified, to customize print settings, a setting step of setting property information by individual customizing operation,
Creating means of the information processing apparatus is characterized by having a generation step of generating a single set of drivers that includes a plurality of device drivers that are customized individually by setting the property information by said setting step program.

Images