JP2005267541A - Peripheral equipment driver, peripheral equipment controller, and installation method for peripheral equipment control driver - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a peripheral equipment driver, a peripheral equipment controller and a method for installing a peripheral equipment control driver for installing a driver in a PC without making it necessary for a user to designate the machine type or option configuration of peripheral equipment. <P>SOLUTION: Only a program which is commonly available to all peripheral equipment is stored in a universal driver whose connection target peripheral equipment is not determined, and when the connection target peripheral equipment is determined, a dependent file stored in the peripheral equipment is acquired and loaded so as to prepare UI capable of setting function processing to be supported by the peripheral equipment, and to register it as a peripheral equipment driver unique to the peripheral equipment in an OS. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a peripheral device driver, a peripheral device control device, and a peripheral device control driver installation method, and more particularly, to a peripheral device driver, a peripheral device control device, and a peripheral device control driver corresponding to a model of a peripheral device connected to a network. It relates to the installation method.

  When a job is issued from a host computer (hereinafter referred to as a PC [Personal Computer]) to peripheral devices such as printers, scanners, fax machines, and copiers connected to the network, and these peripheral devices are managed. In this case, it is necessary to know the type and model of the peripheral device in advance and prepare an appropriate peripheral device control program (hereinafter referred to as a driver) corresponding to the model in the PC.

  In order to install the driver on the OS (Operating System) of the PC, an OS standard installation wizard or a setup tool provided by each vendor is provided, and a single package supports multiple models in the installation work. In this case, the user must select the model to be installed and the optional configuration.

  Conventionally, as a means for informing the user of the model and optional configuration, there is a method of picking up the model name by broadcasting the peripheral device connected to the network, and the locally connected peripheral device is connected with PnP (Plug and Play) There is something to detect.

