![]() ![]() Removed reference to Twon of An's script. Killing the task by process ID will only kill that one task not all instances of AcroRd32 running in memory. The process ID is unique to this specific instance of the application. How will it react to multiple AcroRd32 listed in the task manager? That is why you need to use the process ID that is returned when the program is called. What do you suspect will happen to that second instance of Acrobat Reader when the command "taskkill /f /im AcroRd32.exe" is called? What will happen to the print out from that second instance that is not fully rendered? When that first instance is done printing it will launch the killtask command. The OP didn't mention how the batch file was called, but there is a likelihood of one instance of acrobat reader is already printing when a second instance is started. It only means you didn't read my post, instantly commenting the script instead.īut my comment was around this: since windows is a multi-tasking operating system there may be multiple instances of acrobat reader running at any one time. The issue I see with this is that it will kill all instances of acro reader running. Tasklist |find "AcroRd32.exe" /i || set kill=yes "c:\Program Files\Adobe\Reader 11.0\Reader\AcroRd32.exe" /t "document.pdf" if "%kill%" equ "yes" taskkill /f /im AcroRd32.exe ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |