The environment depends on what the print processor is written for. You can have version for several different environments available on a printserver, which are used when clients connect and need to install the drivers. Where a print processor is put, probably depends on what initialization function it exports (and what processor target it was compiled for) > -----Original Message----- > From: winprndev-bounce@xxxxxxxxxxxxx [mailto:winprndev- > bounce@xxxxxxxxxxxxx] On Behalf Of Alex Egorov > Sent: Thursday, October 16, 2008 9:45 AM > To: Christoph Lindemann > Subject: [WinPrnDev] Re: How to get dll name for print processor > > Hello Christoph, > > > Without having tried it - but maybe GetPrinterDataEx can do the trick. > > > hPrinter: handle to a print server > > pKeyName: "Environments\Windows NT x86\Print Processors\<printproc > name>>" > > pValueName: "Driver" > > > Of course you might specify other environment then "Windows NT x86", > > like "Windows x64" or "Windows 4.0" > > May be you know how I can determine my environment? > > -- > Alex Egorov > > > > --- > Questions? First check the UndocPrint pages at > http://www.undocprint.org/winspool > > To unsubscribe, visit the List Server page at > //www.freelists.org/list/winprndev --- Questions? First check the UndocPrint pages at http://www.undocprint.org/winspool To unsubscribe, visit the List Server page at //www.freelists.org/list/winprndev