Information processing apparatus and control method

A control method using print control software operable in an information processing apparatus capable of communicating with a printer and capable of storing registration information on the printer in a predetermined storage area includes causing a computer of the information processing apparatus to execute obtaining, after an operating system (OS) on the information processing apparatus is updated to a second version capable of using the print control software, with the registration information on the printer stored in the predetermined storage area and being stored during an operation of a first version of the OS on which the print control software is not used, displaying printer information based on the obtained registration information, and registering a print queue with the print control software using the obtained registration information on a basis that the displayed printer information is selected.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates to an information processing apparatus and a control method.

Description of the Related Art

There is a technique for providing a standard print function (OS standard print function) by an operating system (OS) without the requirement for printer-specific software (specific printer driver) provided by a printer vendor (see International Publication No. WO 2013/116704). The OS determines whether a printer is compatible with (supports) the OS standard print function based on information obtained from the printer, and if so, transmits print data generated by the OS standard print function to the printer.

SUMMARY OF THE INVENTION

However, some printers are not compatible with the OS standard print function and cannot interpret print data generated by the OS standard print function. Further, even if a printer is compatible with the OS standard print function, it is often required that printing be performed based on more advanced print settings than the OS standard print function.

A control method according to an aspect of the present invention is a control method using print control software operable in an information processing apparatus, the control method causing a computer of the information processing apparatus to execute: an obtaining step of obtaining registration information on a print queue of a printer not compatible with OS standard print software from a predetermined storage area in a case where the registration information on the print queue is stored in the storage area; and a registering step of registering the print queue with the print control software using the obtained registration information on the print queue.

DESCRIPTION OF THE EMBODIMENTS

Preferred embodiments of the present invention will be hereinafter described in detail with reference to the accompanying drawings. It should be noted that the embodiments described below do not limit the claimed inventions and that not all combinations of features described in the embodiments are essential in solving the problem to be solved by the present invention.

First Embodiment

A printer not compatible with (not supporting) the OS standard print function cannot use the OS standard print function. More specifically, a printer not compatible with the OS standard print function cannot interpret print data in a predetermined format (hereinafter also referred to as “standard format”) specified by the OS standard print function. Thus, the present embodiment uses software called print conversion utility, which enables a print instruction using the OS standard print function by making a printer not having the OS standard print function look as if it is compatible with the OS standard print function. The print conversion utility is installed and used on a personal computer (hereinafter referred to as PC) with the OS installed thereon. The print conversion utility may be provided in a computer different from the PC with the OS installed thereon.

In response to an inquiry from the OS about capability information, the print conversion utility informs as a proxy the capability of a printer not compatible with the OS standard print function. The print conversion utility also converts print data (command) in the standard format into print data (command) in a format supported by the printer and transmits the converted data. After the print conversion utility is installed on the PC, the print conversion utility converts communication with a printer according to a printer-specific protocol into communication conforming to the OS standard print function. Thus, even a printer not compatible with the OS standard print function can issue a print instruction from the PC using the OS standard print function. In a case where a specific printer driver provided by a printer vendor is installed on the PC, even a printer not compatible with the OS standard print function can interpret print data as long as it is generated by the specific printer driver. Accordingly, in a case where a user issues a print instruction via a print execution user interface provided by a specific printer driver, printing can be performed without the OS standard print function.

In a case where a user who used a specific printer driver provided by a printer vendor for printing upgrades the OS of the PC, the specific printer driver may become unusable depending on the upgraded OS. For example, there is a possibility that in order to perform printing from a smartphone or tablet or improve the security of the OS, the OS standard print function goes mainstream and the OS system configuration negates the need for the specific printer driver. In a case where the specific printer driver is unstable after the OS upgrade, the print conversion utility is necessary for printing by a printer not compatible with the OS standard print function.

For printing using the print conversion utility, it is necessary to register printer information (also referred to as print queue) used by a user before an OS upgrade with the print conversion utility. In order to register the print queue with the print conversion utility, it is generally required that a printer used by a user before an OS update be connected to a PC and power be applied to the printer. In addition, print setting information registered with the print queue using the specific printer driver needs to be registered again with the print conversion utility. It is assumed that the print queue described in the present embodiment includes at least one of printer information and print setting information. The print queue will be described later in detail.

