Thu Feb 20 05:58:00 2003
but if the BAT has the command "start <whatever>, the BAT will happily
At 02/19/2003 at 15:43, Shakespearean monkeys danced on Paul V.'s keyboard
>When you execute the 'winvnc -run' the batch file sits and waits for the
>program to stop before it will continue on. Since vnc runs indefinitly, then
>the batch file waits indefintily for it to return, its not froze, its just
>the way batch files work.
>Wscript will allow for you to run a program keep the script running. Easiest
>way is to write it in vbscript.
>Hope that helps
>----- Original Message -----
>From: "Alex Speaks" <email@example.com>
>Sent: Wednesday, February 19, 2003 2:07 PM
>Subject: Batch Files
> > Heres an interesting problem. I'm writing a script to change the VNC
> > passwords on our windows 2000 workstations every week for security.
> > Unfortunatly for some reason the scripts were freezing before
> > termination every time they ran. I did some rooting around in the code
> > and discovered that the command >winvnc -run works just fine if you
> > type it at a command prompt however if you automate it in any way the
> > process is loaded and winVNC functions just fine, but the batch file
> > halts. any ideas? so far I have tried batch files and .cmd files
> > containing :
> > >call winvnc -run
> > >winvnc -run
> > >cmd /c "winvnc -run"
> > >cmd /c winvnc -run
> > >command /c winvnc -run
> > I've also tried it on several machines. this seems to be the problem on
> > all of them.