JP6880392B2 - Information processing equipment and its processing method - Google Patents

Description

An information processing device that controls changes in print settings and its processing method.

Conventionally, in order to print, a printer driver is installed, data created by a document creation application or the like is acquired via GDI (Graphics Device Interface), and the data is output to a printer.

Here, in order to automatically execute printing from the upper server, a configuration is prepared so that printing can be performed using the extended I / F (printer driver SDK) of the printer driver.

When printing from a higher-level server application by changing the print settings (print settings that can be changed by the printer driver), the SDK refers to the DEVMODE structure including the print settings and sets the print settings of the printer driver. It is changed internally and the print data received from GDI is output to the printer.

In recent years, it has been replaced by a 64-bit version of the operating system (hereinafter, 64-bit OS), and a mechanism for changing the print settings related to printing on the 64-bit OS is disclosed. (Patent Document 1)

Japanese Unexamined Patent Publication No. 2013-196503

Even if it becomes a 64-bit OS, a 32-bit application can be executed. Therefore, there are cases where an application running on a higher-level server uses a 32-bit application.
In addition, Microsoft (registered trademark) provides WOW64 so that a 32-bit application can be executed on a 64-bit OS.

On the other hand, as for the printer driver, a PC equipped with a 64-bit OS has a 64-bit version of the printer driver installed. Similarly, since the printer driver SDK is also a 64-bit version and is a library, a 64-bit library cannot be called from a 32-bit application, and automatic printing cannot be performed.
That is, there is a problem that the print setting cannot be dynamically changed to print.

Due to the specifications of 64-bit OS, it is necessary to call from a 64-bit application or an executable file (exe file) in order to call a 64-bit library.

In order to solve this, it is conceivable to change the print settings of the printer driver in advance, but when printing is executed in multiple processes, it is processed by changing the printer driver each time and then executing printing. There was a problem that the speed became slow.

Further, it is conceivable to fix the print setting, but it is difficult to apply it when it is desired to change the print setting for each print data.

Therefore, an object of the present invention is to enable printing processing in which print settings are changed in environments having different architectures.

A print control application built with the first architecture, an operation system of the second architecture capable of executing a program of the first architecture, and a storage means for storing print setting information used for printing. The first information processing apparatus including the above, wherein the call means for calling the interface library of the first architecture from the print control application and the interface library serve as an interface with the first architecture. An execution request means for requesting execution of an execution program of the two architectures, an output means for outputting print setting information to be changed from the interface library to the execution program requested to be executed by the execution request means, and an output means. The change control means that calls the print job generation library of the second architecture from the execution program and changes the print setting information of the storage means by using the print setting information to be changed , and the second architect. The char print job generation library includes a library that serves as an extension interface and a library that generates a print job whose print setting information can be changed according to a request from the extension interface, and the execution program includes a library that serves as the extension interface. call, characterized Rukoto to change the print setting information of the storage means.

According to the present invention, it is possible to perform a print process in which print settings are changed in environments having different architectures.

It is a figure which shows an example of the structure of the print control system in this embodiment. It is a figure which shows an example of the hardware configuration of various devices in this embodiment. It is a figure which shows an example of the hardware composition of the printer 300 in this embodiment. It is a figure which shows the module structure of the print control server 200 in this embodiment. It is a figure which shows the flowchart of the print setting change control process 1 in this embodiment. It is a figure which shows the flowchart of the print setting change control process 2 in this embodiment. It is a figure which shows the flowchart of the print setting change control process 3 in this embodiment. It is a figure which shows an example of the print setting information stored in the external memory 211 (storage part) of the print control server 200 in this embodiment. It is a figure which shows an example of Devmode information in this embodiment. It is a figure which shows the outline which reflects the print setting to the printer object, and performs the print process in this embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram showing an example of a configuration of a print control system according to an embodiment of the present invention.

As shown in FIG. 1, in the print control system of the present invention, the client terminal 100, the print control server 200, and the printer 300 are communicably connected via the network 600. The network may be LAN or WAN.

The print control server 200 acquires a document stored in a storage unit (either its own HDD or an external server) and starts a printing process. The start of the print process may be automatically started at the timing when the document is registered, or may be started according to the print start request from the client terminal 100.

Further, the print control server 200 may be in a cloud environment, or may be an environment in which printing can be executed on the printer 300 from the print control server in the cloud environment. The present embodiment is characterized by the control of the print control server 200, but it goes without saying that the client terminal 100 can be realized by the client terminal 100 having the function of the print control server 200.

The module configuration of the print control server 200 will be described later in FIG. 4, but the print control server 200 executes a print control application constructed with the first architecture (for example, 32 bits) and a program of the first architecture. It is an information processing apparatus including an operation system of a second architecture capable of being capable (for example, a 64-bit version OS) and a storage means for storing print setting information (program information) used for printing.

