Chunk 3.2 w/ Multiple Displays

[ich]

I've been out of the loop for a while and have skipped from Chunk 3.1 and UVNC 1.0.8 to current versions.

With the previous version of Chunk (and UVNC,) I used a customized winvnc.exe that Rudi had put together to resolve multi monitor problems where the cursor is displayed to the client on a different screen from where it actually is on the server. It looks like I'm having the same problems with Chunk 3.2 even though the changes seem to have been rolled into the UVNC 1.0.9.5 that I'm testing as I'm not having any trouble with that.

I've tried replacing the winvnc.exe in the Chunk package with the one from my UVNC install and recompiling, but I'm still getting the same result. It's also, for some reason starting up with "autoscaling" enabled which is a pain when you're taking over a desktop that's 4488x1080.

I'm going to try a few more things but figured I'd post this to see if it's a known issue or I'm overlooking something obvious.

[ich]

Weird.
I just went back to the basic Chunk3.2 package and recompiled without any changes and I'm getting the same thing - both with the "Chunkized" exe and the main UVNC exe.
Of course, all of this is being tested against a "worst case" scenario of a server with 3 displays running at 1280x1024, 1920x1080, and 1280x1024 - two displays running off one video card and the other running off a second PCIe X16 card - and, to top it all off, the client is an ultra-mobile with a 1024x768 screen.

I've done everything I could think of to make sure I'm testing like-to-like and the Standard UVNC service is working just fine but Chunk is giving me all three screens scaled to fit within the client screen, and I'm also getting the "wrong screen" issue where I can look up at the server and see that the cursor is on a different screen than I'm seeing it on the client.

I had a very similar problem with the previous version, which is why I finally gave up the size savings and replaced winvnc.exe with the one Rudi customized for multiple displays because the main 1.0.8 UVNC had identical problems.

As soon as I get home, I'll try to take over this machine from another computer and see if it's the same from another client.

[supercoe]

Change SRC\InstantSupport_Files\ultravnc.ini
Secondary=0 from =1
This will at least not show every screen right away.

[ich]

That at least gives me the primary screen without having to toggle the "Select Full Desktop..." button, but I still have the same issue when I enable viewing of multiple displays.
I've tested on two other multi monitor servers and get the same thing.

My understanding of the previous problem was that it was a problem with how the coordinates where handled and it was part of the winvnc.exe executable, which is why Rudi created a patched exe. I can't imagine any reason that it's doing this with Chunk but not with the main UVNC line.

I've verified that the cursor is on the wrong screen on 3 different multi monitor setups. In a two monitor configuration with both displays exposed to the client, the cursor appears to be at the right coordinates - just on the opposite screen from where the client shows it to be.
Further testing shows that it only happens when the Secondary display is positioned to the LEFT of the Primary display. If the displays are rearranged so that the Secondary is to the RIGHT of the Primary everything behaves properly.

I'll go dig around and see if I can find the post relating to the previous problem.

[ich]

Found the previous thread: [topic=16752]HERE[/topic]

With the previous Chunk version, replacing winvnc.exe in the Chunk compiler with the patched executable resolved the problem. I haven't tried recompiling with that older EXE yet, mostly because I don't want to revert that far back. If I get a few minutes today I'll try that, but I suspect there's something else going on here.

As a side-note: Am I the only one with 15 customers running multi-monitor? No one else is squawking about this. Unfortunately, it seems to be the most common preference for the secondary to be on the left.

[supercoe]

Almost seems like it's a setting the SRC\InstantSupport_Files\ultravnc.ini file.

I don't come across many multi monitor situations and I've only ever done testing with the primary display on the left.

I'll do some testing and let you know what I've found but it might not be until this weekend. Let me know if you find anything.

[ich]

Thanks Supercoe. As always, beer money I've thrown your way is money well spent. Paid support isn't usually this responsive!

If I get a chance to dig around and do further testing I'll post.

[ich]

Updates:
I just went through, same test systems as previously, and did some testing.
Replacing winvnc.exe in ...SRC\InstantSupport_Files, I recompiled Chunk 3.2 with:
A) As is, with "chunked" UVNC Server 1094
B) with standard UVNC Server 1095
C) with standard UVNC Server 1096
D) with customized UVNC Server 108 that Rudi released <- I'm still using this one with Chunk 3.1 currently because of the multi-monitor issue

In all cases, the same behavior is exhibited, except for D) where no matter which monitor(s) I'm viewing the cursor is locked to the left edge of the left-most monitor

Just for grins, I went back to compile Chunk 3.1 with the standard 1096 UVNC Server and found that ChunkVNC.com is only hosting the chunk 3.2 file and I don't still have an uncustomized copy of Chunk 3.1 so I couldn't do this test.

[supercoe]

All of the old files are still on the site you just don't have a link.

http://chunkvnc.com/ChunkVNC_3_1.zip