On Tuesday, 22 November 2016 06:30:19 CET Edgar Olougouna wrote: > Andreas,
Hi Edgar, thanks for the answer. > A core driver needs to ship as part of a driver package that has a > dependency upon it. Based on details in the following references (please > read through below), the list of available core drivers on the print server > would have been provisioned as a result of driver packages being installed > on the server. > > SetupGetInfDriverStoreLocation function > https://msdn.microsoft.com/en-us/library/windows/hardware/ff552194(v=vs.85). > aspx The driver store is a trusted location of inbox and third-party driver > packages. This means that before a driver can be installed it must first be > injected into the driver store, this process is called staging. The driver > store is located under C:\Windows\System32\DriverStore\FileRepository. > Windows keeps a copy of every driver you install in a place called the > Driver Store. It is located in > "C:\Windows\System32\DriverStore\FileRepository". > > Unidrv.dll and Pscript5.dll can be found in ntprint.inf that is > pre-installed on the OS. Microsoft and also other vendors expect that these files are pre-installed on the OS. As Samba is not running on Microsoft Windows, a system with Samba doesn't have these files pre-installed. > Core File GUID > UNIDRV {D20EA372-DD35-4950-9ED8-A6335AFE79F0} > PSCRIPT {D20EA372-DD35-4950-9ED8-A6335AFE79F1} > PCLXL {D20EA372-DD35-4950-9ED8-A6335AFE79F2} > PLOTTER {D20EA372-DD35-4950-9ED8-A6335AFE79F4} > XPSDRV {D20EA372-DD35-4950-9ED8-A6335AFE79F5} These files including the ntprint.inf file are not available on the Microsoft website. So the only way would be to provide a tool to download them from a Windows Print Server. Or how can a 3rd-party who implements [MS-PAR] else provide those files? Best regards, Andreas -- Andreas Schneider GPG-ID: CC014E3D Samba Team a...@samba.org www.samba.org _______________________________________________ cifs-protocol mailing list cifs-protocol@lists.samba.org https://lists.samba.org/mailman/listinfo/cifs-protocol