As described above, it generally takes time and effort for a user to make a preparation for printing using the print conversion utility in a printer not compatible with the OS standard print function after an OS upgrade. A description will be given of a technique to simplify the preparation made by a user for executing printing by means of the print conversion utility for issuing a print instruction using the OS standard print function.

Hardware Configuration of System

FIG. 1is a block diagram showing a hardware configuration of a system used for printing in the present embodiment. The system has a PC101as a host computer and a printer102. The PC101is an example of an information processing apparatus and has an input interface110, a CPU111, a ROM112, a RAM113, an external storage device114, an output interface115, and an input/output interface116. The input interface110is connected to an input device such as a keyboard118or a pointing device117. The output interface115is connected to a display device such as a display unit119.

The ROM112stores an initialization program. The external storage device114stores an application program group, an operating system (OS), a specific printer driver, and various types of data. The RAM113is used as a work memory or the like in the execution of various programs stored in the external storage device114.

In the present embodiment, the CPU111performs processing according to the procedure of a program stored in the ROM112, thereby implementing functions of the PC101to be described later and processing of a flowchart to be described later. The printer102as a device is connected to the PC101via the input/output interface116. Although the PC101and the printer102are separate here, they may be integrated into a single information processing apparatus.

Block Configuration

FIG. 2is a block configuration diagram illustrating the printing system before an OS upgrade in the PC101. In the description below, an OS printing system in the first version before the OS upgrade is referred to as an OS printing system A. An OS printing system in the second version after the OS upgrade is referred to as an OS printing system B (described later with reference toFIG. 3).

The PC101and the printer102are connected to each other via a network208and can communicate with each other. Although a local area network (LAN) is assumed as the network in the present embodiment, the network may be a wide area network (WAN). The network connection may be wired and/or wireless. The PC101controls the printer102connected via the network208.

The PC101has an application201, an OS printing system A202, a network (NW) communication control unit207, a vendor driver203, and a storage area205. The OS printing system A202has a print queue204. The vendor driver203that is a specific printer driver is for providing the printer102with a print instruction. A user installs the vendor driver203on the PC101and the vendor driver203generates the print queue204corresponding to the printer102, whereby the printer102can be provided with a print instruction via the OS printing system A202. In the present embodiment, macOS (Registered Trademark) is assumed as the OS installed on the PC101.

The print queue is an object for executing printing from the OS or a different application. Each print queue includes a name or the presence/absence of sharing, a connected port or server settings, print settings, device-related settings and the like. The print queue is also used as an object for storing print data.

By generating the print queue204, print queue registration information206of the vendor driver203is recorded in the storage area205. The print queue registration information206is information on the print queue204registered with the OS printing system A202such as various settings of the print queue described above.

The OS printing system A202sequentially processes print requests from the application201as jobs for each printer connected to the PC101. The application201is software which generates rendered data based on user instructions. The application described here is software operable on the OS. For example, the application201is word processing software for document creation, image editing software, and New Year's card creation software. Rendered data generated by a rendering application is in a portable document format (PDF) for example. In a case where a user requests printing of rendered data generated by the application201, the request is input to the OS printing system A202as a print job. Upon receipt of the print job, the OS printing system A202generates print data conforming to the function of the printer102via the vendor driver203and registers the print data with the print queue204. The print data registered with the print queue204is sequentially transmitted to the printer102via the vendor driver203and the NW communication control unit207.

The printer102has a NW communication control unit209, a print control unit210, and a printing unit211. The print control unit210receives print data from the PC101via the NW communication control unit209and controls the printing unit211based on the print data to execute printing.

As described above, in the configuration ofFIG. 2, since a print instruction is issued via the specific printer driver, printing can be performed without the OS standard print function.