Further, the print control server calls (for example, a first call) an interface library of the first architecture (for example, a 32-bit DLL) from a print control application (for example, a 32-bit application), and calls an interface library (for example, a 32-bit application). By (DLL), an execution request (for example, exe) of an execution program (for example, exe) of the second architecture (for example, 64 bits), which is an interface with the first architecture, is requested (execution request), and the execution program requested to be executed is sent. On the other hand, the print setting information to be changed is output from the interface library (for example, 32 bit DLL), and the print job generation library of the second architecture (for example, 64 bit printer driver SDK, printer driver) is output from the execution program. The print setting information (for example, Devmode information) of the storage means is changed (change control) by using the print setting information to be called and changed, and when the print setting information is changed by the change control, the print job generation library ( For example, a 64-bit printer driver SDK (printer driver) acquires and outputs the data output by the print control application and the changed print setting information (print data output).

The printer 300 acquires print data from the print control server 200 via a print job generation library (for example, a 64-bit printer driver SDK and a printer driver), and executes printing.
The client terminal 100 can access the print control server 200, specify a document to be printed, and issue a print start command.

As shown as an example, the OS described above is a 64-bit version of the operating system, and in the case of Windows (registered trademark), the environment is such that the 32-bit version of the program (including the application) can be operated by the WOW64 emulator program. It has become. In the operating system including WOW64, specifically, the emulation that calls Win32API to Win64API is performed. This makes it possible to migrate a 32-bit version application (a 32-bit version application running on a 32-bit version OS) to a 64-bit version OS and execute it.

At this time, since the 32-bit version application is programmed for the purpose of executing on the 32-bit version OS, normally, the 32-bit version library can be called from the 32-bit version application, but the 64-bit version library can be called. It has no structure.

In order to have a structure that calls the 64-bit version of the library, it is necessary to modify the 32-bit version of the application, which has the property of becoming complicated for companies using the 32-bit version of the application and companies developing these.

Next, with reference to FIG. 2, an example of the hardware configuration of various devices according to the embodiment of the present invention will be described. FIG. 2 is a diagram showing an example of hardware configurations of various devices according to the embodiment of the present invention. Note that FIG. 2 will be described as a hardware configuration of the information processing device applicable to the print control server 200 shown in FIG. 1, but it goes without saying that it can also be applied as a hardware configuration of the client terminal 100.

In FIG. 2, 201 is a CPU that comprehensively controls each device and controller connected to the system bus 204. Further, the ROM 202 or the external memory 211 is necessary to realize a function executed by a BIOS (Basic Input / Output System) or an operating system program (hereinafter, OS) which is a control program of the CPU 201, and each server or each PC. Various programs described later are stored.

Reference numeral 203 denotes a RAM, which functions as a main memory, a work area, and the like of the CPU 201. The CPU 201 realizes various operations by loading a program or the like necessary for executing a process from the ROM 202 or the external memory 211 into the RAM 203 and executing the loaded program.

Reference numeral 205 denotes an input controller, which controls input from a keyboard (KB) 209, a pointing device such as a mouse (not shown), or the like. Reference numeral 206 denotes a video controller, which controls the display on a display such as a CRT display (CRT) 210. Although it is described as CRT210 in FIG. 2, the display may be not only the CRT but also another display such as a liquid crystal display. These are used by the administrator as needed.

Reference numeral 207 is a memory controller, which is connected to a hard disk (HD) for storing boot programs, various applications, font data, user files, edit files, various data, etc., a flexible disk (FD), or a PCMCIA card slot via an adapter. Controls access to external memory 211 such as CompactFlash® memory.

Reference numeral 208 denotes a communication I / F controller, which connects and communicates with an external device via a network (for example, LAN600 shown in FIG. 1), and executes communication control processing on the network. For example, communication using TCP / IP is possible.

The CPU 201 enables display on the CRT 210 by, for example, executing an outline font expansion (rasterization) process in the display information area in the RAM 203. Further, the CPU 201 enables a user instruction with a mouse cursor or the like (not shown) on the CRT 210.

Various programs described later for realizing the present invention are recorded in the external memory 211, and are executed by the CPU 201 by being loaded into the RAM 203 as needed. Further, a definition file and various information tables used when executing the above program are also stored in the external memory 211, and detailed description of these will be described later.

Next, the hardware configuration of the printer 300 shown in FIG. 1 will be described with reference to FIG. In this description, the printer will be described as a multifunction device. That is, it may be a single function printer or a multifunction printer.
FIG. 3 is a block diagram showing an example of the hardware configuration of the multifunction device as the printer 300 shown in FIG.

In FIG. 3, 316 is a controller unit, which is connected to a scanner 314 functioning as an image input device and a printer unit 312 functioning as an image output device, while being connected to a LAN (for example, LAN 600 shown in FIG. 1) or a public line (WAN). ) (For example, PSTN or ISDN, etc.) to input and output image data and device information.

In the controller unit 316, 301 is a CPU, which is a processor that controls the entire system. Reference numeral 302 denotes a RAM, which is a system work memory for operating the CPU 301, a program memory for recording a program, and an image memory for temporarily recording image data.

