Greetings, Ah yes... when you connect in via terminal services / remote desktop, when you "leave" you logout the desktop session to which you connected - causing the behavior you are seeing below. The Boot Manager could be used to re-log in when you leave - or you can use the old adage if it hurts when I do this, don't do this :)
Regards, Thom Thom C. Blackwell Product Manager Boston Software Systems (866) 653-5105 ex 807 www.bossoft.com Sign up for my weekly webinar! LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Palmer Sent: Wednesday, April 30, 2008 5:16 PM To: [email protected] Subject: [Talk] Scripts Stop Responding I am running scripts on a virtual server. I connect to the virtual server via MS Terminal Services client. As long as I have the client window open the scripts run fine. When I disconnect the client window from the server the scripts stop responding. When I come back into the session the Note on the script window reads "Pause for MIS Directories" or something similar. I believe the script tried to start but Meditech didn't respond. I remember seeing this problem before a couple of years ago but don't remember the fix. Any help will be greatly appreciated. -- Bill Palmer Financial Coordinator, Information Systems Mid-Columbia Medical Center The Dalles, OR 97058 541-296-7417
