Installer and Windows Update

The Amyuni PDF Converter is our Printer Driver that enables you to convert any documents to PDF format. If you have any questions about installing and using the Amyuni PDF Converter please post them here.
Post Reply
zaksoft
Posts: 66
Joined: Fri Feb 20 2004

Installer and Windows Update

Post by zaksoft » Thu Aug 09 2012

1) It is possible to have a .MSM package that we can include easily into a setup ?

2) I dont understand why WU prompt for update Amyuni driver (even for different version) loosing the keys, every user that update force us to
A) Uninstall and re-install if using a previous version with different key (legacy exist, also customers that do not upgrade)
B) Send an installation package
C) Connect with Remote Desktop to insert keys

TIA
Davide Zaccanti

Rich
Posts: 76
Joined: Thu Jun 16 2011

Re: Installer and Windows Update

Post by Rich » Thu Aug 09 2012

  • 1) It is possible to have a .MSI package that we can include easily into a setup ?
You can request this through support@amyuni.com and based on if your maintenance is up to date we can issue an .msi installer
  • 2) I dont understand why WU prompt for update Amyuni driver (even for different version) loosing the keys, every user that update force us to
    A) Uninstall and re-install if using a previous version with different key (legacy exist, also customers that do not upgrade)
    B) Send an installation package
    C) Connect with Remote Desktop to insert keys
In order to possibly control your users from updating the Amyuni PDF Converter through Windows updates, there are two possible solutions:

1- You can install the non-certified version of the driver. This is done by removing the amyuni.inf and atpdf400.cat from your installation package. However this generates warnings when installing the printer.

2- The other option is to use our “Custom Branding” option. This option, which has a fee associated to it, will allow you to install your own version of the PDF Converter with your own custom named DLLs.

http://www.amyuni.com/en/developer/branding/index.html

Additionally, you could also have your custom DLLS certified by Microsoft. This option unfortunately is not just a one-time fee but it is per driver version release. Each time a new version even a service release is issue, the DLLs will need to be re-certified.

What the “Custom Branding” offers is the ability to install the printer driver with your own branded DLLs. These custom dll names are created using the special .inf file and special install.exe that we supply.

You will still receive the updated versions of the PDF Converter but it will be up to you whether you want to use them or not.

Example:

1- We release v4.A.A.A and you decide to include this version as part of your application. Using an .inf file and special installer you install the PDF Converter and your own custom DLL names.

(example you use “ep” as file prefix)

epacfpdf.dll
epacfpdfu.dll
epacfpdfuamd64.dll
epacfpdfui.dll
epacfpdfuiamd64.dll
epcdintf.dll

2- Next v4.B.B.B is released. It is your option to use this new version or not. If you don’t use this version, since you are installing the product with your own DLLs and if the driver version gets updated by Windows updates, it will not affect your product.
Efficient and accurate conversion to PDF, XPS, PDF/A and more. Free trials at - http://www.amyuni.com

Theta
Posts: 25
Joined: Wed Jun 25 2003
Location: Australia

Re: Installer and Windows Update

Post by Theta » Thu Sep 06 2012

Hi,

as per item 1) 'It is possible to have a .MSM package that we can include easily into a setup ?'
I too would like a MSM (Not MSI) package to be easily integrated within my installer, is this something that has been considered?

Rich
Posts: 76
Joined: Thu Jun 16 2011

Re: Installer and Windows Update

Post by Rich » Mon Sep 10 2012

As of this writing there are no plans to create a .MSM file (Windows merge modules).
Efficient and accurate conversion to PDF, XPS, PDF/A and more. Free trials at - http://www.amyuni.com

Post Reply