cupsaddsmb is mean to install a PostScript driver (the Adobe/Microsoft one, with or without a CUPS-specific extension). It explicitely supports Windows 2000 or higher (optionally with the CUPS extension), or Windows 95/98/ME (no CUPS extension available).
This gives: W32X86 --> the directory for "Windows 2000 or higher" client printer drivers WIN40 --> the directory for "Windows 95/98/ME" client printer drivers W32ALPHA --> useless; there are no Win32 computers running on Alpha chips left. W32MIPS --> useless; there are no Win32 computers running on MIPS chips left. W32PPC --> useless; there are no Win32 computers running on PPC chips left. IA64 --> not supported by cupsaddsmb currently x64 --> not supported by cupsaddsmb currently COLOR --> not supported by cupsaddsmb currently So, what can you do if you want Windows client printer drivers for IA64, x64 or COLOR? These drivers come from the printer vendors. You can't use cupsaddsmb to add them. Use the MS "Add Printer Wizard" instead. Run it from a Windows client workstation, point it to the Samba print server, and make sure you log in as a "Printer Admin" to add the drivers. Samba will accept the uploaded drivers just fine, your IA64/x64 clients should happily be able to download and install them (not tested by me, since I still need to come across one such Windows machine), these clients should easily use them to create print jobs, and these print jobs should flawlessly spool through Samba/CUPS (at least if you make sure that CUPS accepts "raw" jobs as "raw" from the clients). -- cupsaddsmb in cupsys-client should support specifying which architecture the drivers are. https://launchpad.net/bugs/66793 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
