Batch Files

[Carl]

If you stop it, you'll lose the connection.

Carl

----- Original Message -----
From: "William Hooper" <whooper@freeshell.org>
To: <vnc-list@realvnc.com>
Sent: Wednesday, February 19, 2003 2:41 PM
Subject: RE: Batch Files


> > -----Original Message-----
> > From: vnc-list-admin@realvnc.com
> > [mailto:vnc-list-admin@realvnc.com] On Behalf Of Alex Speaks
> > Sent: Wednesday, February 19, 2003 2:07 PM
> > To: vnc-list@realvnc.com
> > 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.
> >
> > -AA
>
> I believe this is because the batch file is waiting for an exit code from
> VNC.  Of course VNC doesn't exit until you close it so your batch file
will
> be waiting a while.  It's been a while since I've done batch programming,
so
> I don't know if there is a way to prevent this.
>
> Are you running VNC as a service?  If so use the net commands (because I
> believe the "-run" will make VNC run in app mode anyway.  For example:
>
> net stop winvnc
> <registry edit stuff goes here>
> net start winvnc
>
> --
> William Hooper
> _______________________________________________
> VNC-List mailing list
> VNC-List@realvnc.com
> http://www.realvnc.com/mailman/listinfo/vnc-list