Tim Mangan at Tmurgent.com wrote a utility called Launchit to clean up
after such a mess. See http://www.tmurgent.com/LaunchIt.htm to download.
Also Peter Ghostine at Emergent Online (http://www.Go-eol.com or
http://www.99point9.com) wrote a utility called WTSLaunch that might
help see http://thethin.net/wtslaunch.zip
And the best thing: BOTH Solutions are FREE Regards, Jim Kenzig http://thin.net
Rob Slayden wrote:
********************************************************I've got a weird one involving Adobe Acrobat Reader. We are deploying Reader on all our MF servers (W2K3/MFXPe) to enable CommnuniGate Pro email users to open PDF attachments. Cgate Pro is a web-based email package we are accessing from within IE as our primary application is web-based. Strangely enough, however, when they open a PDF and then close it by exiting the Cgate Pro email program or by accessing the mailbox link again, the Acrobat Reader executable (acrord32.exe) remains in memory on the MF server for that user session until the user logs out. Note that Acrobat Reader open in the context of the Cgate Window, that is, a windows within a window.
Anyone seen anything like that before with Acrobat Reader on MF? Any ideas on how to close the executable without waiting for a user idle timeout or logout?
Thanks!
rob