Re: [cifs-protocol] [REG:116102514847712]: [MS-PAR] Q 2/2 3.1.4.2.9 RpcAsyncGetCorePrinterDrivers (Opnum 64); Where does someone find a copy of CorePrinterDrivers

2016-12-07 Thread Edgar Olougouna via cifs-protocol
Andreas, The list of core printer drivers defined in MS-PAR and MS-RPRN shall be provisioned from drivers installed on the print server. IHVs include the necessary core drivers into their packages. Thus, print server implementers do not need to embed a separate copy of core drivers.

Re: [cifs-protocol] [REG:116102514847712]: [MS-PAR] Q 2/2 3.1.4.2.9 RpcAsyncGetCorePrinterDrivers (Opnum 64); Where does someone find a copy of CorePrinterDrivers

2016-11-22 Thread Andreas Schneider via cifs-protocol
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

Re: [cifs-protocol] [REG:116102514847712]: [MS-PAR] Q 2/2 3.1.4.2.9 RpcAsyncGetCorePrinterDrivers (Opnum 64); Where does someone find a copy of CorePrinterDrivers

2016-11-21 Thread Edgar Olougouna via cifs-protocol
Andreas, 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

[cifs-protocol] [REG:116102514847712]: [MS-PAR] Q 2/2 3.1.4.2.9 RpcAsyncGetCorePrinterDrivers (Opnum 64); Where does someone find a copy of CorePrinterDrivers

2016-10-25 Thread Bryan Burgin via cifs-protocol
[+dochelp on bcc] [+casemail] [Changed title to reflect single issue...was "[MS-PAR] Some questions Printer Driver handling"] Use this thread for the second of your two issues: 116102514847712: [MS-PAR] Q 2/2 3.1.4.2.9 RpcAsyncGetCorePrinterDrivers (Opnum 64); Where does someone find a copy of