Reference numeral 303 denotes a ROM, which stores a system boot program and various control programs. Reference numeral 304 denotes a hard disk drive (HDD), which stores various programs, image data, and the like for controlling the system.

Reference numeral 307 is an operation unit interface (operation unit I / F), which is an interface unit with the operation unit (keyboard) 308. Further, the operation unit I / F 307 plays a role of transmitting the key information (for example, pressing the start button) input from the operation unit 308 to the CPU 301.

Reference numeral 305 is a network interface (Network I / F), which is connected to a network (LAN) 600 to input / output data. Reference numeral 306 is a modem (MODEM), which is connected to a public line to input / output data such as transmission / reception of FAX.

Reference numeral 318 is an external interface (external I / F), which is an I / F unit that accepts external inputs such as USB, IEEE1394, a printer port, and RS-232C. In this embodiment, an IC card of a mobile terminal required for authentication is used. A card reader 319 for reading the (storage medium) is connected to the external I / F unit 318. Then, the CPU 301 can control the reading of information from the IC card of the mobile terminal by the card reader 319 via the external I / F 318, and can acquire the information read from the IC card of the mobile terminal. The above devices are arranged on the system bus 309.

Reference numeral 320 denotes an image bus interface (IMAGE BUS I / F), which is a bus bridge that connects the system bus 309 and the image bus 315 that transfers image data at high speed and converts the data structure.
The image bus 315 is composed of a PCI bus or IEEE 1394. The following devices are arranged on the image bus 315.

Reference numeral 310 denotes a raster image processor (RIP), which expands vector data such as a PDL code into a bitmap image. Reference numeral 311 is a printer interface (printer I / F), which connects the printer unit 312 and the controller unit 316 to perform synchronous / asynchronous conversion of image data. Further, 313 is a scanner interface (scanner I / F), which connects the scanner 314 and the controller unit 316 to perform synchronous / asynchronous conversion of image data.

Reference numeral 317 is an image processing unit, which corrects, processes, and edits the input image data, and corrects, converts the resolution, and the like on the print output image data. In addition to this, the image processing unit 317 performs compression / decompression processing of image data, JPEG for multi-valued image data, JBIG, MMR, MH, etc. for binary image data.

The scanner unit 314 illuminates an image on paper as a document and scans it with a CCD line sensor to convert it into an electric signal as raster image data. The manuscript paper is set in the tray of the manuscript feeder, and when the device user gives an instruction to read and start from the operation unit 308, the CPU 301 gives an instruction to the scanner 314, and the feeder feeds the manuscript paper one by one to read the manuscript image. I do.

The printer unit 312 is a part that converts raster image data into an image on paper, and the method is an electrophotographic method using a photoconductor drum or a photoconductor belt, and ink is ejected from a minute nozzle array and directly on the paper. There is an inkjet method for printing an image, but any method may be used. The start of the print operation is started by the instruction from the CPU 301. The printer unit 312 has a plurality of paper feed stages so that different paper sizes or different paper orientations can be selected, and has a paper cassette corresponding to the plurality of paper feed stages.

The operation unit 308 has an LCD display unit, a touch panel sheet is pasted on the LCD, displays the operation screen of the system, and when the displayed key is pressed, the position information of the operation unit I / F307 is displayed. It is transmitted to the CPU 301 via. Further, the operation unit 308 includes, for example, a start key, a stop key, an ID key, a reset key, and the like as various operation keys.

The display performance of the display unit differs depending on the printer, and the present invention is based on a printer that can be operated via a touch panel, or a printer that simply has a liquid crystal screen and simply displays a character string (displays a printed state or a printed document name). Is configured.

Here, the start key of the operation unit 308 is used when starting the reading operation of the original image. In the center of the start key, there is a two-color LED of green and red, and the color indicates whether the start key is ready for use. Further, the stop key of the operation unit 308 functions to stop the operation during operation. Further, the ID key of the operation unit 308 is used when inputting the user ID of the user. The reset key is used to initialize the settings from the operation unit.

The card reader 319 reads the information stored in the IC card provided in the mobile terminal under the control of the CPU 301, and notifies the CPU 301 of the read information via the external I / F 318.

With the above configuration, the printer 300 can transmit the image data read from the scanner 314 to the LAN 600, and the print data received from the LAN 600 can be printed out by the printer unit 312.

Further, the image data read from the scanner 314 can be faxed to the public line by the modem 306, and the image data received by fax from the public line can be output by the printer unit 312.
The printer 300 corresponds to a printer object (printer information related to an icon displayed on the printer management screen) registered in the print control server.

Next, the module configuration of the print control server 200 according to the present embodiment will be described with reference to FIG. FIG. 4 is a module configuration diagram of the print control server 200 according to the present embodiment. Each module is executed by the CPU 201 of the print control server 200.

The 64-bit version of the operating system 401 is software that realizes the basic operations of the print control server 200. This operating system includes an emulation program for operating a 32-bit version of an application such as WOW64 on a 64-bit version of the operating system. That is, it shows an example of the operation system of the second architecture capable of executing the program of the first architecture.

