Thanks. I'll give that a shot and see if it resolves the problem. 'Preciate
the quick response.
John
-----Original Message-----
From: James Weatherall [mailto:[EMAIL PROTECTED]
Sent: Monday, December 20, 2004 12:12 PM
To: 'John Aldrich'; 'RealVNC List (E-mail)'
Subject: RE: OleMainThreadWndName error
John,
TightVNC is based on the old VNC 3.3 sytem, with some custom features added,
which may well be the cause of the problem you are seeing.
We have never had such an error reported for VNC 4.
Regards,
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of John Aldrich
> Sent: 20 December 2004 15:46
> To: RealVNC List (E-mail)
> Subject: OleMainThreadWndName error
>
> I'm wondering if switching to RealVNC would solve some problems we're
> having... We're using TightVNC 1.2.x here on some windows NT
> workstations
> and when the system goes to reboot, if VNC is installed as a
> service, we get
> an error "OleMainThreadWndName not responding" and we have to end-task
> several times before the system will reboot. As a test, I
> uninstalled the
> service and shut down and restarted an NT workstation that
> was giving that
> error and did not receive the error when the service was NOT
> installed.
>
> If RealVNC will allow the machines to shut down without hanging, I'll
> probably switch those machines to RealVNC.
> Thanks
> John
> _______________________________________________
> VNC-List mailing list
> [EMAIL PROTECTED]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