FIG. 3is a diagram showing a block configuration of the system after the OS update in the configuration shown inFIG. 2. The PC101is identical to the PC101ofFIG. 2. The PC101has an OS printing system B301instead of the OS printing system A202ofFIG. 2. The PC101also has a print conversion utility304. The OS printing system B301has an OS standard print control component302and a print queue303. The print conversion utility304has a vendor driver305and a print queue306. The print queue registration information206recorded in the storage area205is identical to that shown inFIG. 2before the OS upgrade of the PC101. The rest of the configuration is also identical to that shown inFIG. 2.

The OS printing system B301(also referred to as OS standard print software) provides the OS standard print function. Any printer compatible with the OS standard print function can perform printing without the vendor driver.

The print conversion utility304including the vendor driver305is print control software for using a printer not compatible with the OS standard printing. The print control software is installed on the PC101by a user as necessary and thereby made operable on the PC101. The OS printing system B301sequentially processes print requests from the application201as jobs for each printer connected to the PC. In a case where a user requests printing of data generated in the application201, the request is input to the OS printing system B301as a print job.

Upon receipt of the print job, the OS printing system B301generates print data in the standard format conforming to the OS standard print function. In a case where the print job is for a printer compatible with the OS standard print function, the OS printing system B301transmits the generated print data to the printer102via the NW communication control unit207. In contrast, in a case where the print job is for a printer not compatible with (not supporting) the OS standard print function, the OS printing system B301transmits print data in the standard format to the print conversion utility304. The print conversion utility304converts the print data in the standard format into print data in a vendor-specific format and transmits the converted print data to the printer102via the NW communication control unit207. The print conversion utility304has the function of a virtual printer compatible with the OS standard print function. Thus, the OS printing system B301performs processing of outputting the print job for a printer not compatible with the OS standard print function to the virtual printer. In response, the print conversion utility304converts print data into the vendor-specific format using the vendor driver305. The function of the vendor driver305is not necessarily identical to that of the vendor driver203in the OS printing system A202before the OS upgrade. The vendor driver305only needs to have at least a function of converting print data into the printer vendor-specific format.

The print conversion utility304may be used even in a case where a printer supports the OS printing system B301(that is, in a case where a printer can interpret print data in the standard format). More specifically, the print conversion utility304may be used for any print instruction for a printer compatible with the print conversion utility304even in a case where the printer supports the OS printing system B301. More functions can be provided by the use of the print conversion utility. For example, the OS standard function provided by the OS printing system B301is not compatible with advanced print quality settings such as color matching processing and color or brightness adjustments. In short, there is a limit to the OS standard print function. The use of the print conversion utility304makes it possible to provide the same functions as the printer vendor-specific printer driver.

In order to use the print conversion utility304from the application201, it is necessary to register two print queues: the print queue303in the OS printing system B301and the print queue306in the print conversion utility304. The print queue303in the OS printing system B301stores print data of the OS standard print function which has received a print request from the application201. The print queue306in the print conversion utility304stores print data that the print conversion utility304has received from the print queue303. In a case where the print conversion utility304registers the print queue306, the print queue303of the OS standard print function is also automatically registered.

The printer102of the present embodiment is not compatible with the OS standard print function. As described above, the print queue306is necessary in a case where a user performs printing via the print conversion utility304in the application201of the PC101. Without the technique of the present embodiment, it takes time and effort for a user to make a preparation for generation of the print queue306. This will be specifically described below.

FIG. 4is a diagram showing an example of a printer list screen401displayed by the print conversion utility304. The printer list screen401includes an “add” button403for registering a printer and a “delete” button404for deleting a printer. In a case where a press of the “add” button403is detected, the print conversion utility304displays a printer registration screen405ofFIG. 4.

The printer registration screen405includes a printer list406, a “cancel” button407, and a “register” button408. The print conversion utility304displays, in the printer list406, all printers that are connected to the PC101via the network or USB, have power applied thereto, and are not compatible with the OS standard function. In other words, a printer not connected to the PC101via the network or USB or not having power applied thereto is not displayed in the printer list406and cannot be registered. Therefore, a user who has upgraded the OS needs to power on a printer to be registered and connect the printer via the network or USB as a preparation.

In a case where it is detected that a user presses the “register” button408while a printer in the printer list406is selected, the print conversion utility304generates a print queue306corresponding to the selected printer.

