I'm not sure what's the best way of registering print processor. The alternative is to register winprint in winspool when driver is added.
From: Piotr Caban piotr@codeweavers.com
--- loader/wine.inf.in | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/loader/wine.inf.in b/loader/wine.inf.in index 127d1f9ad6a..4f273d14941 100644 --- a/loader/wine.inf.in +++ b/loader/wine.inf.in @@ -602,6 +602,11 @@ HKLM,"Software\Microsoft\OLE","EnableRemoteConnect",,"N" [Printing] HKLM,%Control%\Print\Monitors\Local Port,"Driver",2,"localspl.dll" HKLM,%Control%\Print\Printers,"DefaultSpoolDirectory",2,"%11%\spool\printers" +HKLM,%Control%\Print\Environments\Windows 4.0\Print Processors\winprint,"Driver",,"winprint.dll" +HKLM,%Control%\Print\Environments\Windows ARM\Print Processors\winprint,"Driver",,"winprint.dll" +HKLM,%Control%\Print\Environments\Windows ARM64\Print Processors\winprint,"Driver",,"winprint.dll" +HKLM,%Control%\Print\Environments\Windows NT x86\Print Processors\winprint,"Driver",,"winprint.dll" +HKLM,%Control%\Print\Environments\Windows x64\Print Processors\winprint,"Driver",,"winprint.dll" HKLM,%CurrentVersionNT%\Ports,"FILE:",,"" HKLM,%CurrentVersionNT%\Ports,"LPT1:",,"" HKLM,%CurrentVersionNT%\Ports,"LPT2:",,""
Could we add a `DllRegisterServer` to `winprint.dll`?