1.2.0.8 pre-release

[Rudi De Vos]

1208 WIN8>= (win 8...win 10)
We embedded some functions that only exist
Many fixed to make it better behave on the newer OS's.
*initial 10 sec delay
*some locks caused by server crash
*w8hook is embedded, no more seperate dll needed.
*missing cursor

ALL
http://www.uvnc.eu/download/1208/winvnc_1208.zip
Seperate
http://www.uvnc.eu/download/1208/winvnc.exe
http://www.uvnc.eu/download/1208/vncviewer.exe
http://www.uvnc.eu/download/1208/winvnc_x64.exe
http://www.uvnc.eu/download/1208/vncviewer_x64.exe

[Skyfighter]

Thank you very much for the update!

First observation after installation:
Connecting from a windows 8.1 x64 laptop (using v1.2.0.8 pre-release viewer) to Win7 x64 PC with Dual-Monitor (running v1.2.0.6 and server setting "show primary display"+"show secondary display" both enabled) brings up the remote screen with a wrong aspect ratio. The Screen-width of both remote displays gets shrinked down to the width of one remote-display (the height looks ok); the viewer does not show any scroll-bar in the horizontal direction. If I switch the monitor (Toolbar-Button): viewing the primary or secondary remote-display alone is OK, but both together get shrinked again. The viewer Option "Auto-Scaling" doesn't make any difference...

[Rudi De Vos]

viewer ->option-> scale serverto window is default ON ( previous directx mode)
When server is scaled to window, you don't have the scrollbars.
Before this option was OFF

auto-scaling try to set the window as big as possible keeping the screen in aspect ratio

To change, select option and [v] save connection as default

[Skyfighter]