For example, an information processing apparatus, an information processing method, an information processing system, a storage medium storing an information processing program, and information for automatically configuring a user interface of a control program for controlling the peripheral device according to a function acquired from the peripheral device There are a transmission apparatus and an information processing program product for transmitting a processing program (for example, see Patent Document 1).
JP 2000-137593 A

  However, in the OS standard installation wizard or vendor setup tool, if the peripheral device is powered off at the time of driver installation, the model name and optional configuration of the peripheral device cannot be acquired. In addition, if multiple model names are listed, the correct model name may not be known, and the user may ask the administrator about the model name or check the model name in the peripheral device manual. Work was necessary.

  Accordingly, the present invention provides a peripheral device driver, a peripheral device control apparatus, and a peripheral device control driver installation method that can install a driver on a PC without allowing the user to specify the model name or optional configuration of the peripheral device. The purpose is to do.

  In order to achieve the above object, the invention of claim 1 is stored in an information processing apparatus connected to at least one peripheral device via a network, and is common to all peripheral devices in a peripheral device driver that controls the peripheral device. A differential program to be added to the basic program held by the peripheral device to be connected, a functional program corresponding to a function supported by the peripheral device, and data and programs depending on the peripheral device A process for acquiring a peripheral device dependent file including the peripheral device dependent file, a process for adding the acquired peripheral device dependent file to the basic program, and a basic program with the peripheral device dependent file added to the peripheral device. If it is a dependent program, the process of registering in the information processing apparatus is operated on the computer. And wherein the Rukoto.

  The basic program corresponds to the drawing core program 111, the drawing layouter processing program 121, the PJL output program 131, the UI basic module 12 and the Inf program 151 shown in FIG. 2, and the difference program is the addition of the drawing core program shown in FIG. The function difference file 112, the drawing layouter processing program additional function difference file 122, and the PJL output program additional function difference file 132 are supported. The function program corresponds to the image processing-specific component 17 shown in FIG. The peripheral device dependent file corresponds to the printer dependent file 16 shown in FIG.

  According to a second aspect of the present invention, in the first aspect of the invention, the data dependent on the peripheral device is function correspondence information describing the presence or absence of support corresponding to the function, and the program dependent on the peripheral device is A function-corresponding processing program that configures a user interface specific to the peripheral device based on the function-corresponding information, and displays a user interface configured by the function-corresponding processing program by a basic program to which the peripheral device dependent file is added A process for displaying on the apparatus is caused to operate on a computer.

  The function correspondence information corresponds to the function correspondence information 20 shown in FIG. 3, and the function correspondence processing program corresponds to the UI function correspondence processing module 18 shown in FIG.

  According to a third aspect of the present invention, in the first aspect of the present invention, the processing for starting the function program is caused to operate in a computer by the difference program.

  According to a fourth aspect of the present invention, in the second aspect of the present invention, the function prohibition processing information describing the prohibition of operation conflict between the functions held by the peripheral device to be connected is described from the peripheral device. Based on the acquired function prohibition process information, the computer is caused to operate a process for resolving a conflict that occurs between functions displayed on the user interface.

  The function prohibition process information corresponds to the prohibition process matrix 19 shown in FIG.

  According to a fifth aspect of the invention, in the second aspect of the invention, when the peripheral device is requested to perform processing without displaying the user interface on the display device, the peripheral device supports based on the function correspondence information. A process for confirming a function to be performed, and a process for starting the function program by the difference program according to the confirmation.

  According to a sixth aspect of the present invention, in the first aspect of the invention, when the function program is stored in a storage device on a network, the peripheral device dependent file is acquired from the peripheral device, and the function is stored from the storage device. The computer is caused to operate a process for acquiring a program.

  According to a seventh aspect of the present invention, in the peripheral device control apparatus that controls at least one peripheral device on the network, the peripheral program includes a basic program that is common to all peripheral devices and is held by the peripheral device to be connected. A peripheral device dependent file including a difference program to be added to the basic program, a function program corresponding to a function supported by the peripheral device, and data and programs depending on the peripheral device is acquired from the peripheral device, and the acquisition is performed. The added peripheral device dependent file is added to the basic program, and the basic program to which the peripheral device dependent file is added is registered as a program dependent on the peripheral device.

  The basic program corresponds to the drawing core program 111, the drawing layouter processing program 121, the PJL output program 131, the UI basic module 12 and the Inf program 151 shown in FIG. 2, and the difference program is the addition of the drawing core program shown in FIG. The function difference file 112, the drawing layouter processing program additional function difference file 122, and the PJL output program additional function difference file 132 are supported. The function program corresponds to the image processing-specific component 17 shown in FIG. The peripheral device dependent file corresponds to the printer dependent file 16 shown in FIG.

  The invention according to claim 8 is the invention according to claim 7, wherein the data dependent on the peripheral device is function correspondence information describing the presence or absence of support corresponding to the function, and the program depending on the peripheral device is A function-corresponding processing program that configures a user interface specific to the peripheral device based on the function-corresponding information, and displays a user interface configured by the function-corresponding processing program by a basic program to which the peripheral device dependent file is added It is displayed on a device.

  The function correspondence information corresponds to the function correspondence information 20 shown in FIG. 3, and the function correspondence processing program corresponds to the UI function correspondence processing module 18 shown in FIG.

  The invention according to claim 9 is the invention according to claim 7, wherein the function program is activated by the difference program.

  Further, the invention of claim 10 provides the function prohibition processing information in which the prohibition of operation conflict occurring between the functions held by the peripheral device to be connected is described in the invention of claim 8 from the peripheral device. Acquired, and based on the acquired function prohibition processing information, a conflict occurring between functions displayed on the user interface is resolved.

  The function prohibition process information corresponds to the prohibition process matrix 19 shown in FIG.

  Further, in the invention of claim 11, in the invention of claim 8, when a request is made to the peripheral device without displaying the user interface on the display device, the peripheral device supports based on the function correspondence information. The function program is confirmed, and the function program is started by the difference program according to the confirmation.

  The invention of claim 12 is the invention of claim 7, wherein when storing the function program in a storage device on a network, the peripheral device dependent file is acquired from the peripheral device, and the function is stored from the storage device. It is characterized by acquiring a program.

  According to a thirteenth aspect of the present invention, in a method of installing a peripheral device driver that is stored in an information processing apparatus connected to at least one peripheral device via a network and controls the peripheral device, the peripheral device has a common specification for all peripheral devices. A difference program to be added to the basic program held by a peripheral device to be connected, a function program corresponding to a function supported by the peripheral device, and data and programs depending on the peripheral device. A peripheral device dependent file is acquired from the peripheral device, the acquired peripheral device dependent file is added to the basic program, and the basic program to which the peripheral device dependent file is added is a program that depends on the peripheral device. It is registered in the information processing apparatus.

  According to a fourteenth aspect of the present invention, in the invention of the thirteenth aspect, the data dependent on the peripheral device is function correspondence information describing the presence or absence of support corresponding to the function, and the program dependent on the peripheral device is A function-corresponding processing program that configures a user interface specific to the peripheral device based on the function-corresponding information, and displays a user interface configured by the function-corresponding processing program by a basic program to which the peripheral device-dependent file is added It is displayed on a device.

  The invention of claim 15 is characterized in that, in the invention of claim 13, the function program is activated by the difference program.

  Further, in the invention of claim 16, in the invention of claim 14, function prohibition processing information describing prohibition of operation conflict occurring between the functions held by the peripheral device to be connected is described from the peripheral device. Acquired, and based on the acquired function prohibition processing information, a conflict occurring between functions displayed on the user interface is resolved.

  Further, in the invention of claim 17, in the invention of claim 14, when the peripheral device is requested to perform processing without displaying the user interface on the display device, the peripheral device supports based on the function correspondence information. The function program is confirmed, and the function program is started by the difference program according to the confirmation.

  The invention of claim 18 is the invention of claim 13, wherein when storing the function program in a storage device on a network, the peripheral device dependent file is acquired from the peripheral device and the function is stored from the storage device. It is characterized by acquiring a program.

  According to the present invention, after a user actually connects a peripheral device, it can be used immediately, and when installing as a system such as a PC and a network environment, a printer, a scanner, etc., a specific peripheral device model is provided. Even if it is not selected, it is possible to provide an environment in which peripheral device drivers are installed.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

  As an embodiment of the present invention, a configuration in which a PC (Personal Computer) and a printer are connected via a network and a peripheral device driver according to the present invention is installed in the PC will be described in detail as an example.

  FIG. 1 is a block diagram showing an example of the overall configuration of a print system 1 used in the embodiment of the present invention.

  As shown in FIG. 1, a PC 2 and a plurality of printers 3 are connected via a network 4. A plurality of printers 3 are not necessarily required.

  The configuration of the PC 2 will be described in detail.

  As shown in FIG. 1, the PC 2 includes a CPU 5, a ROM 6, a RAM 7, an HD 8, and an I / F 9.

  A CPU (Central Processing Unit) 5 performs sequence control of the PC 2 main body based on an operating system (hereinafter referred to as OS) which is basic software.

  A ROM (Read Only Memory) 6 records a program executed when the PC 2 is activated.

  A RAM (Random Access Memory) 7 is used as a buffer area of a work area necessary for program execution.

  An HD (Hard Disk) 8 stores an OS, an application program (hereinafter referred to as an application), a peripheral device driver, or various data.

  An I / F (Interface) 9 transmits and receives various data to and from the printer 3 on the network 4.

  Although not particularly illustrated, the PC 2 is a display device such as a monitor display that can visually display various information such as an application screen and a printer driver UI (User Interface), a CD-ROM drive, and a floppy (registered trademark). ) It has a configuration of an input device such as a disk drive or a keyboard and a mouse.

  Next, the peripheral device driver according to the present invention will be described in detail. The peripheral device driver installed in the PC 2 is in a state in which the printer 3 as an actual output destination is undecided and can be applied to all models (that is, common specifications among all models). The peripheral device driver according to the present invention in such a state is a universal driver.

  FIG. 2 is a diagram illustrating an example of the configuration of the universal driver 10.

  As shown in FIG. 2, the universal driver 10 includes a drawing core program 111, a drawing layouter processing program 121, a PJL output program 131, a UI basic module 14, and an Inf file 151.

  The drawing core program 111 performs negotiation processing with the OS and applications.

  The drawing layouter processing program 121 performs page layout and scaling processing according to the value of Devmode.

  The PJL output program 131 performs output processing of the printer JOB language.

  The UI basic module 14 is a program for performing processing for displaying a basic printer driver UI. Specifically, a UI component definition for each function realized by the printer 3 (for example, “paper size selection function” is displayed in a combo box), and a Devmode definition for each function (that is, selected by each function). To which parameter of Devmode the value to be applied is processed).

  Note that Devmode is a parameter for exchanging values between the printer driver defined in the OS and the application.

  The UI basic module 14 supports functions that need to be notified to an application, and supports the basic Devmode (Devmode used in common for all printers).

  The drawing core program 111, the drawing layouter processing program 121, the PJL output program 131, and the UI basic module 14 are described as an Inf file 151.

  Next, the configuration of the printer dependent file stored in the printer 3 will be described in detail.

  FIG. 3 is a diagram illustrating an example of the configuration of the printer-dependent file 16.

  As shown in FIG. 3, the printer-dependent file 16 includes a drawing core program additional function difference file 112, a drawing layouter processing program additional function difference file 122, a PJL output program additional function difference file 132, and image processing. Equal purpose components (monochrome water / forms, color water / forms, color discrimination, image quality adjustment, color adjustment, NIE, RLE compression, DeltaRaw compression, Jpeg compression) 17, UI function compatible processing module 18, prohibition processing It consists of a matrix 19, an Inf file 152, and function correspondence information 20.

  The difference file 112 of the additional function of the drawing core program, the difference file 122 of the additional function of the drawing layouter processing program, and the difference file 132 of the additional function of the PJL output program are function processing program parts different for each model, and the names are Different for each model.

  For example, the Font function (printer font / TT font) or the like as an additional function of the drawing core program 111, and the additional functions of the PJL output program 131 such as enlarged continuous shooting, image repetition, and booklet as additional functions of the drawing layouter processing program 121 , SavedPrint, SecurePrint, etc.

  Note that these difference files are copied to the System folder of the PC 2 when the first printing is executed or when the UI is opened, and the file names are also registered in the registry at the same time. Thereafter, it is called from the universal driver 10 as a processing routine using this registry registration name.

  The purpose-specific component 17 such as image processing is a purpose-specific processing module for image processing such as compression or color conversion.

  The purpose-specific component 17 such as image processing is called from the difference file. That is, the module name to be called for each process is hard-coded in the difference file.

  Further, since the image processing purpose-specific component 17 can be used in common among models, it can also be applied to a configuration in which it is stored in an external device on the network 4 and downloaded when necessary.

  The UI model-compatible processing module 18 describes UI resource or special control processing, and also includes a UI display bitmap prepared for each printer 3.

  The UI model corresponding processing module 18 is copied to the System folder of the PC 2 at the time of the first printing execution or when the UI is opened, and the file name is also registered in the registry at the same time. Thereafter, it is called from the universal driver 10 as a processing routine using this registry registration name.

  The prohibition processing matrix 19 is a file describing prohibition conditions for each model, and is processed in synchronization with the UI function corresponding processing module 18.

  The Inf file 152 is different from the Inf file 151 of the universal driver 10 and is an Inf file 152 corresponding to the model. In addition, when installing PnP (Plug and Play), this Inf file 152 is referred to.

  In the function correspondence information 20, a table of functions and options supported by the stored printer is binary data.

  The function correspondence information 20 includes a Devmode structure and a function information structure FunctionInfo.

  The Devmode structure is a Devmodel target model initial value (information for determining a Devmode value necessary for execution of printing).

  The function information structure FunctionInfo is a structure having fixed-length byte data (option information necessary for UI display) for each function.

  Next, the function information structure FunctionInfo21 will be described in detail.

  FIG. 4 is a diagram illustrating an example of the function information structure FunctionInfo21.

  As shown in FIG. 4, the function information structure FunctionInfo 21 is composed of one Function_Info structure for one control and a plurality of SELECT_ITEM structures subordinate to the Function_Info structure (the number of wItemNums of the Function_Info structure).

