JP2006185157A - Printing control device, printing control method, printing control program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a printing control device that enables a user to recognize only usable printers before commanding printing start. <P>SOLUTION: A client computer 3000 (printing control device) comprises printer drivers for controlling printers 1500 connected via a network 301. A CPU 101 acquires a printer ticket present in a predetermined location (print server 4000) on the network 301. A registry of the client computer 3000 holds printer driver setting information set according to the printer ticket. According to the printer ticket acquired by the CPU 101, the printer driver setting information is set to enable or disable the printer drivers. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a print control apparatus, a print control method, a print control program, and a recording medium that are communicably connected to a printer, and in particular, a print control apparatus, a print control method, a print control program, and a recording medium that restrict use permission of a printer. About.

  Conventionally, in order to share a printer, a configuration in which a client computer and a printer are connected via a network has been adopted, and a plurality of client computers can share and use a printer connected on the network. ing.

  However, from the viewpoint of confidentiality and cost saving, there is a need to restrict the use of printers or restrict the use of printer functions so that output from a specific user or a specific client computer is not permitted. It has occurred.

  On the other hand, for example, when printing from a client computer to a printer, a print job is sent based on the information of “MachineName”, “UserName”, “Time”, and “Status” described in the “User Management File” A printing system that permits printing when a client computer name, a login user name, and a printing time are matched is known (for example, see Patent Document 1).

  In addition, when there are a large number of printers on the network, it may be difficult to determine which printing apparatus should be used in order to obtain a printing style desired by the user. In particular, it is difficult for users who do not know which printers can be used or for users who have little knowledge about printers. In addition, there is a problem that a print output desired by the user cannot be obtained after the user executes printing. In order to obtain an output desired by the user, a print control system is known that automatically selects a printer that can perform printing desired by the user from available printers and performs printing (see, for example, Patent Document 2).