The 32-bit version of the application or program incorporates a 64-bit library (DLL) with a different architecture and cannot be called directly.

The 32-bit version of the print control application 402 is an application constructed with a 32-bit (first architecture) that acquires document data to be printed and executes printing. It should be noted that this is an example of a print control application constructed by the first architecture.

The 32-bit version print control application 402 acquires the pointer of the Devmode information 400 and passes the pointer and the print setting to be changed to the 32-bit version cooperation interface (DLL) 403. In addition, it is an application that executes a print process when the print settings are changed.
The Devmode information 400 shows an example of a storage means for storing print setting information used for printing.

The 32-bit version of the linkage interface (DLL) 403 is a library constructed with 32 bits called from the 32-bit version of the print control application 402, and is a componentized program. The library itself cannot be executed by itself, and can be called by an executable program (application, exe file, etc.) such as an application to realize processing by a DLL program.

The 64-bit version of the linkage interface (exe) 404 is an execution-type program constructed with 64-bit (second architecture), and can be executed independently by an instruction or the like from another program.

The 64-bit version of the printer driver SDK (DLL) 405 is an extension interface of the 64-bit version of the printer driver (DLL) 406, and is a library built with 64 bits. By using this extended interface, it is possible to change print settings and the like without opening the printer driver setting screen, and dynamic print control becomes possible. Further, by passing the print setting to the 64-bit version printer driver SDK (DLL) 405, the private area of the Devmode information managed by the OS (the area of the manufacturer-specific print setting) is managed by the 64-bit version printer driver (DLL) 406 described later. ) Can be changed. That is, it is a print job generation library of the second architecture, and shows an example of a library that serves as an extension interface.

The 64-bit version of the printer driver (DLL) 406 is a library built with 64-bit. It is a program that controls the printer 300, and converts it into a printer description language that can be interpreted by the corresponding printer 300. In addition, print data to be output to the printer 300 is generated based on the set print setting information (Devmode information). It is also possible to generate print data using the print setting information set in the printer object without using the Devmode information. That is, the 64-bit version of the printer driver (DLL) 406 shows an example of a library that generates a print job whose print setting information can be changed according to a request from the extended interface, and includes data output by a print control application and data output by the print control application. It acquires and outputs the changed print setting information.

The significance of having the above-mentioned module configuration in the present embodiment will be described in detail. First, a 32-bit version application (including an exe) cannot call a 64-bit version library, and a 32-bit version application cannot import a 64-bit version library due to the architecture. On the other hand, it is possible in terms of architecture that a 32-bit version application requests a 64-bit version application (including an exe) to be executed and the 64-bit version application is executed, but the calling mechanism of the 32-bit version application must be changed. Therefore, a 32-bit version of the cooperation interface (DLL) 403 is required as a module.

Further, by providing the 64-bit version of the cooperation interface (exe) 404, it is possible to take in the 64-bit version library and execute the process in the process of the 64-bit version application.

The printer object 407 is a printer information group corresponding to the printer 300, and manages printer information including a printer object icon and print settings. For this printer object, it is possible to reflect the print setting of Devmode information by API, and the printer driver can execute printing according to this print setting.

Here, the outline of the operation between each module will be described. First, Devmode information as print setting information is stored in the print control server 200. The 32-bit version of the print control application 402 acquires the pointer of the Devmode information.

The pointer and the print setting to be changed corresponding to the document to be printed are passed from the 32-bit version print control application 402 to the 32-bit version cooperation interface (DLL) 403. When the pointer is passed, the 32-bit version of the cooperation interface (DLL) 403 calls the 64-bit version of the cooperation interface (exe) 404 to establish communication, and passes the pointer and the print setting.

The 64-bit version of the cooperation interface (exe) 404 takes in the 64-bit version of the printer driver SDK (DLL) 405 at the time of execution, and passes a pointer and print settings to the 64-bit version of the printer driver SDK (DLL) 405.

The 64-bit version printer driver SDK (DLL) 405 reads Devmode information based on the pointer, makes a rewrite request to the 64-bit version printer driver (DLL) 406 including print settings, and makes a rewrite request including the print settings, and makes a 64-bit version printer driver (DLL) 406. To change the DLL information.

After that, the 64-bit version printer driver (DLL) 406 returns the result (success, failure) of the change to the 64-bit version printer driver SDK (DLL) 405 as a return value, and the 64-bit version printer driver SDK (DLL) 405 returns. Similarly, the result is returned as a return value to the 64-bit version of the cooperation interface (exe) 404.

Since the 64-bit version of the linked interface (exe) 404 and the 32-bit version of the linked interface (DLL) 403 have established communication (pipe communication), the result is output to the 32-bit version of the linked interface (DLL) 403 in this communication. ..

