Workstation 10 and VMs remote control problem

[balubeto]

Hi

I have upgraded Workstation 9.x to 10.x on a host that has Windows 7 SP1 64-bit and I have upgraded all of the VMs to the new format and I have installed the new VMware Tools.

Using Workstation 10.x to run the VM, I have no problem.

When I use the vmrun utility to run them in the background and I use UltraVNC Viewer 1.1.9.1 to check them (the VNC server is the VNC server integrated in the WS 10), I have problems with the graphical interface of the Guests as you can see from these images:







How come? How do I solve these problems because, when I used the version 9.x, I had not them?

Thanks

Bye

[Rudi De Vos]

Installed wmware workstation 10 ( trial) and loaded a win7.
Then i activated vnc access ( VMware option)
test 1 (vmware gui)
No color invertion ( tried with 32 and 16 bit colors)

test 2 ( nogui)
vmrun -T ws start "h:\vp_image\vmware\win7\windows 7.vmx" nogui
no color invertion

Sorry, can't repeat it.

[balubeto]

Installed wmware workstation 10 ( trial) and loaded a win7.
Then i activated vnc access ( VMware option)
test 1 (vmware gui)
No color invertion ( tried with 32 and 16 bit colors)

test 2 ( nogui)
vmrun -T ws start "h:\vp_image\vmware\win7\windows 7.vmx" nogui
no color invertion

Sorry, can't repeat it.

You could try using a VM of XP Pro SP3?

Thanks

Bye

[balubeto]

If I disable the Accelerate 3D graphics option in the VM settings, the problem described above disappears. How come?

How do I enable this option without this problem?

Thanks

Bye

[Rudi De Vos]

Possible that's one of the reasons i can't repeat it, even with XP pro.
Accelerated 3D graphs use the real video card of the host OS, this mean that it also depend on the type of video card
in your server. I can run xp pro with accerealted 3D graphics on.

But i found one thing.
The encoder used seems to be rawand tight, even when hextile is selected.
Don't know if it has anything todo with it.

You can fast test it by downloading a realvnc viewer.

[balubeto]

Possible that's one of the reasons i can't repeat it, even with XP pro.
Accelerated 3D graphs use the real video card of the host OS, this mean that it also depend on the type of video card
in your server. I can run xp pro with accerealted 3D graphics on.

But i found one thing.
The encoder used seems to be rawand tight, even when hextile is selected.
Don't know if it has anything todo with it.

You can fast test it by downloading a realvnc viewer.

With RealVNC Viewer 5.0.5 64-bit for Windows, the problem has disappeared even with the accerealted 3D graphics option enabled.

So, how should I do to correct the problem that has UltraVNC Viewer 1.1.9.3 64-bit?

Thanks

Bye

[Rudi De Vos]

Looks like this is identical to
http://forum.ultravnc.net/viewtopic.php?f=64&t=28490

Normal, the server should adapt to the veiwer, but it looks like some servers want to viewer to adapt to the server.
( color format)

Now i know the reason of the color shift it's checking if it is some part of the protocol or it's using some sub protocol
to tell it.

[Rudi De Vos]

Looks like vmware vnc server messed things.

Normal, it should used the preffered encoder you select, but it doesn't.
If you tell you support tight encoding, it use it, independed if you tell that you prefer some other encoding.

The problem with tight encoding is that there exist a bug ( rgb-bgr) color convertion when
the server use 24bit depth.

Realvnc works correct as it doesn't have tight encoding

Trying to fix it, a fast way would to disable tight in case you set a fixed encoder.
That way, using vmware you can prevent it by using a viewer setting.

[balubeto]

Looks like vmware vnc server messed things.

Normal, it should used the preffered encoder you select, but it doesn't.
If you tell you support tight encoding, it use it, independed if you tell that you prefer some other encoding.

The problem with tight encoding is that there exist a bug ( rgb-bgr) color convertion when
the server use 24bit depth.

Realvnc works correct as it doesn't have tight encoding

Trying to fix it, a fast way would to disable tight in case you set a fixed encoder.
That way, using vmware you can prevent it by using a viewer setting.

So, how do I fix this bug?

Thanks

Bye

[Rudi De Vos]

It require a code changes. ( i already made it but we are still testing)
You can not fix this bug unless you want to play with the code.

[Rudi De Vos]

Test viewers online
http://www.uvnc.eu/1193/vncviewer_vmwaretest.zip

[balubeto]

Test viewers online
http://www.uvnc.eu/1193/vncviewer_vmwaretest.zip

I tried to control a VM of Ubuntu 13.04 with this testing version and it does no more have the bug mentioned above. Tomorrow, I'll try to control an XP VM but I think that it has no problems.

Thanks

Bye

[balubeto]

It works.

Thanks

Bye

[balubeto]

When you are planning to create another official release that includes the fix for this bug?

Thanks

Bye

[Rudi De Vos]

Not for this bug fix.
Code changes are in the tree, so the are added for next release.
We try to make an update every 2-3 months.

Some people want many updates while other want to keep it to a minimum.
I guess 2-3 months is a good average.