Redistributing PDF-XChange Driver in InstallShield MSI

[ikuning]

Hi,

We're redistributing PDF-XChange Driver using the command line option C:\PDFX4sa_sm.exe /VERYSILENT /NORESTART /COMPONENTS="pdfSaver,PDF-XChange driver,
Help,Languagess" /DIR="C.... as custom action in a Install Shield Basic MSI-Object. With installation everything works fine, but I would also like to uninstall the driver, if our application is uninstalled.

Is there a option for uninstallation as well? I think it would be easier to redistribute if you offer a msi-package for silent installation which can be included in your cutomers setups. Is a msi available and I just didn't find it or does Tracker plan to deliver a msi-package with next releases?

Ingo

[Tracker Supp-Stefan]

Hello Ingo,

There are .msi packages for the PDF XChange PRO bundle
https://www.pdf-xchange.com/downloa ... ro_x86.msi
https://www.pdf-xchange.com/downloa ... ro_x64.msi

and our Viewer
https://www.pdf-xchange.com/downloa ... er_x86.msi
https://www.pdf-xchange.com/downloa ... er_x64.msi

x86 and x64 versions respectively.

Please have a look at our downloads page, they are all there:
https://www.pdf-xchange.com/downloads/users/

Regards,
Stefan

[John - Tracker Supp]

Hi Ingo,

whilst Stefan is correct in regards we do offer MSI installers for our end user versions - these are not the equivalent of the developer's 'reduced' installer and would add significantly in terms of the size of the download you offer to your users.

At this time - you would be better placed to use these installer's if MSI is a must :

PDF-XChange Standard installers :

https://www.pdf-xchange.com/PDFXC_x86.msi
https://www.pdf-xchange.com/PDFXC_x64.msi

and utilize only the required components - see the end user help file for a listing of these - we will look into provideing a specific developers MSI install, but note - there will have to be a build for 32 bit and another for 64 bit as they cannot be mixed and they will always be larger than the exe based installer, additionally - there are 2 as opposed to just one - but I suspect you know this.

With regards the uninstaller - you can indeed call this ...

From the existing '.exe' installer provided - this can be called using the command line using and you must locate and call the file called something like : uninst.exe - I cannot recall for now the exact name - but you should be able to locate this easily enough in the install folder you have specified.

with regards MSI uninstalls - again the same can be done and this is structured along the lines of a call as follows :

msiexec.exe </uninstall | /x> <Product.msi | ProductCode>

hope that helps

[Ivan - Tracker Software]

MSM files for PDF-XChange Driver will be available in days.

[ikuning]

MSM-files would be perfect for my issue, thanks...

[John - Tracker Supp]

Pleasure ..

[ikuning]

Please let me know when MSM will be available. Is there already a MSM-Package I can use?

[Tracker Supp-Stefan]

Hello ikuning,

The files are available already, but we are preparing the documentation for them at the moment.
Should be no more than a few days now.

If you are the explorer type we could provide you stable and working, but with no help files accompanying them MSM files.
If you wish you can write to us at support@pdf-xchange.com and we will send you the files for testing.

Regards,
Stefan

[ikuning]

Hi,

are the msm files ready? I took a look at the latest versions in the download section of your homepage, they were placed at 18th of november, but I think the msm's are not included.

Ingo

[Tracker Supp-Stefan]

Hi Ingo,

Please do contact us using the e-mail in my previous post and we will arrange to send you the .msm files.
I have here with me .msm files for the ViewerAX both 32 and 64 bit versions and can request the rest from the development team.

Regards,
Stefan

[ixm7]

Are these Merge Modules available publicly now?

[John - Tracker Supp]

Do you mean the combined the xcpro40.dll and pxclib40.dll libraries ?

These are not available and not yet complete - these will be released as Version 5 and only available then ....

If I misunderstand - please explain in more detail, thanks.

[ixm7]

I mean the "PDF-XChange Drivers SDK end user distribution installer". I'm assuming that a Merge Module would facilitate integrating that installer into my application installer (no need for custom actions). More importantly, it should automatically handle uninstalling your portion when uninstalling mine (thinking about scenarios where a new version of your SDK is included in a new version of my application...).

[John - Tracker Supp]

apologies - you are correct - you would need this file :

www.tracker-software.com/PDFX4SA_SM_MSM.zip

[ixm7]

Thanks! Can you confirm if this Merge Module would also take care of uninstalling?

[John - Tracker Supp]

Yes - I believe I am correct in saying th entry for uninstall is created as you would expect ...

Let us know if you need any assistance or have any suggestions regarding use.

Thanks

[ikuning]

Hi,

is a documentation about merge-modules properties available?

In my InstallShield-project I can set these properties for merge modules of PDX-Xchange PDF Driver:
Add Printer: Default: _P (Add Printer to control panel or not) - What are a vaild values and meanings?
Log Type: Default: /Z (Type of installation log) - What are a vaild values and meanings?
Printer Name: Default: PDF-XChange 4.0 -Is it possible to set a name which does not start with "PDF-XChange"
Set As Default: /Z - What are a vaild values and meanings?

Deploying with PDFX4.exe has more options:
- AutoUnload
- Key
- UserName
- Organization
- UserEmail
- Lang

How to set these options deploying with merge modules?

Best regards,

Ingo

[Ivan - Tracker Software]

the following are properties for the MSM:

1) InstallPrinter (displayed as "Add Printer"): can have "_P" or "/Z" values ("Yes" or "No" correspondingly)

2) LogType ("Log Type"): "/Z" - None; "/D" - Output debug messages using OutputDebugString API, "/L" - output debug messages to file

3) PrinterName ("Printer Name"): its value is the name of the printer which should be used. The default value is "PDF-XChange 4.0"

4) SetAsDefault ("Set As Default"): "/Z" - No, "/F" - set the newly installed printer as default

The MSM has no properties like "KEY", "Email", etc. because it was designed to be used as a part of developers' installers, not end-user's ones.

P.S. I don't know where the problem is maybe in the WiX we're using to build the MSM, or it is InstallShield, but often it does not show the 'display name' for possible values, but their corresponding values, i.e., "_P" instead of "Yes" for "Add Printer".