VNC viewer crashing - Hardware specific!

[jaybios]

This issue appears to be windows 7 + Hardware specific, i work in a school, currently deployed windows 7 in the library only for testing purposes and fault finding for a summer role out...

2 PCs are MSI Motherboards, same graphics chipset and network chipset as the others and they work fine
7 other PCs are foxconn motherboards

The Foxconn motherboard PCs use Pentium D 2.8ghz CPUs, the MSI boards have E2180s in them, the install on all the PCs is 100% identical (image)

I'll have to edit this post with the model of the boards later.

The crash occurs when the connection is first made, sometimes i have to attempt to connect 3 or 4 times before it'll work, sometimes mouse movement before the connection is ready causes it, sometimes im just not sure.

Anyone have any ideas as to the cause of this issue?

EDIT: I read a few threads the other day in search of the problem, if only i'd done the same today, seems only 2 threads below this one someones having the same problem on windows XP, sorry to have multiplied the threads on the issue (assuming it was the same one)

[supercoe]

Which graphics chipset?

Are you using the most current video drivers?

Doubtful that it is hardware related, most likely software.

[jaybios]

Which graphics chipset?

Are you using the most current video drivers?

Doubtful that it is hardware related, most likely software.

Intel 82945G and it'll be using the built in windows 7 driver on both, it just seems strange that the 2 PCs that are fine have different motherboards, i guess there is some difference in the chipset between the two, i'll have to investigate there differences further tomorrow when i have some time (been a bit to hecktick today)

[B]

Uh, VNC aside, isn't something wrong from the start if you're using an image created on one system platform on different hardware? Are you changing drivers after deploying the image, or just assuming PnP is doing it for you?

[sfhub]

I'm the author one of those other threads. I added your experience to the list I had of other people having similar symptoms.

I doubt your problem is hardware specific.

My guess is this is a generic problem in 1.0.8.2 uvnc viewer and the reason it doesn't happen for everybody is because there is some race condition that needs to be satisfied. That's just a an educated guess based on experience with symptoms from different types of software bugs.

[sfhub]

I'm curious, try changing the connection options from

Track remote cursor locally

to

Let remote server deal with mouse cursor

and see if that makes any difference.

If you want to try it multiple times, make sure you save the settings or it will revert to previous saved settings.