Hello,
Rebuilt on window xp pro machine after a crash drive.
When trying to run instant VNC version 2.0 or 1.43 it will not come up.
You can see it start then stop in processes. I did find a side by side error
in the event. What am I missing?
Paul
I am having the same issue.
On Tuesday, July 12, 2011 12:45 PM, Steve Sobol wrote:
Date: Tue, 12 Jul 2011 09:45:57 -0700
From: Steve Sobol
To: EchoVNC Users
Subject: [Echovnc-users] Viewer not creating an Echoserver tunnel??
Just downloaded and installed the latest EchoVNC package.
The Viewer
OS. not sure how far back
the net.exe command goes either, but it definitely works in Windows
2000.
"%windir%\system32\net.exe" stop winvnc
"%windir%\system32\taskkill.exe" /IM winvnc.exe
-Paul
On 3/11/06, Nick Sweet <[EMAIL PROTECTED]> wrote:
>
>
>
> I a
Scott,
I just had a thought...
Even if you do "wrap" echovnc in another program to allow it to run as
a service it will still attempt to look in HKCU for the settings which
I assume won't be available before logon.
*shrug* it's worth a try I guess.
Thanks,
Paul
On 6/17/05
Hello,
I'm sure Scott will reply shortly, but I just wanted to mention that
until echovnc supports running as a service there are programs out
there that will let any program run as a service. I haven't tried one
myself (would like to!), but here is one I found quickly searching on
google.
http:
Not sure if I am the only one that sees this...I've mentioned it
before and didn't get much of a response.
I am running TightVNC 1.3dev6 and echovnc 1.2. I notice a very
distinct black screen flicker when echovnc is running. I have a
strong feeling this has something to do with it connecting to
can't do a "net
stop" to stop echovnc. Anyone have a good way to stop it once its
running?
-Paul
On Apr 4, 2005 2:38 PM, David Schlesinger <[EMAIL PROTECTED]> wrote:
> This sounds really good, would definitely like it to start as a service.
>
> posting on another iss
u can change the IP of the
hostname and it will still try the old. you can also delete the IP
value from the registry and when you start echovnc it will try to
connect to a blank IP instead of resolving the hostname it has stored.
Long enough for now...
Paul
On Apr 4, 2005 12:26 PM, David Schles
ame hostname, different IP) and was able to
resolve/ping the server at the new address (after ipconfig /flushdns).
When I open echovnc, however, it will error out saying it couldn't
connect to the old IP address.
hope that helps!
Paul
On Apr 1, 2005 5:27 PM, Scott C. Best <[EMAIL PROTEC
again,
Paul
---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/h
any command line
options and I tried a quick VB program and also a "start /min echovnc"
and neither seem to have any effect on the program. Any ideas here
other than changing the code?
Thanks!
Paul
---
This SF.net email is sponsore
11 matches
Mail list logo