The present embodiment will show an example in which the print conversion utility304automatically generates the print queue306based on the premise that the print queue registration information206is present in the storage area205after an OS update of the PC101. In other words, in this example, the print conversion utility304generates the print queue306even in a case where a printer is not connected to the PC101via the network or USB or does not have power applied thereto.

FIG. 5is a flowchart of processing performed by the print conversion utility304at the first activation in the present embodiment. The processing shown inFIG. 5is performed by the CPU111executing the program of the print conversion utility304stored in the ROM112or the external storage device114. In the description of the processing, “S” indicates a step in the flowchart (the same applies hereinafter).

The print conversion utility304starts the activation processing ofFIG. 5only at the first activation. In S501, the print conversion utility304determines whether the print queue registration information206of the vendor driver203is present in the storage area205of the PC101.

The print queue registration information206includes printer information and preset print setting information. In the case of network connection, for example, the printer information includes TXT record information including a Multicast DNS or DNS-SD hostname of the printer and accompanying printer model information. That is, the printer information includes an IP address of the printer or information from which the IP address is derivable. In the case of USB connection, for example, the printer information includes a USB serial number of the printer as a USB device and printer model information. The preset print setting information indicates information on print setting values arbitrarily selected by a user. A specific example will be described below.

FIG. 6is a diagram showing an example of the printer information describing registered printer information. The printer information is described in a markup language. InFIG. 6, lines602to609are printer information registered by USB connection. The description following “serial=” in line608indicates a USB serial number. The description following “MakeModel” in line607indicates printer model information.

InFIG. 6, lines610to617are printer information registered by network connection. The description following “DeviceURI” in line616indicates a Multicast DNS hostname. The description following “MakeModel” in line615indicates printer model information.

FIG. 7is a diagram showing an example of a file describing preset print setting information. The file ofFIG. 7is described in a markup language and interpreted by a key of each markup. InFIG. 7, lines701and708indicate that print settings are described between these lines. Lines702to704describe a sheet size setting and indicate that the setting value is “A4.” Lines705to707describe a duplex setting and indicate that the setting value is “None.”

If the print conversion utility304determines in S501that the print queue registration information206of the vendor driver is not present, the processing is finished. If the print conversion utility304determines in S501that the print queue registration information206of the vendor driver is present, the print conversion utility304proceeds to S502.

In S502, the print conversion utility304determines whether the information whose presence is confirmed in S501includes information on a printer compatible with the print conversion utility304. The print conversion utility304further determines whether a print queue of the print conversion utility304corresponding to that printer is not registered. If the information obtained in S501includes information on a compatible printer and a print queue of the print conversion utility304corresponding to that printer is not registered (if there is a printer satisfying a condition), the print conversion utility304proceeds to S503. If it is determined that there is no printer satisfying the condition, the processing is finished.

In S503, the print conversion utility304generates a printer list showing candidates to be registered with the print conversion utility304based on the print queue registration information. The print conversion utility304displays a printer list screen and proceeds to S504.

FIG. 8is a diagram showing an example of a printer list screen801displayed by the print conversion utility304in S503to show a candidate to be registered with the print conversion utility304. The printer list screen801includes a printer list802, a checkbox803, a “cancel” button804, and a “register” button805. The printer list802displays a list of printers obtained from the print queue registration information.

In S504, a user selects a printer to be registered with the print conversion utility304from the printer list802using the checkbox803. That is, the print conversion utility304performs accepting processing of accepting designation of a printer to be registered with the print conversion utility304. If the print conversion utility304detects a press of the “cancel” button804or the “register” button805, the print conversion utility304proceeds to S505.

In S505, the print conversion utility304determines whether a user presses the “register” button805and selects one or more printers. If the condition is satisfied, the print conversion utility304proceeds to S506. In other cases, the print conversion utility304finishes the processing.

In S506, the print conversion utility304initializes an index number (n=1) and proceeds to S507. In S507, the print conversion utility304starts a loop which is repeated a number of times equal to the number of selected printers. In S508, the print conversion utility304obtains printer information from print queue registration information206of a vendor driver of the n-th printer and registers (generates) a print queue306of the print conversion utility. After that, the print conversion utility304proceeds to S509.

