Okay, I'll try that. Can you please describe the details
of the log setting I need to make to the registry so that:
1. In Service-Mode, it logs all connections to WinVNC.log
2. In User-Mode, it logs all connections to stdout
thanks,
Scott
On Tue, 24 May 2005, James Weatherall wrote:
Scott,
The DebugMode and DebugLevel settings only apply to the VNC 3 series, as
indicated in my posting that you referred to earlier.
For VNC 4 series servers, you need to add the Log setting to the registry,
under HKLM/Software/RealVNC/WinVNC4. VNC 4 will *not* display a log console
when running in Service-Mode - you will need to direct log output to a
different destination, such as the EventLog or a file. Console log output
is normally only available when running in User-Mode.
Regards,
Wez @ RealVNC Ltd.
-----Original Message-----
From: Scott C. Best [mailto:[EMAIL PROTECTED]
Sent: 24 May 2005 17:57
To: James Weatherall
Cc: vnc-list@realvnc.com
Subject: RE: WinVNC 4.1.1 logging
Wez:
I'm sorry to have become the most difficult user of the
day...but I'm not seeing what you describe. When I add DWORD
registry settings DebugMode=4 and DebugLevel=10 to HKLM...WinVNC3,
then all of the older versions correctly open a stdout window
when the service is started. When I add those two DWORDS to
HKLM...WinVNC4, no stdout window is created.
Can any other 4.1.1 user confirm this?
And Wez...can you provide the exact command-line sequence
that you use to generate log files? Not that you *do* generate
log files that way (I understand that you make registry settings
to do it), but if you *were* to use the command-line, can you
provide the exact details of what works for you?
thanks,
Scott
<snip>
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