The 32-bit version of the linkage interface (DLL) 403 returns a result as a return value to the 32-bit version of the print control application 402, and the 32-bit version of the print control application 402 sends a Devmode to the printer object 407 when the result is successful. Requests to change print settings based on information. In the case of the setting that does not use the printer object, when the 32-bit version of the print control application 402 draws in the device context, the print setting is written together with the print data.

The 32-bit version of the print control application 402 requests the operating system 401 to output the acquired document data to the printer corresponding to the modified printer driver, and the 64-bit version of the printer via the operating system's GDI. The driver (DLL) 406 accepts the output data. The 64-bit version of the printer driver (DLL) 406 generates print data corresponding to the printer 300 by using the print settings set in the printer object 407 or the print settings written in the device context, and causes the printer 300 to generate print data. Output.

Next, the processing in the system of this embodiment will be described with reference to the flowcharts of FIGS. 5, 6 and 7. The processing shown in each flowchart is assumed to be executed by the CPU 201 of the print control server 200.

First, with reference to FIG. 5, the processing of the 64-bit version of the cooperation interface (exe) 404 in the present embodiment will be described. FIG. 5 is a diagram showing an example of a flowchart of the print setting change control process 1.

In step S501, a print control command for a predetermined document is executed. The predetermined document is a document that is executed when a document is registered in a predetermined folder from a higher-level server, or is registered in a predetermined folder when a fixed time is reached. Further, the document may be a document specified by the client terminal 100.

In step S502, the print settings corresponding to the document to be printed are acquired. Specifically, the print setting is acquired based on the document name (document identification information) by referring to the print setting table that stores the print setting definition information of FIG. The print setting table may be in a form of holding print setting information as a text file.

Here, FIG. 8 will be described. FIG. 8 is a diagram showing print setting information stored in the external memory 211 (storage unit) of the print control server 200.

The print settings to be changed are stored in association with each document. In addition, the printer name to be output is stored in association with it. The document name is stored in 801. 802 and 803 are print settings, 802 is a standard print setting, and print settings that can be set in the public area of Devmode information are stored. Further, 803 is an extended print setting, and a print setting that can be set in a private area of Devmode information is stored.

In 804, the name of the printer to be printed is stored. This printer name is a printer object name, and based on the printer object name, the target printer 300, its printer driver, and the print settings managed as the printer object can be acquired.

In step S503, the printer name set in 804 is specified, and the pointer of the Devmode information is acquired. In the present embodiment, the Devmode information is acquired by using the pointer, but the Devmode information obtained by the Devmode structure may be acquired.
The Devmode information that can be acquired in step S503 is the default setting information in the print settings managed by the printer object.

Here, the Devmode information will be described with reference to FIG. The Devmode information is information managed by the 64-bit version of the operating system 401, and is defined as the Devmode structure 901. The pointer of the Devmode structure 901 can be obtained by using a function such as EnumPrinters.

The Devmode structure 901 is divided into a public area 902 and a private area 903, each of which is an area in which print settings and the like are registered. The public area 902 is an area that can be changed from a print control application or the like, and standard print settings are registered.

Further, the private area 903 is an area that can be referred to by the 64-bit version printer driver (DLL) 406, and can be changed from the 64-bit version printer driver (DLL) 406, and the manufacturer's own and printer's own extended print settings are registered. ing.

Needless to say, the public area 902 is an area that can be changed from the 64-bit version of the printer driver (DLL) 406. Further, the private area 903 can be changed from the 64-bit version of the printer driver SDK (DLL) 405.

That is, the 64-bit version of the printer driver (DLL) 406 and the 64-bit version of the printer driver SDK (DLL) 405 can be configured as one.

In step S504, the 32-bit version cooperation interface (DLL) 403 incorporated in the 32-bit version print control application 402 is called, and the pointer of the Devmode information and the print setting to be changed are passed. More specifically, the public function call of the 32-bit version of the linkage interface (DLL) 403 is performed, and the pointer and the print setting are passed by the argument at the time of the function call. That is, it is a step showing an example of the first calling means for calling the interface library of the first architecture from the print control application.
In step S505, the pointer of the Devmode information and the print setting to be changed are acquired.

In step S506, an execution request for the 64-bit version of the linked interface (exe) 404 is made, and in step S508, the CPU 201 executes the specified 64-bit version of the linked interface (exe) 404. That is, it is a step showing an example of an execution request means for requesting execution of an execution program of the second architecture, which is an interface with the first architecture by the interface library.

When the 64-bit version of the cooperation interface (exe) 404 is executed, interprocess communication by a pipe is established between the 32-bit version of the cooperation interface (DLL) 403 and the 64-bit version of the cooperation interface (exe) 404.

In step S507, the pointer and the print setting are output to the 64-bit version of the cooperation interface (exe) 404 by interprocess communication using the established pipe. That is, it is a step showing an example of the output means for outputting the print setting information to be changed from the interface library to the execution program requested to be executed by the execution request means.
In step S509, the input of the pointer and the print setting is received from the 32-bit version of the cooperation interface (DLL) 403.