In this print control system, a printer driver and a printer that match print settings set by the user are automatically selected, and printing processing is performed. In this print control system, a printer that satisfies the selected function is automatically selected from printers grouped in advance.
JP 2001-188663 A JP-A-7-121322

  However, after instructing the start of printing, the printing system of Patent Document 1 refers to the “user management information file” and determines whether or not printing can be performed at the stage of transmitting a print job to the printer. After instructing the start of printing, the system knows the result of whether printing can be performed for the first time. Therefore, there is a problem that it is not known whether printing can be performed until the start of printing is instructed. The mechanism for managing printing is performed by mutual communication between the printer server and the client, and there is a problem that it cannot be applied to a stand-alone client.

  When the administrator unilaterally restricts printing to the client, it is unclear which printer can perform printing and which functions can be used with an available printer. Therefore, it is conceivable to use the technique of Patent Document 2 in order to automatically search for a printer that can print under desired conditions.

  However, in Patent Document 2, since a printer group that matches a function desired by the user is selected from a group of printers grouped in advance, a printer that meets the user's request is selected from a limited range. It will be. Therefore, the subject that the range of the function which a user desires has narrowed implicitly is mentioned.

  Further, in Patent Document 2, there is a problem that the user is forced to grasp the function of the printer. Furthermore, since it is impossible to suggest which printers can be used by the client and what functions can be selected from the printers, there is a disadvantage in that useless setting is performed.

  An object of the present invention is to provide a print control apparatus, a print control method, a print control program, and a recording medium that allow a user to recognize only a usable printer before instructing the start of printing.

  In order to achieve the above object, a print control apparatus according to claim 1 is a print control apparatus including a printer driver that controls a printer connected via a network, and printer setting data existing at a predetermined position on the network. A printer setting data acquisition unit for acquiring the printer driver, a holding unit for holding setting information of the printer driver set based on the printer setting data, and the printer driver can be used or used based on the acquired printer setting data And a driver setting means for performing setting for disabling the setting information of the printer driver.

  The print control method according to claim 10 is a print control method applied to a print control apparatus including a printer driver for controlling a printer connected via a network, and printer setting data existing at a predetermined position on the network. A printer setting data acquisition step for acquiring printer information, a holding step for holding printer driver setting information set based on the printer setting data, and the printer driver can be used or used based on the acquired printer setting data And a driver setting step for performing setting for disabling the setting information of the printer driver.

  The print control program according to claim 11 is a print control program executed by a computer including a printer driver for controlling a printer connected via a network, and acquires printer setting data existing at a predetermined position on the network. A printer setting data acquisition module, a holding module for holding printer driver setting information set based on the printer setting data, and the printer driver can be used or not used based on the acquired printer setting data And a driver setting module for setting the printer driver setting information for the setting information of the printer driver.

  A recording medium according to claim 12 is a computer-readable recording medium having a printer driver for controlling a printer connected via a network, and a printer for acquiring printer setting data existing at a predetermined position on the network A setting data acquisition module, a holding module that holds setting information of a printer driver set based on the printer setting data, and the printer driver can be used or disabled based on the acquired printer setting data And a driver setting module for performing setting for the setting information of the printer driver.

  According to the print control apparatus of claim 1, the print control method of claim 10, the print control program of claim 11, and the recording medium of claim 12, printer setting data existing at a predetermined position on the network is acquired, Printer driver setting information set based on the printer setting data is held, and settings for enabling or disabling the printer driver are set for the printer driver setting information based on the acquired printer setting data. Therefore, the setting information of the printer driver set based on the printer setting data is updated, and the latest printer environment can always be reflected. As a result, it is possible to make the user recognize only usable printers before instructing the start of printing.

  According to the second and third aspects of the present invention, it is possible to make the user recognize only usable printer functions before instructing the start of printing.

  According to the print control apparatus of the seventh aspect, the printer can be set without the user being aware of the prohibited items. Thereby, a user's print setting can be performed smoothly.

  According to the print control apparatus of the eighth aspect, it is possible to execute automatic selection of the printer in accordance with the user's request, and the user's troublesomeness in selecting the printer can be reduced.

  According to the printing control apparatus of the ninth aspect, it is possible to use a printer that is not permitted to be used or a function whose use is restricted.

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

  FIG. 1 is a block diagram showing a configuration of a printing system to which a printing control apparatus according to an embodiment of the present invention is applied.

  The printing system in FIG. 1 mainly includes a client computer (hereinafter referred to as “client PC”) 3000 and a printer 1500 as print control apparatuses.

  In FIG. 1, the ROM 103 or the external memory 111 included in the client PC 3000 includes a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as “OS”) that is a control program of the CPU 101, and functions executed by the client PC 3000. Various programs described below necessary for realizing the above are stored. The OS used in this embodiment is, for example, Windows (registered trademark) XP manufactured by Microsoft Corporation, but is not limited thereto. The RAM 102 functions as a main memory or work area for the CPU 101. The CPU 101 implements various processes by loading a program necessary for executing various processes, necessary data, and the like into the RAM 102 and executing the programs.

  An input controller (input C) 105 controls input from a keyboard (KB) 109 or a pointing device such as a mouse (not shown). A video controller (VC) 106 controls display on a display device such as a CRT display (CRT) 110. The display may be a liquid crystal display or the like as well as a CRT. These are used by the administrator as needed.

  The memory controller (MC) 107 includes a hard disk (HD), a floppy (registered trademark) disk (FD), a boot program, browser software, various applications, font data, user files, edit files, various data, and the like. Alternatively, access to an external memory 111 such as a compact flash (registered trademark) memory connected to the PCMCIA card slot via an adapter is controlled.

  The communication I / F controller (communication I / FC) 108 is connected to and communicates with an external device via the network 121, and executes communication control processing of the client PC 3000. For example, Internet communication using TCP / IP or data transmission / reception with the printer 1500 is performed.

  For example, the CPU 101 can display the CRT 110 by executing outline font development (rasterization) processing in a display information area (not shown) in the RAM 102. Further, the CPU 101 enables a user instruction with a mouse cursor (not shown) on the CRT 110.

  The CPU 112 included in the printer 1500 outputs information to a printing unit (printer engine) 117 connected to the system bus 115 based on a control program stored in the program ROM of the ROM 113b or a control program stored in the external memory 114. As an image signal. Further, a control program of the CPU 112 is stored in the program ROM of the ROM 113b. Font data used in generating the output information is stored in the font ROM of the ROM 113a, and the data ROM of the ROM 113c is used on a computer in the case of a printer without the external memory 114 such as a hard disk. Information is also stored.

  The CPU 112 can communicate with the client PC 3000 via the input unit 118, and is configured to be able to notify the client PC 3000 of information in the printer. A RAM 119 is a main memory of the CPU 112 and functions as a work area. The RAM 119 is configured such that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown).

  The RAM 119 is also used as an output information expansion area, environment data storage area, NVRAM, and the like. Access to the external memory 114 such as a hard disk (HD) or an IC card is controlled by a memory controller (MC) 120. The external memory 114 is connected to the controller (MC) 120 as an optional device, and stores font data, an emulation program, form data, and the like. The input unit 118 is provided with an operation panel, and an operation switch or an LED display is disposed on the operation panel.

  The number of external memories 111 and 114 is not limited to one, and it is sufficient that at least one external memory is provided. The memory controllers (MC) 107 and 120 have different option font cards and language systems for adding option fonts to the built-in fonts. A plurality of external memories storing a program for interpreting the printer control language may be connected. Furthermore, the printer 1500 may have an NVRAM (not shown) and store printer mode setting information from the operation panel.

  In this embodiment, it is assumed that the page description language (hereinafter referred to as “PDL”) supported by the printer 1500 is, for example, a relatively advanced PDL manufactured by Canon Inc. called LIPS. It is not limited.

  A print control program (hereinafter referred to as “printer driver”) for realizing the present invention is recorded in the external memory 111 and is executed by the CPU 101 by being loaded into the RAM 102 as necessary. Furthermore, definition files and various information tables used by the printer driver according to the present invention are stored in the external memory 111, and detailed descriptions thereof will be described later.

  FIG. 2 is a system block diagram schematically showing a flow when transmitting print job data from the client PC 3000 shown in FIG. 1 to the printer 1500.

  An application program (hereinafter referred to as “application”) 201, a graphic engine 202, a printer driver 203, and a print subsystem 204 in the client PC 3000 exist as files (program modules) stored in the external memory 111 shown in FIG. When each file is executed, it is loaded into the RAM 102 and executed by the OS or a module using the module.

  The application 201 and the printer driver 203 can be added to the hard disk (HD) of the external memory 111 via the FD of the external memory 111, a CD-ROM (not shown), or the network 301 described later.

  The application 201 stored in the external memory 111 is loaded into the RAM 102 and executed by the CPU 101. When printing is performed from the application 201 to the printer 1500, output (rendering) is similarly performed using the graphic engine 202 that is loaded into the RAM 102 by the CPU 101 and executed.

  The graphic engine 202 activates a printer driver 203 prepared for each printing apparatus. As a result, the printer driver 203 is loaded from the external memory 111 to the RAM 102 and executed by the CPU 101. The graphic engine 202 uses the printer driver 203 to convert the output of the application 201 into a printer control command by PDL. The printer control command converted by the printer driver 203 is output to the printer 1500 via the print subsystem 204 and the communication I / FC 108 (not shown).

  The print subsystem 204 is activated by the OS, loaded from the external memory 111 to the RAM 102 and executed by the CPU 101, and performs print job scheduling, connection control with the printer 1500, and status management of the printer 1500. Is going.

  The printer driver 203 generates a printer control command in response to the printing or drawing command output instructed from the application 201, and not only instructs the printer 1500 to be reflected in the print output, but also the printer driver 203 and the printer 1500 main body. A function (hereinafter referred to as “user interface”) for performing settings for controlling the functions of the printer, a function for storing the settings, a function for providing information about the capabilities of the printer driver 203 and the printer 1500 main unit to the application and the OS, A function for generating a printer control command when the function set in the user interface is a function of the printer, and a function for realizing the function when the function set in the user interface is a function performed by the printer driver. Etc.

  FIG. 3 is a configuration diagram illustrating a modified example of the printing system illustrated in FIG. 1.

  In FIG. 3, reference numeral 301 denotes a network, 302 denotes a local interface, and a plurality of client PCs 3000, one printer 1500, and one print server 4000 are connected via the network 301. Another printer 1500 is connected to the print server 4000 via the local interface 302.

  As shown in the figure, the printer 1500 is connected to the print server 4000 via the local interface 302 such as Centronics or USB, and further connected to the network 3000 via the print server 4000. It may be configured to be directly connected to 301. Note that the input unit 118 of the printer 1500 directly connected to the network 301 has a function of a network interface card (NIC).

  When a print job is transmitted from each client PC 3000 to the printer 1500 connected to the network 301 via the print server 4000, first, each client PC 3000 sends a print job to the print server computer 4000 via the print subsystem 204 of FIG. Send. The print server 4000 transmits the print job transmitted from each client PC 3000 to the printer 1500 via a print subsystem on the print server 4000 (not shown). Thus, each client PC 3000 can transmit a print job to the printer 1500 via the print server computer 4000.

  When transmitting a print job from each client PC 3000 to the printer 1500 directly connected to the network 301, each client PC 3000 transmits the print job to the printer 1500 directly connected to the network 301 via the print subsystem 204. To do.

  Next, the basic processing flow of a printer driver suitable for applying the present invention will be described with reference to the timing chart of FIG.

  FIG. 4 is a status diagram showing the basic processing flow of the application 201, the graphic engine 202, and the printer driver 203 when printing is performed. In particular, the application 201, the graphic engine 202, and the printer driver 203 shown in FIG. Corresponds to the process. In addition, the same code | symbol is attached | subjected to the same thing as FIG.

  As shown in FIG. 2, the application 201 does not directly communicate with the printer driver 203 but via the graphics engine 202 of the OS. Therefore, the application 201 itself is actually connected to the graphics engine 202. Communicate. The graphic engine 202 receives an instruction from the application 201 and instructs the printer driver 203.

  First, the application 201 notifies the graphic engine 202 of settings for printing such as single-sided / double-sided setting, page unit output / number of copies output setting, and number of copies setting via the memory secured in the RAM 102, and the printer driver 203 The graphic engine 202 receives from the graphic engine 202 a request for initializing a memory area newly stored in the RAM 102 that stores the print settings and information necessary for the printer driver 203 to perform print processing based on the print settings. (Step S401). As a result, the printer driver 203 secures a memory area for holding information (printer driver information) necessary for the printer driver 203 to perform print processing, and initializes the memory area in accordance with the print settings.

  Next, when the printer driver 203 refers to the memory area and completes necessary processing in response to the received initialization processing request, the printer driver 203 print capability of the printer driver 203 according to the print setting received in step S401. Is notified to the graphic engine 202. The application 201 acquires a handle value necessary for associating the print job that is finally transmitted to the printer 1500 and the print setting reflected in the print job from the graphic engine 202 (step S402).

  Next, when the application 201 notifies the graphic engine 202 of a print start request, the printer driver 203 receives the print start request from the graphic engine 202 (step S403). Accordingly, the printer driver 203 starts PDL generation processing, and first, the printer 1500 generates a printer command necessary for starting printing. However, the process of generating a printer command necessary for the printer 1500 to start printing is performed even when the printing process of the first page (first page) is started (when the first page drawing instruction is received from the application). There may be.

  Further, the application 201 notifies the graphic engine 202 of a drawing instruction for realizing drawing of a drawing object such as a character or an image. The printer driver 203 receives the drawing instruction from the graphic engine 202 (step S404). As a result, the printer driver 203 appropriately generates a printer control command reflecting a specified drawing object, a page break, and a request for changing print settings (not shown) in the middle, and outputs the printer control command to the printer 1500. Note that the number of pages to be printed depends on the designation from the application 201.

  Next, when the application 201 notifies the graphic engine 202 of a print end request, the printer driver 203 receives the print end request from the graphic engine 202 (step S405). As a result, the printer driver 203 generates a printer command necessary for the printer 1500 to end printing, and ends the PDL generation processing.

  Finally, the application 201 notifies the graphic engine 202 of the handle value discard request acquired in step S402, and the printer driver 203 stores information necessary for the printer driver 203 to perform print processing from the graphic engine 202. A request to discard information (printer driver information) in the memory area to be received is received. As a result, the printer driver 203 performs a process of discarding the printer driver information (step S406).

  One job for transmission to the printer 1500 is generated by the processing of steps S403 to S405 described above.

  In addition to the printing system including the printer 1500 and the host client PC 3000 shown in FIGS. 1 and 2, the printing system according to the present embodiment further has a configuration in which print data from the application 201 is temporarily spooled with intermediate code data. In this printing system, the contents of intermediate code data once spooled can be processed. As a result, functions that the application does not have, such as enlargement / reduction or printing by reducing a plurality of pages into one page, can be realized with respect to the print data from the application 201.

  FIG. 5 is a diagram showing a system configuration in which the printer driver 203 is expanded so as to generate a spool file 504 once composed of an intermediate code when a print command is sent from the graphic engine 202 to the printer driver 203.

  In the system shown in FIG. 5, the system is expanded as compared with the system shown in FIG. 2 so as to spool the intermediate code data.

  In the extended system of FIG. 5, the dispatcher 501 receives a DDI function that is a print command from the graphic engine 202. When the print command (DDI function) received by the dispatcher 501 from the graphic engine 202 is based on the print command (GDI function) issued from the application 201 to the graphic engine 202, the dispatcher 501 stores it in the external memory 111. The spooler 503, which is an internal spool processing module, is loaded into the RAM 102, and a print command (DDI function) is sent to the spooler 503 instead of the normal print data creation processing 507.

  The spooler 503 analyzes the received print command, converts it into an intermediate code for each page, and outputs it to the spool file 504. The spool file of the intermediate code stored in this page unit is called a page drawing file (PDF: Page Description File). Further, the spooler 503 acquires processing settings (bookbinding printing, Nup, double-sided, stapling, color / monochrome designation, etc.) relating to the print data set for the printer driver 203 from the printer driver 203 as a file for each job. Save to the spool file 504.

  At this time, the setting file stored in units of jobs is referred to as a job setting file (sometimes simply called SDF: Spool Description File). This job setting file will be described later. The spool file 504 is generated as a file on the external memory 111, but may be generated on the RAM 102. Further, the spooler 503 loads the spool file manager 505 stored in the external memory 111 into the RAM 102 and notifies the spool file manager 505 of the generation status of the spool file 504. Thereafter, the spool file manager 505 determines whether printing can be executed in accordance with the contents of the processing settings relating to the print data stored in the spool file 504.

  When the spool file manager 505 determines that printing can be executed using the graphic engine 202, the despooler 506 stored in the external memory 111 is loaded into the RAM 102, and the despooler 506 is described in the spool file 504. Instructed to print the page drawing file of the intermediate code.

  The despooler 506 processes the page drawing file of the intermediate code included in the spool file 504 according to the job setting file including the processing setting information included in the spool file 504, regenerates the GDI function, and again converts the GDI function via the graphic engine 202. Output.

  When the print command (DDI function) received by the dispatcher 501 from the graphic engine 202 is based on the print command (GDI function) issued from the despooler 506 to the graphic engine 202, the dispatcher 501 is not the spooler 1103. Then, a print command is sent to the normal print data creation processing 507 of the printer driver. The printer driver 203 generates a printer control command including PDL based on the DDI function acquired from the graphic engine 202 and outputs the printer control command to the printer 1500 via the print subsystem 204.

  In the system shown in FIG. 5, the contents of the spool file 504 can be processed. As a result, functions that the application 201 does not have, such as enlargement / reduction or printing by reducing a plurality of pages into one page, can be realized with respect to print data from the application 201. In order to process the print data, settings are made from a window provided by the printer driver 203, and the printer driver 203 stores the setting contents on the RAM 102 or the external memory 111.

  Hereinafter, specific processing executed by the client PC 3000 will be described using the system configuration described with reference to FIGS.

  FIG. 6 is a flowchart showing processing of the entire printing system of FIG.

  First, after starting the client PC 3000, the CPU 101 of the client PC 3000 determines whether or not to obtain a printer ticket stored in the print server 4000 (step S1001). A printer ticket is a file that describes restrictions on the use of a printer. The contents of the printer ticket include a usable printer, a user, a client PC name, and a function that restricts use. Details of the contents of the printer ticket will be described later. The printer ticket is centrally managed by the print server 4000, and the administrator changes or corrects the contents of the printer ticket.

  The determination in step S1001 refers to a flag for determining whether or not the CPU 101 acquires a printer ticket in the registry area (hereinafter referred to as “registry”) of the external memory 111. If the flag is on, the printer ticket Is acquired.

  If the printer ticket is acquired as a result of the determination in step S1001, the client PC 3000 transmits a printer ticket acquisition message to the print server 4000 via the network 301, and the client PC 3000 receives the latest information from the print server 4000. A printer ticket is acquired and stored in the external memory 111 (step S1002). Although a method for acquiring a printer ticket via a network has been described here, acquisition from a recording medium such as a floppy (registered trademark) disk or a CDROM is also possible.

  Next, the CPU 101 reads the printer ticket file stored in the external memory 111 and stores the printer ticket information in the RAM 102 or the ROM 103 (step S1003). Details of the printer ticket file reading process will be described later (FIG. 10).

  Next, based on the printer ticket restriction information stored in the RAM 102 or the ROM 103, the CPU 101 performs use permission setting for a printer driver that can be used by the client PC 3000 (step S1004). Details of processing for setting permission or non-permission of use of a printer driver that can be used in the client PC 3000 will be described later (FIG. 11).

  Finally, based on the printer ticket restriction information stored in the client RAM 102 or ROM 103, the CPU 101 sets a restriction on the function of the printer driver that can be used by the login user (step S1005). Details of the function restriction setting process of the printer driver will be described later (FIG. 12).

  In the processing of the entire printing system described above, each client 3000 obtains a printer ticket at the time of activation in the printing system environment of FIG. 3, so that the latest printer environment can always be reflected on each client 3000. That is, each client 3000 acquires a printer ticket at the time of activation, so that each client 3000 can flexibly cope with various printing environments.

  FIG. 7 is a diagram showing an outline of a printer ticket. The numbers shown on the left side of FIG. 7 indicate line numbers and do not constitute the contents of the printer ticket. The same applies to FIGS. 8 and 9.

  The printer ticket takes a format in which a tag <PRINTTICKET> (line 5) is written at the beginning of the file and a tag </ PRINTTICKET> (line 35) is written at the end of the file, and a header portion 10001 (6 lines) indicating file information. And the condition data portion 10002 (lines 14 to 34) indicating conditions for determining whether to permit use of the printer.

  The printer ticket header section 10001 includes a printer ticket format version (FormatVersion), file version (FileVersion), file size (FileSize), file name (FileName), and update date (Update).

  The condition data section 10002 includes a printer (ModelName) that permits or does not permit printing, a user (User), a client PC (PC), a printer function (Feature), and a function that restricts use (RestricFeature).

  Here, the format of the member structure of the printer ticket is shown in Table 1.

  The members in Table 1 that define the format of the printer ticket have the same format defined within the printer driver or an application bundled with the printer driver. When reading a printer ticket, the printer driver or an application bundled with the printer driver acquires printer ticket information based on this member.

  In this embodiment, only the members listed in Table 1 are introduced. However, addition of members, reading of the members, and addition of processing of the printer driver or application bundled with the printer driver are also executed. .

  The members of the header part 10001 are described between a tag <PrintTicket.Header> (line 6) and a tag </PrintTicket.Header> (line 12). Members of the condition data portion 10002 are described between a tag <PrintTicket.EnablePrinter> (line 14) and a tag </PrintTicket.EnablePrinter> (line 34).

  Each member of the header part 10001 and the condition data part 10002 is always composed of a tag <member name> and tag </ member name>, and data is described between them.

  Data in the part described as “*” or “YYYYMMDD” between the tag <member name> and tag </ member name> of each member described in the 7th to 11th lines of the header part 10001 Is specified. Data is input in “...” Between the tag <member name> and tag </ member name> of each member described in the 16th to 31st lines of the condition data portion 10002. The header part 10001 and the condition data part 10002 describe items according to Table 1.

  Next, the printer ticket condition data portion 10002 in FIG. 7 will be described.

  The condition data portion 10002 indicates whether there are various usage restrictions between the tag <PrintTicket.EnablePrinter> (line 14) and the tag </PrintTicket.EnablePrinter> (line 34) and the number of printer groups to which the restriction is applied. One tag <MEMBERTAG fTag1 = "ENABLE or DISABLE" NumTag2 = "number of items"> (15th line), tags <EnabelePrinter> (16th line) and tags for the number of items indicated by this NumTag2 Includes EnablePrinter> (line 32).

  If there is an item that restricts the printer group, each member "ModelName", "User" in the condition data section of the printer ticket between the tag <EnabelePrinter> (line 16) and the tag </ EnablePrinter> (line 32) Describe the restrictions for "," Feature "," RestricFeature ". This restriction content is also described using a ConstraintsBase tag.

  Here, the naming rules of “MEMBERTAG”, “fTag1”, and “NumTag2” in the ConstraintsBase tag are as follows. “MEMBERTAG” is an arbitrary uppercase character string, and is described as, for example, ENABLEPRINTER, MODELIST, or USERLIST. Tag1 of fTag1 is an arbitrary character string, and "f" is prefixed to Tag1. For example, fEnablePrinter, fModelList, and fUser are described. Tag2 of NumTag2 is an arbitrary character string, and "Num" is prefixed to Tag2. For example, it is described as NumPrinter, NumModel, NumUser.

  fTag1 specifies ENABLE or DISABLE, and NumTag2 specifies the number of items held by each member of the condition data.

  Table 2 shows the interpretation of members by specifying the values of fTag1 and NumTag2.

  FIG. 8 is a diagram illustrating an example of a printer ticket.

  In the figure, information necessary for the header is described in the 7th to 11th lines, and items to be restricted are described in the 14th to 43rd lines. The ConstraintsBase tag on the 15th line is a ConstraintsBase tag that defines a printer group to be restricted, and means that there is one printer group to be restricted.

  The 17th to 21st lines specify the printer to be restricted. The ConstraintsBase tag on the 18th line is a CnstraintsBase tag for a printer that restricts use, and indicates that there is one printer that is permitted to be used. The 19th line specifies a printer (Printer1).

  In the 22nd to 28th lines, the user whose use is restricted is designated. The ConstraintsBase tag on the 23rd line is a ConstraintsBase tag for a user whose use is restricted, and indicates that there are three users who are permitted to use. In the 24th to 26th lines, users (Administrator, taro, hanako) who are permitted to use are designated.

  In the 29th to 32nd lines, a client whose use is restricted is designated. The ConstraintsBase tag on the 30th line is a ConstraintsBase tag for a client whose use is restricted, and means that all clients can be used here. In this case, there is no need to specify the client name.

  Lines 33 to 36 designate printer functions that are permitted or not permitted. The tag on the 34th line is a ConstraintsBase tag for a printer function that restricts whether or not it can be used, and means that all the printer functions can be used. In this case, it is not necessary to specify the function of the printer that permits or disallows use.

  In the 37th to 40th lines, the printer functions for which usage restrictions are set are designated. The tag on the 38th line is a ConstraintsBase tag for the function of the printer that restricts use, and means that all the functions can be used here (there is no function of the printer that restricts use). In this case, it is not necessary to describe the function of the printer that restricts use.

  In FIG. 8, the client PC 3000 storing this printer ticket means that only three users can use Printer1. There are no restrictions on the functions of the printer or restrictions by the client PC.

  FIG. 9 is a diagram illustrating another example of a printer ticket.

  In FIG. 9, there are two types of groups, Group 1 (reference numeral 10003 in the figure) and Group 2 (reference numeral 10004 in the figure), on which the printer driver installed on the client PC 3000 is restricted. As for the client that holds this printer ticket, in Group 1, Printer 1 can be used by three users from client PCs of Client-0001 to 0004, and all functions of Printer 1 can be used. In Group 2, Printer 2 and Printer 3 can be used by two users from client PCs of Client-0001 to 0002, and the saddle stitch function (SaddleStitch), the staple function (Staple), and the Z folding function (Z- fold), punch punching function (HolePunch) cannot be used. The page layout (Layout) can only specify 2 pages (2PagePerSheet), 4 pages (4PagePerSheet), and 6 pages (6PagePerSheet) per sheet. The printing method (Duplex) is fixed only for duplex printing (2SidePrint).

  FIG. 10 is a flowchart for executing the printer ticket reading process in step S1003 of FIG. This process is mainly executed by the CPU 101.

  First, initialization of three flags used for reading a printer ticket is executed (step S2001). These flags are used to avoid unnecessary reading of the printer ticket. Specifically, there are bPrintTicket flag, bRegPTData flag, and bCompare flag. When the bPrintTicket flag is “1”, it indicates that the acquisition of the printer ticket information is completed. When the bRegPTData flag is “1”, the registry Indicates that there is information on the printer ticket used last time, and when the bCompare flag is “1”, the information on the printer ticket used last time in the registry and the information on the printer ticket read this time are the same.

  Next, it is determined whether or not the previously used printer ticket information exists in the registry of the client 3000 (step S2002). If there is information on the printer ticket used last time in the registry, the information is read into the RAM 102 or the ROM 103 (step S2003), and the bRegPTData flag is set to 1 (step S2004).

  Next, it is determined whether or not a printer ticket file exists in the external memory 111 of the client 3000 (step S2005). If there is no printer ticket file, the process ends without reading the printer ticket. On the other hand, if the printer ticket file exists, the printer ticket header information is read (step S2006).

  Next, it is determined whether or not there is information on the printer ticket used last time in the registry, that is, whether or not the bRegPTData flag is “1” (step S2007), and there is no information on the printer ticket used last time in the registry. In step S2011, the condition data portion of the printer ticket is read (step S2011), the bPrintTicket flag is set to “1” (step S2012), and the process ends.

  In step S2007, if there is information on the printer ticket used last time in the registry, whether or not the header information of the printer ticket used last time in the registry is the same as the header information of the printer ticket newly read in step S2006. Is discriminated (step S2008). The header information is compared by comparing each of the file version (FileVersion), file size (FileSize), file name (FileName), and update date (Update), which are members of the header part of the printer ticket. If the header information is not the same in step S2008, the process proceeds to step S2011. On the other hand, if the header information is the same, the printer ticket is not read, the condition data part of the printer ticket stored in the registry is read (step S2009), and the bCompare flag is set to “1” (step S2009). In step S2010), the bPrintTicket flag is set to “1” (step S2012), and this process ends.

  FIG. 11 is a flowchart for setting permission or disapproval of use of the printer driver installed in the client PC 3000 based on the printer ticket information read from the registry. This process is mainly executed by the CPU 101.

  First, it is determined whether acquisition of printer ticket information has been completed (bPrintTicket flag = 1?), That is, whether reading of printer ticket information has been performed in step S1003 of FIG. 6 (step S3001).

  If the result of this determination is that the printer ticket has not been read, use of the printer driver is not restricted for the client PC 3000, and it is determined whether or not the information on the previously used printer ticket exists in the registry. (BRegPTData flag = 1?) (Step S3010). If the information on the printer ticket used last time exists in the registry, the information on the printer ticket in the registry is deleted (step S3011), and this process ends, while the information on the printer ticket used last time does not exist in the registry. In this case, the process of step S3011 is skipped, and this process is terminated.

  If it is determined in step S3001 that the printer ticket has been read, all printer drivers installed in the client PC 3000 are acquired (step S3002).

  The processing in steps S3003 to S3005 is processing for determining whether or not the printer driver acquired in step S3002 has the use permission listed in the printer ticket.

  Specifically, whether the acquired printer driver corresponds to a printer that is permitted to be used (step S3003), whether the logged-in user is permitted to use (step S3004), and It is determined whether or not the PC being used is permitted to use (step S3005). If any one of the steps S3003 to S3005 does not satisfy the condition, information indicating that the use of the printer driver is not permitted for the login user is written in the registry of the external memory 111 and set (step S3006).

  If all the conditions of steps S3003 to S3005 are satisfied, it is determined whether or not the processing of steps S3003 to S3005 has been completed for all the acquired printer drivers (step S3007). In step S3003, on the other hand, if the processing is completed, it is determined whether or not the previously used printer ticket information in the registry is different from the currently read printer ticket information (bCompare flag = 0) (step S3003). In step S3008), if different, the printer ticket information is stored in the registry (step S3009), and the process ends. If they are the same, the printer ticket information is not saved in the registry, and the process ends.

  When the above processing is completed, printer driver setting information (that is, use permission or use disapproval information) set based on the printer ticket is written and held in the registry.

  Note that the processing in steps S3004 to S3006 is performed when fTag1 of the ConstraintsBase tag specified by each member of the printer ticket is ENABLE. When DISABLE, the determination condition in each step is inverted.

  FIG. 12 is a flowchart showing processing for restricting the function of the printer driver based on information in the condition data portion of the printer ticket. This process is mainly executed by the CPU 101.

  First, it is determined whether the acquisition of the printer ticket information is completed (bPrintTicket flag = 1?), That is, whether the reading of the printer ticket information has been performed in step S1003 of FIG. 6 (step S4001). If the printer ticket information has not been read, the process is terminated without limiting the function of the printer driver. If the printer ticket information has been read, a list of printer drivers that are permitted to be used (that is, usable printer drivers) set in step S1004 in FIG. 6 and the functions of the printer drivers are stored in the registry. The stored setting information is acquired (step S4002).

  The processes in steps S4003 to S4006 are executed for each printer driver in order to limit the use of functions for all available printer drivers.

  Specifically, first, it is determined whether or not there is a function that permits or disallows use with reference to the feature in the condition data portion of the printer ticket (step S4003). If there is a function for permitting or not permitting use, the function is set (step S4004). This setting is performed for the printer driver setting information stored in the registry acquired in step S4002. If there is no function for permitting or not permitting use, the process proceeds to step S4005 described later.

  Next, it is determined whether or not there is a function for restricting use with reference to the ResistFeature in the condition data portion of the printer ticket (step S4005). If there is a function that restricts use, a restriction is set for the function that is subject to use restriction (step S4006). The setting is performed for the printer driver setting information stored in the registry acquired in step S4002. If there is no function for restricting use, the process advances to step S4007.

  Finally, it is determined whether or not the setting related to the function restriction has been completed for all usable printer drivers (step S4007). If not, the process returns to step S4003. Ends this processing.

  If there is no printer ticket in the external memory 111 and each client 3000 cannot acquire a printer ticket at the time of startup, the CPU 101 sets printer driver setting information (that is, the printer driver setting) based on the printer ticket. Disable use permission setting information and printer driver function restriction setting information). This makes it possible to use printers that are not permitted in the registry and functions that are restricted from being used. For example, when you take an in-house computer home and use it, the printer setting information stored in the registry cannot be reflected at home. If you cannot disable the printer driver setting information, you cannot use the home printer at all. However, since the printer driver setting information can be invalidated, such a situation can be avoided.

  FIG. 13 is a flowchart illustrating processing executed by the client PC 3000 when a print instruction is issued from the application 201.

  If no printer driver that can be used is set in step S1004 in FIG. 6, even if the user selects printing from the application 201, a dialog for performing printing processing is not displayed as an operation of the application 201. Therefore, if no usable printer driver is set, the application 201 restricts the printing process itself in the previous stage of the flow shown in FIG. 13, and thus printing cannot be executed.

  The process shown in FIG. 13 is executed when one or more printer drivers that can be used in step S1004 in FIG. 6 are set.

  First, when printing is performed from the application 201, it is determined whether or not the user performs print settings for print data (step S5001). The print setting means that when a dialog for printing is displayed from the application 201, a control for performing detailed print settings prepared by the application 201 is pressed on the dialog. The name displayed as this control varies depending on the application, such as “Properties” and “Printer Settings”.

  If the user performs printing without performing print settings in step S5001, a normally used printer is selected, and the printer driver function performs printing with initial value settings (step S5003).

  When the user performs print settings in step S5001, a pseudo user interface that displays all the functions of the available printer driver is displayed on the CRT 110, and the user is allowed to select a desired print function. A printer corresponding to the optimum printer driver is automatically selected based on the selected function (step S5002).

  Next, it is determined whether or not to perform print setting again for selecting another printer for the printer selected in step S5002 or S5003 (step S5004). This process is executed based on whether or not the user selects a control for making detailed print settings prepared by the application 201. When this control is selected, the process of step S5002 is executed again.

  If it is determined in step S5004 that the print setting is not performed again, it is determined whether or not the print execution button is pressed on the dialog for printing displayed by the application 201 (step S5005). If the print execution button is not pressed within a predetermined time, this process is terminated without printing. On the other hand, if the print execution button is pressed, printing is executed (step S5006), and this process ends.

  FIG. 14 is a flowchart showing a process of displaying a pseudo user interface that displays all functions of a usable printer driver and a process of selecting a printer corresponding to the optimum printer driver from the functions selected by the user. This process is mainly executed by the CPU 101.

  First, a list of printer drivers permitted to be used and setting information of each printer driver stored in the registry are acquired (step S6001).

  Based on the printer driver setting information acquired in step S6001, a list of functions displayed on the user interface of the printer driver is created (step S6002). The function list is created by referring to DEVMODE in the registry in which the information of each printer driver is stored, and creating a list of usable functions. In the DEVMODE of each printer driver in the registry, functions that can be used by the printer driver and functions that cannot be used are already set. In step S6002, the use restricted function set in step S1005 is considered. Items of functions that are prohibited or restricted are not displayed on the user interface (UI). For example, if there is a printer capable of stapling but there is a restriction that stapling cannot be used by all printers in the printer ticket, the stapling control is not displayed on the integrated UI. In addition, in the case where restrictions are imposed on the function items of the printer driver, the restricted items are not displayed. For example, in N-up printing (N page / Sheet: function to specify how many logical pages are printed on one physical sheet), if only 2up and 4up are allowed in the printer ticket, other items 1up, 6up, 8up and 16up are not displayed on the integrated UI.

  A UI for displaying all functions of the printer driver is created from the list of usable functions created in step S6002 and displayed (step S6003). The user performs print settings from this user interface.

  In step S6003, a print function is selected, that is, print settings are made in accordance with a user input via a UI that displays all the functions of the printer driver (step S6004).

  After the user completes the setting, when an instruction to close the UI is input, the UI is closed (step S6005).

  Next, it is determined whether there is a printer driver that can reflect all of the functions selected by the user in printing (step S6006). If there is a printer driver that can reflect all of the functions selected by the user in printing, the printer corresponding to the printer driver is determined as a printer to be used for printing (step S6007), and the process is terminated.

  On the other hand, if there is no printer driver that can reflect all of the functions selected by the user in printing in step S6006, the functions of the available printer driver and the functions selected by the user are compared, and the degree of coincidence between the functions is determined. Is calculated (step S6008). In calculating the degree of coincidence between the two functions, the function set by the user is compared with the function of the usable printer driver, and a higher priority is given to the one with the larger number of matched functions.

  Then, the printer corresponding to the printer driver with the highest priority is selected as a printer candidate for printing (step S6009).

  A message as to whether or not to perform printing with the printer selected in step S6009 is displayed on the CRT 110, and it is determined whether or not to perform printing with the printer selected in step S6009 in accordance with an input from the user (step S6010). ). In the above message, “Yes” and “No” buttons are displayed for printing with the printer selected in step S6009.

  In step S6010, when printing is performed with the selected printer (that is, when the “Yes” button is pressed), the printer is determined as a printer for printing (step S6007), and this process ends.

  In step S6010, when printing is not performed with the selected printer (that is, the “NO” button is pressed), it is determined whether there is a next candidate printer (step S6011).

  If there is a next candidate printer, the next highest priority printer is selected as a candidate (step S6012), and the process returns to step S6010. On the other hand, if there is no next candidate printer in step S6011, a message indicating that there is no printable printer is displayed on the CRT 110 (step S6013), a normally used printer is selected, and a message to that effect is displayed on the CRT 110. This is displayed (step S6014), and this process is terminated.

  FIG. 15 is a flowchart showing processing of the entire printing system of FIG. 3, and is a modification of FIG.

  In FIG. 15, the virtual printer generation process in step S1006 is added to the process described in FIG. Step S1006 that is different from FIG. 6 will be described below.

  In step S1006, a virtual printer driver generation process for the virtual printer is performed.

  At the start of the processing in step S1006, the existing virtual printer driver is deleted and a new virtual printer driver is generated. This process is a printer driver installation process, and collects and integrates all DEVMODE (printer function information) information of the printer driver that can be used at this time, thereby generating a new DEVMODE.

  In this process, the generated virtual printer driver is set as a default printer (ordinary printer). FIG. 16 shows a display example of a dialog when printing from the application 201, and a virtual printer is selected as the default printer.

  Further, when the virtual printer driver is generated in step S1006, the processing in steps S6001 and S6002 in FIG. 14 is not necessary, and the print screen provided by the application 201 to start the processing in FIG. When a detailed setting display instruction for performing print settings is received from the user, it is determined whether or not the printer driver corresponding to the printer specified on the print screen provided by the application 201 is a virtual printer driver. If a virtual printer driver is specified, a setting screen for detailed setting is generated using the virtual printer driver property sheet stored in the external memory 111. If the virtual printer driver is not specified, a detailed setting screen on a normal property sheet is generated. FIG. 17A shows an example of a setting screen for detailed setting generated using a property sheet for a virtual printer driver, and FIG. 17B shows detailed setting generated using a normal property sheet. An example of a setting screen for use is shown. As shown in FIG. 17A, in a virtual printer, usage restrictions are imposed on N-up printing, and only 2up, 4up, and 6up are allowed.

  As described above in detail, according to the present embodiment, the CPU 101 acquires a printer ticket that exists at a predetermined position on the network (for example, the print server 4000), and based on the acquired printer ticket, the printer 101 Since the setting for enabling or disabling the driver is held in the registry, the registry is updated when the client 3000 is activated, and the latest printer environment can always be reflected. As a result, when the client 3000 is activated, a printer that can be used automatically is determined, and the user can be made to recognize only the printer that can be used before instructing the start of printing.

  In addition, the setting for enabling or disabling the printer driver function and the restriction setting for the usable printer driver function are stored in the registry based on the printer ticket. In addition, it is possible to make the user recognize only the functions of the usable printer.

  In particular, since the printer use control process is performed for each user, each client computer, and each printer, and the use permission setting of the printer can be automatically set, management relating to the printer use can be facilitated. In addition, since the restriction can be performed in units of functions of the printer, the cost can be reduced by limiting the number of printed sheets, limiting the number of pages to be output on one sheet, and fixing to monochrome printing.

  Also, by integrating the functions of multiple printer drivers that are set to be usable in the registry, a list of newly integrated printer driver functions is displayed, and an instruction to select the function of the displayed printer driver is input. When there is a printer driver that can reflect all of the functions of the printer driver related to the input selection instruction to printing, it is determined that the printer driver functions related to the input selection instruction are printed. When it is determined that there is no printer driver that can be reflected in the screen, the degree of coincidence between the function of the printer driver related to the input selection instruction and the functions of a plurality of printer drivers set to be usable in the registry is calculated. The printer corresponding to the printer driver with the largest number of matching functions is selected as the printer that performs printing. You can perform the automatic selection of the printer along The demands, burden of the user in the printer selection can be reduced.

  In the user interface that integrates the functions of a plurality of printer drivers and displays the functions, the printer driver that is permitted to use, the use prohibition function that is imposed on the printer driver that can be used, and the printer driver that can be used. Since the user interface includes at least one of the restricted functions, the printer can be set without being aware of the prohibited items. Thereby, a user's print setting can be performed smoothly.

  As long as the functions of the embodiment of the present invention are executed, a connection is made via a network such as a LAN or WAN, whether it is a single device or a system composed of a plurality of devices. The present invention can also be applied to a system in which processing is performed. That is, the configuration of various terminals connected in the embodiment is merely an example, and it goes without saying that there are various configuration examples depending on applications and purposes.

  In addition, an object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the embodiments to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus as a storage medium. This can also be achieved by reading and executing the stored program code.

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

  Examples of the storage medium for supplying the program code include a floppy (registered trademark) disk, a hard disk, a magneto-optical disk, a CD-ROM, a CD-R, a CD-RW, a DVD-ROM, a DVD-RAM, and a DVD. -RW, DVD + RW, magnetic tape, nonvolatile memory card, ROM, etc. can be used. Alternatively, the program code may be downloaded via a network.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) running on the computer based on the instruction of the program code. A case where part or all of the actual processing is performed and the functions of the above-described embodiments are realized by the processing is also included.

 Further, after the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. This includes the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing.

