WinVnc: problems modifying 1.0.1 source files.

[Jean-Louis MARRO]

Hello,

As the post is rather long, i will summarize the questions after thanking a lot the VNC development " team " for the great job they are doing, permitting people like me to use, and have the possibility to modify this wonderful tool...

------------------------------------------------------------------------------------
Questions:
1. On what Windowsplatform and with which compiler and linker have you generated the binaries related to the 1.0.1 version of VncViewer and WinVnc ?
2. Did someone meet the " freezing " behaviour of WinVnc on Windows XP Professional platform ?
3. What kind of differences there is between executable generated onto a Windows Xp Professional Version 2002 Service Pack 2 ( Intel Pentium 4, CPU 2.8GHz, 1GB RAM ) under the platform Miscrosoft Development Environment .NET 2003 ( version 7.1.3088 ) and the executables got from the download directory.
------------------------------------------------------------------------------------

First, i have to say that the binaries got from the download directory ARE WORKING VERY WELL for the purposes they are intending to match.

I plan to add some options permitting to display the different screens of an Windows XP Display ( several monitors ) onto the different screens of another Windows XP Display ( several monitors. )

Therefore, i modified slighlty the interfaces of WinVnc and VnvViewer to meet the application requirements using the version 1.0.1 of the sources got from the address :
http://prdownloads.sourceforge.net/ultr ... p?download
using the code already written into the winvnc/winvnc directory.

The different options necessary for my application to work are implemented and are working pretty well between the platforms Linux ( using a " basic " VNC software not modified ) and the platform Windows XP Professional. When using the VncViewer on Windows XP, the display can be set on any screen ( say first, second, or third. ) When using the WinVnc on the Windows XP platform, the " basic " VNC viewer on the Linux platform is displaying the screen i wanted to display on the Linux dedicated screen.

------------------------------------------------------------------------------------
The PROBLEM is occuring when attempting to address TWO Windows XP Professional platforms with the VncViewer AND the WinVnc server COMPILED FROM THE SOURCES.

The symptom: the viewer is freezing very quickly ( some seconds ) even if there is not a lot of mouse events to cope with.
------------------------------------------------------------------------------------

I first thought that the problem was occuring due to the modifications i did on the source code, but even if the source version WITHOUT MODIFICATIONS i had the same problems.
Moreover, when executing COMPILED FROM THE SOURCES, i had a core dumped into the file 'vncencodehext' ( RUN TIME checking error. )

I succeeded to prevent this core to occur using a hack ( !! ) into the macro definition... ( modification joint below. )

When executing the programs under a .NET debugging session, the problem occuring is always related with a decoding format leading to a
buffer clearance ( message below )

Receiving cursor shape update, cursor 32x32
Buffer cleared, sync should be back OK..Continue
Receiving cursor shape update, cursor 32x32

The format " seems sometimes erratic ".

------------------------------------------------------------------------------------
Below are the modifications i intended to do to cope with the freezing
behaviour...
------------------------------------------------------------------------------------

File: 20060330.

Due to some problems using the " compiled " winvnc.exe ( Active(Debug) )
( project .NET conversion )

1. Use the 'vncviwer' OMNITHREAD project...

Maybe the source differences found between the " same " project related with the server WinVnc and the client VncViewer were leading to an erroneous behavior...

THIS DIDN'T LEAD to cope with my problem.

2. Make the link to be INCREMENTAL

THIS DIDN'T LEAD to cope with my problem.

3. Delete the Additional Compilation Option '/D'

NECESSARY for the projects to compile ( due to translation from .dsw to .sln project. )

4. Change Additional Dependencies

ws2_32.lib
winmm.lib
version.lib

with :

comctl32.lib
winmm.lib
wsock32.lib
version.lib

THIS DIDN'T LEAD to cope with my problem.

5. Ingnore Specific Library: LIBCD.lib

NECESSARY for WinVnc to be linked.

6. Modify file winvnc\winvnc\vncencodehext.cpp to prevent a run time error

Run-Time Check Failure #3 - The variable 'fg' is being used without being defined.

into :