In S509, the print conversion utility304obtains preset print setting information from the print queue registration information206of the vendor driver of the n-th printer and hands over the information to the print queue306of the print conversion utility304. The print settings handed over in S509are usable in a print execution user interface provided by the print conversion utility304. In S510, the print conversion utility304increments the index number, proceeds to S511, and repeats the loop.

As described above, in a case where the print queue306of the print conversion utility304is registered, the print queue303of the OS printing system B301is also automatically registered. That is, in a case where the print conversion utility304registers a printer with itself, the print conversion utility304adds internally generated information about compatibility with the OS standard print function to information about the registered printer and responds to the OS printing system B301. The information about the printer includes a model name, a printer name, and printer installation location information for example. The internally generated information about compatibility with the OS standard print function includes an UUID and capability information for example. The print conversion utility304executes a registration command to register the print queue303of the printer102with the OS printing system B301based on information about a printer (printer102) for which the print conversion utility304acts as a proxy to respond to the OS printing system B301. The information about a printer for which the print conversion utility304acts as a proxy to respond to the OS printing system B301is a model name, a printer name, printer installation location information, a UUID, or capability information for example. In this manner, the print conversion utility304instructs the OS printing system B301to register the print queue303. A user only executes the processing for registering the print queue with the print conversion utility304, whereby the print queue303of the OS printing system301B is also automatically registered.

As described, in the present embodiment, a print instruction can be appropriately output to the printer102by means of the OS standard print function by using the print conversion utility304. In addition, in a case where print queue information based on which printing was executed via the vendor driver before an OS upgrade of the PC101is present after the OS upgrade of the PC, the print conversion utility304informs a user of the printer list. The print conversion utility304allows a user to select a printer to be registered with the print conversion utility, thereby simplifying print queue registration with the print conversion utility. Further, a user can register the print queue even in a case where a printer used before the OS upgrade is not connected to the PC or does not have power applied thereto. Accordingly, a user can be saved from having to make a preparation for printing in a printer not compatible with the OS standard print function using the print conversion utility after the OS upgrade. A user can also reuse preset print settings registered with the print queue of the vendor driver.

Second Embodiment

In the first embodiment, the print queue306is automatically generated based on the premise that the print queue registration information206recorded in the storage area205is present after the OS upgrade of the PC101. In the present embodiment, the print queue306is automatically generated based on the premise that the print queue registration information206recorded in the storage area205is not present after the OS upgrade of the PC101.

FIG. 9is a block diagram showing the system configuration before the OS upgrade ofFIG. 2with the Internet901and a server902added thereto. The server902may be a network server connected to the PC101via the network208or the Internet901or may be a local server connected to the PC101only via the network208. In addition, inFIG. 9, the PC101has a save tool905(print queue registration information save tool), which is software for saving print queue registration information. Although the print queue registration information206is recorded in the storage area205before the OS upgrade, the print queue registration information206recorded in the storage area205is not present after the OS upgrade.

Print Queue Registration Information Save Processing

FIG. 10is a flowchart of processing of saving the print queue registration information206using the save tool905(save software) for saving print queue registration information before the OS upgrade of the PC101. Although the save tool905is installed on the PC101in the present embodiment, the server902or a different apparatus may have the save tool905.

If the save tool905is activated, the save tool905determines in S1001whether the print queue registration information206of the vendor driver is present in the storage area of the PC101. If the save tool905determines in S1001that the print queue registration information of the vendor driver is not present in the storage area of the PC101, the processing is finished. If the save tool905determines in S1001that the print queue registration information of the vendor driver is present, the save tool905proceeds to S1002.

In S1002, the save tool905generates a registered printer list and displays the generated printer list.

FIG. 11is a diagram showing an example of a registered printer list screen1101displayed by the save tool905. The printer list screen1101has a printer list1102, a checkbox1103, a “cancel” button1104, and a “save” button1105.

In S1003, a user selects a printer corresponding to print queue registration information206to be saved using the checkbox1103. That is, the save tool905accepts the selection of a printer corresponding to print queue registration information206to be saved. If a user presses the “save” button1105or the “cancel” button1104, the save tool905proceeds to S1004.

