Also thanks, but...
Thank you for the working solution, but it does not quite seem complete, at least for me. Whenever I use the created Adobe PDF Converter to create a PDF, the following four processes start and do not close themselves when the printing is complete:
a) Acrobat.exe *32 (Username: SYSTEM)
b) acrodist.exe *32 (Username: SYSTEM)
c) acrotray.exe *32 (Username: SYSTEM)
d) acrotray.exe *32 (Username: [my username])
After about 3-5 minutes, processes (b) and (c) do close themselves, while (a) and (d) seem to insist on staying alive.
This has two most undesirable effects:
1) These processes take up memory because they are technically running, even though they aren't doing anything after the PDF is printed.
2) Acrobat.exe maintains a lock on the newly created PDF, so I cannot move or delete it until I forcibly kill the Acrobat.exe process.
So I have the following questions:
1) Is there some way to ensure that all processes close after a PDF has been created?
2) If not, is there some way to automatically remove Acrobat.exe's hold on the new PDF other than opening the Task Manager and forcibly killing it?
3) Or is all this simply a result of Adobe's sloppy programming practices, and is a necessary evil we must live with if we're to use their PDF converter?