For example, in the case of a model having a saw turbine and a large capacity discharge tray, the Function_Info structure is
strFuncName ← "Destination"
wSelMethod ← combo box wItemNum ← 5
The five SELECT_ITEM structures subordinate to this Function_Info structure are
SELECT_ITEM structure 1 {strItemName ← “standard”, idDevmode ← dmOutput, dwValue ← 1}
SELECT_ITEM structure 2 {strItemName ← “saw turbine 1”, idDevmode ← dmOutput, dwValue ← 3}
SELECT_ITEM structure 3 {strItemName ← “saw turbine 2”, idDevmode ← dmOutput, dwValue ← 4}
SELECT_ITEM structure 4 {strItemName ← “saw turbine 3”, idDevmode ← dmOutput, dwValue ← 5}
SELECT_ITEM structure 5 {strItemName ← “large capacity discharge tray”, idDevmode ← dmOutput, dwValue ← 9}
It becomes.

In the case of a model having a staple or booklet folding function, the Function_Info structure is
strFuncName ← “Finish”
wSelMethod ← combo box wItemNum ← 3
And the three SELECT_ITEM structures subordinate to this Function_Info structure are
SELECT_ITEM structure 1 {strItemName ← “none”, idDevmode ← dmFinish, dwValue ← 0}
SELECT_ITEM structure 2 {strItemName ← “staple”, idDvmode ← dmFinish, dwValue ← 1}
SELECT_ITEM structure 3 {strItemName ← “booklet folding”, idDevmode ← dmFinish, dwValue ← 2}
It becomes.

  Note that the function correspondence information 20 may be stored in the same location as the printer-dependent file 16 or in another location (for example, a memory on the printer 3 or an external device on the network 4). good. In this case, the automatic update may be performed by obtaining a time stamp or the like of another holding location and comparing it with the time stamp or the like of the function corresponding information in the printer driver.

  The value of Devmode when the universal driver 10 is first installed (printer-independent installation) is set to an appropriate temporary setting value. Since this temporary setting value is not actually used, any value may be used, but it is more practical to set the value to be actually used. This temporary setting value is registered in the OS by the same process as the standard value of Devmode of the conventional printer 3 at the first installation, and the version at this time is set to “1.00”.