In S1004, the save tool905determines whether a user presses “save” and selects one or more printers. If the condition is satisfied, the save tool905proceeds to S1005. In other cases, the processing is finished.

In S1005, the save tool905displays a screen for allowing a user to select a storage location (save location) of the print queue registration information206.

FIG. 12is a diagram showing an example of a selection screen1201of the save tool905for selecting a storage location of print queue registration information. In S1006, a user selects a storage location of print queue registration information. That is, the save tool905accepts the selection of a storage location of print queue registration information. In the case of storing the print queue registration information in a desired location, a user selects a radio button1202and inputs a folder path to the storage location to an input box1204or opens a file explorer by the “select” button1205and selects a file path. The folder path selected by the file explorer is reflected in the input box1204. The selected folder path corresponds to a storage area903. In the case of storing the print queue registration information in the server, a user selects a radio button1203, inputs account information to an input box1206, and inputs a password to an input box1207. If a user presses an “OK” button1209or a “cancel” button1208, the save tool905proceeds to S1007. If the save tool905determines that a user selects “OK” in S1007, the save tool905proceeds to S1008. In other cases, the processing is finished.

In S1008, the save tool905initializes an index number (n=1). In S1009, the save tool905starts a loop which is repeated a number of times equal to the number of selected printers. In S1010, the save tool905obtains printer information from print queue registration information206of a vendor driver of the n-th printer and stores the printer information in the location selected by a user in S1006as a print queue registration information backup904. The printer information is the same as that described in the first embodiment. After that, in S1011, the save tool905obtains preset print settings from the print queue registration information206of the vendor driver of the n-th printer and stores the settings in the location selected by a user in S1006as the print queue registration information backup904. The save tool905increments the index number in S1012, proceeds to S1013, and repeats the loop.

Automatic Print Queue Generation Processing of Print Conversion Utility

FIG. 13is a diagram showing a block configuration of the system after the OS upgrade of the PC101in the present embodiment. InFIG. 13, the Internet901and the server902shown in the system configuration ofFIG. 9are added to the system configuration ofFIG. 3. The print queue registration information backup904is information stored in the print queue registration information save processing ofFIG. 12. The storage area storing the print queue registration information backup904is the storage area903of the PC101in the example ofFIG. 13but may be a storage area of the server902. Alternatively, the print queue registration information backup904may be stored in both of the storage area903of the PC101and the storage area of the server902.

FIGS. 14A and 14Bare totally a flowchart of the first activation processing of the print conversion utility304in the present embodiment. The print conversion utility304starts the activation processing ofFIGS. 14A and 14Bonly at the first activation.

In S1401, the print conversion utility304displays an input screen of a storage location of the saved print queue registration information.FIG. 15is a diagram showing an example of an input screen1501of a storage location of the saved print queue registration information.

In S1402, a user inputs a storage location of the print queue registration information backup904stored (saved) in the print queue registration information save processing. That is, the print conversion utility304accepts the input of a storage location of the saved print queue registration information. In a case where the information is stored in a desired location, a user selects a radio button1502and directly inputs a folder path to an input box1504or presses a “select” button1505, opens a file explorer, and selects a file path. In a case where the information is stored in the server, a user selects a radio button1503and inputs account information to an input box1506and a password to an input box1507. If a user presses an “OK” button1509, the print conversion utility304proceeds to S1403. If a user presses a “cancel” button1508, the processing is finished.

In S1403, if the print conversion utility304determines that a storage location of the print queue registration information is input by a user in S1402and the print queue registration information is present in that storage location, the print conversion utility304proceeds to S1404. In other cases, the processing is finished.

In S1404, the print conversion utility304determines whether the print queue registration information whose presence is confirmed in S1403includes information on a compatible printer and a print queue of the print conversion utility304corresponding to that printer is not registered. If there is no printer satisfying the condition, the processing is finished. If there is a printer satisfying the condition, the print conversion utility304proceeds to S1405.