Perfect. Disabling "scale server to window" did it.
(I haven't even seen that option until you mentioned it - sorry!)

[szymon.nowak]

On Win 8.1 and Win 10 work for me ok , Can I ask for a version w2k and vncviever with options file (portable)

[Rudi De Vos]

From win8, there is a new method of capturing screen data, this method doesn't work on w2k.

In a w2k version thoose functions need to be disabled else the exe want run.
A w2k exe will run on all OS's but will be a lot slower on win8>= because it lack the enw functions.

For the pre-release tests we focus on win8 >=

[szymon.nowak]

ok, I understand if I can run versions win8 32bit on xp 32bit and win732/64 win8/64 ?

[Rudi De Vos]

test run on win7 win 8 win10 32/64 ( compiler VS 2013)
New capture function exist only on win8 win10

XP require another compiler, some kernel functions does not exist in xp ( VS2010 or VS2013 in XP mode)
w2k require even an older compiler (VS 2008)

[Skyfighter]

findings until now (using updated prerelease 2015-09-02):
- tiny dot-cursor-problem seems to be resolved (with older versions using Ultra2-encoding I always got a dot-cursor which made this encoding unusable on high-resolution displays because the dot was hard to track/see)
- could not provoke the "connection still open after client is closed" up to now -> looks promising!
- viewer crashed a few times but I'm not sure why (perhaps clipboard transfer...I believe the crashes occured on copying text into clipboard while the viewer was in background)

[Rudi De Vos]

Thanks for the feedback

All time was spend on the server, this need to be stable before stress testing the viewer.

As test we connected 5 simultanious viewers every 10 seconds and killed them after a few seconds.
Test run stable for more then an hour... but you are correct, this doesn't stress test the viewer.

[happy]

Hi,

I am testing at home 1.2.0.8 on w7 x64 and w8.1 x64 with repeater and without.

on all servers I use SecureVNCPlugin64.DSM 2.3.0.0 with password.

when connect from w7 to w8.1 I get a warning: "Accept insecure connection when normally..."
If I run Viewer on w8.1 and click Config DSMPlugin I get warning "The Plugin cannot be loaded. Please check its integrity."

If I switch back to 1.2.0.6 on w8.1 no problems connection it is secure, plug in can be loaded.

I can do a lot of testings if required.

[Rudi De Vos]

"The Plugin cannot be loaded. Please check its integrity."
You are using a 32bit plugin with a 64 exe or a 64bit plugin with a 32bit exe

Normal the setup.exe copy the correct plugin, but with the zip you need to check it yourself.

[happy]

Yes you are right, somehow I switched destination Dir name x32 - x64 when I copied files from zip to storage dir and did not payed attention to files name after that when I copy to w8.1 x64.
All it is ok now on w7 & w8.1 x64

thank you.

[Arno-BS]

findings until now (using updated prerelease 2015-09-02):
- could not provoke the "connection still open after client is closed" up to now -> looks promising!

I had this issue again, sorry!

Client: 1.2.0.8 on Win7 x64
Server: 1.2.0.8 on Win8.1 x64

Arno

[Prisma]

I know the viewer hasn't been tested that much. But I'm able to confirm frequent crashes. I had to switch back to 1.2.0.6 viewer.
I'm also not sure if "scale server to window" with default ON is a good decision. The quality/sharpness of scaled windows is pretty poor.
And possibly the crashed are related to the usage of directX ?! I'm using Windows 10...

[Rudi De Vos]

Instead of switching to 1.2.0.6 you could also set it back off and save as default.
set
[_] scale server to window
save as default

frequent crashes ?
when: on startup /while running / on exit
Is there some logic in the crashes..

[Prisma]

OK, you're right. I've to be more detailed:

Server: 1.2.0.6 different OS, most of them Win7
Viewer: 1.2.0.8 Windows 10

Crashes happen while running. Normal clicking, as far as I can remember, no crtl-C/crtl-V operations. No visible logic.


(If I use a .vnc file, whats the name of the parameter to switch "scale server to window" off? ServerScale=0? directx=0?)

[Rudi De Vos]

m_Directx = readInt("directx", m_Directx, fname) != 0;

[Skyfighter]

I am still using prerelease 2015-09-02 (viewer and server x64) and the viewer is not stable: especially connecting with the prerelease viewer (viewer @ win8.1 x64) to older machines (e.g. win7 x64 uvnc v1.2.0.6 server) leads to a crashing viewer on regular basis (seems to happen every 5-7 minutes - no matter if the viewer is minimized / idle in foreground / in use). Using the prerelease viewer connecting to the prerelease server works much better.

[Vinche]

Hello,

Same problem for me as @Skyfighter. Viewer (under Win10) randomly crashes when connecting to older version (v1.2.0.6).

[Skyfighter]

findings until now (using updated prerelease 2015-09-02):
- could not provoke the "connection still open after client is closed" up to now -> looks promising!

I had this issue again, sorry!

Jep, you are right: had the issue two times with prerelease 2015-09-02 (client & server @ win8.1 x64)

[Rudi De Vos]

especially connecting with the prerelease viewer (viewer @ win8.1 x64) to older machines (e.g. win7 x64 uvnc v1.2.0.6 server)
Perhpas that i good test...

I'm trying to make automated test scripts

like
server test bat

Code: Select all

:loop
start vncviewer -connect 172.16.20.62
timeout /t 1
start vncviewer -connect 172.16.20.62
timeout /t 1
start vncviewer -connect 172.16.20.62
timeout /t 12
taskkill /f /im vncviewer.exe
timeout /t 6
goto loop

This start /kill 3 viewers in a endless loop to the same server to test server stability.

If some have an idea about some other auto test, please let me know.

[happy]

I just had a crash on Viewer on w7 x64 connected with server on w7 x32 via Repeater:

Code: Select all

Faulting application name: vncviewer.exe, version: 1.2.0.8, time stamp: 0x55e48cfb
Faulting module name: vncviewer.exe, version: 1.2.0.8, time stamp: 0x55e48cfb
Exception code: 0xc0000409
Fault offset: 0x00000000000aaaaa
Faulting process id: 0x1c4
Faulting application start time: 0x01d0f9d37203fcc7

and I found in log 5 more crashes on w7 x64, I think for server:

Code: Select all

Faulting application name: winvnc.exe, version: 1.2.0.8, time stamp: 0x55e730f4
Faulting module name: winvnc.exe, version: 1.2.0.8, time stamp: 0x55e730f4
Exception code: 0xc0000005
Fault offset: 0x0000000000083b49
Faulting process id: 0xcfc
Faulting application start time: 0x01d0f792f3c3818f

[Rudi De Vos]

Thanks for the feedback,

standard debug info is general.

Exception code: 0xc0000409 -> buffer overflow somewere in the software
Exception code: 0xc0000005 -> unassign memory used

[Rudi De Vos]

Added special crashdump version.
I'm spending hours on trying to crash uvnc while i should spend hours on debugging it...

On crash the exe generate a minidump that can be imported in the debug info from uvnc src.
This pinpoint in most cases to the crash location instead of just generating a general error.

32bit http://www.uvnc.eu/download/1208/uvnc_1208_crashrpt.zip
64bit http://www.uvnc.eu/download/1208/uvnc_1 ... ashrpt.zip

Software used from crashreport ( http://crashrpt.sourceforge.net/ )

[happy]

I try to run new debug version on w7 x64 and get error can't load plugin.... is that version for x32 only ?

[Rudi De Vos]

Sorry, i only made 32 bit crashreport version.
Errors are the same for 32/64 bit, the only difference is that a 64bit version is a little faster.

I see if i get a 64b version also online tomorrow

[Rudi De Vos]

64bit
http://www.uvnc.eu/download/1208/uvnc_1 ... ashrpt.zip

[Rudi De Vos]

Any crashdump to analyse ?

[happy]

I just installed x64 crash ver on w7 x64:

Strange I was unable to start the crash log ver server service on w8.1 x64... so I had to restore back the no crash ver.

I just had few crash on viewer x64 on w7 but I can't find any log in install dir ?
I started viewer as Admin and after crash I still can't see any log, where are the logs stored ?

Code: Select all

Faulting application name: vncviewer.exe, version: 1.2.0.8, time stamp: 0x560adc2c
Faulting module name: vncviewer.exe, version: 1.2.0.8, time stamp: 0x560adc2c
Exception code: 0xc0000409
Fault offset: 0x00000000000aaaba
Faulting process id: 0x123c
Faulting application start time: 0x01d0fc5b3df8f635

Code: Select all

Faulting application name: vncviewer.exe, version: 1.2.0.8, time stamp: 0x560adc2c
Faulting module name: vncviewer.exe, version: 1.2.0.8, time stamp: 0x560adc2c
Exception code: 0xc0000409
Fault offset: 0x00000000000aaaba
Faulting process id: 0x3ec
Faulting application start time: 0x01d0fc5a8254b35d

Code: Select all

Faulting application name: vncviewer.exe, version: 1.2.0.8, time stamp: 0x560adc2c
Faulting module name: vncviewer.exe, version: 1.2.0.8, time stamp: 0x560adc2c
Exception code: 0xc0000409
Fault offset: 0x00000000000aaaba
Faulting process id: 0xc6c
Faulting application start time: 0x01d0fc579069f561

p.s.
this dir it is empty... ( no idea if count but my GP it is config for no logs sent to MS .. )

Code: Select all

c:\Users\Admin\AppData\Local\CrashRpt\UnsentCrashReports\UVNC_1.2.0.8\Logs\