In step S510, the 64-bit version printer driver SDK (DLL) 405 incorporated in the 64-bit version cooperation interface (exe) 404 is called. The pointer and print settings are passed to the 64-bit version of the printer driver SDK (DLL) 405 in order to change the Devmode information. That is, it is a step of showing an example of the change control means for calling the print job generation library of the second architecture from the execution program and changing the print setting information of the storage means by using the print setting information to be changed.

Next, the process following FIG. 5 will be described with reference to FIG. In FIG. 6, the 64-bit version of the printer driver (DLL) 406 will be described up to rewriting the Devmode information. FIG. 6 is a diagram showing an example of a flowchart of the print setting change control process 2.
In step S601, the 64-bit version of the printer driver SDK (DLL) 405 acquires the pointer and print settings.

In step S602, the 64-bit version printer driver SDK (DLL) 405 passes a pointer and a print setting to be changed to the 64-bit version printer driver (DLL) 406 as a print setting change request. It is assumed that a pointer and print settings are passed as arguments of the function of the 64-bit version of the printer driver (DLL) 406.
In step S603, the 64-bit version of the printer driver (DLL) 406 accepts the pointer and the print setting as a request for changing the print setting.

In step S604, Devmode information is specified based on the received pointer, and rewriting is performed based on the received print setting. The public area 902 is rewritten for the standard print setting, and the private area 903 is rewritten for the extended print setting.

Next, the process following FIG. 6 will be described with reference to FIG. 7. FIG. 7 describes from the 64-bit version of the printer driver (DLL) 406 to the output processing to the printer. FIG. 6 is a diagram showing an example of a flowchart of the print setting change control process 3.

First, in step S604, the 64-bit version printer driver (DLL) 406 rewrites the Devmode information (success, failure), and returns the result (success, failure) to the 64-bit version printer driver SDK (DLL) 405 as a return value.

In step S701, the 64-bit version printer driver SDK (DLL) 405 acquires the rewritten result (success, failure) and returns it as a return value to the 64-bit version cooperation interface (exe) 404.

In step S702, the 64-bit version of the linkage interface (exe) 404 acquires the rewritten result (success, failure) and rewrites it to the 32-bit version of the linkage interface (DLL) 403 using the established communication (success, failure). ) Is output.

In step S703, the 32-bit version of the linkage interface (DLL) 403 returns the rewritten result (success, failure) to the 32-bit version of the print control application 402 as a return value.
In step S704, the result (success, failure) rewritten by the 32-bit version print control application 402 is acquired.

In step S705, the rewriting result is determined. If the rewriting is successful (OK), the process is transferred to step S707, and if the rewriting is unsuccessful (NG), the process is transferred to step S706.

In step S706, since the rewriting failed, a print error notification is given. For the error notification, any method such as an email notification to the administrator or a notification to be left as a log may be used.
In step S707, since the rewriting was successful, the document to be printed is acquired.
In step S708, the Devmode information in which the print settings have been rewritten is acquired based on the pointer.

In step S709, it is determined whether or not the acquired Devmode information is reflected as the print setting of the printer object. It is determined whether to reflect the printer object by the set value held by the 32-bit version print control application 402. When printing by multi-process is executed, it is set not to be reflected in the printer object, and when printing without multi-process (sequential printing processing is performed), it is set to be reflected in the printer object. If it is reflected in the printer object, the process is transferred to step S710, and if it is not reflected in the printer object (print execution by a multi-process), the process is transferred to step S712. That is, it is a step showing an example of a determination means for determining whether or not to reflect the print setting information on the printer object.

In step S710, the print settings are reflected on the printer object based on the printer name (804 in FIG. 8) of the printer corresponding to the document to be printed. The print settings are reflected in the printer object using the API of the operating system. That is, it is a step showing an example of the setting process execution means for executing the setting process for reflecting the print setting information on the printer object when it is determined that the print setting information is reflected on the printer object. ..
In step S711, the document data to be printed is output to the device context of the operating system.

In step S712, the document data to be printed and the Devmode information are output to the device context of the operating system. That is, an example of drawing processing execution means in which the print control application executes drawing processing using the data to be printed and the changed print setting information when it is determined that the print setting information is reflected in the printer object. It is a step showing.

In step S713, the 64-bit version of the printer driver (DLL) 406 acquires print data as drawing information via the operating system. In the case of step S712, Devmode information is also acquired.

In step S714, the print setting reflected in the printer object or the print data reflecting the Devmode information (print setting) acquired in step S713 is generated. That is, when the print setting information is changed by the change control means, the print job generation library (printer driver) acquires and outputs the data output by the print control application and the changed print setting information. This is a step showing an example of data output means.
In step S715, the generated print data is output to the target printer.

Next, with reference to FIG. 10, the outline of performing the printing process by reflecting the print settings on the printer object will be described. FIG. 10 is a schematic diagram in which a print process is performed by reflecting the print settings on the printer object.
The higher-level program corresponds to the 32-bit version of the print control application 402 described above.
The 32-bit DLL, which has the same interface as the PrinterDriverSDK (32-bit), corresponds to the 32-bit version of the linked interface (DLL) 403.

