I think you can make use of nested installation, I mean include the dependent .msi also in your original package and trigger it silently while launching your .pdf creator tool. You cna as well write a custom action to check for the existence of dependent app on the machine, so that the dependent .msi only gets triggered in its absence.
Just a thought, may oy may not help, u can give a try:)