FIG. 5 shows a process performed by the universal driver 10 when a print instruction is received without opening the UI (when printing a test page, printing without opening the UI with a print button or “Ctl + P” from an application). The version of Devmode called at the time of printing, which will be described with reference to the flowchart shown, is checked (step S501).

  If the version is not 1.00 (NO in step S501), the process ends.

  If the version is 1.00 (YES in step S501), a printer-dependent file is acquired from the printer (step S502).

  Note that the name of the printer dependent file 16 is different for each model. For example, the name of the difference file 112 of the additional function of the drawing core program is “AddCore.dll”, the name of the difference file 122 of the additional function of the drawing layouter processing program is “AddRay.dll”, and the difference of the additional function of the PJL output program The name of the file 132 is first registered in the universal driver 10 as “AddPJL.dll”. By registering the file name in the registry when acquiring the printer dependent file 16 and calling the name registered in the universal driver 10 first, the printer dependent file 16 acquired from the printer can be used as a processing module. .

  In addition, when the printer 3 is a model that supports Network MIB or the like, a configuration in which the printer dependent file 16 is acquired from the printer 3 and the optional configuration of the printer 3 is acquired at the same time is also applicable. However, the Devmode acquired from the function correspondence information 20 is not prohibited in principle, but the option configuration acquired from the printer 3 is not assumed or the function correspondence information 20 is changed due to an update or the like. May be prohibited.

  The acquired printer dependent file is copied to the System folder (step S503), the corresponding Devmode value is acquired (step S504), and a prohibition check is performed (step S505).

  If there is no prohibition (NO in step S506), the process proceeds to step S510.

  If there is a prohibition (YES in step S506), it is confirmed whether or not the change is possible (step S507).

  If the change is possible (YES in step S507), the conflict value is changed (step S508).

  If the change is impossible (NO in step S507), a function drop message due to competition is displayed (step S509).

  The registry Devmode is merged (step S510).

  It should be noted that the specified value of the corresponding model driver is determined by registering the difference file of the additional function and merging the registry Devmode.

  Version 1. xx is changed (step S511), and the process is terminated.

  When the printer driver is activated, the difference file 112 “AddCore.dll” of the additional function of the drawing core program is loaded. This name is fixed and hard-coded in the universal driver 10. Since the contents of the difference file are different for each model, the purpose-specific component 17 such as image processing is loaded according to the model configuration or function.

  A process performed by the universal driver 10 when the UI is opened (when the UI is opened from the printer properties or when the setting screen of the printer 3 is opened from the print menu of the application) will be described in detail. If a predetermined registry key has not been created at the time when the opening of the UI is instructed, it is determined that the UI is opened for the first time.

  When the specified value of Devmode has already been set (Version is not 1.00) (for example, when printing has already been performed by a test print or the like), the Function_Info structure is acquired from the printer 3 and the Function_Info structure is acquired. If successful, a predetermined registry key is created and the acquired Function_Info structure is stored. At the UI display time, UI information is configured in the memory area according to the Function_Info structure.

  When the specified value of Devmode is not set (Version is 1.00) (when the UI is opened for the first time when printing is not performed), the specified value of Devmode is obtained by performing the processing of the flowchart shown in FIG. When the Function_Info structure is acquired from the printer 3 and the Function_Info structure is successfully acquired, a predetermined registry key is created, and the acquired Function_Info structure is stored. At the UI display time, UI information is configured in the memory area according to the Function_Info structure.

  Next, processing performed by the universal driver 10 when the UI is opened will be described with reference to the flowchart shown in FIG.

  The version of Devmode is checked (step S601).

  If the version is not 1.00 (NO in step S601), the process proceeds to step 603.

  When Version is 1.00 (YES in step S601), the specified value of Devmode is acquired by performing the processing of the flowchart shown in FIG. 5 (step S602).

  The presence / absence of the Function_Info structure is checked (step S603).

  If there is a Function_Info structure (YES in step S603), the process advances to step S605.

  If there is no Function_Info structure (NO in step S603), the Function_Info structure is acquired from the printer (step S604).

  The data is expanded in the UI memory (step S605), the prescribed value of Devmode is reflected (step S606), and if a prohibition occurs in the prescribed value of Devmode, the conflict is resolved (step S607), and the process is terminated.

  Then, in the UI display process, a model-specific UI can be realized by changing the UI function support processing module 18 names from the UI basic module 14 with fixed names and changing the contents for each model. Further, by including a machine bit map or the like, the UI display bit map can be changed according to the connected model.

  By setting a specified value of Devmode and storing the Function_Info structure acquired from the printer 3, the universal driver 10 is registered in the OS as a printer driver dependent on the printer 3.

  Next, the function correspondence information 20 will be described in detail.

  FIG. 7 is a diagram illustrating an example of the function correspondence information 20.

  As shown in FIG. 7, the function correspondence information 20 describes whether or not there is support for a function in the printer 3 (for example, Printer A) and options corresponding to the function.

  Note that “corresponding Devmode” indicates Devmode corresponding to each function, and “component” indicates a component corresponding to each option name. The component “B1” indicates the drawing core, the component “B2” indicates the drawing layouter process, the component “B3” indicates the PDL output, the component “B4” indicates the monochrome water / forms, and the component “B3”. “B5” indicates color water / forms, component “C1” indicates color discrimination, component “C2” indicates image quality adjustment, component “C3” indicates color adjustment, and component “C4” indicates NIE. , Component “C5” indicates RLE compression, component “C6” indicates DeltaRaw compression, and component “C7” indicates JPEG compression.

  Next, the function prohibition processing matrix 19 will be described in detail.

  FIG. 8 is a diagram illustrating an example of the main rule ability prohibition processing matrix 19.

  As shown in FIG. 8, the prohibition process matrix 19 of the main rule shows competing data for each function and options for each function (in the case of prohibition, “x” is attached).

  For example, the option name “A3” corresponding to the function name “document size” is prohibited from the option name “same as document size” corresponding to the function name “output size”, and the option corresponding to “paper tray selection”. The name “tray 1” is the option name “user-defined size” corresponding to the function name “original size”, the option names “OHP film”, “thick paper”, “coated paper”, “label” corresponding to the function name “paper type”. "Paper", "postcard", and "envelope" are prohibited.

  Accordingly, when “A3” is selected for the function name “document size”, the UI basic module 14 dims out the option name “same as document size” corresponding to the function name “output size” in gray. When “tray 1” is selected as the function name “paper tray selection”, the option name “user-defined size” corresponding to the function name “original size” and the option name “OHP” corresponding to the function name “paper type” are selected. Dim out the film, cardboard, coated paper, label paper, postcard, and envelope in gray.

  FIG. 9 is a diagram illustrating an example of the graphics prohibition processing matrix 19.

  As shown in FIG. 9, the graphics prohibition processing matrix 19 shows competing data for each function and options for each function (in the case of prohibition, “x” is attached).

  Note that the printer driver registered in the OS does not need to be overwritten by the universal driver 10, and can be registered as another icon. In that case, a single universal driver 10 can automatically create a plurality of printer icons corresponding to a plurality of types of printers 3 on the network 4.

  In addition, as the timing of requesting the function correspondence information 20 from the printer 3, it can be considered that the load on the network 4 or a decrease in printing performance is made at the time of each printing. Considering this, it is possible to condition the required timing, and several cases can be selected as conditions.

