Just purchased PDF Converter Pro 4.0 (to upgrade from version 1.58). I have it installed and working fine on my (development) PC, and I have made the necessary changes to my PowerBuilder application to make use of the new version of PDF Converter. The application also runs correctly with no problems on my PC. Both the developer PC and deployment PC's are running Windows XP Professional 32-bit.
I have followed the documented instructions for deploying PDF Converter 4.0 with my application onto another PC to work out the deployment details, and I have used the supplied Install.exe utility to create a Windows printer definition on the test deployment PC. On the deployment test PC, the PDF Converter functionality works, but when the application executes the DriverInit method, a dialog window containing a progress bar momentarily appears near the upper-left corner of the screen. It appears the PDF Converter is installing/copying some files to the C:\Windows\System32\spool\drivers\w32x86\amyuni_amyunidocumentconverter400 and/or the C:\Windows\System32\spool\drivers\w32x86\3 folders. This happens every time I run the app on the deployment test PC. If I temporarily rename the amyuni.inf file on the deployement PC and run my application, the files do not get (re-)copied, but I receive an "Arguments are Invalid" message instead.
I surmise from all of this that PDF Converter is running some kind of install that is controlled by the amyuni.inf file. This is a little troubling, as I thought the purpose of the Install utility was to provide a working printer definition and therefore not have to perform any additional installation steps when PDF Converter is used. I have been unable to find any information about this process in the product documentation or on the web site, so I'm posting my questions here.
My application works, but I very much need the PDF Converter utility to do its job quietly. What do I need to change in my application and/or the deployment steps to make it work (a) without performing whatever installation it is performing, or (b) quietly and discretely so my users do not get alarmed?
Thank you!
PDF Converter copies files during DriverInit
Re: PDF Converter copies files during DriverInit
Jose Pimentel responded to an e-mail I had sent to the Support Team, asking me to make sure that my application was indeed invoking the PDFDriverInit method when I thought it was using DriverInit (my app attempts to determine if the PDF printer definition exists, then uses DriverInit if the printer definition exists and PDFDriverInit if it does not exist).
A minor fault in my logic resulted in PDFDriverInit getting called every time. Now that DriverInit gets called instead, the printer driver installation no longer is performed, and therefore the Copy Files dialog window never appears. Even better, the application is speedier since it no longer has to incur the overhead of setting up the Windows printer definition.
Many thanks to Jose for pointing me in the right direction!
A minor fault in my logic resulted in PDFDriverInit getting called every time. Now that DriverInit gets called instead, the printer driver installation no longer is performed, and therefore the Copy Files dialog window never appears. Even better, the application is speedier since it no longer has to incur the overhead of setting up the Windows printer definition.
Many thanks to Jose for pointing me in the right direction!