> winvnc.exe!vncEncodeHexT::EncodeHextiles32(unsigned char * source=0x00000000, unsigned char * dest=0x00000000, int rx=0, int ry=0, int rw=0, int rh=0) Line 405 + 0x317 C++


D:\UltraVnc\src\ultravnc\winvnc\winvnc>fc vncencodehext-SAVE.cpp vncencodehext.cpp
Comparaison des fichiers vncencodehext-SAVE.cpp et VNCENCODEHEXT.CPP
***** vncencodehext-SAVE.cpp
\
int x, y, w, h;
\
int rectoffset, destoffset; \
CARD##bpp bg, fg, newBg, newFg; \
BOOL mono, solid;

BOOL validBg = FALSE;
***** VNCENCODEHEXT.CPP
\
int x = 0; int y = 0; int w = 0; int h = 0; /* _IMMI_INTERFACE_ */ \
int rectoffset = 0; int destoffset = 0; /* _IMMI_INTERFACE_ */ \
CARD##bpp bg = 0; CARD##bpp fg = 0; CARD##bpp newBg = 0; CARD##bpp newFg = 0; /* _IMMI_INTERFACE_ */ \
BOOL mono = FALSE; BOOL solid = FALSE; /* _IMMI_INTERFACE_ */ \
BOOL validBg = FALSE;
*****

***** vncencodehext-SAVE.cpp
\
validFg = FALSE;
***** VNCENCODEHEXT.CPP
\
if (newFg != fg) /* _IMMI_INTERFACE_ */ \
{ /* _IMMI_INTERFACE_ */ \
fg = newFg; /* _IMMI_INTERFACE_ */ \
PUT_PIXEL##bpp(fg); /* _IMMI_INTERFACE_ */ \
} /* _IMMI_INTERFACE_ */ \
validFg = FALSE;
*****

D:\EGUERMIN\UltraVnc\src\ultravnc\winvnc\winvnc>


Note: i can't build the Active(Release) version due to the MISSING library winvnc\Release\messages.lib

[Marscha]

not an excuse, but maybe an explanation:
the code on which 1.0.1 is based is really old (started with realvnc 3.3.something).
There were a lot of additions and modifications done which increase complexity.
What's missing is some cleanup of the code but my feeling is that this is too late now.

There is an effort to start a new development line based on realvnc 4.1.1 and VC++ 8.0.
But this implies that a lot of the features of 1.0.1 are not available for some time.

[Jean-Louis MARRO]

Thank you Marscha for your reply and the information it contains.

I understant you remark, but the binary version is working pretty well ! I think that modifying the sources used to obtain the binaries, or " using the correct platform or compiler options " will lead me to achieve my objectives.

Are you aware of such issues ? ( Or, can you put me in touch with such a person ? )

Jean Louis.

P.S. : If you think that i am at deadlock while modifying the sources of UltraVnc, do you know a freeware or shareware, even simpler, that i can modify to reach my goals ?

[Rudi De Vos]

You could download a svn client and use it to download the source from
http://sc.uvnc.com/svn/ultravncV1/

This code was changed to compile on VS2005, i guess this is closer to
.net then VC6

[redge]

Jean-Louis MARRO ,

Would you add your code source to SVN
or if no,
make available only exe files for Windows and Linux and maybe MacOSX

It would be greatly appreciated from many users and developers want better multi monitors compatibility and usage.

[Jean-Louis MARRO]

Thank you Rudi for your reply. Unfortunately, the version got from the address you gave had the same behaviour as the " basic " version got from the download of the version 1.0.1 ( i checked that some sources where changed. )
One of the same problem i had to cope with is the modification of the file 'vncencodehext.cpp' in which I HAD TO INITIALIZE SOME VARIABLES as stated into the first posted message.

I wonder why the EXE download files are working pretty well !
Maybe the solution is the plaform i'm using to generate the executables ( see the first post ) ?

Does anyone has some clues ?
Thank you in advance for any idea,

Jean Louis.

[Jean-Louis MARRO]

To the " UltraVnc community ".

We are planning to add the " evolutions " to SVN, but these are dedicated to the Windows platform only ( adressing one screen of the extended display. )

Jean Louis.