Hi,
sure, when we have tested it I will post my short report here.
Thanks!
Maciej

Thanks for the answer. Basically we create an instance of the PDF printer only on demand, for the life time of our process only and remove it when the application is shut down. I believe it shouldn't be an issue then, if the old version remains there - it will not be used and that's all. When we'll ...

Hello! For the last few years we were distributing the V4 of the drivers with our product to customers, to support "printing to PDF" function. Now we've decided to upgrade to the latest version (6.x). We're installing the drivers with the following command line parameters: /VERYSILENT /COM...

Hi, we have a log from a failing upgrade. What we're doing is simply invoking the installation over existing PDF Xchange, without uninstalling it first. We're using the 4.0.214.1, installing it over some older version (like 4.0.196 I think) The following is the content of the log you advised us to r...

Hello,
we're installing the PDF XChange printer driver along with our software (to utilize "print to PDF" function). Currently we're using the version 4.0.210. Should we expect any issues with using the printer under Windows 8.1?
Regards,
Maciej Tokarski

It sounds plausible (unfortunately for us). Is this a must, the restart? Is there no workaround? All other components of our installation do not require it... Antoher question - in case of an upgrade installation we have a scenario in which we don't uninstall anything, but simply call the installer ...

Hello, we're using pdfx4sa_sm.exe to install the printer on a system. We face a failing uninstall/install scenario now, and we need some support. During upgrade installation of our software, we uninstall PDF-Xchange driver/printer, and then try to install it again. The installation fails with code 8...

Hi, we're using "PDF-XChange Drivers API" installer (executable pdfx4sa_sm.exe). We can't exchange it easily for already released products of our own, therefore my question was if you were aware of any installation issues related to internet connection. If you're not sure, we must investig...

Hello, one of our customers experienced problems recently when upgrading our product. Our installer checks the version of the actual PDFXchange driver installed, and simply calls your installer if necessary. In this case some older version of PDFXchange was going to be replaced with the version 4.0....

Thank you!
Maciej

When you have just this printers installed, is any of them default ? Yes, I have written it in my previous posting. There's always some default printer set before we install and use PDF-XChange. I have a kind of impression that Win7 tries to be "intelligent" at times, setting the new prin...

Hello, 1) the /DRVWOPRN is indeed what we needed - the default printer installed along was only creating confusion in our environment. Thanks again for the info! 2) Anyway, the problem with "default printer" persists, now affecting the temporary printer created for the lifetime of our app....

Thank you!

Hi, We set the full output path for pdf report via API: m_pPrinter->Option[L"Save.File"] = fullpath; Our testers observed that whenever the path contains a single "%" the character is simply removed from path/name. I know "%" has to do with macros, but I was sure it wil...

Thank you for the prompt answer, we'll try it out during this week's integration build, I am going to drop here a line.
Regards!
Maciej

Hello! We're using the following parameters to install the PDF-XChange driver during the installation of our product: PDFX4SA_sm.exe /VERYSILENT /COMPONENTS="pdfSaver,PDFXChangedriver" /NORESTART /PNAME="PDF-XChange 4.0-GUID" It worked fine under Windows XP/Vista. Since we've bee...

Hi, it works fine, thank you for the hint! It made our reporting much much faster! I believe this kind of information should be included in your documentation too. Just by looking at your examples and the docs, I was convinced ApplyOptions is a MUST, whenever one sets printer's properties. Regards, ...

Hi Ivan,
thanks a lot! This is something I couldn't read out of the docs and examples. I was pretty sure ApplyOptions must be used always when any option changes, to really be utilized by the printer.
I will give it a try and drop a line here whether it works.

Regards!
Maciej

Any ideas? I noticed a following topic here at the forum: https://forum.pdf-xchange.com/viewtopic.php?f=39&t=6411&p=28255&hilit=docpath#p28276 . Ivan writes: "...%[DocPath] can be empty, because not all applications provide path as a part of printed document". I do not understa...

Hi, our application generates documents on your printer using Win32 API (CreateDC, StartDoc, PlayMetafile etc.). It works fine (apart from some issues on Win7, but it's not the point here). We need PDFs to be saved automatically under specific names in particular destination folders. So far I implem...

Hello! We create our own temporary PDF-Xchange printer only for the life time of our app. We don't need the default printer being created by the installer (pdfx4sa_sm.exe), because it's confusing our customers. Is there a way (a command line parameter?) not to install the default PDF printer at all?...

I did some more experimenting; the conclusion is: RemoveOrphanPrinters acts differently under Citrix that under pure Windows Server TS solution. Under Citrix it removes a printer which belongs to other active session! In Windows TS environment it doesn't do that. Why is it so? Can you give me a hint...

Hello, For a year or two we've been using your PDF-Printer in our product, and we are very pleased with it. We have to maintain pretty an old solution, which includes a kind of a "native" print spooler. The spooler gets EMF files from instances of our main app and uses PlayMetafiles functi...