The present invention relates generally to data processing systems and, more particularly, to the automatic installation of printers in a distributed environment.
The Microsoft WINDOWS NT operating system, sold by Microsoft Corporation of Redmond, Wash., provides a point and print capability. In other words, a user of the workstation that runs the operating system merely needs to identify a target printer on the network (such as by pointing a mouse cursor at an icon for the printer) and then request to print a document in order to print on the target printer. Critical printer configuration information (such as the printer driver and other printer configuration data) is stored on the print servers for network printers. Each print server is a dedicated machine that runs the same operating system and is responsible for controlling a grouped of one or more printers. The print server stores the critical printer configuration information for the printers that are associated with it. When an application requests to initiate a print job, the print server retrieves a copy of printer driver for the printer to the requesting workstation and carries out the print request via a remote procedure call (“RPC”) mechanism. The retrieval of the printer configuration information and the installation of the printer are transparent to the user.
In accordance with a first aspect of the present invention, a method is practiced in a distributed system that has a workstation and a remote network. The remote network includes a printer and a network server. In this method, a database of printer configuration information is provided in shared memory at the network server. The printer configuration information stored at the network server includes printer configuration information for the printer in the network. The printer configuration information for the printer in the remote network is retrieved from the shared memory of the network server in response to request from the workstation. This retrieved information is used to install the printer for use by the workstation. The preferred embodiment may be practiced in an environment with multiple workstations and multiple servers. The servers and workstations may be running different platforms.
In accordance with another aspect of the present invention, a method is practiced in a distributed system having a workstation and a network with printers and a network server. In this method, configuration information for the printers is provided at the network server. In response to a request from the workstation to print on a selected one of the printers, printer configuration information for the selected printer is copied from the network server to the workstation. The printer configuration information is installed at the workstation and the selected printer is then used to service the print request.
In accordance with a further aspect of the present invention, a database of printer configuration information and printer drivers is provided at a network server. A database of printer configuration information and printer drivers for installable printers is provided at a server. Available printer configuration information is retrieved from the network server for one of the printers in the network. This available printer configuration information is provided to the workstation. It is determined that the provided printer configuration information is incomplete and in response, the locally maintained database is accessed to retrieve the complete configuration information and a printer driver for the selected printer.
In accordance with yet another aspect of the present invention, a distributed system includes a network that has at least one printer for executing print jobs and a network server for regulating access to the network. The network server includes a database of printer configuration information for the printer. The distributed system also includes a workstation that is interfaced with the network. The workstation may issue a request to execute a print job on the printer in the network. The workstation runs an operating system that includes a retrieval mechanism and an installer. The retrieval mechanism retrieves the printer configuration information for the network server in response to a request or execute a print job. The installer installs the printer configruaoin information that is retrieved by the retrieval mechanism so that the workstation may use the printer.
The preferred embodiment of the present invention provides a point and print capability within an operating system. This point and print capability allows a user to initiate a print job on a printer within a distributed system by merely identifying the printer and making the request to print. Any installation and configuration that is required for the document to be printed on the printer is performed automatically and transparently by the operating system.
The workstation 12 includes a memory 26 that holds a copy of an operating system 28. This operating system 28 includes client code for acting as a client of the network server 20. The operating system 28 also includes a number of graphical device interface (GDI) functions that help to configure and install printers. In the preferred embodiment of the present invention, the operating system 28 is an embellished version of the Microsoft WINDOWS operating system.
The operating system 28 provides a user interface that allows the user to select a printer that the user wishes to employ to print a document. The list of printers available to a user may include printers that are part of a network served by the network servers 18 or 20. For example, as shown in
The Netware server 20 holds an object-oriented database known as the “bindery” that contains definitions for users, groups, security and other objects of the associated network. The bindery 24 is like the bindery found in the Netware network operating system, version 3.11. The bindery 24 is used in the preferred embodiment of the present invention to hold the printer configuration and driver information for the printers of the network server 20.
As mentioned above, the operating system provides an implementation of the WIN32 API as specified by Microsoft Corporation. The WIN32 API provides a number of functions for manipulating printers to configure and install printers. Some of these functions will be described in more detail below.
A call is then made of the GetPrinter( ) function, which retrieves data stored in the bindery for the target printer. The handle to the printer that was returned by the OpenPrinter( ) function is passed as a parameter to the GetPrinter( ) function to identify the target printer. The GetPrinter function returns a PRINTER_INFO_2 structure that holds data about the target printer. In the preferred embodiment of the present invention, the PRINTER_INFO_2 data structure is of the following form:
LPTSTR
LPTSTR
LPTSTR
LPTSTR
LPTSTR
LPTSTR
LPTSTR
LPTDEVMODE
LPTSTR
LPTSTR
LPTSTR
LPTSTR
DWORD
DWORD
DWORD
DWORD
DWORD
DWORD
DWORD
DWORD
At this point in the process, the operating system knows the handle to the printer and has received data about the printer. The GetPrinterDriver( ) function is called to obtain printer driver data for the given printer from the bindery of the print server (step 42). A DRIVER_INFO_3A or a DRIVER_INFO_2 structure is returned in response to this function call. The operating system first tries to get a DRIVER_INFO_3A structure, but if cannot get a complete DRIVER_INFO_3A structure, it tries to get a DRIVER_INFO_2 structure. An error message is returned in response to the GetPrinterDriver( ) function call, if a complete DRIVER_INFO_3A structure is not available. The DRIVER_INFO_3A structure has the following format:
The DRIVER_INFO—2 structure has the following format:
DWORD
LPTSTR
LPTSTR
LPTSTR
LPTSTR
LPTSTR
A list of dependent files is then built and these files are copied to the workstation 10, wherein the printer is configured (step 44). The list of dependent files is obtained from the DRIVER_INFO_3A structure, if one is available and if the structure includes a list of dependent files. If, however, the DRIVER_INFO_3A structure is not available or if the available structure does not include a list of dependent files, the heuristic approach must adopted as described below. The list of dependent files is printer model dependent. When a printer is installed on a print server, a list of files that is needed for the printer model is determined by the printer installation program. This information may be stored within the DRIVER INFO 3A structure.
The requisite configuration information is then added to the local database of configuration information (i.e., the registry) to install the printer (step 46). In particular, the AddPrinterDriver( ), AddPrintProcessor( ), AddMonitor( ), and AddPrinter( ) functions are called to add the print driver, print processor, monitor and printer configuration information to the registry. The print processor is a dynamic link library (DLL) that interprets data types to convert data from one data type to another data type, and the print monitor monitors a port associated with the printer. Print processor and monitors are known in the art.
Once the printer is successfully installed by completing the steps described above, the application program that prints a document may then begin printing. The installation that adds the printer driver, print processor monitor and printer information to the local memory space is performed by the network client portion of the operating system 28.
In some instances, the operating system 28 will be unsuccessful in retrieving complete information for the target printer. In such instances, the preferred embodiment of the present invention employs a heuristic to attempt to discern the appropriate information about the printer.
The above description has focused on the instance wherein a printer is automatically installed by requesting to print on the printer. It should also be appreciated that the printer may be alternatively installed by explicit user request. The installation is performed as described above, but is performed using a printer installation wizard.
Suppose a user selects the printer associated with icon 78 in FIG. 6C. In such a case, edit box 68 (
While the present invention has been described with reference to a preferred embodiment thereof, those skilled in the art will appreciate the various changes in form and detail may be departing from the intended scope of the present invention as defined in the independent claims.
This application is a continuation of U.S. patent application Ser. No. 08/318,070, filed Oct. 5, 1994, now abandoned.
Number | Name | Date | Kind |
---|---|---|---|
4698688 | Ochi et al. | Oct 1987 | A |
4829468 | Nonaka et al. | May 1989 | A |
5150454 | Wood et al. | Sep 1992 | A |
5228118 | Sasaki | Jul 1993 | A |
5268993 | Ikenoue et al. | Dec 1993 | A |
5287194 | Lobiondo | Feb 1994 | A |
5287434 | Bain et al. | Feb 1994 | A |
5299296 | Padalino et al. | Mar 1994 | A |
5303336 | Kageyama et al. | Apr 1994 | A |
5327526 | Nomura et al. | Jul 1994 | A |
5349648 | Handley | Sep 1994 | A |
5353388 | Motoyama | Oct 1994 | A |
5371837 | Kimber et al. | Dec 1994 | A |
5450571 | Rosekrans et al. | Sep 1995 | A |
5580177 | Gase et al. | Dec 1996 | A |
6230211 | Mahajan | May 2001 | B1 |
Number | Date | Country | |
---|---|---|---|
Parent | 08318070 | Oct 1994 | US |
Child | 08641087 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 08641087 | Apr 1996 | US |
Child | 10425679 | US |