1 is a block diagram illustrating a configuration of a printing system to which a printing control apparatus according to an embodiment of the present invention is applied. FIG. 2 is a system block diagram schematically showing a flow when transmitting print job data from the client PC 3000 shown in FIG. 1 to the printer 1500. It is a block diagram which shows the modification of the printing system shown in FIG. FIG. 6 is a status diagram illustrating a basic processing flow of an application 201, a graphic engine 202, and a printer driver 203 when printing is performed. FIG. 2 is a diagram illustrating a system configuration in which the printer driver 203 is extended to generate a spool file 504 that includes intermediate code when a print command is sent from the graphic engine 202 to the printer driver 203. 4 is a flowchart illustrating processing of the entire printing system in FIG. 3. It is a figure which shows the outline | summary of a printer ticket. It is a figure which shows an example of a printer ticket. It is a figure which shows another example of a printer ticket. 7 is a flowchart for executing a printer ticket reading process in step S1003 of FIG. 6. 6 is a flowchart for setting permission or non-permission of use of a printer driver installed in a client PC 3000 based on information of a printer ticket read from a registry. 6 is a flowchart illustrating processing for restricting the function of a printer driver based on information in a condition data portion of a printer ticket. 10 is a flowchart illustrating processing executed by a client PC 3000 when a print instruction is issued from an application 201. 5 is a flowchart illustrating processing for displaying a pseudo user interface that displays all functions of a usable printer driver and processing for selecting a printer corresponding to an optimum printer driver from functions selected by a user. FIG. 7 is a flowchart showing processing of the entire printing system in FIG. 3, and is a modification of FIG. 6. 6 is a diagram illustrating a display example of a dialog when printing from an application 201. FIG. FIG. 17A is a diagram illustrating an example of a setting screen for detailed setting generated using a property sheet for a virtual printer driver, and FIG. 17B illustrates details generated using a normal property sheet. It is a figure which shows an example of the setting screen for a setting.

