| |
A printer driver is a software entity that directly supports a physical printer, enabling it to carry out the functions it is intended to perform.
Hardware vendors develop printer drivers, which are specific to each printer. Most printers require different printer drivers for each operating system they interact with. NDPS allows you to view a complete list of printer drivers currently loaded in the Broker's Resource Management Service (RMS)for Windows, and to add additional printer drivers from diskettes and Windows .CAB files.
NDPS ships with only English-language drivers. To make drivers in other languages available for installation on workstations, you will first need to add those drivers to the RMS through the procedure described in this section.
While the majority of printer drivers in common use today can be used with NDPS, some cannot. A few drivers do not work on a network at all, while others might not contain an index file or have an index file that is incorrectly formatted. If you attempt to add a printer driver to the Resource Management Service from a diskette and receive an error message stating that a printer driver cannot be found, you should contact the driver's vendor.
Printer drivers cannot be installed to the Resource Management Service from multiple floppy disks. If a printer driver is shipped on more than one disk, copy the files to a directory on a hard drive or network drive and install the driver from there.
Make sure the Resource Management Service is enabled either in Novell iManager or by going to your server console and viewing the Broker status screen.
In Novell iManager, click Manager Broker and then select the Broker you want to work with.
Click Resource Management Service and then the type of printer driver you want to add.
Add or delete printer drivers to or from the list.
When adding a resource, you will need to browse to the location of the print driver's .INF file. If the file contains multiple print drivers, you will need to select the drivers you want to add to RMS.
Click OK or Apply to save your changes to the database.
The drivers will not be added to the database until you do this.
The process described above might not work if the driver installation .INF file uses subdirectory paths in filename designations within the Copy Files sections of the .INF file. This format is not currently supported by NDPS. There are two possible solutions for this problem:
| |