1. Only once for the first time. 2. A certain amount of time has elapsed since the previous acquisition of the function correspondence information 20. 3. When an information update request is received from the printer 3 side When an information update request is made through the UI In case 1, if the printer driver is registered as a printer driver with the printer name on the OS of the PC 2, no information request is issued. When the printer driver name is overwritten as the universal driver 10 as it is, if an additional function difference file exists, an information request is not issued or an information acquisition end key is registered in the registry.

  In case 2, the time stamp of the final history is registered in the registry or the like at the end of information acquisition. If the time stamp is registered, the current time is compared with the time stamp at the timing when the printer driver UI is opened. If the specified time has passed, an information acquisition request is issued to the printer.

  In case 3, when an installation option is changed or a consumable (such as a toner cartridge) is replaced, an information request command is transmitted from the printer program to the PC. In response, the printer driver issues an information acquisition request to the printer.

  In case 4, when an instruction means is given from the user such as attaching a driver update button to the printer driver UI, an information request is issued according to the instruction selection.

The present invention can also be applied to a configuration in which the PC 2 and the printer 3 are locally connected (whether wired or wireless). )
Further, the present invention is not limited to the configuration in which the universal driver 10 is installed in the PC 2 as in the above-described embodiment, and the configuration of the peripheral device control device having the same function as that of the universal driver 10 described above. Applicable.