The 64-bit process that calls the PrinterDriverSDK (64-bit) corresponds to the 64-bit version of the linked interface (exe) 404.
The Printer Driver SDK (64-bit) corresponds to the 64-bit version of the printer driver SDK (DLL) 405.
The Printer Driver (64-bit) corresponds to the 64-bit version of the printer driver (DLL) 406.

(1) The host program uses the API of the OS to acquire a pointer to Devmode information.
(2) In order to change the print setting of the DEVMODE extended area, the pointer acquired by the higher-level program and the print setting to be changed (for example, 4in1 layout information) are passed to the 32-bit PLL which has the same interface as the PrinterDriverSDK (32-bit). The same interface as the PrinterDriverSDK (32bit) means to use the function of the PrinterDriverSDK (32bit) that was used when the upper program was executed on the 32-bit version of the OS. For example, the upper program originally called it. It has an interface called function A (argument, argument) of the PrinterDriverSDK (32bit). As a result, it is possible to seamlessly exchange prints in different architectures and perform print control with dynamically changed print settings without modifying the host program.
The 32-bit DL, which has the same interface as the PrinterDriverSDK (32-bit), runs a 64-bit process that calls the PrinterDriverSDK (64-bit) and passes a pointer and print settings to change. The 64-bit process that calls the PrinterDriverSDK (64-bit) passes the pointer and the print settings to be changed to the PrinterDriverSDK (64-bit), and requests the PrinterDriver (64-bit) to rewrite the print settings. The PrinterDriver (64bit) changes the Devmode information and returns the result of the change (for example, OK indicating success) to the higher-level program via each module.

(3) The host program reflects the changed Devmode information on the printer object using the API of the OS.

(4) After changing the print setting of the printer object, the print process of the document to be printed is executed, and the print data to which the changed print setting is applied is output to the printer 300 corresponding to the printer object.
This enables printing with dynamically changed print settings, even in configurations using different architectures.

Although the present embodiment has been described above, according to the present embodiment, it is possible to perform a print process in which the print settings are changed in an environment having a different architecture.

In particular, by providing the 32-bit version of the cooperation interface (DLL) 403, it is possible to perform a printing process in which the print settings are dynamically changed without changing the configuration of the 32-bit version of the print control application 402.

Further, by providing the 64-bit version of the cooperation interface (exe) 404, the 64-bit version of the cooperation interface (exe) 404 can be seamlessly executed from a different architecture (32-bit) in the 64-bit version of the operating system 401. The print settings can be passed and the Devmode information can be rewritten with the 64-bit version printer driver that is a DLL. In this way, by dynamically rewriting the Devmode information with different architectures, it is possible to smoothly perform the print process in which the print settings are changed.

Further, by writing the data to be printed and the rewritten Devmode information in the device context, it is possible to generate print data reflecting appropriate print settings even in the print process by multi-process, and the efficient print process. Can be realized.

The present invention can be, for example, an embodiment as a system, an apparatus, a method, a program, a storage medium, or the like, and specifically, may be applied to a system composed of a plurality of devices. It may be applied to a device consisting of one device.

The present invention includes a module that supplies the above-mentioned module directly or remotely to the device. The present invention also includes cases where the computer of the device can also read and execute the supplied program code.

Therefore, in order to realize it on a computer, the program code itself installed on the computer also realizes the present invention. That is, the present invention also includes the computer program itself for realizing the present invention.

Recording media for supplying programs include, for example, flexible disks, hard disks, optical disks, optical magnetic disks, MOs, CD-ROMs, CD-Rs, CD-RWs, and the like. There are also magnetic tapes, non-volatile memory cards, ROMs, DVDs (DVD-ROM, DVD-R) and the like.

In addition, as a program supply method, a browser of a client computer is used to connect to an Internet homepage. Then, the computer program itself of the present invention or a compressed file including the automatic installation function can be supplied from the homepage by downloading it to a recording medium such as a hard disk.

Further, the program read from the recording medium is written to the memory provided in the function expansion board inserted in the computer or the function expansion unit connected to the computer. After that, based on the instruction of the program, the function expansion board, the CPU provided in the function expansion unit, or the like may perform a part or all of the actual processing, and the processing of the above-described embodiment may be realized by the processing.

It should be noted that the above-described embodiments merely show examples of embodiment in carrying out the present invention, and the technical scope of the present invention should not be construed in a limited manner by these. That is, the present invention can be implemented in various forms without departing from the technical idea or its main features.

100 Client terminal 200 Print control server 300 Printer 600 Network (LAN)
201 CPU
401 64-bit version operating system 402 32-bit version print control application 403 32-bit version linkage interface (DLL)
404 64-bit version cooperation interface (exe)
405 64-bit version printer driver SDK (DLL)
406 64-bit version printer driver (DLL)
407 Printer object

Claims (7)

