FW: A little help needed

[Arnt Witteveen]

Oh *%=A3%*$, Outlook and Html mail don't go toghether very well. Below =
is the
same thing, hopefully readable this time.

The Vnc people will propably answer this better, but I'll try my hand =
at
some of this...

> -----Original Message-----
> From: Jeferson Charles Mayer [mailto:jeff.charles "at" zaz.com.br]
>=20
> I am a newcomer to VNC. Some days ago, I downloaded the WinVNC =
3.3.3r2
> source code and tried to compile it under Win95, using VC++ 5.0. =20

A word of warning here: I believe they switched to using VC6 recently.

> Before trying to modify the source code, I would like to understand =
some
> points, so I'm asking for some help:
> =20
> 1. I get errors when compiling the WinVNC server, specifically =
related to
> constants and types used in low level hooking. I suppose that this is
> happening because some functions, types and constants (like
WH_KEYBOARD_LL,
> KBDLLHOOKSTRUCT, etc.) are WinNT specific. Do you have any =
recommendation
> for a Win95 build? Should I just strip off such code?=20
=20
This may be explained by the above ? In any case, I think that the =
server
for 95 and NT are the same, if not there will probably be a #define =
WIN95 or
something (ok, I'm guessing here)...

> 2. In the "Connection options" dialog (WinVNC viewer), encoding =
options:
> When I click on "Raw", the original option doesn't toggle, that is, I =
get
2
> radio buttons checked at the same time. I first noticed that when I
> downloaded and ran the installation pack. So, after I downloaded the
source
> code, I found out that the "Raw" radio button has its "group" =
property
> checked. Isn't that just wrong?=20
=20
Yes, I think it is.=20

> 3. Running VNC on a 10Mb local network, server and viewer both on =
Pentium
> 233MHz, I did a simple test: just moving the mouse pointer around (no
mouse
> buttons pressed). The effect was the following: at the server =
machine, I
> could see a smooth movement of the pointer, but, an the viewer, I =
just
could
> see a mouse pointer jumping terribly, unless I moved it VERY slowly. =
Well,
> it just seemed that something was very wrong, because all I was doing =
was
> moving normally the mouse around the desktop, using 16 bits color =
depth,
> 800x600 at both ends. What could cause so much overhead?=20
=20
Nothing... If the server were X-win, it would work fast, I think. I'm =
in
almost the same situation as you (but a 100Mb network), and I notice =
the
same thing. From what I've read on this list, the problem is not so =
much
getting the update acress the wire, but determining when something has
updated/changed... This seems to go much better under X-Win than under
MS-Win.
=20
Arnt

=20

---------------------------------------------------------------------
The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------