How about a "sleep" command in the batchfile, say "sleep 30" or something like that to give WinVNC time to launch.
-----Original Message----- From: Andrew Borland [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 30, 2004 1:00 PM To: [EMAIL PROTECTED] Subject: Re: Simple .exe a remote client can run for support? Angelo, I have been attempting to follow your suggested batch file: > rem start batchfile > start winvnc4.exe > winvnc4.exe -connect www.xxx.yyy.zzz::aa > but I am finding that the "winvnc4.exe -connect" is being executed so soon after the "start winvnc4" command, that the server isn't actually up and running in time to service the connect request. Have you ever observed anything similar? Have you any suggestions on how to slow things down a bit? Regards, Andrew Borland (UK) _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
