This is a very small application.

CutePDF Writer installs itself as a "printer subsystem". This enables virtually any Windows applications (must be able to print) to create professional quality PDF documents.

Anyway when i sequence this the printer is installed on the sequenced machine successfully. there is nothing but an html file that is created in the start menu and the virtual printer in the printers section in control panel.

My problem is deploying this to an XP/Win7 machine it delivers the html file in the startmenu but it believes that is the application. So triggers when accessing the html document and closes down when closing the .html readme!! :( It does not show the virtual printer at all.

Any ideas?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


As far as I know app-v'ing anything that contains a printer driver (or any driver for that matter) does not work. Furthermore, considering the fact that this app needs to be available at all times, I'd suggest making this application as an MSI package instead, since you have no valid trigger for it, unless you'd make extra shortcuts for all the applications you'd want to use CutePDF with, like "MS Word with CutePDFPrinter", "Excel with CutePDFPrinter", ...

All in all, not a good candidate for App-V'ing I'm afraid.


Answered 02/17/2011 by: pjgeutjens
Red Belt

Please log in to comment