SC update 2018

Single Click discussions / bugs

SC update 2018

Postby Rudi De Vos » 2018-04-27 21:22

SC update ( test 1)

https://www.uvnc.eu/download/1220/SC_2018_test1.zip

howto test:
modify helpdesk.txt
start winvnc.exe

update win8>=

Current no online creator for it. Just run winvnc.exe in a folder with the helpdesk.txt, this act te same as executing the generated sc.
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 6105
Joined: 2004-04-23 10:21

Re: SC update 2018

Postby SpyMashine » 2018-09-19 13:08

I saw Online creator is up, but it runs without admin rights, could you make another version with admin rights when running exe like previous version?
SpyMashine
 
Posts: 2
Joined: 2018-07-03 08:30

Re: SC update 2018

Postby adam314315 » 2019-10-17 03:51

Hello,

The SC_2018_test1.zip link is not anymore active. Could you please advise where to download last version of source code for Single Click?

Thanks
Adam.
adam314315
8
8
 
Posts: 8
Joined: 2019-10-16 11:16

Re: SC update 2018

Postby Rudi De Vos » 2019-10-20 14:04

That zip seems to be gone after server cleanup.

But found in local svn "-Added support for the SecureVNCPlugin" from 2019
extracted as
https://www.uvnc.eu/download/1230/Z_SC_2019.zip
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 6105
Joined: 2004-04-23 10:21

Re: SC update 2018

Postby adam314315 » 2019-10-21 21:39

Great thanks for the link.
While loading this SC 2019 version in Visual Studio it seems there is an issue due to missing file sc\winvnc\vnchooks\vnchooks.vcxproj for the project vnchooks. Maybe you could have a look when you have some time?
adam314315
8
8
 
Posts: 8
Joined: 2019-10-16 11:16

Re: SC update 2018

Postby Rudi De Vos » 2019-10-23 18:25

The vnchooks didn't changed for years and is a seperate dll.
Re-uploaded with vnchooks
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 6105
Joined: 2004-04-23 10:21

Re: SC update 2018

Postby David4 » 2020-01-05 01:22

Thanks for working on the code and sharing.
In the last days I tried to compile the 2019 source, but always get errors. I tried several things, cleaned up the directories and so on, but without success.
For many years now I always got it to work, in the last years with the 2015 source. There are always lots of warnings but the exe worked fine.

Now these 3 LNK2019-errors are remaining:
Code: Select all
videodriver.obj : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol ""protected: int __thiscall ScreenCapture::osVersion(void)" (?osVersion@ScreenCapture@@IAEHXZ)" in Funktion ""public: __thiscall VideoDriver::VideoDriver(void)" (??0VideoDriver@@QAE@XZ)".
videodriver.obj : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol ""public: __thiscall ScreenCapture::ScreenCapture(void)" (??0ScreenCapture@@QAE@XZ)" in Funktion ""public: __thiscall VideoDriver::VideoDriver(void)" (??0VideoDriver@@QAE@XZ)".
vncdesktop.obj : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol ""public: __thiscall DeskDupEngine::DeskDupEngine(void)" (??0DeskDupEngine@@QAE@XZ)" in Funktion ""protected: int __thiscall vncDesktop::InitVideoDriver(void)" (?InitVideoDriver@vncDesktop@@IAEHXZ)".
.\..\Debug/winvnc.exe : fatal error LNK1120: 3 nicht aufgelöste externe Verweise.
Could you help please? (Sorry I didn't find out how to post without line-wrap)

And on this occasion: in the source there are a lot of changes to 2015, some new files, but one piece of code is irritating me. In videodriver.cpp:
Code: Select all
hFile0 = CreateFile("c:\\video0.dat", GENERIC_READ | GENERIC_WRITE, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL);
hFile1 = CreateFile("c:\\video1.dat", GENERIC_READ | GENERIC_WRITE, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL);
...

What is this for? In root-directory users usually have no write access. Here file creation would fail.
David4
8
8
 
Posts: 22
Joined: 2010-08-11 15:13

Re: SC update 2018

Postby Rudi De Vos » 2020-01-05 16:19

A mirror driver use memory mapped files to share the framebuffer.
The driver can create multiple framebuffers video0, video1, but mostly only video0 exist
The mirror driver create it, and vnc (SC) use it as shared memory to import the framebuffer.
CreateFile with " OPEN_EXISTING"
used XP-WIN7


Looks like deskdupengine.cpp and screencapture.cpp are not included in the winvnc project.
You use the headers in videodriver and vncdesktop but don't compile the corresponding cpp
->"nicht aufgelöstes externes Symbol"

Using VS2010 they are in the build... strange
Solution
Add the 2 files to the winvnc sub-project
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 6105
Joined: 2004-04-23 10:21

Re: SC update 2018

Postby David4 » 2020-01-06 21:26

Rudi De Vos wrote:Add the 2 files to the winvnc sub-project

I thought I did this... Sorry, now SC compiles without errors. Thank you. Didn't test any further. When I have more time I continue.
David4
8
8
 
Posts: 22
Joined: 2010-08-11 15:13

Re: SC update 2018

Postby adam314315 » 2020-03-01 18:54

Hello,

1. While trying to compile Z_SC_2019 with VS2019 and implementing previous solution I got 2 remain errors;
> C2039 'logon' is not a member of 'vncDesktop' in file vnclogon.cpp
> C1083 Cannot open include file: 'libjpeg/jpeglib.h': No such file or directory (caused by include in vncEncodeTight.cpp)
@Rudy could you please help?

2. I succeeded to compile Z_SC_2010 with VS2019 but I noticed that the 2 files generating the errors vnclogon.cpp and vncEncodeTight.cpp didn't get imported in the VS2019 project when I open the project with Visual Studio. But as said the build succeeded and created the winvvnc.exe file in Debug folder.

3. What are the main differences between Z_SC_2010 and Z_SC_2019 ?

4. What is the difference between opening winvnc.dsw or winvnc.sln ? Any recommandation ?

Adam.
Thanks for helping
adam314315
8
8
 
Posts: 8
Joined: 2019-10-16 11:16


Return to SC

Who is online

Users browsing this forum: No registered users and 9 guests