When launching WinVNC4 from a command prompt on XP Pro SP2 (obviously in user mode), the console remains blocked even if the -noconsole switch is specified. I would suggest that the -noconsole "should" mean that it detaches from a command shell window even if it is started from one - but this is open to debate since we don't exactly have ISO standards for Windows commandline parameters... ;)
This is not a high priority problem AFAICS since there are workarounds using the start command. Since the start command has a quirk that makes this less than obvious (it interprets the first unnamed argument surrounded by quotes it encounters as a command prompt window title) I'll document it here - feel free to requote/adapt.
(1) If winvnc4. exe is in the usual location - for example, "C:\Program Files\RealVNC\VNC4\winvnc4.exe" - it can be started by specifying the start directory with the /D command, like this:
start /D"C:\Program Files\RealVNC\VNC4" winvnc4.exe
(2) Add the VNC4 folder to your path -or- copy the binaries to a directory already in your path. _______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