In S1405, the print conversion utility304generates a registration candidate printer list and displays a printer list screen801showing a candidate to be registered with the print conversion utility304as shown inFIG. 8. Since S1406to S1413are identical to S504to S511described with reference toFIG. 5except for the use of the print queue registration information backup904stored in the storage location (storage area) selected by a user, the description thereof is omitted.

As described above, in the present embodiment, print queue information based on which printing was executed via the vendor driver before the OS upgrade of the PC is saved by the save tool905before the OS upgrade of the PC. After the OS upgrade of the PC, the print conversion utility informs a user of the printer list. The print conversion utility allows a user to select a printer to be registered with the print conversion utility, thereby simplifying print queue registration with the print conversion utility. Further, a user can register the print queue even in a case where a printer used before the OS upgrade is not connected to the PC or does not have power applied thereto. A user can also reuse preset print settings registered with the print queue of the vendor driver.

Third Embodiment

In the second embodiment, the print queue registration information of the vendor driver is saved using the save tool905before the OS upgrade of the PC101. In the present embodiment, the print queue registration information is saved by not the save tool905but the vendor driver.

FIG. 16is a diagram showing a block configuration of the system before the OS upgrade in the present embodiment. The configuration ofFIG. 16is basically identical to the system configuration ofFIG. 2except that the vendor driver203stores (saves) the print queue registration information as a print queue registration information backup1602in a storage area1601.

Print Queue Registration Information Save Processing

In the present embodiment, it is assumed that the print queue registration information is saved at the time of first activation after the installation or update of the vendor driver203or at the time of first activation after the registration of a new print queue with the vendor driver203.

FIG. 17is a flowchart of processing at the first activation after the installation or update of the vendor driver203or after the registration of a new print queue with the vendor driver203. The vendor driver203performs the processing ofFIG. 17at the first activation.

In S1701, the vendor driver203initializes an index number (n=1). In S1702, the vendor driver203starts a loop which is repeated a number of times equal to the number of existing print queues. In S1703, the vendor driver203obtains printer information from print queue registration information206of a vendor driver of the n-th printer and registers a print queue registration information backup1602. The location of the storage area1601for the print queue registration information backup1602is predetermined by the vendor driver203.

In the present embodiment, in a case where a user changes preset print setting information of the print queue registration information, the vendor driver203saves the information.

FIG. 18is a flowchart of processing of saving preset print setting information by the vendor driver203. In S1801, if the vendor driver203determines that a user changes preset print setting information, the vendor driver203proceeds to S1802. In S1802, the vendor driver203obtains the preset print setting information from the print queue registration information206and registers the print queue registration information backup1602. If the vendor driver203determines in S1801that a new print queue is not registered, the processing is finished.

Automatic Print Queue Generation Processing of Print Conversion Utility

FIG. 19shows a system configuration after the OS upgrade of the PC101. The print queue registration information backup1602is information recorded in the print queue registration information save processing by the vendor driver203.

The processing at the first activation of the print conversion utility304is basically the same as that described in the first embodiment. More specifically, since the processing is different from that described in the first embodiment only in a storage area for which the print conversion utility304determines whether the print queue registration information of the vendor driver is present in S501, the description thereof is omitted.

As described above, in the present embodiment, print queue information based on which printing was executed via the vendor driver before the OS upgrade of the PC is automatically saved by the vendor driver before the OS upgrade of the PC. After the OS upgrade of the PC, the print conversion utility informs a user of the printer list. The print conversion utility allows a user to select a printer to be registered with the print conversion utility, thereby simplifying print queue registration with the print conversion utility. Further, a user can register the print queue even in a case where a printer used before the OS upgrade is not connected to the PC or does not have power applied thereto. A user can also reuse preset print settings registered with the print queue of the vendor driver.

Other Embodiments

In the third embodiment, the vendor driver203stores the print queue registration information backup1602in the storage area1601in the PC101. However, the storage area is not limited to this. As described in the second embodiment, the vendor driver203may be configured to store the print queue registration information backup1602in a predetermined server.

This application claims the benefit of Japanese Patent Application No. 2020-014841 filed Jan. 31, 2020, which is hereby incorporated by reference wherein herein in its entirety.