A print control application built with the first architecture, an operating system of the second architecture capable of executing a program of the first architecture, and a storage means for storing print setting information used for printing. An information processing device that includes
A calling means for calling the interface library of the first architecture from the print control application, and
An execution request means for requesting execution of an execution program of the second architecture, which is an interface with the first architecture by the interface library.
An output means for outputting print setting information to be changed from the interface library to the execution program requested to be executed by the execution request means.
A change control means that calls the print job generation library of the second architecture from the execution program and changes the print setting information of the storage means by using the print setting information to be changed .
The print job generation library of the second architecture includes a library that serves as an extension interface and a library that generates a print job whose print setting information can be changed according to a request from the extension interface.
The execution program calls the library to be the expansion interface, the information processing apparatus according to claim Rukoto to change the print setting information of the storage means. A print control application built with the first architecture, an operating system of the second architecture capable of executing a program of the first architecture, and a storage means for storing print setting information used for printing. An information processing device that includes
A calling means for calling the interface library of the first architecture from the print control application, and
An execution request means for requesting execution of an execution program of the second architecture, which is an interface with the first architecture by the interface library.
An output means for outputting print setting information to be changed from the interface library to the execution program requested to be executed by the execution request means.
A change control means that calls the print job generation library of the second architecture from the execution program and changes the print setting information of the storage means by using the print setting information to be changed.
The call by the calling means is an information processing apparatus characterized in that the pointer of the print setting information of the storage means and the print setting information to be changed are passed by the function call of the interface library of the first architecture. A print control application built with the first architecture, an operating system of the second architecture capable of executing a program of the first architecture, and a storage means for storing print setting information used for printing. An information processing device that includes
A calling means for calling the interface library of the first architecture from the print control application, and
An execution request means for requesting execution of an execution program of the second architecture, which is an interface with the first architecture by the interface library.
An output means for outputting print setting information to be changed from the interface library to the execution program requested to be executed by the execution request means.
A change control means that calls the print job generation library of the second architecture from the execution program and changes the print setting information of the storage means by using the print setting information to be changed.
When the print setting information can be changed in the print job generation library of the second architecture by the control by the change control means, the determination means for determining whether or not the print setting information is reflected in the printer object, and the determination means.
When it is determined that the print setting information is reflected in the printer object, the print control application further includes a setting process execution means for executing the setting process for reflecting the print setting information for the printer object. An information processing device that features it. When it is determined that the print setting information is reflected in the printer object, the print control application further includes a drawing process execution means for executing the drawing process using the data to be printed and the print setting information. The information processing apparatus according to claim 3. A print control application built with the first architecture, an operating system of the second architecture capable of executing a program of the first architecture, and a storage means for storing print setting information used for printing. It is a processing method of an information processing device including
A call step for calling the interface library of the first architecture from the print control application, and
An execution request step for requesting execution of an execution program of the second architecture, which is an interface with the first architecture by the interface library,
An output step that outputs print setting information to be changed from the interface library to the execution program requested to be executed by the execution request step.
The execution program includes a change control step of calling the print job generation library of the second architecture and changing the print setting information of the storage means by using the print setting information to be changed.
The print job generation library of the second architecture has a library that serves as an extension interface and a library that generates a print job whose print setting information can be changed according to a request from the extension interface.
The execution program is a processing method characterized in that the library serving as the extension interface is called to change the print setting information of the storage means. A print control application built with the first architecture, an operating system of the second architecture capable of executing a program of the first architecture, and a storage means for storing print setting information used for printing. It is a processing method of an information processing device including
A call step for calling the interface library of the first architecture from the print control application, and
An execution request step for requesting execution of an execution program of the second architecture, which is an interface with the first architecture by the interface library,
An output step that outputs print setting information to be changed from the interface library to the execution program requested to be executed by the execution request step.
The calling step includes a change control step of calling the print job generation library of the second architecture from the execution program and changing the print setting information of the storage means by using the print setting information to be changed. The call by is a processing method characterized in that the pointer of the print setting information of the storage means and the print setting information to be changed are passed by the function call of the interface library of the first architecture. A print control application built with the first architecture, an operating system of the second architecture capable of executing a program of the first architecture, and a storage means for storing print setting information used for printing. It is a processing method of an information processing device including
A call step for calling the interface library of the first architecture from the print control application, and
An execution request step for requesting execution of an execution program of the second architecture, which is an interface with the first architecture by the interface library,
An output step that outputs print setting information to be changed from the interface library to the execution program requested to be executed by the execution request step.
A change control step of calling the print job generation library of the second architecture from the execution program and changing the print setting information of the storage means by using the print setting information to be changed .
When the print setting information can be changed in the print job generation library of the second architecture by the control by the change control step, a determination step of determining whether or not to reflect the print setting information in the printer object, and a determination step.
When it is determined that the print setting information is reflected in the printer object, the print control application performs a setting process execution step for executing the setting process for reflecting the print setting information on the printer object. A processing method characterized by including.

Images