search for: alpha_axp

...dows NT R4000] and version [0] we have:[0] drivers in environment [Windows NT R4000] and version [1] we have:[0] drivers in environment [Windows NT R4000] and version [2] we have:[0] drivers in environment [Windows NT R4000] and version [3] we have:[0] drivers in environment [Windows NT Alpha_AXP] and version [0] we have:[0] drivers in environment [Windows NT Alpha_AXP] and version [1] we have:[0] drivers in environment [Windows NT Alpha_AXP] and version [2] we have:[0] drivers in environment [Windows NT Alpha_AXP] and version [3] we have:[0] drivers in environment [Windows NT P...

...river AGFA-AccuSet v52.3 for arch [Windows 4.0] - error 0x705! Failed to remove driver AGFA-AccuSet v52.3 for arch [Windows NT x86] - error 0x705! Failed to remove driver AGFA-AccuSet v52.3 for arch [Windows NT R4000] - error 0x705! Failed to remove driver AGFA-AccuSet v52.3 for arch [Windows NT Alpha_AXP] - error 0x705! Failed to remove driver AGFA-AccuSet v52.3 for arch [Windows NT PowerPC] - error 0x705! result was NT_STATUS_UNSUCCESSFUL rpcclient $> The driver file's have themselves been removed from the print$ share but i want to remove them properly. Also, where are the printer dri...

...irectory to place all of your drivers. Then it goes on to say that you need to create the following directory tree under that: [print$]----- |-W32X86 ; "Windows NT x86" |-WIN40 ; "Windows 95/98" |-W32ALPHA ; "Windows NT Alpha_AXP" |-W32MIPS ; "Windows NT R4000" |-W32PPC ; "Windows NT PowerPC" Of course, you would customize this to whatever architectures you were tyring to support. I was recently trying to install the driver for an Epson Stylus C80 printer, and it...

...DRIVER cannot get driver (for architecture: Windows NT x86): WERR_UNKNOWN_PRINTER_DRIVER cannot get driver (for architecture: Windows NT x86): WERR_UNKNOWN_PRINTER_DRIVER cannot get driver (for architecture: Windows NT R4000): WERR_INVALID_ENVIRONMENT cannot get driver (for architecture: Windows NT Alpha_AXP): WERR_INVALID_ENVIRONMENT cannot get driver (for architecture: Windows NT PowerPC): WERR_INVALID_ENVIRONMENT cannot get driver (for architecture: Windows IA64): WERR_UNKNOWN_PRINTER_DRIVER cannot create directory \x64: NT_STATUS_OBJECT_NAME_COLLISION opening file \x64\3\PSCRIPT5.DLL on originating...

I began playing around with 2.2.0a2 yesterday. The text docs have instructions for setting up the "print$" share and installing drivers for client download. This involves browsing to the samba share from a W2K or NT server, accessing the "printers" folder, and right clicking on each printer to install drivers. I've managed to get W2K/NT and Win98/95 drivers

Hello list! On all my samba installations (3.0.20b) I can delete all unused printer drivers with rpcclient regardless which user name or password i use. Is this a general feature or might it depend on my settings? Thanks, Martin -- Martin Zielinski mz@seh.de Software Development SEH Computertechnik GmbH www.seh.de

...tory tree below the [print$] share for each architecture you wish to support. [print$]----- |-W32X86 ; "Windows NT x86" |-WIN40 ; "Windows 95/98" |-W32ALPHA ; "Windows NT Alpha_AXP" |-W32MIPS ; "Windows NT R4000" |-W32PPC ; "Windows NT PowerPC" ----clap--- -- /"\ | Kari \ / ASCII Ribbon Campaign | Hurtta X Against...