Explanation of symbols

101 CPU
102 RAM
103 ROM
104 System bus 105 Input controller 106 Video controller 107 Memory controller 108 Communication I / F controller 109 Keyboard 110 CRT
111 External memory (HD, FD)
1500 Printer 1501 Operation unit 3000 Client computer 4000 Print server

Claims (12)

A print control apparatus comprising a printer driver for controlling a printer connected via a network,
Printer setting data acquisition means for acquiring printer setting data existing at a predetermined position on the network;
Holding means for holding setting information of a printer driver set based on the printer setting data;
A print control apparatus comprising: a driver setting unit configured to set the printer driver setting information for enabling or disabling the printer driver based on the acquired printer setting data. .   2. The driver setting unit, based on the printer setting data, performs a setting for enabling or disabling the function of the printer driver for setting information of the printer driver. The printing control apparatus described.   The print control apparatus according to claim 2, wherein the driver setting unit sets a restriction on a function of a usable printer driver for the setting information of the printer driver based on the printer setting data.   4. The print control apparatus according to claim 1, wherein the driver setting unit generates a virtual printer driver.   The print control apparatus according to claim 4, wherein the driver generation unit sets the generated virtual printer driver as a default printer.   Receiving means for receiving a detailed setting display instruction for a printer, and whether or not a printer driver corresponding to the printer related to the detailed setting display instruction is the virtual printer driver when the detailed setting display instruction is received And a print setting for generating a print setting screen using the property sheet for the virtual printer driver when the printer driver corresponding to the printer related to the detailed setting display instruction is the virtual printer driver. 6. The printing control apparatus according to claim 4, further comprising a screen generation unit.   The driver generation unit integrates the functions of a plurality of printer drivers set to be usable in the printer driver setting information held in the holding unit, and generates a newly integrated printer driver function. The print control apparatus according to claim 1, wherein:   A display means for displaying a list of functions of the newly integrated printer driver; a selection instruction input means for inputting a selection instruction for the function of the printer driver displayed in the list; and a printer driver related to the input selection instruction. When it is determined that there is no printer driver capable of reflecting all the functions of the printer driver related to the input selection instruction and printing with a determination unit that determines whether there is a printer driver that can reflect all of the functions in printing The degree of coincidence for calculating the degree of coincidence between the function of the printer driver related to the input selection instruction and the functions of a plurality of printer drivers set to be usable in the printer driver setting information held in the holding unit The printer corresponding to the printer driver having the largest number of functions matched by the calculating means and the matching degree calculating means is printed. The print control apparatus according to claim 7, characterized in that it comprises selecting means for selecting a printer.   Storage means for storing printer setting data acquired by the printer setting data acquisition means, and no printer setting data exists in the storage means, and the printer setting data is acquired when an acquisition operation is performed by the printer setting data acquisition means 9. A printing control apparatus according to claim 1, further comprising setting information invalidating means for invalidating setting information of a printer driver set based on the printer setting data when the setting cannot be made. . A print control method applied to a print control apparatus including a printer driver for controlling a printer connected via a network,
A printer setting data acquisition step of acquiring printer setting data existing at a predetermined position on the network;
Holding process for holding printer driver setting information set based on the printer setting data;
And a driver setting step for performing setting for enabling or disabling the printer driver for setting information of the printer driver based on the acquired printer setting data. . A print control program executed by a computer including a printer driver for controlling a printer connected via a network,
A printer setting data acquisition module for acquiring printer setting data existing at a predetermined position on the network;
A holding module for holding setting information of a printer driver set based on the printer setting data;
A print control program comprising: a driver setting module configured to set the printer driver for setting information for enabling or disabling the printer driver based on the acquired printer setting data. . A computer-readable recording medium having a printer driver for controlling a printer connected via a network,
A printer setting data acquisition module for acquiring printer setting data existing at a predetermined position on the network;
A holding module for holding setting information of a printer driver set based on the printer setting data;
A recording medium comprising: a driver setting module configured to set the setting information of the printer driver to enable or disable the printer driver based on the acquired printer setting data.

Images