1 is a block diagram illustrating an example of an overall configuration of a print system 1 used in an embodiment of the present invention. 2 is a diagram illustrating an example of a configuration of a universal driver 10. FIG. 3 is a diagram illustrating an example of a configuration of a printer dependent file 16. FIG. It is a figure which shows an example of the function information structure FunctionInfo21. 7 is a flowchart showing processing performed by the universal driver 10 when a print instruction is received without opening the UI (when printing a test page, printing without opening the UI with a print button or “Ctl + P” from an application). is there. It is a flowchart which shows the process which the universal driver 10 performs when UI is opened. It is a figure which shows an example of the function corresponding | compatible information 20. FIG. It is a figure which shows an example of the main rule ability prohibition process matrix 19. FIG. It is a figure which shows an example of the prohibition process matrix 19 of graphics.

Explanation of symbols

1 Printing system 2 PC
3 Printer 4 Network 5 CPU
6 ROM
7 RAM
8 HD
9 I / F
10 Universal Driver 111 Drawing Core Program 112 Difference File of Additional Functions of Drawing Core Program 121 Drawing Layouter Processing Program 122 Difference File of Additional Functions of Drawing Layouter Processing Program 131 PJL Output Program 132 Difference File of Additional Functions of PJL Output Program 14 UI basic module 151, 152 Inf file 16 Printer-dependent file 17 Component according to purpose such as image processing 18 UI function compatible processing module 19 Prohibited processing matrix 20 Function corresponding information

