hello damon, it takes a few seconds when i start vnc (winvnc -run), so the next command that connects is to early and gives me the error that there is no vnc available to connect. i "solved" the problem with a "pause", i cannot figure out how "start" can help here:
start winvnc.exe -run rem wait a little.... pause start winvnc.exe -connect 10.1.1.1 if i use "start /wait winvnc -run" the the bath stucks. i do not know which other parameters i should use to make the batch "wait". do you know how to solve this? best regards arno > start the VNC-Server in a batchfile >> Try prefixing your 'winvnc' commands with 'start', i.e.: >> start winvnc _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
