Problems adding driver to the RMS database

  • 10054966
  • NOVL18534
  • 12-Jul-2000
  • 13-Jan-2003

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Fact

Novell Distributed Print Services (NDPS) 2.1.1

Novell Distributed Print Services (NDPS) 2.0

Novell NetWare 5.1

Novell NetWare 5.0

NDPS Resource Management Service (RMS) is enabled on the server.

Driver adds fine as a Windows 95/98 driver resource.

Symptom

Problems adding driver to the RMS database

Driver cannot be added as an NT driver.

Cause

Possible mis-match between the INF file and the Windows platform on which it is intended for use.

Fix

Choose the correct Resource Type (e.g. "Windows 2000 Printer Drivers", Windows NT4 Printer Drivers", "Windows 95/98 Printer Drivers", etc.) in the RMS broker "Add Resources" dialog.  You cannot add a Windows 95/98 driver as an NT4 resource type or vice-versa.  For details on adding a driver and choosing the resource type see the document How to add new print drivers to the NDPS Broker.

Contact the printer manufacturer for a new .INF file.

NOTES:   According to the syntax in the .INF file, the driver may be indicating a different platform than it's being added to the RMS broker for.  For example, it may be the same driver needed for NT, and may work fine on an NT workstation, but according to the .INF file it is designed as a Windows 95/98 driver.  To double check this open the .INF file in Notepad or similar,  and look for the "[Version]" section near  the top of the file.   If the driver is designed for NT, the version section will begin with:
 
[Version]
Signature=$Windows NT$
 
If the driver is designed for Windows 95/98, the version section of the inf file will begin with:
 
[Version]
Signature="$Windows 95$"  (this may also "$Chicago$")
 
NWAdmin32 keys off of these version signatures when determining if a driver is suitable to add to the RMS database.  If the version signature in the .inf does not match with the type of resource you are trying to add, no drivers will show as available to be added.   

(You can force the driver to install by editing the version signature of the .inf file to show the desired operating system, but whether it will actually print or not is another question.  Novell does not suggest you edit third party .INF files.)

Also review the following related information documents:

Cannot add NDPS drivers using NTPRINT.INF or MSPRINT.INF.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.