File Installation:

	Copy winvnc.exe, vncviewer.exe and vnchooks.dll into destination folder.
	If you're running Windows 9x, you need to copy omnithread_rd.dll into
	your Windows\System folder. If you're using NT/2000/XP then copy that
	into winnt\system32.

Install as service:

	C:\Program Files\ORL\VNC> winvnc -install 

	Windows NT : The WinVNC service is installed and set up to run whenever
	the machine is booted into Windows NT but IS NOT YET RUNNING! It will
	run when the machine next reboots. If you want to start it immediately:

	net start winvnc

	The service should now be running, but won't know that you are logged in
	until you log out and back in again. It won't yet appear on the taskbar.

	Now type winvnc -servicehelper and this starts the helper program. This
	is used to display an icon in the taskbar, as well as work out who logged
	on the local box. This is important if you want to use individual user
	settings.

	Now run "winvnc -defaultsettings" (without the quotes) and this will
	display a dialog box for the default user settings.

Remove:

	When you wish to install a new version of WinVNC or simply wish to remove
	WinVNC from   your machine, you must first remove the service from the
	system, using the WinVNC Administrative Tools or the -remove command-line
	option. A message about failure to remove the service usually indicates
	that it was not installed in the first place!

Ports:
	A VNC server listens on two ports. The exact port numbers depend on the VNC
	display number, because a single machine may run multiple servers. The most
	important one is 59xx, where xx is the display number. The VNC protocol
	itself runs over this port. So for most PC servers, the port will be 5900,
	because they use display 0 by default.

	To run on a different port, you need to tell the viewer the right display
	number. Normally, display numbers come between 0 and 99. If you specify any
	number smaller than 99, the viewers add 5900 to get the port number. If you
	specify a larger number, the viewers take it as a port number directly. So
	how do you use port numbers lower than 99? You have to specify a negative
	display number! For example, to connect to a server running on port 80 on
	machine 'snoopy':

		vncviewer snoopy:-5820 (because -5820 + 5900 = 80)

	5500 (Viewer in listening mode)
	5900 (VNCServer)
	5800 (VNCServer Java: http://192.168.1.100:5800)

	-run
		Causes WinVNC to run normally & ignore rest of command-line.
	-install
		Installs the WinVNC service and continues reading the command-line.
	-remove
		Removes the WinVNC service and continues reading the command-line.
	-settings
		Tells a running copy of WinVNC to show the User Properties box.
	-defaultsettings
		Tells a running copy of WinVNC to show the Default Properties box.
	-connect host
		Tells a running copy of WinVNC to initiate an outgoing connection
		to a listening viewer running on the specified machine. This is the
		equivalent of the 'Add New Client' menu option. You can put multiple
		-connect options on one command line to connect to multiple viewers
		at once.
	-kill
		Kills a running copy of WinVNC.
	-about
		Tells a running copy of WinVNC to show its About box.

	If no options are given then WinVNC runs normally. Multiple options may
	be given, so, for example, to upgrade a currently running WinVNC service
	to a new version, you could use: 

	WinVNC_new -remove -install
	which will stop & remove the old copy & install the new one as a service

	WinVNC_new -kill -run
	which will stop the running copy & run the new version as an application

	use_GetUpdateRect
		When a window recieves a message, (WM_PAINT), indicating that
		it should repaint itself, it is possible to find out precisely
		which regions have changed, so that WinVNC need only scan those
		for potential updates,increasing efficiency. However, this can
		cause graphical glitches occasionally, particularly when an
		application scrolls the contents of its window, in which case
		only the revealed section of the window is marked as needing to
		be updated. If these glitches prove to be a problem then edit the
		\use_GetUpdateRect entry in the registry. A value of one
		indicates that this optimisation will be used, while a value of
		zero indicates that it will not.
	use_Timer
		A number of Windows applications, most notably the Clock program,
		use WM_TIMER events to trigger updates to their displays, rather
		than WM_PAINT messages. By default, timer messages are not used
		to notify WinVNC of potential updates, since many programs use
		timer events for purposes other than updating the screen. As a
		result, the clock and a few other applications don't normally
		update correctly under WinVNC. The fix to this is to edit the
		\use_Timer entry in the registry. A value of one indicates
		that WM_TIMER messages will trigger WinVNC updates, while a value
		of zero indicates that they will not.
	use_KeyPress
		Some Windows applications write characters directly to the screen
		when a user types into a window, rather than using WM_PAINT messages
		to cause the text to be redrawn. To fix this, WinVNC can scan the
		window every time a key is pressed, in order to catch the change.
		To set this value for a problem application, edit the
		\use_KeyPress entry in the registry. A value of one indicates
		that key presses will cause updates, while a value of zero indicates
		that they will not.
	use_LButtonUp
	use_MButtonUp
	use_RButtonUp
		Some Windows applications update the display directly in response
		to mouse clicks, without using intermediate WM_PAINT messages, for
		example. In order to catch such updates, it is necessary to trigger
		WinVNC to update the relevant window whenever the left mouse button
		is released. To set this value for a problem application, edit the
		\use_LButtonUp entry in the registry. A value of one
		indicates that left-button clicks will cause updates, while a value
		of zero indicates that they will not. The same rules apply to the
		middle and right buttons using the appropriate value name.
	use_Deferral
		The VNCHooks library catches messages sent to windows before they
		are dealt with by the window. As a result, sending an update message
		to WinVNC to indicate the potential change can result in WinVNC sending
		the updated area to the client before it has actually been redrawn by
		the application! This is a common problem, especially on multiprocessor
		versions of NT, so deferred updates are used by default. Deferred
		updates are handled by posting a custom message back into the window's
		own message queue rather than posting to WinVNC directly. By the time
		this custom message is seen again by the VNCHooks library, the message
		that caused it will have been handled and the update can then be
		forwarded to WinVNC without danger of being handled prematurely. A few
		programs don't handle these extra messages in their queue very well,
		so this optimisation is optional. It can be set by editing the
		\use_Deferral entry in the registry. A value of one indicates
		that deferred updates will be used, while a value of zero indicates that
		they will not.