Dan, Most ActiveX applications (most notably Microsoft one) are poorly behaved and cannot cope with unknown messages arriving in their message queues. This is a known issue with Microsoft's ActiveX that the older vnchooks.dll, amongst others, could trigger.
The VNC 4 series hooks are designed not to trigger this bug in Microsoft's ActiveX. Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dan Chernin > Sent: 22 March 2005 02:45 > To: [email protected] > Subject: VB error in 4.3.7 > > In certain situations, when trying to create an object from a > "Thread Per > Object" VB ActiveX Exe, I get error 462: "The remote server > machine does not > exist or is unavailable"; on closer examination, it turns out > that the exe > just suddenly "vanished". I can reproduce this consistently > in VNC 4.3.7, but > it occurs on other machines which are not even running VNC. > Further I can no > longer reproduce it (at least not yet) when running VNC > 4.1.1. Microsoft is > claiming that it must have been a bug in the VNC 4.3.7 > vnchooks.dll that has > been fixed. Was there such a bug? And if it's a bug in VNC, > why does the > problem occur on non-VNC machines: Microsoft's "explanation" > is that it must > be a problem with other apps which inject hook DLL's into > running processes. > Does this sound plausible? > > Thanks... > > Dan > _______________________________________________ > 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