Claims (18)

In a peripheral device driver that is stored in an information processing apparatus connected to at least one peripheral device via a network and controls the peripheral device,
It has a basic program that is common to all peripheral devices,
Peripheral device dependent file including a differential program added to the basic program held by the peripheral device to be connected, a function program corresponding to a function supported by the peripheral device, and data and programs depending on the peripheral device, Processing acquired from the peripheral device;
Processing for adding the acquired peripheral device dependent file to the basic program;
A peripheral device driver that causes a computer to perform a process of registering the basic program to which the peripheral device dependent file is added as a program dependent on the peripheral device, in the information processing apparatus. The data depending on the peripheral device is
It is function correspondence information describing the presence or absence of support corresponding to the function,
The program that depends on the peripheral device is:
A function handling processing program that configures a user interface specific to the peripheral device based on the function correspondence information;
The peripheral device driver according to claim 1, wherein the computer is caused to operate a process of displaying a user interface configured by the function corresponding processing program on a display device by a basic program to which the peripheral device dependent file is added. The peripheral device driver according to claim 1, wherein the computer is caused to operate a process of starting the function program by the difference program. Processing to obtain from the peripheral device function prohibition processing information describing prohibition of operation conflict between the functions held by the peripheral device to be connected;
The peripheral device driver according to claim 2, further comprising: causing the computer to perform a process of resolving a conflict that occurs between functions displayed on the user interface based on the acquired function prohibition process information. When requesting the peripheral device to perform processing without displaying the user interface on the display device,
Based on the function correspondence information, a process for confirming a function supported by the peripheral device;
The peripheral device driver according to claim 2, wherein, according to the confirmation, the computer is caused to operate a process of starting the function program by the difference program. When storing the function program in a storage device on a network,
The peripheral device driver according to claim 1, wherein the peripheral device-dependent file is acquired from the peripheral device, and the computer is caused to operate a process of acquiring the functional program from the storage device. In a peripheral device control apparatus that controls at least one peripheral device on the network,
It has a basic program that is common to all peripheral devices,
Peripheral device dependent file including a differential program added to the basic program held by the peripheral device to be connected, a function program corresponding to a function supported by the peripheral device, and data and programs depending on the peripheral device, Acquired from the peripheral device,
Add the acquired peripheral device dependent file to the basic program,
A peripheral device control apparatus, wherein the basic program to which the peripheral device dependency file is added is registered as a program depending on the peripheral device. The data depending on the peripheral device is
It is function correspondence information describing the presence or absence of support corresponding to the function,
The program that depends on the peripheral device is:
A function handling processing program that configures a user interface specific to the peripheral device based on the function correspondence information;
8. The peripheral device control device according to claim 7, wherein a user interface configured by the function corresponding processing program is displayed on a display device by a basic program to which the peripheral device dependent file is added. The peripheral device control device according to claim 7, wherein the function program is activated by the difference program. The function prohibition processing information describing the prohibition of operation conflict occurring between the functions held by the peripheral device to be connected is acquired from the peripheral device,
The peripheral device control device according to claim 8, wherein a conflict that occurs between functions displayed on the user interface is resolved based on the acquired function prohibition processing information. When requesting the peripheral device to perform processing without displaying the user interface on the display device,
Based on the function correspondence information, check the functions supported by the peripheral device,
The peripheral device control device according to claim 8, wherein the function program is activated by the difference program according to the confirmation. When storing the function program in a storage device on a network,
The peripheral device control device according to claim 7, wherein the peripheral device dependent file is acquired from the peripheral device, and the function program is acquired from the storage device. In a method of installing a peripheral device driver that is stored in an information processing device connected to at least one peripheral device via a network and controls the peripheral device,
A basic program that is common to all peripheral devices
Peripheral device dependent file including a differential program added to the basic program held by the peripheral device to be connected, a function program corresponding to a function supported by the peripheral device, and data and programs depending on the peripheral device, Acquired from the peripheral device,
Add the acquired peripheral device dependent file to the basic program,
A method of installing a peripheral device driver, wherein the basic program to which the peripheral device dependent file is added is registered in the information processing apparatus as a program depending on the peripheral device. The data depending on the peripheral device is
It is function correspondence information describing the presence or absence of support corresponding to the function,
The program that depends on the peripheral device is:
A function handling processing program that configures a user interface specific to the peripheral device based on the function correspondence information;
The method for installing a peripheral device driver according to claim 13, wherein a user interface configured by the function corresponding processing program is displayed on a display device by a basic program to which the peripheral device dependent file is added. The peripheral device driver installation method according to claim 13, wherein the function program is activated by the difference program. The function prohibition processing information describing the prohibition of operation conflict occurring between the functions held by the peripheral device to be connected is acquired from the peripheral device,
The peripheral device driver installation method according to claim 14, wherein a conflict that occurs between functions displayed on the user interface is resolved based on the acquired function prohibition processing information. When requesting the peripheral device to perform processing without displaying the user interface on the display device,
Based on the function correspondence information, check the functions supported by the peripheral device,
The peripheral device driver installation method according to claim 14, wherein the function program is activated by the difference program according to the confirmation. When storing the function program in a storage device on a network,
The peripheral device driver installation method according to claim 13, wherein the peripheral device dependent file is acquired from the peripheral device, and the function program is acquired from the storage device.

Images