Tim Kent tim.kent at wkconsulting.com.au Tue May 18 01:09:20 GMT 2004
Hi,
I'm trying to add a Windows NT/2000 OKI C5100 print driver to a Samba 2.2.3a server.
Can't you try to use a more current Samba version?
(The most current versions have support for the "version" tag of printer drivers...)
I've been told that this driver does some server-side stuff, so I'll have to use 'adddriver' in rpcclient.
I've read the manual page for rpcclient, and I printed out a 'Windows 2000 Printer Test Page' to get all the relevant information.
This is probably just something simple, but I've checked this out a couple of times and keep getting a syntax error. Do I have too many files listed, and if so do I need all of these listed files?
tim at test:~$ rpcclient test -U root
INFO: Debug class all level = 2 (pid 9287 from pid 9287)
Enter Password:
session setup ok
Domain=[TEST] OS=[Unix] Server=[Samba 2.2.3a-13 for Debian]
rpcclient $> adddriver "Windows NT x86" "OKI C5100:IMFNT4.DLL:OPHCWDDM.SDD:SDNTOK.DLL:OP51ENU.HLP:\
OKI HiperC Language Monitor:RAW:ABEXPW32.DLL,CANLKN.PRF,CNNbapie.DLL,\
CNNsCore.DLL,CNPPDCE.DLL,CNXADR.DLL,CNXCOV1.EMF,CNXCOV2.EMF,\
CNXCOV3.EMF,CNXCOVL.EMF,CNXCR.DLL,CNXDMAN.DLL,CNXECR.DLL,CNXP5EE.DLL,\
CNXP5EE0.CNT,CNXP5EE0.HLP,CNXP5EEP.DLL,CNXP5EEU.DLL,CNXPRASX.DLL,\
CNZ005N.ICC,CNZ006N.ICC,CNZ007N.ICC,CNZE15N.ICC,CNZE18N.ICC,\
CNZE21N.ICC,CNZN15N.ICC,CNZN18N.ICC,CNZN21N.ICC,CNZP15N.ICC,\
CNZP18N.ICC,CNZP21N.ICC,CnP5eE.DLL,CnP5eE0.CNT,CnP5eE0.HLP,\
CnP5eEUI.DLL,CnP5eEUM.DLL,DCS.DLL,DCSTBL.DLL,GP300FK.XPD,GP300PK.XPD,\
IMF32.DLL,IMFPRINT.DLL,ML51NSAR.DLL,OK001U2H.CAP,OK009U0H.CCM,\
OK714NHE.VER,OMRDM32.DLL,OP5100.DAT,OP5100.UNZ,OP51ICB.BIN,\
OPCLB002.DLL,OPCST000.DLL,OPDMN004.DLL,OPDVA002.DLL,OPHCRENU.DLL,\
OPHCSENU.DLL,OPHCWDDM.DLL,OPHCWDUI.DLL,OPHCWINF.DAT,OPHCWM00.DAT,\
OPHCWNXS.DLL,OPHCWNXT.DLL,OPHCWS00.DAT,OPNE000C.SCR,OPRCL000.DLL,\
OPS00ENU.DLL,OPS00JPN.DLL,OPUSB000.DLL,QDPRIOK.DLL,RDMWIN32.DLL,\
SDDM.INI,SDDMOK.DLL,SDDMUK.DLL,SDIMFOK.DLL,SDNTUM4.DLL,SDOK.DLL,\
SQMCODER.DLL,SROK.DLL,ZENOCMM.DLL,ZENOICM.DLL,ZGDIOK.DLL,ZLANG.DLL,\
ZSPOOL.DLL,ZSPOOLOK.EXE,ZTAG32.DLL"
Usage: adddriver <Environment>\
<Long Printer Name>:<Driver File Name>:<Data File Name>:\
<Config File Name>:<Help File Name>:<Language Monitor Name>:\
<Default Data Type>:<Comma Separated list of Files>
I know that looks like a very long list, but that's what the 'Windows 2000 Printer Test Page' told me! I'm assuming that most of those files are related to some kind of monitor that I could perhaps do without.
The "adddriver" subcommand expects (for Windows NT/2000) to find all the files in the "[print$]/W32X86/" subdirectory. It then moves the files into "[print$]/W32X86/2/" and creates the fake "registry" entries (in the *.tdb files) for the driver.
If your "adddriver" command fails once (for one reason or another, like mistyping anything), you can't repeat it without makeing sure that all initial files are still in "[print$]/W32X86/". Your failed first adddriver command may have moved away all or part of the files. Your second attempt at the adddriver command now will fail because it doesn't find the files you reference.
Lastly, I'd recommend to run the command "all in one":
rpcclient -Uroot%passwd -c 'adddriver "Windows NT x86" "OKI....:yada:..."' sambahostname
As far as my syntax is concerned I have the files in the right order.
It looks like your syntax is OK. But I remember having had problems with 2.2.3a and adddriver. If nothing else works, an upgrade to 3.0.4 should help....
Cheers, Tim
Cheers, Kurt
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
