[Samba] Windows 95/98 Generic Text Driver and rpcclient

Dustin Hawkins jdhawk at ch9.us
Tue Oct 21 22:35:41 GMT 2003

I'm using Samba 3.0.0-2 on Redhat 8 as a print server. Everything seems to
be working well except the Windows 4.0 Generic Text drivers. I've set up
the W32X86 drivers and they work perfectly under XP/2000, but I cant seem
to figure out the Win9x situation.
I installed the Generic Driver and printed a test page under Win98 to get
the list of files it uses, but unfortunatly they are not as detailed as
the Windows 2000 Test Pages that tell you what each file does.

Here is what I have from the Win98 Test Page:
Driver Name: TTY.DRV
Driver Version: 4.0
Color Support: Np
Port name: \\printsrv\test
Data Format: RAW
Files used by this driver:

The 2000 Test Page looks more like this:

Printer model:  Generic / Text Only
     Color support:  No
     Port name(s):   FILE:
     Data format:    RAW
     Share name:
     Driver name:    UNIDRV.DLL
     Data file:      TTY.GPD
     Config file:    UNIDRVUI.DLL
     Help file:      UNIDRV.HLP
     Driver version: 5.00
     Environment:    Windows NT x86
     Additional files used by this driver:
      C:\WINNT\System32\spool\DRIVERS\W32X86\3\TTYRES.DLL    (5.00.2134.1)
      C:\WINNT\System32\spool\DRIVERS\W32X86\3\TTY.DLL       (5.00.2134.1)
      C:\WINNT\System32\spool\DRIVERS\W32X86\3\TTYUI.DLL     (5.00.2134.1)
      C:\WINNT\System32\spool\DRIVERS\W32X86\3\UNIRES.DLL    (5.00.2149.1)

as you can see the Win2k Test page lays everything out for you so its easy
to generate the right rpcclient statement.

my rpcclient statement for the Win9x drivers looks something like this:

rpcclient -U'root' -c'adddriver "Windows 4.0"

it installs fine on my samba server, even copys the files over on the
Win98 box, but if you try to look at the printer properties or print it
throws and error. If I try to mimic the Windows2000 driver setup which
uses UNIDRV.DLL as its Device Driver, the Windows98 box refuses to install
the driver saying that UNIDRV.DLL is not a vaild driver...(INF corruption

I checked the msprint.inf file as well and it had no usefull information.
Has anyone figured out the proper place for these five files in the
adddriver statement? or am I missing one that the test page lied to me


More information about the samba mailing list