Robert M. Martel
2002-Oct-28 19:41 UTC
[Samba] Samba, Cups, printer driver download problems
I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running Solaris 9. Cups has replaced the stock system V lp spooler on this system (original packages removed.) Cups working from UNIX command line is A-OK. I have been working on setting up Samba to play nice with cups. I have followed the instructions from both the Cups and Samba websites to set up downloading of the generic Adobe postscript drivers to MS Windows PCs and use CUPS as a RIP. So far I have been unable to get the Windows 98 drivers to download to the client PC - when adding the printer the client ends up asking the user what type of printer is being added. Driver downloads for W2K work OK. The relevant lines from a Samba log file seem to be: ----------------- [2002/10/28 14:17:46, 9] printing/nt_printing.c:get_a_printer_2(2702) Unpacked printer [ur10] name [\\techops\ur10] running driver [ur10] [2002/10/28 14:17:46, 10] printing/nt_printing.c:get_a_printer(3302) get_a_printer: [ur10] level 2 returning WERR_OK [2002/10/28 14:17:46, 10] printing/nt_printing.c:get_a_printer_driver_9x_compatible(1825) driver key: [DRIVERS/WIN40/0/ur10] [2002/10/28 14:17:46, 8] printing/nt_printing.c:get_a_printer_driver_3(1758) get_a_printer_driver_3: [DRIVERS/WIN40/0/ur10] info3->name [ur10] info3->datafile [\print$\WIN40\0\ur10.PPD] info3->helpfile [\print$\WIN40\0\ADOBEPS4.HLP] info3->monitorname [PSMON.DLL] info3->defaultdatatype [RAW] info3->environment [Windows 4.0] info3->driverpath [\print$\WIN40\0\ADOBEPS4.DRV] info3->configfile [] [2002/10/28 14:17:46, 10] smbd/lanman.c:get_printerdrivernumber(799) 9x compatable driver line for [ur10]: [ADOBEPS4.DRV:ur10.PPD:ADOBEPS4.HLP:PSMON.DLL:RAW:] [2002/10/28 14:17:46, 3] smbd/lanman.c:get_printerdrivernumber(836) Can't determine number of printer driver files [2002/10/28 14:17:46, 3] smbd/lanman.c:api_DosPrintQGetInfo(918) api_DosPrintQGetInfo: Driver files count: 0 [2002/10/28 14:17:46, 10] printing/nt_printing.c:get_a_printer(3277) get_a_printer: [ur10] level 2 [2002/10/28 14:17:46, 6] rpc_parse/parse_prs.c:prs_debug(60) 000000 sec_io_desc_buf nt_printing_getsec ------------------- Cupsaddsmb ran without errors and the WIN40 subdirectory is populated with files. Can anyone offer any advice? Thanks, Bob Martel ****************************************************************************** Speaking only for myself - CSU pays better people than me to speak for them. Bob Martel - System Administrator | I met someone who looks Maxine Goodman Levin College of Urban Affairs | a lot like you Cleveland State University | She does the things you do (216) 687-2214 | But she is an IBM bob@urban.csuohio.edu | -Jeff Lynne ******************************************************************************
Le lun 28/10/2002 ? 20:40, Robert M. Martel a ?crit :> > I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running > Solaris 9. Cups has replaced the stock system V lp spooler on this system > (original packages removed.) > > Cups working from UNIX command line is A-OK. > > I have been working on setting up Samba to play nice with cups. I have > followed the instructions from both the Cups and Samba websites to set up > downloading of the generic Adobe postscript drivers to MS Windows PCs and use > CUPS as a RIP. > > So far I have been unable to get the Windows 98 drivers to download to the > client PC - when adding the printer the client ends up asking the user what type > of printer is being added. Driver downloads for W2K work OK. >bug in cupsaddsmb (fixed in 1.1.16?) , some files are not copied right. Problem : automatic downloading of adobe drivers added with cupsaddsmb fails with message "unable to open file adopeps4.drv" at the end of install on win98 client Cause: cupsaddsmb sends a rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0" "printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" which forgets adobeps4.drv; Solution: the proper command should read : rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0" "printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
No -----Message d'origine----- De : David Morel [mailto:david.morel@amakuru.net] Envoy? : mardi 29 octobre 2002 10:30 ? : samba@lists.samba.org Objet : Re: [Samba] Samba, Cups, printer driver download problems Le lun 28/10/2002 ? 20:40, Robert M. Martel a ?crit :> > I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running > Solaris 9. Cups has replaced the stock system V lp spooler on this system> (original packages removed.) > > Cups working from UNIX command line is A-OK. > > I have been working on setting up Samba to play nice with cups. I have > followed the instructions from both the Cups and Samba websites to set up > downloading of the generic Adobe postscript drivers to MS Windows PCs anduse> CUPS as a RIP. > > So far I have been unable to get the Windows 98 drivers to download to the> client PC - when adding the printer the client ends up asking the userwhat type> of printer is being added. Driver downloads for W2K work OK. >bug in cupsaddsmb (fixed in 1.1.16?) , some files are not copied right. Problem : automatic downloading of adobe drivers added with cupsaddsmb fails with message "unable to open file adopeps4.drv" at the end of install on win98 client Cause: cupsaddsmb sends a rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0" "printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW: ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" which forgets adobeps4.drv; Solution: the proper command should read : rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0" "printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW: ADOBEPS4.DRV:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Sorry I did a mistake it wasn't for this mail. -----Message d'origine----- De : Kalkoul Morad [mailto:M-Kalkoul@arte-tv.com] Envoy? : mardi 29 octobre 2002 11:05 ? : 'David Morel'; samba@lists.samba.org Objet : RE: [Samba] Samba, Cups, printer driver download problems No -----Message d'origine----- De : David Morel [mailto:david.morel@amakuru.net] Envoy? : mardi 29 octobre 2002 10:30 ? : samba@lists.samba.org Objet : Re: [Samba] Samba, Cups, printer driver download problems Le lun 28/10/2002 ? 20:40, Robert M. Martel a ?crit :> > I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running > Solaris 9. Cups has replaced the stock system V lp spooler on this system> (original packages removed.) > > Cups working from UNIX command line is A-OK. > > I have been working on setting up Samba to play nice with cups. I have > followed the instructions from both the Cups and Samba websites to set up > downloading of the generic Adobe postscript drivers to MS Windows PCs anduse> CUPS as a RIP. > > So far I have been unable to get the Windows 98 drivers to download to the> client PC - when adding the printer the client ends up asking the userwhat type> of printer is being added. Driver downloads for W2K work OK. >bug in cupsaddsmb (fixed in 1.1.16?) , some files are not copied right. Problem : automatic downloading of adobe drivers added with cupsaddsmb fails with message "unable to open file adopeps4.drv" at the end of install on win98 client Cause: cupsaddsmb sends a rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0" "printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW: ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" which forgets adobeps4.drv; Solution: the proper command should read : rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0" "printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW: ADOBEPS4.DRV:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba